Hello,
I've downloaded the GeoServer demo and got it running under win and linux. I managed to import my own data (shapes and postgis), and all went well. (The GUI is very nice for first time users, making Geoserver a joy to use.)
All went well till I had to shutdown the service (running as a background process under linux). It couldn't find stop.jar (missing in the demo?) and I used some brute force to kill -9 it.
Now, when I start the geoserver and only see
~GeoServer1.5.0/bin$ ./startup.sh
GEOSERVER DATA DIR is /home/utaddei/GeoServer1.5.0/data_dir
1 [main] INFO org.mortbay.log - Logging to org.slf4j.impl.SimpleLogger@anonymised.com via org.mortbay.log.Slf4jLog
355 [main] INFO org.mortbay.log - jetty-6.0.1
577 [main] INFO org.mortbay.log - Started SelectChannelConnector @ 0.0.0.0:8080
I then freezes there. I can see a page, when I point my browser to http://my.server:8080 (that is, something is running), but pointing to http://my.server:8080/geoserver I see
<snip>
HTTP ERROR: 404
NOT_FOUND
RequestURI=/geoserver/welcome.do
Powered by Jetty://
</snip>
Any ideas about what's happening?
Cheers,
Ugo
Ugo Taddei ha scritto:
Hello,
I've downloaded the GeoServer demo and got it running under win and linux. I managed to import my own data (shapes and postgis), and all went well. (The GUI is very nice for first time users, making Geoserver a joy to use.)
Thank you 
All went well till I had to shutdown the service (running as a background process under linux). It couldn't find stop.jar (missing in the demo?) and I used some brute force to kill -9 it.
Stop.jar was used in a old version of Jetty that we don't
use anymore. 1.5.0 should have a shutdown.sh command in geoserver/bin to
stop Geoserver.
Now, when I start the geoserver and only see
~GeoServer1.5.0/bin$ ./startup.sh
GEOSERVER DATA DIR is /home/utaddei/GeoServer1.5.0/data_dir
1 [main] INFO org.mortbay.log - Logging to org.slf4j.impl.SimpleLogger@anonymised.com via org.mortbay.log.Slf4jLog
355 [main] INFO org.mortbay.log - jetty-6.0.1
577 [main] INFO org.mortbay.log - Started SelectChannelConnector @ 0.0.0.0:8080
I then freezes there. I can see a page, when I point my browser to http://my.server:8080 (that is, something is running), but pointing to http://my.server:8080/geoserver I see
<snip>
HTTP ERROR: 404
NOT_FOUND
RequestURI=/geoserver/welcome.do
Powered by Jetty://
</snip>
Any ideas about what's happening?
We need the full Geoserver log, which is not enabled by default in the
binary distribution unfortunately. Could you do the following?
Go in the data_dir, locate services.xml, and turn:
<loggingToFile value = "false" />
to
<loggingToFile value = "true" />
Now, let's hope that before failing Geoserver does dump some useful log
into the data_dir/logs directory (which should be created during startup
with logging enabled).
Cheers
Andrea
577 [main] INFO org.mortbay.log - Started SelectChannelConnector @ 0.0.0.0:8080
This is where the console output indicates that Geoserver has
started--until something is clicked/changed via the web interface (or
some other method).
<snip>
HTTP ERROR: 404
NOT_FOUND
RequestURI=/geoserver/welcome.do
Powered by Jetty://
</snip>
Any ideas about what's happening?
Looks like the welcome and other pages are not getting compiled...
Possibly Jetty's logs will offer more insight.
And...Ugo??? As in the legendary Ugo from the Visad project? I am
reading through your
tutorials since last night--thanks for your outstanding work!! I gotta
implement zoom now
Alex
Hi Alexander
Alexander Petkov wrote:
577 [main] INFO org.mortbay.log - Started SelectChannelConnector @ 0.0.0.0:8080
This is where the console output indicates that Geoserver has
started--until something is clicked/changed via the web interface (or
some other method).
<snip>
HTTP ERROR: 404
NOT_FOUND
RequestURI=/geoserver/welcome.do
Powered by Jetty://
</snip>
Any ideas about what's happening?
Looks like the welcome and other pages are not getting compiled...
Possibly Jetty's logs will offer more insight.
...and where do I find the logs? The ones from geoserver are empty (as nothing happended).
And...Ugo??? As in the legendary Ugo from the Visad project? I am
reading through your
:-)=)
Thanx, thanx. Whether I'm legendary, I doubt. But I'm glad the tutorial helped you (and others!).
tutorials since last night--thanks for your outstanding work!! I gotta
implement zoom now
Alex
Cheers,
Ugo
hello Andrea,
Andrea Aime wrote:
Ugo Taddei ha scritto:
Hello,
I've downloaded the GeoServer demo and got it running under win and linux. I managed to import my own data (shapes and postgis), and all went well. (The GUI is very nice for first time users, making Geoserver a joy to use.)
Thank you
All went well till I had to shutdown the service (running as a background process under linux). It couldn't find stop.jar (missing in the demo?) and I used some brute force to kill -9 it.
Stop.jar was used in a old version of Jetty that we don't
use anymore. 1.5.0 should have a shutdown.sh command in geoserver/bin to
stop Geoserver.
Well, it shutdown.sh does call stop.jar:
exec "$_RUNJAVA" -DSTOP.PORT=8079 -DSTOP.KEY=geoserver -jar stop.jar
Now, when I start the geoserver and only see
~GeoServer1.5.0/bin$ ./startup.sh
GEOSERVER DATA DIR is /home/utaddei/GeoServer1.5.0/data_dir
1 [main] INFO org.mortbay.log - Logging to org.slf4j.impl.SimpleLogger@anonymised.com via org.mortbay.log.Slf4jLog
355 [main] INFO org.mortbay.log - jetty-6.0.1
577 [main] INFO org.mortbay.log - Started SelectChannelConnector @ 0.0.0.0:8080
I then freezes there. I can see a page, when I point my browser to http://my.server:8080 (that is, something is running), but pointing to http://my.server:8080/geoserver I see
<snip>
HTTP ERROR: 404
NOT_FOUND
RequestURI=/geoserver/welcome.do
Powered by Jetty://
</snip>
Any ideas about what's happening?
We need the full Geoserver log, which is not enabled by default in the
binary distribution unfortunately. Could you do the following?
Go in the data_dir, locate services.xml, and turn:
<loggingToFile value = "false" />
to
<loggingToFile value = "true" />
Now, let's hope that before failing Geoserver does dump some useful log
into the data_dir/logs directory (which should be created during startup
with logging enabled).
I did that, but got no logs. I got a new version installed, and that is at least is ok. Hopefully I can copy my datastores/ftypes to the new version.
Cheers
Andrea
Thanks for helping.
Ugo
I did that, but got no logs. I got a new version installed, and that is
at least is ok. Hopefully I can copy my datastores/ftypes to the new
version.
There;s also the way to reuse your existing catalog and data even
after you upgrade:
http://docs.codehaus.org/display/GEOSDOC/3+GeoServer+Data+Directory
Alex
hi,
Alexander Petkov wrote:
I did that, but got no logs. I got a new version installed, and that is
at least is ok. Hopefully I can copy my datastores/ftypes to the new
version.
There;s also the way to reuse your existing catalog and data even
after you upgrade:
http://docs.codehaus.org/display/GEOSDOC/3+GeoServer+Data+Directory
Alex
Yep. I did this and got them running again.
Cheers,
Ugo
> Well, it shutdown.sh does call stop.jar:
exec "$_RUNJAVA" -DSTOP.PORT=8079 -DSTOP.KEY=geoserver -jar stop.jar
This is actually a bug. It should be running start.jar with "--stop" as
a parameter. shutdown.bat has the correct behavior. Opening a jira for this.
http://jira.codehaus.org/browse/GEOS-1129
Now, when I start the geoserver and only see
~GeoServer1.5.0/bin$ ./startup.sh
GEOSERVER DATA DIR is /home/utaddei/GeoServer1.5.0/data_dir
1 [main] INFO org.mortbay.log - Logging to
org.slf4j.impl.SimpleLogger@anonymised.com via org.mortbay.log.Slf4jLog
355 [main] INFO org.mortbay.log - jetty-6.0.1
577 [main] INFO org.mortbay.log - Started SelectChannelConnector @
0.0.0.0:8080
I then freezes there. I can see a page, when I point my browser to
http://my.server:8080 (that is, something is running), but pointing to
http://my.server:8080/geoserver I see
<snip>
HTTP ERROR: 404
NOT_FOUND
RequestURI=/geoserver/welcome.do
Powered by Jetty://
</snip>
Any ideas about what's happening?
We need the full Geoserver log, which is not enabled by default in the
binary distribution unfortunately. Could you do the following?
Go in the data_dir, locate services.xml, and turn:
<loggingToFile value = "false" />
to
<loggingToFile value = "true" />
Now, let's hope that before failing Geoserver does dump some useful log
into the data_dir/logs directory (which should be created during startup
with logging enabled).
I did that, but got no logs. I got a new version installed, and that is
at least is ok. Hopefully I can copy my datastores/ftypes to the new
version.
Cheers
Andrea
Thanks for helping.
Ugo
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
!DSPAM:4007,4666bcd449001012714783!
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Ugo Taddei ha scritto:
hi,
Alexander Petkov wrote:
I did that, but got no logs. I got a new version installed, and that is
at least is ok. Hopefully I can copy my datastores/ftypes to the new
version.
There;s also the way to reuse your existing catalog and data even
after you upgrade:
http://docs.codehaus.org/display/GEOSDOC/3+GeoServer+Data+Directory
Alex
Yep. I did this and got them running again.
Good. Just in case you get stuck again, I'd like to have geoserver logs
available. Can you enable file logging in the geoserver configuration?
Cheers
Andrea