[Geoserver-users] geoserver gets 404 error on start page - had been working fine previously

I had geoserver working fine for a couple months serving WMS and WFS content on my site through postgress that I had been working with. Today all of a sudden the content no longer shows on the map and I started getting the 404 error below from here when I try to go to the geoserver itself:
http://myhost:8080/

Error 404 - Not Found.No context on this server matched or handled this request.

Contexts known to this server are:

=======================

If I go to http://myhost:8080/geoserver or
http://myhost:8080/geoserver/web
it show nothing in the browser and the console log shows:

3084081 [btpool0-8] WARN org.mortbay.log - handle failed
java.io.IOException: FULL head
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:276)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)

On Fri, Feb 26, 2010 at 1:48 PM, Lammie Jonson <jrubiando@anonymised.com> wrote:

If I go to http://myhost:8080/geoserver or
http://myhost:8080/geoserver/web
it show nothing in the browser and the console log shows:

3084081 [btpool0-8] WARN org.mortbay.log - handle failed
java.io.IOException: FULL head
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:276)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)

Is it possible that your disk is full?
What does df -h say?

Ian

--
Ian Turton