Hi David, thank you for your answer and your help with the problem in the #geonode IRC channel. The patch worked fine, now I can upload shapefile, but the problem still remains if I try to upload a GeoTiff file.
Ciao Luca 2010/10/18 David Winslow <[email protected]>: > Hi Luca, > I ran into failing uploads after setting up RC1 as well; the problem for me > was the one described in http://projects.opengeo.org/CAPRA/ticket/838 . A > patch that resolved it for me is under discussion > at http://github.com/GeoNode/geonode/pull/10 . If you would like to try out > that code for yourself and don't know how to use it in your deployment, > please contact us in IRC (the #geonode channel on irc.freenode.net). I also > hope to produce an RC2 this week which includes a fix for this issue. > Anyway, about troubleshooting: > I should write a page in the docs about this, but there are several places > error messages may appear in GeoNode: > > Tomcat's error log (tomcat/logs/catalina.out) > GeoServer's error log (geoserver_data/logs/geoserver.log) > Django's error reporting system. Django may report errors in one of two > ways (built-in): > > You set DEBUG=True in local_settings.py and re-attempt the action that > failed. A detailed log with information for programmers will show up in > your browser for failed requests. > You configure your Django application to send email, and add a list of > admins to local_settings.py. This would simply involve adding a line like: > [ADMINS=("Luca", "[email protected]"),]and then setting up email. > See http://docs.djangoproject.com/en/dev/topics/email/ > or http://rob.cogit8.org/blog/2008/Aug/31/using-gmails-smtp-server-django/ > for some info on that. Error messages will be sent to the users listed in > the ADMINS setting, which has to be a tuple of tuples (the extra comma at > the end is important.) > > Unfortunately, the upload view is a little overzealous in hiding errors and > presenting obscured/simplified messages to the user instead, so none of > these logging systems presented much useful information (I found the cause > of the problem by removing a lot of the error wrapping code manually). A > nice improvement would be to have it log the real error using the usual > Django mechanisms while still presenting a human-readable error instead of a > stack-trace. > -- > David Winslow > OpenGeo - http://opengeo.org/ > On Mon, Oct 18, 2010 at 6:19 AM, Luca Casagrande <[email protected]> > wrote: >> >> Hello everybody, >> I installed GeoNode RC1 following the awesome guide on Github [1] and >> all is fine. >> I am planning to use it for the Italian GFOSS.it Association. >> Just some small notices on it, to be sure that it can be followed also >> by new people: >> - Tell people to become root or use sudo on most command; >> - The Geoserver interface doesn't work as written in point 2 of "Changes >> after Tomcat is Running"; >> - Type exit once created the db; >> - unzip GeoNode-1.0-RC1/geonode-client/ -d /var/www/geonode/htdocs/ >> should be unzip GeoNode-1.0-RC1/geonode-client.zip -d >> /var/www/geonode/htdocs/ >> - in the end point people to http://localhost/ >> >> The only problem I have with my installation is that I can't upload any >> ShapFile (it says to contact the admin and highlight in red the layer >> name). >> How can I debug this troubles? Apache/Geoserver/Geonetowork logs doesn't >> show any troubles. >> >> Thank you for your great work >> Luca >> >> [1]: >> >> http://github.com/dwins/geonode/blob/issue_822_deployment_docs/docs/source/deploy/ubuntu.rst >> >> > > -- Luca Casagrande http://www.lucacasagrande.net twitter: lucacasagrande
