With that "Four hundred and four!" error page. One or more reloads fix that.
Note: In case this helps: if my .lighttpd.conf is not loaded, the path requested is really a 404, because I'm rewriting almost everything to a FastCGI handler.
Version: unspecified
Severity: normal
I'm not sure I understand the report. I can tell you that it takes several seconds before the lighttpd is started (and might take up to ~30s or so if the grid is really loaded), so while restarting you'll get the default apache for that period.
Perhaps that is what you are experiencing?
(In reply to comment #1)
I'm not sure I understand the report. I can tell you that it takes several
seconds before the lighttpd is started (and might take up to ~30s or so if
the
grid is really loaded), so while restarting you'll get the default apache for
that period.Perhaps that is what you are experiencing?
Yes :) my public_html is almost empty and everything is handled by the FastCGI webapp configured in lighttpd, so when Apache is handing requests for me everything is 404.
But if so, can't the webservice command wait until the server is really started? Having a "started" message outputted with the server still being started seems misleading.
Sorry, it's not really possible to do so (the script can know when the job has been submitted, not when the process is ready to accept connections).
That said, with the new webservice scheme, the error is not ambiguous: the error displayed is that there is no running webservice.