Turns out, I am not going crazy. The culprit for this seems to be my
desktop PC. I am using my work laptop during the day and desktop PC in
the evening. So the problem went away when I shut my desktop down last
night and I couldn't see the problem during the day. Turn my desktop on
and the messages start again:
Code:
--------------------
[22-01-19 21:15:08.2839] IO 10.03416 : Slim::Web::HTTP::processHTTP
[22-01-19 21:15:18.3988] IO 10.00898 : Slim::Web::HTTP::processHTTP
[22-01-19 21:15:28.5075] IO 10.00832 : Slim::Web::HTTP::processHTTP
[22-01-19 21:15:38.6196] IO 10.00981 : Slim::Web::HTTP::processHTTP
--------------------
Kill squeezelite on my desktop, messages stop.
Now promise you won't laugh....I was running it with -s 192.168.1.3:9000
after reading a comment on this bug when I was 'trying to troubleshoot
something else'
(https://forums.slimdevices.com/showthread.php?115547-Squeezelite-and-quot-player-already-active-quot-messages):
https://github.com/ralph-irving/squeezelite/issues/154#issuecomment-968386878
All this does is hammer the LMS web interface with connection attempts,
hence the terrible performance. It "fixes" the "player already active"
messages because it's not really connected, 9000 being the wrong port.
It seems like you can pass any port number at all to Squeezelite and it
doesn't give you any feedback that it couldn't connect!
------------------------------------------------------------------------
troffasky's Profile: http://forums.slimdevices.com/member.php?userid=70248
View this thread: http://forums.slimdevices.com/showthread.php?t=115787
_______________________________________________
Squeezecenter mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
