My server is hibernated over night, and I use Wake Up On Standby to wake the server up at 06:40.
This morning, after the server woke up, I got the following in my log: [06:40:47.1411] Slim::Networking::SimpleAsyncHTTP::onError (230) Failed to connect to http://www.mysqueezebox.com/api/v1/players (Timed out waiting for data) [06:40:47.1437] Slim::Networking::SqueezeNetwork::Players::_players_error (241) Unable to get players from SN: Timed out waiting for data, retrying in 300 seconds [06:40:52.2694] Slim::Networking::SimpleAsyncHTTP::onError (230) Failed to connect to http://www.mysqueezebox.com/api/v1/players (Timed out waiting for data) [06:40:52.2710] Slim::Networking::SqueezeNetwork::Players::_players_error (241) Unable to get players from SN: Timed out waiting for data, retrying in 600 seconds [06:40:52.2726] Slim::Networking::SimpleAsyncHTTP::onError (230) Failed to connect to http://www.mysqueezebox.com/api/v1/players (Timed out waiting for data) [06:40:52.2740] Slim::Networking::SqueezeNetwork::Players::_players_error (241) Unable to get players from SN: Timed out waiting for data, retrying in 900 seconds [06:40:52.2792] Slim::Networking::SimpleAsyncHTTP::onError (230) Failed to connect to http://www.mysqueezebox.com/api/v1/players (Timed out waiting for data) [06:40:52.2807] Slim::Networking::SqueezeNetwork::Players::_players_error (241) Unable to get players from SN: Timed out waiting for data, retrying in 1200 seconds [06:40:52.2821] Slim::Networking::SimpleAsyncHTTP::onError (230) Failed to connect to http://www.mysqueezebox.com/api/v1/players (Timed out waiting for data) [06:40:52.2834] Slim::Networking::SqueezeNetwork::Players::_players_error (241) Unable to get players from SN: Timed out waiting for data, retrying in 1500 seconds It's possible that SimpleAsyncHTTP didn't work because it takes a few seconds for network cards to re-establish connections after hibernations. However, the first attempt was a 06:40:47, and it said it would retry in 300 seconds. It then tried again 5 seconds later (which happens to be 300/60). Subsequent checks have no retry delay at all. Is there a problem with the calculation of the next retry time, or is this just a dodgy message? _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
