WoL and other issues with 7.4 26644

[MadScientist]

For some reason 7.4 26644 keeps waking my SG from standby (XP machine).

Another, possibly related, issue is that random 'Song mix' won't clear unlil you have cleared the playlist. This is maintained even if SB3/Transporter has been turned off and there is continued disc read activity by SC. It is also impossible to restart a random 'Song mix' until the old playlist has been cleared.

Not sure if anyone can suggest what's going on? Here's a portion of the SC server log during my SC standby/wake period

Log

05-17 10:34:34.6883] Slim::Utils::Misc::msg (1154) Warning: [10:34:34.6877] getpeername() on closed socket GEN118 at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>IO/Socket.pm line 258.
[09-05-17 10:35:49.2662] Slim::Utils::Misc::msg (1154) Warning: [10:35:49.2656] getpeername() on closed socket GEN118 at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>IO/Socket.pm line 258.
[09-05-17 10:35:49.2673] Slim::Utils::Misc::msg (1154) Warning: [10:35:49.2667] getpeername() on closed socket GEN171 at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>IO/Socket.pm line 258.
[09-05-17 10:35:51.1145] Slim::Networking::Slimproto::client_readable (407) client_readable: Client not found for slimproto msg op: STAT
[09-05-17 10:35:52.9172] Slim::Utils::Misc::msg (1154) Warning: [10:35:52.9166] getpeername() on closed socket GEN118 at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>IO/Socket.pm line 258.
[09-05-17 10:35:56.8944] Slim::Networking::Slimproto::client_readable (407) client_readable: Client not found for slimproto msg op: STAT
[09-05-17 10:35:56.8951] Slim::Networking::Slimproto::client_readable (407) client_readable: Client not found for slimproto msg op: STAT
[09-05-17 10:35:56.8958] Slim::Networking::Slimproto::client_readable (407) client_readable: Client not found for slimproto msg op: STAT
[09-05-17 10:35:57.2466] Slim::Utils::Misc::msg (1154) Warning: [10:35:57.2460] getpeername() on closed socket GEN118 at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>IO/Socket.pm line 258.
[09-05-17 10:35:57.6031] Slim::Utils::Misc::msg (1154) Warning: [10:35:57.6025] getpeername() on closed socket GEN118 at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>IO/Socket.pm line 258.
[09-05-17 10:36:27.6099] Slim::Utils::Misc::msg (1154) Warning: [10:36:27.6093] getpeername() on closed socket GEN118 at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>IO/Socket.pm line 258.
[09-05-17 10:36:57.2871] Slim::Utils::Misc::msg (1154) Warning: [10:36:57.2866] getpeername() on closed socket GEN118 at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>IO/Socket.pm line 258.
[09-05-17 10:36:57.6258] Slim::Utils::Misc::msg (1154) Warning: [10:36:57.6252] getpeername() on closed socket GEN118 at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>IO/Socket.pm line 258.
[09-05-17 10:37:27.6414] Slim::Utils::Misc::msg (1154) Warning: [10:37:27.6408] getpeername() on closed socket GEN118 at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>IO/Socket.pm line 258.
[09-05-17 10:37:57.3331] Slim::Utils::Misc::msg (1154) Warning: [10:37:57.3326] getpeername() on closed socket GEN118 at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>IO/Socket.pm line 258.
[09-05-17 10:37:57.6568] Slim::Utils::Misc::msg (1154) Warning: [10:37:57.6562] getpeername() on closed socket GEN118 at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>IO/Socket.pm line 258.
[09-05-17 10:38:27.6724] Slim::Utils::Misc::msg (1154) Warning: [10:38:27.6718] getpeername() on closed socket GEN118 at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>IO/Socket.pm line 258.
[09-05-17 10:39:47.4015] Slim::Utils::Misc::msg (1154) Warning: [10:39:47.4009] getpeername() on closed socket GEN118 at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>IO/Socket.pm line 258.

[autopilot]

I have also had problems with my server waking with 26644, but not sure exactly why. A server can't wake itself up if its sleeping can it?, most likely that the nightly came with updated firmware for a player thats had some changes to the WOL code - but dont think anything has been updated has it?

Baffled TBH.

[MadScientist]

I have also had problems with my server waking with 26644, but not sure exactly why. A server can't wake itself up if its sleeping can it?, most likely that the nightly came with updated firmware for a player thats had some changes to the WOL code - but dont think anything has been updated has it?

Baffled TBH.

My SC still wakes with all players turned off completely, so it's nothing to do the the players. 26644 appears to make SG more sensitive to spurious network pings.

Equally baffled

MS