Well that was easy :)
Thanks for the quick help. Switching it to a fully qualified domain
name and using /etc/hosts to catch it made everything work like a
charm after the re-install.
So it sounds like the error message I thought might be coming from the
Server actually was and I wasn't even str
Django's URLField requires a fully-qualified domain (like foo.com), so if
you're using something like http://reviews/, it'll complain. I want to
change this at some point, since internal domains should be fine. Are you
using such a domain in that field?
I imagine the media field is actually fine,
I'm not sure, but I might be having the same site media problem. I'm
familiar with django, but not the way djiblets does the database
settings stuff.
Basically, the MEDIA_URL isn't being set at all. I've tried setting it
through the admin interface, but what I'd think would be the correct
value o
The Permissions have been set:
drwxrwxrwx 3 www-data www-data 4096 Jan 19 20:05 .
drwxrwxrwx 5 www-data www-data 4096 Jan 19 20:05 ..
lrwxrwxrwx 1 www-data www-data 99 Jan 19 20:05 errordocs ->
/usr/local/lib/python2.6/site-packages/ReviewBoard-1.0alpha1-py2.6.egg/reviewboard/htdocs/errordocs
Okay, so you're getting a "Forbidden" error with this directory, but the
HTML file for that is missing so it's sending a 404 instead.
What you're seeing is a config error on your server where Apache's user is
unable to access your media directory. The user just doesn't have the
permissions require
I added the line to vhosts.conf file
"Options FollowSymLinks"
When i tried accessing the http://135.254.219.50/media/ - I got this
error on the browser
Page not found (404)
Request Method: GET
Request URL:http://135.254.219.50/error/HTTP_FORBIDDEN.html.var
Regards,
Roshan Pius
On Tue, J
That file seems to have some issues. Perhaps the browser tried to normalize
the file paths, but they end up looking like:
There's also a bunch of custom HTML in there, and existing HTML that's
modified. Definitely looks like the browser is doing it.
Can you look at the source for that file in y
Hi ,
The post-review worked once i removed the old cookies file.
<<<
> You may want to also try going to http://yoursite/admin/, logging in,
> clicking on "Settings", and then checking what the "Media URL" is set to. It
> should be "/media/". If not, you can set this and then click "Save." It
> s
Can you run post-review with -d and attach the debug log?
Is it just asking for a password over and over? If so, try deleting
~/.post-review-cookies.txt.
I'm imagining the problem is the site root or media root. Can you attach the
HTML file of any page on your install? It'll help me determine if
Hi ,
I've run into major issues with post-review as well now. it is not
able to post the reviews as well.
It keeps retrying and retrying but fails.
Thanks,
Roshan Pius
On Tue, Jan 20, 2009 at 12:27 PM, roshan pius
wrote:
>
>ServerName xxx.xxx.com
>DocumentRoot /srv/www/htdocs
ServerName xxx.xxx.com
DocumentRoot /srv/www/htdocs/review-board-evros/htdocs
# Error handlers
ErrorDocument 500 /errordocs/500.html
# Serve django pages
PythonPath
"['/srv/www/htdocs/review-board-evros/conf'] + sys.path"
Hmm. If sounds like the site install went fine. Can you e-mail me the
resulting Apache config and the HTML from any page on the site
(something generic like the login page would do).
It's probably either the site root setting, or Apache is looking in
the wrong place for media files.
Christian
Hi
1.I'm not using a domain name as of now, running it directly with an
IP:(xxx.xxx.xxx.xxx).Will get a domain later. But i was running before
with direct IP.
2.As is said, i was running the old reviewboard off the svn checkout
so i didn't have a rb-site installation so "rb-site upgrade" is not
p
A few things I need to know first:
1) Is your Review Board install using its own subdomain, or is it in a
directory off a domain?
2) If it's in a directory off a domain, did you specify that directory
during the install?
3) Is this using an existing database?
4) Try running rb-site upgrade on t
14 matches
Mail list logo