I run volumio on two Raspberry Pis – a Pi4 with a HifiBerry Dac Plus Pro and a Pi3 with a HifiBerry Amp2. I upgraded both to volumio 2.17 yesterday
(major improvements – thank you very much). The Pi4 is fine, but the Pi3 has a severe problem. It’s not clear that the upgrade CAUSED the problem, but it did emerge following the upgrade.
The problem is with MPD. My main music library is an NFS share. It is successfully mounted and the permissions are fine (the same filesystem is shared with the Pi4 which has no problem scanning ). But MPD is failing because of a Max connections reached' problem and mpc from the command line reports Connection closed by server’. Here is the relevant part of /var/log/mpd.log:
Feb 26 09:54 : zeroconf: No global port, disabling zeroconf
Feb 26 09:57 : client: [0] opened from local
Feb 26 09:57 : exception: No such directory
Feb 26 09:57 : exception: std::bad_alloc
Feb 26 09:57 : exception: std::bad_alloc
Feb 26 09:57 : zeroconf: No global port, disabling zeroconf
Feb 26 09:57 : client: [0] opened from 127.0.0.1:38166
Feb 26 09:57 : client: [1] opened from local
Feb 26 09:58 : exception: std::bad_alloc
Feb 26 09:58 : exception: std::bad_alloc
Feb 26 09:58 : zeroconf: No global port, disabling zeroconf
Feb 26 09:58 : client: [0] opened from 127.0.0.1:38378
Feb 26 09:58 : client: [1] opened from local
Feb 26 09:58 : client: [2] opened from local
Feb 26 09:58 : client: [3] opened from local
Feb 26 09:58 : client: [4] opened from local
Feb 26 09:58 : client: [5] opened from local
Feb 26 09:58 : client: [6] opened from local
Feb 26 09:58 : client: [7] opened from local
Feb 26 09:58 : client: [8] opened from local
Feb 26 09:58 : client: [9] opened from local
Feb 26 09:58 : client: [10] opened from local
Feb 26 09:58 : client: [11] opened from local
Feb 26 09:58 : client: [12] opened from local
Feb 26 09:58 : client: [13] opened from local
Feb 26 09:58 : client: [14] opened from local
Feb 26 09:58 : client: [15] opened from local
Feb 26 09:58 : client: [16] opened from local
Feb 26 09:58 : client: [17] opened from local
Feb 26 09:59 : client: [18] opened from local
Feb 26 09:59 : client: [19] opened from local
Feb 26 09:59 : client: Max connections reached
Feb 26 09:59 : client: Max connections reached
Feb 26 09:59 : client: Max connections reached
(repeated many times)
The std::bad_alloc exception ' line is not reassuring. (The exception: No such directory’ entry seems harmless since it also appears in the log for the Pi4 which runs problem-free.)
I’d be very grateful for any advice or pointers. Thanks for all your work,
Jim