Volumio Shuts Down during Library Indexing

I have a large library of mixed music, mp3, wav, flac, m4a, etc.

It seems Volumio handles it all fine as I can play all of it while its building my library, but at some point every single time before its finished the system shuts down.

I lose connection to the web interface and I lose ability to connect via SSH.

Ping is still working however.

I am unsure if its simply too many songs for the OS (I think its crashing near 16000 songs) or something else.
I was running journal this last time and this is all I have:

Sep 04 14:11:21 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:11:25 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:11:29 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:11:33 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:11:37 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:11:41 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:11:45 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:11:49 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:11:53 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:11:57 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:12:01 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:12:05 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:12:09 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:12:13 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:12:17 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:15:10 volumio volumio-remote-updater[566]: [2017-09-04 14:14:33] [fatal] handle_write_frame error: websocketpp.transport:10 (A transport action was requested after shutdown) Sep 04 14:16:25 volumio volumio-remote-updater[566]: [2017-09-04 14:15:31] [disconnect] Disconnect close local:[1006,A transport action was requested after shutdown] remote:[1006] Sep 04 14:17:22 volumio volumio-remote-updater[566]: [2017-09-04 14:16:56] [info] Error getting remote endpoint: system:9 (Bad file descriptor) Sep 04 14:18:09 volumio volumio-remote-updater[566]: [2017-09-04 14:17:13] [error] handle_connect error: Timer Expired Sep 04 14:19:36 volumio volumio-remote-updater[566]: terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >' Sep 04 14:20:23 volumio volumio-remote-updater[566]: what(): cancel: Bad file descriptor Sep 04 14:12:13 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:12:17 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:15:10 volumio volumio-remote-updater[566]: [2017-09-04 14:14:33] [fatal] handle_write_frame error: websocketpp.transport:10 (A transport action was requested after shutdown) Sep 04 14:16:25 volumio volumio-remote-updater[566]: [2017-09-04 14:15:31] [disconnect] Disconnect close local:[1006,A transport action was requested after shutdown] remote:[1006] Sep 04 14:17:22 volumio volumio-remote-updater[566]: [2017-09-04 14:16:56] [info] Error getting remote endpoint: system:9 (Bad file descriptor) Sep 04 14:18:09 volumio volumio-remote-updater[566]: [2017-09-04 14:17:13] [error] handle_connect error: Timer Expired Sep 04 14:19:36 volumio volumio-remote-updater[566]: terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >' Sep 04 14:20:23 volumio volumio-remote-updater[566]: what(): cancel: Bad file descriptor Sep 04 14:12:13 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:12:17 volumio volumio[919]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Sep 04 14:15:10 volumio volumio-remote-updater[566]: [2017-09-04 14:14:33] [fatal] handle_write_frame error: websocketpp.transport:10 (A transport action was requested after shutdown) Sep 04 14:16:25 volumio volumio-remote-updater[566]: [2017-09-04 14:15:31] [disconnect] Disconnect close local:[1006,A transport action was requested after shutdown] remote:[1006] Sep 04 14:17:22 volumio volumio-remote-updater[566]: [2017-09-04 14:16:56] [info] Error getting remote endpoint: system:9 (Bad file descriptor) Sep 04 14:18:09 volumio volumio-remote-updater[566]: [2017-09-04 14:17:13] [error] handle_connect error: Timer Expired Sep 04 14:19:36 volumio volumio-remote-updater[566]: terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >' Sep 04 14:20:23 volumio volumio-remote-updater[566]: what(): cancel: Bad file descriptor

Updated from a Pi1 to a Pi3 thinking it was not enough hardware power, that seems to not be the issue, so I hope somebody knows how to fix it and can help.

Regards,

Those errors seem to originate from the volumio-updater. Did you try to update while you were scanning?

No, I did not.

I have tried about 5 times, atleast one of those times I tried to update before kicking it off and it said there were no updates.
I have also completely flashed a new install to my SD card and went directly into building the library with nothing between and had the same issue.

I am experiencing the same error with the latest Volumio version and RPI 2 as well as RPI 3. When scanning the library after a few minutes Volumio starts showing the page load symbol and freezes. When reloading the page in the browser it does not refresh and is gone.

The IP scanner still finds it in the network though.

I am experiencing the same problem. I am using version 2.246 on an RPi3. My library is about 15,000 tracks. I can load it successfully on versions 2.041 and 2.185 in about 40 minutes. When I try to install the music on 2.246 it proceeds VERY slowly right from the start. With version 2.246 it is processing about 1200 to 1500 songs per hour. It has completely frozen several times, once around 3,000 songs and twice around 6,000 plus various other freezes. I have tried different SD cards, no difference. If I start with version 2.185 and install my music there, I can then upgrade to version 2.246 without any problems but I just can’t install it in a fresh version of 2.246. Library is mostly (98%) ALAC with some FLAC, AIFF and DSD.

As an experiment, I plugged my backup USB HDD directly into the Pi and 2.246 installed my music with no problem at all.

I’m having the same problem. I have had to roll back to 2.141.
I have several Pi3 based volumios. All were failing to update i.e. the device would download and appear to install an update but remain at the same version. I overcame this by following some advice online to run the sudo -ldconfig -v command (and also to delete user data if the update button ceased to work).
I got the systems updated but they all hang or reboot before successfully completing a scan of my NAS music libraries.
I can reboot and play music but the library is incomplete and if I try to an update or rescan I hit the same problem.
It’s been a pain rolling back because I don’t have the img file, so I’m having to clone from the one device I didn’t update - but creating the img of that system is 16GB…
Can we not maintain links to old version of 2.x? The links for the 1.x versions are all there.

Does anyone else have any logs around the time (before) the problem occurs please?

BTW: links to the last few stable versions of Volumio would be a good idea imho.

Edit: it seems to me that people have more trouble updating when they are using the /dev test versions of Volumio rather than stable releases. This could be quite subjective, and I hold my hands up to that (no hard facts at all); please try the test versions by all means, but if you want the minimum effort route to great music, just stick to the official updates. This is my personal opinion, and apologies to Michelangelo & the Volumio team if this means fewer people are testing.

Does the problem persist if you remove those files?
It seems some later mpd version fixes some issue with AIFF headers…

I can send logs after a reboot of a hung system if that’s useful.
my guess is that the hang/reboot is related to the new functionality to display thumbnails in the library.
Easiest way to check would be if there was some way to disable that feature… is there?

Same here: I have a huge collection of FLAC files (17000+ files) provided on a NAS (accessed via cifs) which were properly indexed in previous versions. The current version (2.246) freezes when updating/regenerating the index after having added a few new albums. When frozen, a login via ssh is not possible, ping is possible though.

Also flashing version 2.246 onto a new card does not help. System freezes at approx. 360 albums.

Hence: Neither updating a previously working collection nor a feshly flashed version were able to index/update the collection.

Cheers,
Stefan

Thank you for the info guys, I am personally taking care of this. It seems a problem with albumart server. I should be able to release a new image soon that fixes this

FYI: just to be sure that the issue is neither caused by my network nor the file access restriction settings, I reverted back to version 2.201. Indexing went fine, no problem observed.

Cheers

Just checking in,
I was using the stable release when I reported the problem.

Just got power back on from Hurricane Irma, so time to get all my stuff back to normal operation.

If you have any specific steps that you need to help debug the problem let me know.
I put home assistant on my RPI for a bit so I need to put Volumio back onto it.

Move HA to my FreeNas server running inside a Ubuntu Server VM to get my RPI3 back for this.

It looks like Michelangelo is working on this but I thought I would respond to this question just FYI. I deleted the AIFF files from my NAS and tried to load the library again. Same result VERY slow processing right from the beginning followed eventually by the system freezing.

Great product, great support. Thanks

Hi guys,

I understand that’s not my specific system which in cause, 'cause I have similar problem : partial indexation and shut down with the actual version of Volumio.

Thx

Hi,
there is a new PI test image out which should solve this problem, for the brave: please try.
Check Staff Communications/ HELP NEEDED TO TEST…

====> “test” means “may not be stable with all features”

Can you point me to any resource where I can the download the test image? I’ll give it a try and compare the scan results using my current version (2.201) as a reference.

help-needed-test-the-new-updater-t7057-80.html#p38017

Did a fresh install of the test/beta version and just got done indexing my main library without issues.
It had one spot where it stalled a very long time, from there it moved on fine.

I found that spot was very close to the same spot the stable release was crashing. I must have a file or files that the stable release just does not like, but the beta version was able to push through it.

I have not put much other testing in yet, this is just a preliminary report.

I have flashed the test image (volumio-2.272-2017-09-09-pi.img.zip) onto a new card and so far everthing seems to be fine! Indexing was a breeze (1100+ albums and 15900+ tracks).

I’ll continue testing this version on my Raspi (2b) and keep you posted in case I identify any further issue.

Cheers