SqueezeBox Server won’t scrobble to LastFm
For the second time this week, I saw that my Squeezebox Server won't scrobble my played (and loved) tracks to last.fm! I started investigating, and in the server log of my Squeezebox server, I found the following errors:
Slim::Networking::SqueezeNetwork::_error (447) Unable to login to SN: Couldn't resolve IP address for: www.mysqueezebox.com
Slim::Networking::SqueezeNetwork::_init_error (180) Unable to login to mysqueezebox.com, sync is disabled: Couldn't resolve IP address for: www.mysqueezebox.com
Slim::Networking::SqueezeNetwork::_init_error (190) mysqueezebox.com sync init failed: Couldn't resolve IP address for: www.mysqueezebox.com, will retry in 2400
Slim::Plugin::AudioScrobbler::Plugin::_handshakeError (361) Error handshaking with Last.fm: Couldn't resolve IP address for: post.audioscrobbler.com
EV: error in callback (ignoring): pack_sockaddr: invalid host at /AnyEvent/DNS.pm line 1089
So if my Squeezebox server can't resolve the host name at startup it will never try to resolve the host name again. I tested the theory by restarting the Squeezebox server, and it immediately scrobbled all the buffered tracks once restarted!
The problem is due to the fact that on my PC, Squeezebox server was started either before the wireless network adapter was fully started or before my wireless network was started (as I shut this down each night). I now run version 7.4.1 of Squeezebox server. I can't see this planned for 7.4.2, so I guess I have to register this at the Squeezebox forum!
But as long as the problem is solved once I restart, and all played tracks are buffered, there is no need to worry!




April 23rd, 2010 - 18:13
Thx, I’ve got the same issue on my Mac. Restarting the SB server fixed it up.