[Xitami] Console log

[Ewen McNeill]

In message <3B94511D.C09F5A7@rci.rutgers.edu>, Paul Reid writes:
>My Xitami has worked fine for way over a year with little
>trouble. It went down yesterday and I discovered 5,000 log-files
>with the numeric suffix (meaning it could not write to the main
>logfile?) all written within a few minutes of each other

Numbering the suffix is Xitami's strategy for making thing unique when
it is renaming them, or otherwise needs a unique name.  It suggests that
possibly Xitami was resarting its logging a lot during the time period
in question -- possibly because Xitami itself was restarting a lot
during that period.  (Which it can be configured to do under Windows if
it has network issues, mainly to deal with people on dialup connections.)

>2001/09/03 13:33:12: smthttp: error on socket 216: WSAESHUTDOWN
>2001/09/03 13:33:12: smthttp: error on socket 196: WSAESHUTDOWN
>2001/09/03 13:33:12: smthttp: error on socket 164: WSAESHUTDOWN
>2001/09/03 13:33:12: smthttp: error on socket 132: WSAESHUTDOWN
>2001/09/03 13:33:12: smthttp: error on socket 72: WSAESHUTDOWN
>
>What is WSAESHUTDOWN and why am I getting bursts of them? 

WSAESHUTDOWN appears to be basically equivilent to the Unix EPIPE -- ie
indicating that a connection that was open before has been closed
(presumably by the other end) at some point between when it was last
seen as open and when the next read/write attempt as made.

In this case either someone is connecting to your webserver and
abandoning their connections before Xitami gets a chance to answer
(which seems unlikely given the clustering of them you got "all at
once"), or something has confused Xitami or NT's networking into
thinking they've all closed.

If you haven't already tried the classic NT solution (rebooting) it's
probably worth doing to ensure the network stack has been reinitialised.

>(By the way: neither http://www.xitami.com nor
>http://www.xitami.com seems to be working for me today: no response.) 

The xitami.com website is hosted for us by OpenAvenue (the Open Source
company); it appears that they're having some sort of issue with that
webserver.  I've sent them an email asking them to look into it.

Thanks for the report.

Ewen

-- 
Ewen McNeill, Technical Consultant, iMatix Corporation  www.imatix.com