Bug 13918 - SqueezeCenter 7.3.3/7.3.4 will not stay started on ReadyNas
: SqueezeCenter 7.3.3/7.3.4 will not stay started on ReadyNas
Status: RESOLVED WORKSFORME
Product: Logitech Media Server
Classification: Unclassified
Component: Database
: 7.3.4
: Infrant ReadyNAS Other
: -- normal (vote)
: ---
Assigned To: Walker LaRon
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-09-08 16:50 UTC by Walker LaRon
Modified: 2009-09-23 11:46 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments
SC 7.3.3 log file (24.42 KB, text/plain)
2009-09-08 16:50 UTC, Walker LaRon
Details
SC 7.3.4 Log File (100.36 KB, text/plain)
2009-09-08 16:51 UTC, Walker LaRon
Details
SC 7.3.4 log file (256.76 KB, text/plain)
2009-09-23 11:39 UTC, Brian
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Walker LaRon 2009-09-08 16:50:42 UTC
Created attachment 5804 [details]
SC 7.3.3 log file

Ticket 090820-001107


ReadyNas

Clean installs of SqueezeCenter 7.3.3 and 7.3.4


Customer states will work for a few days, and then his log fills up with the
following message:  (will also attach log file)

[09-09-03 12:47:20.2852] main::init (270) Starting SqueezeCenter (v7.3.4,
r28351, Sat Aug 29 03:03:11 PDT 2009)
2009-09-03 12:47:37 SqueezeCenter died. Restarting.


Thanks,

LaRon
Comment 1 Walker LaRon 2009-09-08 16:51:15 UTC
Created attachment 5805 [details]
SC 7.3.4 Log File
Comment 2 Michael Herger 2009-09-09 03:29:02 UTC
Run the cleanup tool Netgear provides, then try again. This is working fine for hundreds of users, including myself.
Comment 3 James Richardson 2009-09-10 09:40:49 UTC
LaRon: Please try the clean up tool as Michael suggests.  if you still see the issue, please reopen the bug
Comment 4 Walker LaRon 2009-09-10 11:35:34 UTC
Hello All,

Are you referring to the CleanSqueezeCenter_DB tool provided by Netgear?

http://www.readynas.com/?page_id=94

If so, we've done this a few times already.  If there is another tool, please let me know.

Thanks,

LaRon
Comment 5 Brian 2009-09-23 11:39:04 UTC
Created attachment 5902 [details]
SC 7.3.4 log file
Comment 6 Brian 2009-09-23 11:46:36 UTC
Additional comments to attached log file dated 09/23/09:

The ReadyNAS is configured to auto-shutdown at night and auto-boot in the morning. SqueezeCenter continued its die/restart loop until the morning of September 8 at which time it started successfully.

It continued through a series of successful stops and starts until September 23 at which time it died and the die/restart loop again initiated. This was preceded by the following log entries:

2009-09-23 00:30:09 squeezecenter_safe stopped.
2009-09-23 06:37:17 squeezecenter_safe started.
[09-09-23 06:37:57.0418] main::init (270) Starting SqueezeCenter (v7.3.4, r28351, Sat Aug 29 03:03:11 PDT 2009)
[09-09-23 06:38:01.7184] Slim::Networking::Async::DNS::init (93) No DNS servers responded, you may have problems with network requests.
2009-09-23 06:38:17 SqueezeCenter died. Restarting.

Prior to this, beginning on September 20, other errors began appearing in the log entries:

2009-09-20 01:00:10 squeezecenter_safe stopped.
2009-09-20 08:03:09 squeezecenter_safe started.
[09-09-20 08:03:43.8989] main::init (270) Starting SqueezeCenter (v7.3.4, r28351, Sat Aug 29 03:03:11 PDT 2009)
[09-09-20 10:49:28.3626] Slim::Utils::Scanner::Remote::__ANON__ (223) Error: Can't connect to remote server to retrieve playlist: Connect timed out: .
[09-09-20 20:00:18.1264] Slim::Utils::Scanner::Remote::__ANON__ (223) Error: Can't connect to remote server to retrieve playlist: 400 Server Full.
2009-09-21 00:30:10 squeezecenter_safe stopped.
2009-09-21 06:33:11 squeezecenter_safe started.
[09-09-21 06:33:47.8529] main::init (270) Starting SqueezeCenter (v7.3.4, r28351, Sat Aug 29 03:03:11 PDT 2009)
2009-09-22 00:30:10 squeezecenter_safe stopped.
2009-09-22 06:32:57 squeezecenter_safe started.
[09-09-22 06:33:37.6393] main::init (270) Starting SqueezeCenter (v7.3.4, r28351, Sat Aug 29 03:03:11 PDT 2009)
2009-09-23 00:30:09 squeezecenter_safe stopped.

Please advise as to next steps. Thank you.