Felix Karpfen <[EMAIL PROTECTED]> writes:
> However, my logs of these activities are loaded with "unususal systems
> events" such as:
>
> ,----[ errors.txt ]-
> | > Jan 3 08:03:57 eureka wwwoffled[509]: WWWOFFLE Fetch.
> | > Jan 3 08:04:07 eureka wwwoffled[509]: WWWOFFLE Fetch finished.
> | > Jan 3 08:07:45 eureka wwwoffles[9774]: Nothing to read from the wwwoffle proxy
> socket; timed out or connection lost? [Interrupted system call].
> | > Jan 3 08:07:45 eureka wwwoffles[9774]: Could not parse HTTP request (Empty
> request).
> | > Jan 3 08:07:45 eureka wwwoffles[9775]: Nothing to read from the wwwoffle proxy
> socket; timed out or connection lost? [Interrupted system call].
> | > Jan 3 08:07:45 eureka wwwoffles[9775]: Could not parse HTTP request (Empty
> request).
> | > Jan 3 08:07:47 eureka wwwoffles[9770]: Cannot write to client; disconnected?
> | > Jan 3 08:07:47 eureka wwwoffles[9778]: Nothing to read from the wwwoffle proxy
> socket; timed out or connection lost? [Interrupted system call].
> | > Jan 3 08:07:47 eureka wwwoffles[9778]: Could not parse HTTP request (Empty
> request).
> | > Jan 3 08:07:47 eureka wwwoffles[9779]: Nothing to read from the wwwoffle proxy
> socket; timed out or connection lost? [Interrupted system call].
> | > Jan 3 08:07:47 eureka wwwoffles[9779]: Could not parse HTTP request (Empty
> request).
> | > Jan 3 08:07:47 eureka wwwoffles[9772]: Cannot write to client; disconnected?
> `----
>
> Is a tweak to "wwwoffle.conf" on the cards, or do I just hope that the
> "unusual systems events" will go away on their own?
You could tweak wwwoffle.conf by setting 'use-syslog=no' so that these
messages never get logged into syslog. This would only hide the
"problems" rather than making them go away.
There are two different types of error message that you are getting.
1a) Nothing to read from the wwwoffle proxy socket; timed out or connection lost?
When WWWOFFLE was reading the request that came from the browser there
was no data to read (or a timeout occured). The particular message
that you have got is that there was an "Interrupted system call", but
this is strange because the WWWOFFLE low-level read functions will try
again in this particular case.
1b) Could not parse HTTP request
This error always comes after the first error but is a more general
error saying that WWWOFFLE cannot understand what the browser asked
for.
2) Cannot write to client; disconnected?
When WWWOFFLE was writing data to the browser the connection was
broken (by the browser) and WWWOFFLE failed to continue writing.
Possibly this was caused by pressing the "stop" button in the browser
or following a link before the page finished loading.
None of these errors are important unless they start occuring all of
the time or are related to times when you expect to be getting
something from WWWOFFLE but it fails.
--
Andrew.
----------------------------------------------------------------------
Andrew M. Bishop [EMAIL PROTECTED]
http://www.gedanken.demon.co.uk/
WWWOFFLE users page:
http://www.gedanken.demon.co.uk/wwwoffle/version-2.8/user.html
