CharcoalGray's XML Page: "sock accept failed"?

I'm running Hijack 276.

- When I am connected to the player via the serial port with Hyperterminal, and

- I have CharcoalGray99's XML page open on the player via ethernet at the same time, and

- The page is doing the "auto refresh" trick to update the player display on the XML page...

Sometimes I will see the following message on the serial terminal:

khttpd: sock_accept: accept() failed, rc=-104

This seems to coincide with a missed screen update on the XML page.

Does this indicate a problem, or is this normal for the XML page?

Note, I have noticed this on two different computers, one running IE6 and one running IE5.5.

khttpd: sock_accept: accept() failed, rc=-104

What's your refresh interval set at?

Result code 104 is ECONNRESET which is "Connecion Reset by Peer." Based on that, it looks to me like your refresh interval is probably set pretty low, and the khttpd is sending its output, but the refresh interval is hit and the browser closes the connection and reopens another one to refresh. Try increasing the refresh interval and see if that helps.

Not sure what Hyperterminal would have to do with this scenario, though.

I believe the refresh interval is set to the default that the XML page comes with. I haven't changed it from the defaults since the last time I re-installed the pages from scratch.

Hrm well I could be off on my analysis, but the result code does indicate the TCP connection is being broken by the browser.

Oh, I think your analysis is correct, I'm just wondering if this is normal. Anyone else get this?

I saw that result code during khttpd development/testing, and eventually concluded that it must be due to the browser giving up on a refresh attempt, closing the connection, and then retrying the refresh.

This will happen whenever the player does not respond to the player before the player asks for the NEXT refresh, which can happen if the player is busy with disk access.

To test this theory, do a full-collection shuffle/unshuffle while running the browser thingie.. should see lots of those messages.

Cheers