pmendiuk wrote: > I really like using the log window but occasionally the log window stops > showing CLI data. It seems like I have to deselect and then select the > debug options to get it to come back.
rgdawson wrote: > "I really like using the log window." - I can't say I ever expected to > read something like that, haha :) > > The reasons I can think of for that is that (1) nothing is happening so > nothing to log, or (2) The Telnet connection dropped, or (3) some > unknown bug in the logging code > > (1) OK, I'll rule out this out. But SLX uses Telnet primarily to enable > the media keys and monitor for certain events like play name changes, > new track info for notifications, get server status, get a list of > connected players and stuff like that. So if none of that is going on, > you won't see anything. Also, you won't see there anything the > browser/skin is doing. > > (2) Do you see any indication in the log, such as "Telnet disconnected". > If the telnet connection is being dropped, then certain other > functions, like media keys would stop functioning. If this happens > again, look for telnet disconnected and see if media keys are still > working. Then again, the telnet connection is checked every few seconds > and it should automatically reconnect, so I don't know if this is it > either. I do have a telnet keep-alive thing going on, but maybe I don't > have the time value set right for all circumstances. How long has SLX > been running when it seems to stop showing CLI commands? Maybe I need > to shorten the keep-alive interval. > > (3) It is interesting that changing debug level gets the messages to > come back. I suppose there could be a bug in there where a proposed log > event is sent, but not logged depending on the log level. I can look > there and re-check that code, but I have never seen this. > > Thanks for letting me know. > > R Greg Dawson OK, I looked into this. A very long time ago I saw this one time. So, I added a line of code to enable keep alive on the telnet socket binding and I never saw it again, so figured that was that. After your post I decided to look into that keep alive function call. And digging into how Windows works, I have determined that that the keepalive call basically expires after a couple of hours (Based on a system wide Registry setting and two hours is default for Windows). So I am guessing your SLX was basically idle for longer than that, maybe twice as long as that. In any case, I'll modify the code to prevent it from expiring (by re-calling the keep-alive function periodically) and we'll see if that solves the issue. R Greg Dawson Squeezelite-X ------------------------------------------------------------------------ rgdawson's Profile: http://forums.slimdevices.com/member.php?userid=65236 View this thread: http://forums.slimdevices.com/showthread.php?t=108550 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
