No, the build doesn't install geos for you. I neglected to update the readme when we added this dependency.
-d On 08/06/2010 09:28 AM, Chris Holmes wrote: > Ok, that made a bit more progress. I can go to GeoNetwork without OOM > errors. GeoServer still bombs while trying to request authorization. > If I go to localhost:8000 though I get this error: > > TemplateSyntaxError at / > > Caught ViewDoesNotExist while rendering: Could not import > geonode.maps.views. Error was: Could not find the GEOS library (tried > "geos_c", "GEOS"). Try setting GEOS_LIBRARY_PATH in your settings. > > Request Method: GET > Request URL: http://localhost:8000/ > Django Version: 1.2 > Exception Type: TemplateSyntaxError > Exception Value: > > Caught ViewDoesNotExist while rendering: Could not import > geonode.maps.views. Error was: Could not find the GEOS library (tried > "geos_c", "GEOS"). Try setting GEOS_LIBRARY_PATH in your settings. > > **** > > So I guess I need to install GEOS? Or is the build supposed to have > done that already? > > On 8/6/10 9:11 AM, Gabriel Roldan wrote: > >> First run the django server like this: >> paster serve --reload shared/dev-paste.ini >> >> Then on another terminal, go to src/geoserver-geonode-ext and run jetty >> with the startup.sh script that's in there, in order to avoid the >> GeoNetwork out of memory problem. It's a known issue with geonetwork. >> >> >> Hope that helps, >> Gabriel >> >> On 8/5/10 9:05 PM, Chris Holmes wrote: >> >>> That didn't work. >>> >>> Seb also suggested that I do run jetty independently, as sometimes the >>> main thing will stop if jetty takes awhile to start. >>> >>> I did that, but when I tried to go to GeoServer I got a stack trace >>> where the ultimate cause was 'Error connecting to GeoNode authentication >>> server: Connection refused', but the GeoNode authentication server >>> wasn't running, since I was trying to start jetty first. If I tried >>> GeoNetwork I got out of memory errors. >>> >>> I'll try out increasing the memory, and starting up django right after I >>> get jetty running (though I'm pretty sure I did, and it did fail). It's >>> the same error as before. >>> >>> thanks, >>> >>> C >>>
