Database update stops after a few artists

Hi,

I am new to Volumio, I have just installed in in a VM for testing purposes… I have been a Squeezebox/LMS server user for more than 12 years and currently looking at modern alternatives for my Squeezebox infrastructure…

Anyway, I have my music stored on a network share to which I can connect successfully in Volumio, but the update seems to stop after only a few artists:

Image5.png

The logs are showing these errors repeatedly:

volumio.log

2020-02-26T19:21:19.694Z - info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
2020-02-26T19:21:19.695Z - error: MPD error: false == true
2020-02-26T19:21:23.695Z - info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
2020-02-26T19:21:23.695Z - error: MPD error: false == true
2020-02-26T19:21:27.694Z - info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
2020-02-26T19:21:27.695Z - error: MPD error: false == true
2020-02-26T19:21:31.694Z - info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
2020-02-26T19:21:31.694Z - error: MPD error: false == true
2020-02-26T19:21:35.694Z - info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
2020-02-26T19:21:35.694Z - error: MPD error: false == true
2020-02-26T19:21:39.693Z - info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
2020-02-26T19:21:39.693Z - error: MPD error: false == true
2020-02-26T19:21:43.694Z - info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
2020-02-26T19:21:43.694Z - error: MPD error: false == true

mpd.log

Feb 26 19:21 : client: Max connections reached
Feb 26 19:21 : client: Max connections reached
Feb 26 19:21 : client: Max connections reached
Feb 26 19:21 : client: Max connections reached
Feb 26 19:21 : client: Max connections reached
Feb 26 19:21 : client: Max connections reached
Feb 26 19:21 : client: Max connections reached
Feb 26 19:21 : client: Max connections reached
Feb 26 19:21 : client: Max connections reached
Feb 26 19:22 : client: Max connections reached
Feb 26 19:22 : client: Max connections reached

So any hint here about what may be going wrong?

Thanks!

Here is a larger chunk of the mpd.log from when it starts failing:

Feb 26 23:07 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1979] Tusk/09 Not That Funny.flac
Feb 26 23:07 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1979] Tusk/10 Sisters Of The Moon.flac
Feb 26 23:07 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1979] Tusk/11 Angel.flac
Feb 26 23:07 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1979] Tusk/12 That's Enough For Me.flac
Feb 26 23:07 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1979] Tusk/13 Brown Eyes.flac
Feb 26 23:07 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1979] Tusk/14 Never Make Me Cry.flac
Feb 26 23:07 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1979] Tusk/15 I Know I'm Not Wrong.flac
Feb 26 23:07 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1979] Tusk/16 Honey Hi.flac
Feb 26 23:07 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1979] Tusk/17 Beautiful Child.flac
Feb 26 23:07 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1979] Tusk/18 Walk A Thin Line.flac
Feb 26 23:07 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1979] Tusk/19 Tusk.flac
Feb 26 23:07 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1979] Tusk/20 Never Forget.flac
Feb 26 23:07 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1979] Tusk/21 Think About Me (Single Remix).flac
Feb 26 23:07 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1979] Tusk/22 Not That Funny (Single Remix).flac
Feb 26 23:07 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1979] Tusk/23 Sara (Single Edit).flac
Feb 26 23:07 : exception: std::bad_alloc
Feb 26 23:07 : exception: std::bad_alloc
Feb 26 23:07 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1980] Live/01 Monday Morning.flac
Feb 26 23:07 : zeroconf: No global port, disabling zeroconf
Feb 26 23:08 : client: [0] opened from local
Feb 26 23:08 : client: [1] opened from 127.0.0.1:37002
Feb 26 23:08 : client: [2] opened from local
Feb 26 23:08 : client: [3] opened from local
Feb 26 23:08 : client: [4] opened from local
Feb 26 23:08 : client: [5] opened from local
Feb 26 23:08 : client: [6] opened from local
Feb 26 23:08 : client: [7] opened from local
Feb 26 23:08 : client: [8] opened from local
Feb 26 23:08 : client: [9] opened from local
Feb 26 23:08 : client: [10] opened from local
Feb 26 23:08 : client: [11] opened from local
Feb 26 23:08 : client: [12] opened from local
Feb 26 23:08 : client: [13] opened from local
Feb 26 23:08 : client: [14] opened from local
Feb 26 23:08 : client: [15] opened from local
Feb 26 23:08 : client: [16] opened from local
Feb 26 23:08 : client: [17] opened from local
Feb 26 23:08 : client: [18] opened from local
Feb 26 23:08 : client: [19] opened from local
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:08 : client: Max connections reached
Feb 26 23:09 : client: Max connections reached
Feb 26 23:09 : client: Max connections reached
Feb 26 23:09 : client: Max connections reached
Feb 26 23:09 : client: Max connections reached
Feb 26 23:09 : client: Max connections reached
Feb 26 23:09 : client: Max connections reached
Feb 26 23:09 : client: Max connections reached
Feb 26 23:09 : client: Max connections reached
Feb 26 23:09 : client: Max connections reached
Feb 26 23:09 : client: Max connections reached
Feb 26 23:09 : client: Max connections reached
Feb 26 23:09 : client: Max connections reached
Feb 26 23:09 : client: Max connections reached

I have increased the max connections in mpd.conf and now I am not getting the client: Max connections reached message anymore, however it still hangs after the same file:

Feb 27 09:25 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1974] Heroes Are Hard To Find/01 Heroes Are Hard To Find.flac
Feb 27 09:25 : exception: std::bad_alloc
Feb 27 09:25 : exception: std::bad_alloc
Feb 27 09:25 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1974] Heroes Are Hard To Find/02 Coming Home.flac
Feb 27 09:25 : update: added NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1974] Heroes Are Hard To Find/03 Angel.flac
Feb 27 09:25 : zeroconf: No global port, disabling zeroconf
Feb 27 09:26 : client: [0] opened from local
Feb 27 09:26 : client: [1] opened from 127.0.0.1:42886
Feb 27 09:26 : client: [2] opened from local
Feb 27 09:26 : client: [3] opened from 127.0.0.1:42892
Feb 27 09:26 : client: [4] opened from local
Feb 27 09:26 : client: [5] opened from local
Feb 27 09:26 : client: [6] opened from local
Feb 27 09:26 : client: [7] opened from local
Feb 27 09:26 : client: [8] opened from local
Feb 27 09:26 : client: [9] opened from local
Feb 27 09:26 : client: [10] opened from local
Feb 27 09:26 : client: [11] opened from local
Feb 27 09:26 : client: [12] opened from local
Feb 27 09:26 : client: [13] opened from local
Feb 27 09:26 : client: [14] opened from local
Feb 27 09:26 : client: [15] opened from local
Feb 27 09:26 : client: [16] opened from local
Feb 27 09:26 : client: [17] opened from local
Feb 27 09:26 : client: [18] opened from local
Feb 27 09:26 : client: [19] opened from local
Feb 27 09:26 : client: [20] opened from local
Feb 27 09:26 : client: [21] opened from local
Feb 27 09:26 : client: [22] opened from local
Feb 27 09:26 : client: [23] opened from local
Feb 27 09:26 : client: [24] opened from local
Feb 27 09:26 : client: [25] opened from local
Feb 27 09:26 : client: [26] opened from local
Feb 27 09:26 : client: [27] opened from local
Feb 27 09:26 : client: [28] opened from local
Feb 27 09:26 : client: [29] opened from local
Feb 27 09:26 : client: [30] opened from local
Feb 27 09:26 : client: [31] opened from local
Feb 27 09:26 : client: [32] opened from local
Feb 27 09:26 : client: [33] opened from local
Feb 27 09:26 : client: [34] opened from local
Feb 27 09:27 : client: [35] opened from local
Feb 27 09:27 : client: [36] opened from local
Feb 27 09:27 : client: [37] opened from local
Feb 27 09:27 : client: [38] opened from local
Feb 27 09:27 : client: [39] opened from local
Feb 27 09:27 : client: [40] opened from local
Feb 27 09:27 : client: [41] opened from local
Feb 27 09:27 : client: [42] opened from local
Feb 27 09:27 : client: [43] opened from local
Feb 27 09:27 : client: [44] opened from local
Feb 27 09:27 : client: [1] closed

So it’s after this file that I’m seeing the exception: std::bad_alloc errors:

NAS/musiXerver/@!Hi-Res Stereo/[F-K]/Fleetwood Mac/[1974] Heroes Are Hard To Find/01 Heroes Are Hard To Find.flac

However, the file plays perfectly in foobar and also passes the integrity check, so I am not sure what upsets mpd while reading it…
Image5.png

Same here.

I have the same issue as well, the log also says max number or connections reached and it won’t add anything else. Well, in my case it does not show anything at all in the Music Library. It adds some then suddenly disappears, and the log shows the mentioned error.

Hi,

Did you already upgrade to v2.713 ? I think there was a fix.

Best Regards
Josef

Hello guys,

yes me too having same troubles. I supposed that the cause could be due to a last music folder added to my HDD (USB attached, no NAS), supposing that some special characters were inside music file tags.

So I delete latest added data, but I’ve not solved: after 20/30 seconds from the beginning of the scan all counters reset to zero and I’m not able to do nothing anymore…

I’m using Volumio version 2.713

I have the latest Volumio version just downloaded the image from the site 2 days ago…

And it’s the same for me, it hangs after some 3000 tracks then after a couple of minutes the library is completely empty, so I can’t play anything at all…

I am in 2.713 precisely, and having this same issue. Seems to be widespread reading some other comments here.

Yes. Exactly same issue here. I started to notice this problem at 2.712

Same here.

Inviato dal mio iPhone utilizzando Tapatalk

Good day,
Also having the same problem. Update to 2.713 did not changed anything.

Regards!
Sergey

Hello everyone I have the same problem, I thought it was my DAC that had a problem so I changed my raspberry and formatted my microsd.
After reinstalling the same problem the media doesn’t load.
I think it’s due to the latest version…

I’m going back to an earlier version…

Have a nice day

Hi,

Same here with both v2.703 and v2.713 on a RPi4.
Also noticed very high usage of RAM during mpd update and mpd logs a bad_alloc error which would be consistent with a crash due to lack of memory.
Manually killing mpd before it crashes dumps the database in the tag_cache db file thereby allowing to resume the scan rather than starting from 0.
Unfortunately, it is very hard to predict when it is going to crash and then very cumbersome to scan your entire library through a lot of scan/backup tag_cache/resume cycles :smiley:

Hope it is going to be an easy fix…
If anyone finds out I am quite curious about the cause.
In the meantime, lets go back to a previous version, chill, have a beer, and trust volumio devs to fix it :wink:

What would be the most recent and stable version to downgrade? Thanks.

For those wanting to experiment, this was caused by those 2 commits:
github.com/volumio/Volumio2/com … 8bf53d7f51
github.com/volumio/Volumio2/com … 8bf53d7f51

As it seems, those values crash mpd under some circumstances (for example on my systems it never ever crashed).

For those on 2.713:
Just go to playback options and save them. The issue should disappeear.
Please let us know.

Otherwise, feel free to manually edit mpd.conf by setting those values
max_playlist_length “81920”
max_output_buffer_size “81920”

Let us know

In my case saving the playback options didn’t work. Once I do it and go back to Rescan, it stops at some point.
EDIT: no change after editing the mpd.conf as per your suggestion. Here my log: http://logs.volumio.org/volumio/j5KboHa.html

Hey
Thanks for looking into it michelangelo.
Unfortunately I cannot test it out right now but shouldn’t we change the values back to 8192000 (8MB) as they were before the commits?

2.698 works fine in my hands
updates.volumio.org/pi/volumio/2 … pi.img.zip

Yes…
Manually changing:
max_playlist_length to “81920”
max_output_buffer_size to “81920”
In mpd.conf solved the problem for me