"Timeout waiting to send data" while tailing the log over admin.cgi
 

I have a simple installation of SHOUTcast DNAs/win64 v2.0.0.29, freshly installed using the installer from SHOUTcast.com. For my config, I copied sc_serv_relay.conf and updated the streamrelayurl. I made no other changes.

I fired up the server, and was able to get to the web admin panel without problem. Then, I tried to tail the logs. The log tail worked for a minute or so, but then disconnected. I tried over and over again, but it still kept getting disconnected. I noticed that in the logs, I get this error:

code:


2013-03-29 18:23:14	E	msg:[DST 127.0.0.1:29600] Timeout waiting to send data (1364599394 1364599336[58] )

This bug is easily reproducible... just go to the log tail URL with a browser, or a tool like cURL:

code:


curl "http://localhost:8000/admin.cgi?sid=1&mode=viewlog&viewlog=tail&pass=changeme"

Now, this disconnect occurs exactly the same time another log line comes in. Immediately before disconnect, the client receives a log line or two from what was presumably in the server's buffer. What I suspect is happening is that the server has a buffer for outgoing data. If that buffer isn't full, the data doesn't go out. When the server goes to send more data, it sees that there is still data in the buffer from several seconds prior and assumes the problem is that the client has disconnected. It then disconnects the client. This probably isn't an issue for busier servers with regular log entries.

I monitor my logs remotely with the tail feature. I cannot upgrade to v2 until this issue is resolved in some way. Thank you for your time.

tail mode is known to be buggy in that build. it might be better in the internal builds (aka what will become the now mythical next build) but i'm not 100% sure. as such without a newer build (no eta) then as much as it pains me, if this is key to your usage then you're going to have to use the legacy v1.

Thank you DrO for your swift response. I might just have to code up something to serve up the logs on my own for now.

On another note, I had checked the known issues list before posting: http://forums.winamp.com/showthread.php?t=332841 As tail is known to be broken, I would recommend adding it to the list.

Thanks again.

if i put everything in the known issues, no one would read it. it probably should be but your the first person to openly post about it not being right so i didn't view it as high volume enough to warrant being specifically noted.