Hi David,

Your advice was spot on. There were a series of errors recorded in the logs, 
which I think I have now resolved:
1) A typo in geonode.wsgi
2) Invalid syntax in my secret_key in local_settings.py (I thought I needed 
this, but each time I generated one using the instructions and pasted it into 
local_settings.py I got an error about invalid syntax so I left it as an empty 
string)
3) OGRFailure, so I needed to install libproj_dev

I am not in a position to access the site at a localhost address (even using 
proxying in firefox) but I can certainly now see the geonode site at the root 
address, even though it's missing all the css etc, which I would expect. I will 
investigate further on Monday (and am very much looking forward to getting to 
grips with GeoNode!)

Many thanks

Jo

----- Original Message -----
From: "Joanne Cook" <[email protected]>
To: [email protected]
Sent: Friday, 10 December, 2010 6:00:00 PM
Subject: Re: [geonode] Ubuntu deployment issues

Hi David,

I think you're correct- sorry, I get a 500 error from http://localhost,
rather than a tomcat error. I did follow the instructions to disable the
default site and enable the geonode one. I will check the mod_wsgi
settings though.

Many thanks

Jo

----- Original Message -----
From: "David Winslow" <[email protected]>
To: [email protected]
Sent: Friday, 10 December, 2010 5:48:05 PM
Subject: Re: [geonode] Ubuntu deployment issues

Do you really get a tomcat error from http://localhost/ ? That sounds
like some proxying problem... if http://localhost/ is not the Django
app, that would cause some issues for GeoServer trying to retrieve user
info. I would recommend reviewing your apache proxy/mod_wsgi
configuration.


http://docs.geonode.org/1.0-RC3/logging.html may be of use to you. You
should also have some basic error reporting from mod_wsgi in
/var/log/apache2/error_log .


-- David Winslow
OpenGeo - http://opengeo.org/


On Fri, Dec 10, 2010 at 12:41 PM, Joanne Cook < [email protected]
> wrote:


Dear All,

I am attempting to deploy Geonode, using the most recent Release
Candidate (RC4), using the instructions here:
http://docs.geonode.org/1.0-RC3/deploy/ubuntu.html

As far as I can tell (which isn't saying much), all the steps have
completed correctly. However when I try and access either the geoserver
instance at http://localhost:8080/geoserver-geonode-dev , or the site
root page at http://localhost I get an apache tomcat error saying:
Error connecting to GeoNode authentication server: GeoNode communication
failed, status report is: 500, Internal Server Error

Looking through the tomcat logs (catalina.out) it seems to work it's way
through the geoserver startup, but then I get an error when I try and
actually access the pages noted above.

The geonetwork install seems to be working OK, in that I can get to the
front page of that at http://localhost:8080/geonetwork . I can browse
the static files, eg
http://localhost/geonode-client/gn/theme/app/img/header-bg.png

Any help would be greatly appreciated.

Many thanks

Jo

--
----------------------------------------------------- Joanne Cook
Senior IT Support and Development
Oxford Archaeology (North)
01524 880212
http://thehumanjourney.net


------ Files attached to this email may be in ISO 26300 format (OASIS
Open Document Format). If you have difficulty opening them, please visit
http://iso26300.info for more information.

--
----------------------------------------------------- Joanne Cook
Senior IT Support and Development
Oxford Archaeology (North)
01524 880212
http://thehumanjourney.net


------ Files attached to this email may be in ISO 26300 format (OASIS
Open Document Format). If you have difficulty opening them, please visit
http://iso26300.info for more information.

-- 
-----------------------------------------------------
Joanne Cook
Senior IT Support and Development
Oxford Archaeology (North)
01524 880212
http://thehumanjourney.net


------
Files attached to this email may be in ISO 26300 format (OASIS Open Document 
Format). If you have difficulty opening them, please visit http://iso26300.info 
for more information.

Reply via email to