Volumio server is craching and I must reboot it

Help and Support
#1

Hi

The volumio server is crashing very often and the only way I found to fix the problem is to either restart the Pi box or doing a “sudo reboot”

Here is the log file I generated after a reboot: http://logs.volumio.org/volumio/lR9m0cm.html

Volumio version: “2.917”
HW: Raspberry Pi 3 Model B Plus Rev 1.3
OS: “Raspbian GNU/Linux 8 (jessie)”

Could the problem be related to what the journal reports hereafter

volumio@volumio:~$ sudo journalctl -p 3
-- Logs begin at Sat 2021-11-20 10:41:07 UTC, end at Sat 2021-11-20 10:54:33 UTC. --
Nov 20 10:41:08 volumio kernel: snd-allo-boss-dac soc:sound: snd_soc_register_card() failed: -517
Nov 20 10:41:08 volumio kernel: snd-allo-boss-dac soc:sound: snd_soc_register_card() failed: -517
Nov 20 10:41:08 volumio kernel: snd-allo-boss-dac soc:sound: snd_soc_register_card() failed: -517
Nov 20 10:41:08 volumio kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
Nov 20 10:41:08 volumio kernel: snd-allo-boss-dac soc:sound: snd_soc_register_card() failed: -517
Nov 20 10:41:08 volumio kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
Nov 20 10:41:08 volumio kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar  2 2020 23:30:41 version 7.45.202 (r724630 CY) FWID 01-72f6ece2
Nov 20 10:41:09 volumio kernel: Under-voltage detected! (0x00050005)
Nov 20 10:41:11 volumio kernel: brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled
Nov 20 10:41:13 volumio systemd-udevd[778]: failed to execute '/usr/bin/hciconfig' '/usr/bin/hciconfig hci0 up': No such file or directory
Nov 20 10:41:17 volumio ntpd_intres[835]: host name not found: 0.debian.pool.ntp.org
Nov 20 10:41:17 volumio ntpd_intres[835]: host name not found: 1.debian.pool.ntp.org
Nov 20 10:41:17 volumio ntpd_intres[835]: host name not found: 2.debian.pool.ntp.org
Nov 20 10:41:17 volumio ntpd_intres[835]: host name not found: 3.debian.pool.ntp.org
Nov 20 10:41:19 volumio winbindd[882]: [2021/11/20 10:41:19.345611,  0] ../lib/util/debug.c:603(reopen_logs_internal)
Nov 20 10:41:19 volumio winbindd[882]: Unable to open new log file '/var/log/samba/log.winbindd': No such file or directory
Nov 20 10:41:19 volumio winbindd[882]: [2021/11/20 10:41:19.347309,  0] ../lib/util/debug.c:603(reopen_logs_internal)
Nov 20 10:41:19 volumio winbindd[882]: Unable to open new log file '/var/log/samba/log.winbindd': No such file or directory
Nov 20 10:41:19 volumio winbindd[891]: [2021/11/20 10:41:19.414095,  0] ../source3/winbindd/winbindd_cache.c:3235(initialize_winbindd_cache)
Nov 20 10:41:19 volumio winbindd[891]: initialize_winbindd_cache: clearing cache and re-creating with version number 2
Nov 20 10:41:19 volumio nmbd[885]: [2021/11/20 10:41:19.425773,  0] ../lib/util/debug.c:603(reopen_logs_internal)
Nov 20 10:41:19 volumio nmbd[885]: Unable to open new log file '/var/log/samba/log.nmbd': No such file or directory
Nov 20 10:41:19 volumio nmbd[885]: [2021/11/20 10:41:19.428716,  0] ../lib/util/debug.c:603(reopen_logs_internal)
Nov 20 10:41:19 volumio nmbd[885]: Unable to open new log file '/var/log/samba/log.nmbd': No such file or directory
Nov 20 10:41:19 volumio nmbd[894]: [2021/11/20 10:41:19.434394,  0] ../source3/nmbd/asyncdns.c:157(start_async_dns)
Nov 20 10:41:19 volumio nmbd[894]: started asyncdns process 895
Nov 20 10:41:19 volumio nmbd[894]: [2021/11/20 10:41:19.439800,  0] ../lib/util/become_daemon.c:135(daemon_status)
Nov 20 10:41:19 volumio nmbd[894]: STATUS=daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...NOTE: NetBIOS name resolutio
Nov 20 10:41:19 volumio winbindd[891]: [2021/11/20 10:41:19.468574,  0] ../lib/util/become_daemon.c:124(daemon_ready)
Nov 20 10:41:19 volumio winbindd[891]: STATUS=daemon 'winbindd' finished starting up and ready to serve connections

Cheers

Charles

#2

Curious to know what mpd_radio_fix.sh does? :slight_smile:

#3

What is the purpose to execute such a file “mpd_radio_fix.sh” ? Where can I find it ?

#4 
`WARNING!!! Some remote endpoints cannot be reached!
Failing endpoints: 
https://oauth-performer.dfs.volumio.org, 5235 ms
https://browsing-performer.dfs.volumio.org, 5235 ms
https://radio-directory.firebaseapp.com, 5235 ms`
#5

Please send the log when it crashes and you have to reboot. This way we understand why you have to reboot

#6

AFAIK it’s not part of the standard Volumio install - and it seems to be running on your system. Can you share it’s contents?

cat /home/volumio/mpd_radio_fix.sh

EDIT: Could it be this – Decoder is to slow - #16 by throwawayuser

#7

As I cannot ssh anymore now to the PI volumio, box I will reboot it and will try to share the previous log. Is the old log still available ?

#8

I dont see any message from mpd that decoder is too slow
here is the output of the command

cat /home/volumio/mpd_radio_fix.sh
#!/bin/bash

while :
do
  OUT=$(tail -n 1 /var/log/mpd.log)

if [[ $OUT == *"Decoder is too slow"* ]]; then

  /usr/bin/mpc stop
fi

  sleep 1
done
#9

Audio stopped suddenly. Here is a new log: http://logs.volumio.org/volumio/JVj5iMV.html

#10

Why do you have this?
You do realise it’s just stopping mpd?
I would just move to Volumio 3.x release.

#11

Why do you have this?

Why do you mean here by this ?

You do realise it’s just stopping mpd?

This is perhaps due to another issue which finally stops volumio.
The mpd process is still running

root 618 1 0 08:42 ? 00:00:18 /bin/bash /home/volumio/mpd_radio_fix.sh
mpd 674 1 1 08:42 ? 00:01:47 /usr/bin/mpd --no-daemon
[/quote]

#12

Please can you be careful with quotes … your last post doesn’t make sense.

You might not think that “mpd_radio_fix.sh” isn’t causing your problems, but surely it would be sensible to remove or disable the script to test. You have introduced a non-standard script into Volumio, which makes debugging problematical. Try:

sudo systemctl stop mpd_radio_fix
sudo systemctl disable mpd_radio_fix

to stop it temporarily, and see if has any effect.

Do you see your problem with more than one source? Here mpd complains a lot about streamingp.shoutcast.com.

#13

I disabled the service you mentioned. Will check if volumio is working now :wink:

#14

FYI: For the moment I only use volumio with streaming radios as source

Question: As the pi + volumio is connected to the net, which such mpd - streamingp.shoutcast.com occur ?

#15

Streaming of a web radio stopped again

http://logs.volumio.org/volumio/rjvlQNj.html

#16

Are you sure you are running a stock Volumio image?
Perhaps, list out all the mods you have carried out aswell so we can trouble shoot better :wink:
Or better yet, use a fresh install and confirm if your issues come from the installed mods?

#17

OK, so we are seeing the “Nov 22 07:06 : player: Decoder is too slow; playing silence to avoid xrun” errors, which is why you were running the mpd_radio_fix.service presumably … but this doesn’t sort the problem. I don’t know the cause of this error … hopefully some one else will chip in here.

You’re still using the same source though. Can you try another radio stream (from a different provider) please?

Edit: As @asthespy says, a fresh install with no modifications would be useful.

Edit 2: I’ve read the whole of the original thread that sparked your “fix” now, and it is obviously a strange one that is difficult to reproduce on every system. Also, the number of people affected seems relatively small … I wasn’t aware of it as a problem at all from forum posts. One suggestion, which no one seemed to try, was to use a later version of MPD … have a go with Volumio3, and see how you get on with that (with your source for which you are seeing the problem).

#18

I have installed on Pi an official volumio image 1 year and did regularly volumio upgrades. I recently upgraded using the Volumio UI the version to 2.917

#19

The only thing I did is to configure the list of the web radio using from my macbook such a sshpass command

sshpass -p "xxxx" scp radio-playlist/my-web-radio volumio@192.168.1.100:/data/favourites/
sshpass -p "xxxx" scp radio-playlist/radio-favourites volumio@192.168.1.100:/data/favourites/
1 Like
#20

Are you sure? You seem to have a lot of funky stuff going on under your mounts - perhaps you tried installing docker or something?