Bugzilla – Bug 3902
Infrant ReadyNAS NV playlist crashes
Last modified: 2008-12-18 11:11:39 UTC
Some ReadyNAS NV users are having an issue where saving playlist causes a Slimserver crash. This is particularly annoying on the ReadyNAS because it is difficult to restart the process. It is also difficult due to the fact that some versions of the ReadyNAS operating system do not store the Squeezebox log. Justin Maggard of Infrant writes: > If they've got the RAIDiator 3 beta installed, the log file is in the > .zip file that's created when you do "Download All Logs" from the Logs > tab. Other than that, it's not accessible on the P9 release. Affected users report that the saved playlist is three bytes long, characters that Dan identifies as a UTF BOM. He states that might happen if Slimserver somehow tries to save an empty playlist. The web UI is written to prevent that from ever happening. What I would like is for affected users to upload their logs, if available, using the 'Attach file' link, above. I'm also very interested at this time whether this problem only affects users with more than one squeezebox attached to the server. To be certain the second squeezebox is not attached, it's easy to temporarily unplug its power connection.
Here is the log output from the Infrant admin after a crash from saving a playlist. (reference 6731) The customer tried disconnecting one of the Squeezeboxes and saving then but it still crashed. (he has two SBs)
Created attachment 1431 [details] Log file output after a crash
I'm trying to reproduce this problem, and my ReadyNAS just keeps running! Daniel, do you think it's possible for you to try to figure out from the customer exactly what steps, from opening the Slimserver web page, they are performing to get the crash? For instance, does the following cause a crash? 1) Open Slimserver web page. 2) In the right-hand pane where the current songs are listed, hit 'Clear' to clear the current playlist. 3) Verify that the right-hand pane says "Empty" 4) In the left-hand pane, click "Browse albums" 5) Click an album to get the list of tracks 6) Click the "+" sign next to ONE track to add it to the playlist in the right-hand pane. 7) Click the "Save" link above the playlist. 8) Verify that the track you selected now shows up in the left-hand pane. 9) Click in the text-entry box labeled "Name" and type in a name for the playlist, such as "testplaylist". 10) Click "Save" to save the playlist.
(In reply to comment #3) > I'm trying to reproduce this problem, and my ReadyNAS just keeps running! > > Daniel, do you think it's possible for you to try to figure out from the > customer exactly what steps, from opening the Slimserver web page, they are > performing to get the crash? > > For instance, does the following cause a crash? > > 1) Open Slimserver web page. > 2) In the right-hand pane where the current songs are listed, hit 'Clear' to > clear the current playlist. > 3) Verify that the right-hand pane says "Empty" > 4) In the left-hand pane, click "Browse albums" > 5) Click an album to get the list of tracks > 6) Click the "+" sign next to ONE track to add it to the playlist in the > right-hand pane. > 7) Click the "Save" link above the playlist. > 8) Verify that the track you selected now shows up in the left-hand pane. > 9) Click in the text-entry box labeled "Name" and type in a name for the > playlist, such as "testplaylist". > 10) Click "Save" to save the playlist. > Those are the exact steps I use to get the Squeezebox and SlimServer to crash. The ReadyNAS *does* keep running -- I can view it in RAIDiator and in Front View. After clicking "Save," to save the playlist, the Squeezebox goes black. When I refresh the SlimServer page it gives a "can't connect" error message in both panes. When I try to power on the Squeezebox with the remote, it attempts to connect for a few moments but then gives a "can't connect" error message. The Squeezebox goes black again. I then reset the Squeezebox network connection with the remote. The Squeezebox acquires an IP address and then goes black. I go to Front View, reboot the ReadyNAS and everything is running fine.
Sorry I should have been more clear. I should have said 'SlimServer running on my ReadyNAS just keeps on running'. I can tell that what's happening is that Slimserver is crashing, but there's not enough hints in the log for me to grasp WHY it's crashing. How large is your music library? What kind of files do you have? Mp3? flac? both? something else? Where are you storing your music on the NAS? That is, on the Server Settings page, what does the Music Folder text box have in it? Maybe if I can set up my system to be more similar to yours I can cause the same error!
(In reply to comment #5) > How large is your music library? 6% of 681 GB. > What kind of files do you have? Mp3? flac? both? something else? FLAC only. > Where are you storing your music on the NAS? That is, on the Server Settings > page, what does the Music Folder text box have in it? /c/media/music > Maybe if I can set up my system to be more similar to yours I can cause the > same error! Whatever I can do to help, my friend!
Dan thinks this may have to do with the ReadyNAS running perl 5.6. I will follow up with customer.
Chris, per your request I have tried running with only one SB3 connected and encountered the same problem. When I specify a playlist file name and press Save, SlimServer locks up. I can get going again by stopping the SlimServer on the admin Streaming Services page and restarting it again. I do not need to reboot the NV. Cheers, David
David, what version of the ReadyNAS software are you running? This info is listed next to "Firmware:" on the "Welcome" screen.
Hm! Discussing this issue in email, Infrant pointed me to an update to the RAIDiator 3.0 beta they say has fixed some customer issues with Slimserver. I love companies that work on Saturday! http://www.infrant.com/download/addons/Temp_0.1.bin Please let me know if it helps!
(In reply to comment #9) > David, what version of the ReadyNAS software are you running? This info is > listed next to "Firmware:" on the "Welcome" screen. v3.00B5-p1-T1 [1.00.022] ...and no luck with the suggested RAIDiator patch. Thanks for continuing to look into it. David
Quick Update. Not that I was optimistic but... I've upgraded to the Official Release of Raidiator 3.0 with no additional success. David.
i'm experiencing this bug as a TWO-PART issue: 1. attempting to save a playlist causes slimserver to crash exactly as described in detail above. 2. slimserver fails to recognise pre-existing playlists in the assigned playlists folder, even after a re-scan of the playlists/music folder(s). fyi, i consider part 2 of the issue (not yet even mentioned yet in this bug report) far more critical for my personal use since i generate my playlists by other means, and simply play them on my slims. rarely do i save playlists generated on my slims, so that portion of the issue doesn't really affect me, but i *must* be able to play my existing playlists. should i report the second issue as a separate bug??? i suspect that the two are related, but i'm not 100% sure. some details of my setup: * server: slimserver 6.3.1 on readynas nv running RAIDiator� v3.00c1-p1 [1.00a024] * players: three original slimp3 players running firmware version 2.3, all three sync'd together * network: 10/100 wired ethernet using dhcp * slimserver music folder assigned to: /c/Media/Music/All (contains thousands of mp3s at various bitrates) * slimserver playlists folder assigned to: /c/Media/Music/Playlists (contains a couple dozen m3u playlists) also note that i have not experienced this issue in any way running slimserver 5.4.1 (among other versions) on two different windows machines over the years.
Chris: has this been escalated to Infrant?
It looks like I've not yet asked an important question in reproducing this. What do you all have your Playlists Folder set to? Thanks!
(In reply to comment #15) > It looks like I've not yet asked an important question in reproducing this. > What do you all have your Playlists Folder set to? > > Thanks! > my folders are configured as follows.... music: /c/Media/Music/All playlists: /c/Media/Music/Playlists
There was a RAIDiator update after 3.00c1-p1 that addressed the playlist issues. You can find the changelog at http://www.infrant.com/forum/viewtopic.php?t=5772 .
If anyone's still seeing this problem, please reopen this bug.
(In reply to comment #18) > If anyone's still seeing this problem, please reopen this bug. i just updated to raidiator 3.00c1-p2 and i am STILL SEEING PROBLEMS with playlists. specifically, issue #2 from my above comment (comment #13) does not seem to be resolved. issue #1 from that comment does appear to be resolved, but as i stated that is not the main problem for me. i absolutely need slimserver to recognize my *existing* playlists for it to be of any use to me. i don't appear to have permissions to re-open this bug. can you please re-open it, and make sure it's marked "critical" and high priority?
Subject: Re: Infrant ReadyNAS NV playlist crashes chris, i'm afraid this problem still exists. please have a look at the comment i just added to the bug report. bugzilla wouldn't let me change the bug status from "resolved" though. can you please look into this? it really is a show-stopper for me. thanks, grayson ____________ Grayson King 802.238.5402 On 10/10/06, Slim Devices Bugzilla <bugs@web.slimdevices.com> wrote: > https://bugs-archive.lyrion.org/show_bug.cgi?id=3902 > > > chris@slimdevices.com changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|NEW |RESOLVED > Resolution| |FIXED > > > > > ------- Comment #18 from chris@slimdevices.com 2006-10-10 14:28 ------- > If anyone's still seeing this problem, please reopen this bug. > > > > > ------- You are receiving this mail because: ------- > You are a voter for the bug, or are watching someone who is. > You are on the CC list for the bug, or are watching someone who is. >
I have opened bug 4344 for issue 2 in your earlier comment, Grayson. Please have a look and correct me if I got any of the details wrong. I also asked for some additional info there.