Bug 17919 – 7.7.2 prevents Disc 'spin down'

Bug 17919 - 7.7.2 prevents Disc 'spin down'

Summary:

7.7.2 prevents Disc 'spin down'

Status:	RESOLVED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Misc
Version:	7.7.2
Platform:	Infrant ReadyNAS RAIDiator (SPARC)

Importance:	-- normal (vote)
Target Milestone:	---
Assigned To:	Unassigned bug - please assign me!

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2012-03-05 01:27 UTC by Simon Pepper
Modified:	2012-03-13 01:42 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Simon Pepper 2012-03-05 01:27:21 UTC

I am noticing that with the 7.7.2 Beta (r33866) on ReadyNAS Duo (SPARC) that the discs don't spin down after a specified period of inactivity, which I have set to 5 minutes.

Looking at the server log, there is a repeated message:

[12-03-01 22:56:50.1224] Slim::Networking::SqueezeNetwork::Players::_player s_error (334) Unable to get players from SN: Connect timed out: Transport endpoint is not connected, retrying in 300 seconds
[12-03-01 23:00:49.0170] Slim::Networking::SqueezeNetwork::_error (596) Unable to login to SN: Connect timed out: Transport endpoint is not connected
[12-03-01 23:01:50.0475] Slim::Networking::SqueezeNetwork::_error (596) Unable to login to SN: Connect timed out: Transport endpoint is not connected
[12-03-01 23:01:50.0596] Slim::Networking::SqueezeNetwork::Players::_player s_error (334) Unable to get players from SN: Connect timed out: Transport endpoint is not connected, retrying in 600 seconds

There is also this error

[12-03-04 12:30:23.9582] Slim::Utils::Timers::__ANON__ (273) Error: Timer Slim::Web::Cometd::sendResponse failed: illegal file descriptor or filehandle (either no attached file descriptor or illegal value):  at /usr/share/perl5/Slim/Networking/IO/Select.pm line 150.

Is there something misconfigured in this build?

Comment 1 Simon Pepper 2012-03-13 01:42:13 UTC

With r33882 this seems to have been fixed.