Bug 4832 - Windows update-forced reboot loses current playlist
: Windows update-forced reboot loses current playlist
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Web Interface
: 6.5.2
: PC Windows XP
: P2 normal (vote)
: ---
Assigned To: Spies Steven
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-19 09:53 UTC by Matt Richards
Modified: 2008-12-18 11:12 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Richards 2007-03-19 09:53:59 UTC
I have only experienced this once, but it's annoying.  I received some automatically downloaded updates from Microsoft for XP, and when I said "yes" to the reboot request, SlimServer restarted with my penultimate current playlist, losing the 35 or so tracks I had recently added.  It would be nice if SS flushed the current playlist to disk whenever it is changed, so that if a restart of any kind is required the playlist is not lost.

Of course, it's possible that it _does_ that, and I have simply encountered some sort of anomalous situation.  I suspect that Windows told SS to "shut down" for the reboot.  Part of that shutdown should be the saving of the current playlist.
Comment 1 Spies Steven 2007-03-19 10:21:13 UTC
Matt, I do know there is an option to Maintain Client Playlists under Behavior in Server Settings. I will investigate if it should work they way you describe. Otherwise I will change this bug to an enhancement request.
Comment 2 Matt Richards 2007-03-19 10:40:06 UTC
[actual person] SS: "I do know there is an option to Maintain Client Playlists under Behavior
in Server Settings."

Indeed so.  I had not seen it before . . . mine is set to remember playlists, which I assume is the default.  But apparently [software] SS does not do so when a forced reboot takes place.
Comment 3 Spies Steven 2007-03-19 15:14:31 UTC
Matt, I tried every combination I could think of to reproduce the behavior you describe. I've tried using the shutdown command from the Command Prompt to unplugging the machine and when SlimServer comes back up the playlist has been saved.

I see the bug was reported with version 6.5b3 selected. Perhaps this behavior is not in the current release?

My test machine version info:
SlimServer Version: 6.5.1 - 11206 - Windows XP - EN - cp1252
Server IP address: 172.16.0.5
Perl Version: 5.8.8 MSWin32-x86-multi-thread
MySQL Version: 5.0.22-community-nt 
Comment 4 Matt Richards 2007-03-19 15:50:53 UTC
Hi Steven,

I'm running 6.5.2 - 11639, which is not the absolute most current, I'm sure, but should be fairly close.  I forgot to look at that "Version" box on the bug.  Sorry about that.

The specific thing that triggered it for me was a forced reboot caused by Windows Update.  That might be difficult to replicate, but at some point your server should get something pushed out to it I would think.  I'm glad this feature works under other stressful circumstances.  I don't know how Windows Update kills other running processes, but possibly whatever command it uses is not one that SlimServer recognizes as requiring the current playlist to be saved.


Comment 5 Matt Richards 2007-03-20 06:16:20 UTC
I've just upgraded SlimServer and done a regular ol' reboot, and once again the current playlist was lost, going back to the previous version.
Comment 6 Spies Steven 2007-03-20 12:00:42 UTC
Matt, I installed 6.5.2 nightly and the playlist was saved correctly after a shutdown. I think something else is at play here. Are you running you own version of Perl or MySQL perhaps?

My test machine version info:
SlimServer Version: 6.5.2 - 11648 - Windows XP - EN - cp1252
Server IP address: 172.16.0.5
Perl Version: 5.8.8 MSWin32-x86-multi-thread
MySQL Version: 5.0.22-community-nt 
Comment 7 Matt Richards 2007-03-20 12:46:21 UTC
Nope, no home-grown anything.  It should be a fairly stock system, just Windows XP SP2, Slimserver, Rhapsody, not much else I believe.  I go in through the web interface across a network.

I'm certainly willing to believe something else is going on, as I lately had another very odd problem, wherein I while scrolling through tracks (using the remote on a Squeezebox) I didn't get all of them (but that seemed to fix itself when I sort of went out of that artist and then back in), but I don't know what it would be.  I really don't think there's anything particularly out of the ordinary on this system.  I'll try scandisking and such.
Comment 8 Matt Richards 2007-03-20 13:20:29 UTC
Ha!  Running chkdsk on a reboot got me back to an old playlist also.  Oh well.
Comment 9 Spies Steven 2007-03-21 09:03:05 UTC
Matt, is this working OK for you now? I would like to close this bug. Thanks!
Comment 10 Matt Richards 2007-03-21 12:06:18 UTC
No, it's definitely not working OK.  Every type of reboot I have done on that machine has lost the playlist.  But if you can't replicate it, I suppose closing it is the logical move.  I have encountered other strangenesses, so it's possible it's my system, although why that would be I cannot imagine.
Comment 11 Spies Steven 2007-03-21 15:51:29 UTC
I'm sorry to hear that. Can use successfully save a playlist normally? Does the playlist file show up in your designated playlist folder? Can you open the playlist successfully after a shutdown? I wonder if this is a database issue.
Comment 12 Ross Levine 2007-03-21 16:17:36 UTC
Could this have something to do with bug 4835? Strange behavior surrounding the current playlist during disconnect / reboot. 
Comment 13 Spies Steven 2007-03-23 13:05:50 UTC
Ross, thanks for the heads up. I don't think Matt's problem is related at this time. I think it may be with MySQL. I suggested that Matt clear out the cache to see if it makes any difference. I suppose falling back to 6.3.1 might be the next thing to try if clearing the cache does not work.
Comment 14 Spies Steven 2007-03-26 10:04:35 UTC
Matt, would you be willing to uninstall SlimServer 6.5.2 and install 6.3.1 and see if you get the same behavior? 6.3.1 and lower used SQLite and 6.5.0 and higher used MySQL. If 6.3.1 works properly for you MySQL may be the issue on your system.

More information on SQLite and MySQL:
http://wiki.slimdevices.com/index.cgi?SQLite

SlimServer 6.3.1 available here:
http://www.slimdevices.com/downloads/SlimServer_v6.3.1/
Comment 15 Matt Richards 2007-03-26 10:41:02 UTC
Yeah, I'll try that.
Comment 16 Matt Richards 2007-03-27 03:16:50 UTC
I downgraded to 6.3.1 and rebooted about four times.  Each time I got back the playlist I had had prior to the reboot, so that worked properly.
Comment 17 Matt Richards 2007-03-27 05:46:07 UTC
As a possibly related follow up . . . I keep a lot of oldtime radio programs on my server.  I believe there are 481 Jack Benny programs, each named ZZ_Jack Benny something and each on the album ZZ_oldradio.

I had noticed that 6.5.2 inexplicably used to think there were three different ZZ_oldradio albums under ZZ_Jack Benny, one with most of the files, and two each with a few of the files.  6.3.1 only sees one ZZ_oldradio album under ZZ_Jack Benny, with all of the files in it.  I don't know if this is also related to whatever database problems I might be having or not, but I thought I would mention it.

The playlist problem I'm having sounds to me like the database not flushing to disk, but I don't know why that would be something the database didn't handle itself at shutdown.
Comment 18 Chris Owens 2007-05-15 14:34:04 UTC
Unable to reproduce this in time for 6.5.2.  It'll stay open though so that Steven can continue to work on it.
Comment 19 Matt Richards 2007-05-22 07:59:43 UTC
I have retried this in the current nightly and the problem seems to be gone.
Comment 20 Michael Herger 2007-12-10 06:45:49 UTC
thanks for the positive feedback.
Comment 21 Chris Owens 2008-03-07 09:05:10 UTC
This bug is being closed since it was resolved for a version which is now released!  Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html

If you are still seeing this bug, please re-open it and we will consider it for a future release.