Hello David, Yes, i can view the layers directly in Geoserver's layer preview and also download while logged in as admin user.
I run *geonode updatelayers* to push the layer to geonode but i am unable to view the layer(plus all the other layers) at the GUI. When i click the layer link at the GUI, an "*Internal server error"* is returned. Geonode users cannot use the geospatial data search results at this point. The error messsage is generic, setting DEBUG=TRUE in the /etc/geonode/local_settings.py generates a more detailed exception at the GUI See: http://pastebin.ca/2155442 I have considered reducing the number of threads and increasing the number of processes- will give you an update. I am running Geonode 1.2 on Ubuntu 11.10. >From the error message, is it possible to tell why i cannot view the layers? Regards, On Fri, May 25, 2012 at 6:31 PM, David Winslow <[email protected]> wrote: > Are you sure that the geoserver logs are empty? That's surprising; in the > default configuration any uncaught exceptions should be dumped to the logs. > > The sequence of log messages suggests that the layer was not in fact > successfully uploaded; try logging in as an administrative user and viewing > the layer directly in GeoServer's Layer Preview. Does that work? If not, > visiting the configuration page in GeoServer for the suspect layer should > give you an idea of what's wrong with the configuration. > > I have seen the threading warnings you mention as well - and I have also > seen poor multithreading support in httplib2 can cause errors in GeoNode > sites (see http://code.google.com/p/httplib2/issues/detail?id=66) You > can reduce the number of threads and increase the number of processes in > /etc/apache/sites-available/geonode (the very first line) to reduce the > frequency of these errors, but at the expense of some RAM. > > -- > David Winslow > OpenGeo - http://opengeo.org/ > > On Fri, May 25, 2012 at 9:35 AM, Ketty Adoch <[email protected]> wrote: > >> Hello, >> >> I used the genode_import command to import a shapefile to geonode. The >> import process is successful since the layer appears in the geospatial data >> search output at the GUI. How ever when i try to view the layer from the >> GUI, an "Internal Server Error" is returned. Non of the already uploaded >> layers can be viewed. >> >> 1.)At the terminal, the error returned is "*xml.parsers.expat.ExpatError: >> XML or text declaration not at start of entity: line 4710, column 11"* >> >> A more detailed out put of the error can be found here >> http://pastebin.ca/2153859. >> >> 2.)I checked the geoserver.log file but it's empty(thought i would get >> some leads to a data rendering error). >> >> 3.Since the error(at the terminal) is displayed after the upload process, >> i thought it wise to check the apache.log file(for detailed info about the >> upload process) and this is the output: >> >> [Fri May 25 07:02:28 2012] [error] Exception KeyError: >> KeyError(-1211217264,) in <module 'threading' from >> '/usr/lib/python2.6/threading.pyc'> ignored >> [Fri May 25 07:02:29 2012] [error] Exception KeyError: >> KeyError(-1211217264,) in <module 'threading' from >> '/usr/lib/python2.6/threading.pyc'> ignored >> [Fri May 25 08:35:55 2012] [error] Exception KeyError: >> KeyError(-1211217264,) in <module 'threading' from >> '/usr/lib/python2.6/threading.pyc'> ignored >> [Fri May 25 08:36:28 2012] [error] Exception KeyError: >> KeyError(-1211217264,) in <module 'threading' from >> '/usr/lib/python2.6/threading.pyc'> ignored >> [Fri May 25 08:36:29 2012] [error] Exception KeyError: >> KeyError(-1211217264,) in <module 'threading' from >> '/usr/lib/python2.6/threading.pyc'> ignored >> >> 4.) The threading.pyc file seems to have high level content. :-( >> >> Has any one on the list seen this kind of error before? >> >> >> Regards, >> >> Ketty Adoch. >> Twitter:@kadoch >> Skype: adockatie >> >> >> >> >> >
