This is the error I got when I started the geo-server as a standalone server and tried to bind it when starting geonode . http://pastebin.com/RRT1NWZA My geo-server is running on A.B.C.D ip with port 8080 . I tried to bind it using paver host -b A.B.C.D:8080 . Even though the geoserver is still up and running , I get an internal server error . I did all the necessary changes in jetty.xml and settings.py so as to point to that geoserver . -- *Satyajit Sarangi*
The "Address already in use" means pretty much what it sounds like - there's already a server listening to the port GeoNode is trying to use. You can see what service that is by using the netstat command - on Linux I usually invoke it like this (Tcp sockets that are Listening, listed with process Numbers and Process names): netstat -tlnp You should bring down any servers that are already listening on the ports you want GeoNode to use, or change GeoNode's settings to use a different port. -- David Winslow OpenGeo - http://opengeo.org/ On Tue, Apr 5, 2011 at 5:25 AM, Satyajit Sarangi <writetosatyajit@gmail.com>wrote: > This is the error I got when I started the geo-server as a standalone > server and tried to bind it when starting geonode . > http://pastebin.com/RRT1NWZA > > My geo-server is running on A.B.C.D ip with port 8080 . I tried to bind it > using paver host -b A.B.C.D:8080 . Even though the geoserver is still up and > running , I get an internal server error . I did all the necessary changes > in jetty.xml and settings.py so as to point to that geoserver . > > -- > *Satyajit Sarangi* > >
src/owslib/owslib/csw.py There is a function called getrecords(). It takes cql as a parameter. It is set to none. How do i set it to the constraints i want? -- Regards Smitha V (MT2009149) 2nd Year MTech IIITB
Hello. I have pasted the django.log . As you said , the geoserver log has java stack trace . So how do I go about it from here in solving the problem for this there was an error while attempting to upload your data. Please try again, or contact and administrator if the problem continues. "<http://dev.geonode.org/trac/ticket/796> while uploading ? http://pastebin.com/e9d5DgbF Thank you -- *Satyajit Sarangi*
The "bad credentials" error in the Django log indicates that GeoNode is making administrative requests to GeoServer and GeoServer does not recognize the user. This is fairly surprising since GeoNode includes a customized version of GeoServer which shares user information with the Django application. Perhaps you are using an unmodified GeoServer build with GeoNode? -- David Winslow OpenGeo - http://opengeo.org/ On Tue, Mar 22, 2011 at 12:28 PM, Satyajit Sarangi < writetosatyajit@gmail.com> wrote: > Hello. > I have pasted the django.log . As you said , the geoserver log has java > stack trace . So how do I go about it from here in solving the problem for > this there was an error while attempting to upload your data. Please try > again, or contact and administrator if the problem continues. "<http://dev.geonode.org/trac/ticket/796> while > uploading ? > http://pastebin.com/e9d5DgbF > > Thank you > -- > *Satyajit Sarangi* > >
Please keep discussion on the public mailing list. Your error suggests to me that you have configured the GEONODE_BASE_URL for GeoServer incorrectly. Do you have an entry in web.xml like: <context-param> <param-name>GEONODE_BASE_URL</param-name> <param-value>192.168.0.195</param-value> </context-param> Instead it should be <context-param> <param-name>GEONODE_BASE_URL</param-name> <param-value>*http://*192.168.0.195*/*</param-value> </context-param> In URL parlance this portion of a URL is called the "scheme", hence the error message you were seeing. -- David Winslow OpenGeo - http://opengeo.org/ ---------- Forwarded message ---------- From: Satyajit Sarangi <writetosatyajit@gmail.com> Date: Tue, Mar 22, 2011 at 3:02 PM Subject: Re: [geonode] To: David Winslow <dwinslow@opengeo.org> I tried to run the server that comes with the geonode and it throws up this error . http://pastebin.co <http://pastebin.com/XYtf6f2C> * * m/XYtf6f2C <http://pastebin.com/XYtf6f2C> . On Tue, Mar 22, 2011 at 11:03 AM, Satyajit Sarangi < writetosatyajit@gmail.com> wrote: > Yeah we are . This is mainly because the geoserver present in the GeoNode > installation throws up a "500 internal server error" . Thus we are using a > separate installation of geo-server > > > On Tue, Mar 22, 2011 at 11:00 AM, David Winslow <dwinslow@opengeo.org>wrote: > >> The "bad credentials" error in the Django log indicates that GeoNode is >> making administrative requests to GeoServer and GeoServer does not recognize >> the user. This is fairly surprising since GeoNode includes a customized >> version of GeoServer which shares user information with the Django >> application. Perhaps you are using an unmodified GeoServer build with >> GeoNode? >> >> -- >> David Winslow >> OpenGeo - http://opengeo.org/ >> >> >> On Tue, Mar 22, 2011 at 12:28 PM, Satyajit Sarangi < >> writetosatyajit@gmail.com> wrote: >> >>> Hello. >>> I have pasted the django.log . As you said , the geoserver log has java >>> stack trace . So how do I go about it from here in solving the problem for >>> this there was an error while attempting to upload your data. Please try >>> again, or contact and administrator if the problem continues. "<http://dev.geonode.org/trac/ticket/796> while >>> uploading ? >>> http://pastebin.com/e9d5DgbF >>> >>> Thank you >>> -- >>> *Satyajit Sarangi* >>> >>> >> > > > -- > *Satyajit Sarangi* > > -- *Satyajit Sarangi*
Hello There are two logs being generated . One at django.log the other at the geoserver log . Which log would you want to take a look ? I also followed http://dev.geonode.org/trac/ticket/796 this patch . But the layer_upload.html was already updated thought it still is throwing the same error . The server dealing in other pages like map_search.html and all that is working fine . Just that uploading a shape file isn't , throwing up the error stating " there was an error while attempting to upload your data. Please try again, or contact and administrator if the problem continues. "<http://dev.geonode.org/trac/ticket/796> Thank full for all the help till now . -- *Satyajit Sarangi*
Both logs may have useful information; Django and GeoServer are both involved in the upload process. I usually check the Django log first since the GeoServer logs tend to have a lot of long Java stack traces in them. If you will use a website such as pastebin.com to paste your log files, I can take a look at your error and possibly recommend a solution. -- David Winslow OpenGeo - http://opengeo.org/ On Mon, Mar 21, 2011 at 3:45 PM, Satyajit Sarangi <writetosatyajit@gmail.com > wrote: > Hello > > There are two logs being generated . One at django.log the other at the > geoserver log . Which log would you want to take a look ? I also followed > http://dev.geonode.org/trac/ticket/796 this patch . But the > layer_upload.html was already updated thought it still is throwing the same > error . The server dealing in other pages like map_search.html and all that > is working fine . Just that uploading a shape file isn't , throwing up the > error stating " there was an error while attempting to upload your data. > Please try again, or contact and administrator if the problem continues. "<http://dev.geonode.org/trac/ticket/796> > Thank full for all the help till now . > -- > *Satyajit Sarangi* > >
I am getting this error while trying to upload data in geonode . "There was an error while attempting to upload your data. Please try again, or contact and administrator if the problem continues. " . How do I fix it ? I am using an older version of geonode . Any idea how to get around this error without going for a fresh installation ? -- *Satyajit Sarangi*
You need to find out what is causing this error. Please turn up the logging level in Apache as described here. http://docs.geonode.org/1.0/logging.html and then inspect the apache logs for the stack-trace. If you need to, please paste the errors here so we can try to help you debug this. Jeff On Fri, Mar 18, 2011 at 12:38 AM, Satyajit Sarangi <writetosatyajit@gmail.com> wrote: > > I am getting this error while trying to upload data in geonode . "There was > an error while attempting to upload your data. Please try again, or contact > and administrator if the problem continues. " . How do I fix it ? I am using > an older version of geonode . Any idea how to get around this error without > going for a fresh installation ? > -- > Satyajit Sarangi > >
Hello
On a fresh installation of geonode on my local-machine , a
geonode-client folder is created . But when I try to do an installation on
my server , no folder of the name geonode-client is created . I tried
getting the geonode-client as mentioned in the github page but I failed to
build it as it gave this error
[exec] error: pathspec
'build/ringo/e0dce2be640fc6fb43a1239d252948d10687ba9c' did not match
any file(s) known to git.
BUILD FAILED
/home/palantir/geonode1/src/geonode-client/build.xml:22: exec returned: 1
How do I get the geonode-client up and running on the server ?
--
*Satyajit Sarangi*
> On a fresh installation of geonode on my local-machine , a > geonode-client folder is created . But when I try to do an installation on > my server , no folder of the name geonode-client is created . I tried > getting the geonode-client as mentioned in the github page but I failed to > build it as it gave this error > > [exec] error: pathspec > 'build/ringo/e0dce2be640fc6fb43a1239d252948d10687ba9c' did not match any > file(s) known to git. > > > BUILD FAILED > /home/palantir/geonode1/src/geonode-client/build.xml:22: exec returned: 1 > > How do I get the geonode-client up and running on the server ? How are you running/deploying geonode on the server? Did you build a release from source from a recent master checkout? With a recent master checkout/build/deploy, you now need the following alias in your apache config pointing to wherever you have your geonode release tree. Alias /media/ /var/www/geonode/wsgi/geonode/src/GeoNodePy/geonode/media/ This should also be added to your local_settings.py with SITEURL set appropriately (ideally with a trailing slash. GEONODE_CLIENT_LOCATION = SITEURL + 'media/static/' Also, make sure you are looking at the most current deploy docs ... https://github.com/geonode/geonode/blob/master/docs/source/deployment.rst https://github.com/geonode/geonode/blob/master/docs/source/deploy/ubuntu.rst https://github.com/geonode/geonode/blob/master/docs/source/deploy/centos.rst Hope that helps? Jeff