Sounds stop, and it seems not a moode issue

[Phil35]

Hello,

The pi3 with moodeaudio runs like a charm since two years.
Thanks to @Tim Curtis and all the team that makes it happens. You're the best / really!

I would like to share an issue I have since a few days.
env:
- HW: pi3 with 1Go of memory
- OS: Debian GNU/Linux 12 (bookworm)
- USB Key: Creative Technology, Ltd Creative BT-W4
- with moode-player=9.0.8-1moode1

suddenly the sounds stops at the wifi system, with a message on moode web interface about MPD hum (see screenshot hereafter)

looking at with command

moodeutl -t

last line is:

20240903 181736 watchdog: Error: MPD restarted (check syslog for messages)

journalctl -S "2024-09-03 18:00:00"
Sep 03 18:14:13 moodeaudio kernel: hwmon hwmon1: Undervoltage detected!
Sep 03 18:14:19 moodeaudio kernel: hwmon hwmon1: Voltage normalised
Sep 03 18:16:42 moodeaudio kernel: hwmon hwmon1: Undervoltage detected!
Sep 03 18:16:46 moodeaudio kernel: hwmon hwmon1: Voltage normalised
Sep 03 18:16:48 moodeaudio kernel: hwmon hwmon1: Undervoltage detected!
Sep 03 18:16:54 moodeaudio kernel: hwmon hwmon1: Voltage normalised
Sep 03 18:17:08 moodeaudio dbus-daemon[358]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.2314' (uid=0 pid=120766>
Sep 03 18:17:08 moodeaudio systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Sep 03 18:17:09 moodeaudio dbus-daemon[358]: [system] Successfully activated service 'org.freedesktop.timedate1'
Sep 03 18:17:09 moodeaudio systemd[1]: Started systemd-timedated.service - Time & Date Service.
Sep 03 18:17:36 moodeaudio systemd[1]: mpd.service: Main process exited, code=killed, status=11/SEGV
Sep 03 18:17:36 moodeaudio systemd[1]: mpd.service: Failed with result 'signal'.
Sep 03 18:17:36 moodeaudio systemd[1]: mpd.service: Consumed 1h 36min 14.207s CPU time.
Sep 03 18:17:36 moodeaudio systemd[1]: Starting mpd.service - Music Player Daemon...
Sep 03 18:17:37 moodeaudio mpd[1207846]: Ignoring the 'pid_file' setting in systemd mode
Sep 03 18:17:37 moodeaudio systemd[1]: Started mpd.service - Music Player Daemon.

oups I noticed:

Undervoltage detected

I search for, since the last two months:

journalctl -S "2024-07-03 18:00:00"|grep "Undervoltage detected"

one occurency on Aug 25
one occurency on Aug 26
15 occurencies on Aug 29
one occurency on Aug 30
35 occurencies on Sep 03

I think the power for the pi should changed however there is this popup and if I choose another station, the sound is ok.
see there: https://ibb.co/b6Z26Px
I checked at the same time no "Undervoltage detected"  in log.


I also found a nice script to monitor voltage, see there: https://gist.github.com/Paraphraser/17fb...86e1207c7e

./vcgencmd_power_report.sh
vcgencmd get_throttled (0x50000)
  under-voltage has occurred since last reboot
  throttling has occurred since last reboot
vcgencmd measure_volts:
     core volt=1.3188V
  sdram_c volt=1.2000V
  sdram_i volt=1.2000V
  sdram_p volt=1.2250V
Temperature: temp=53.2'C

sumup, there is two problems:
-the radio station sometimes has issue. it explains the 502 code
-the pi starts to have a power issue

Am i right?

Thanks for your advises and feedbacks
Best regards
Phil

[Nutul]

-the radio station sometimes has issue. it explains the 502 code

Every error in the 500 range is on the SERVER (that is: the "radio" station) side: you cannot do anything to fix it yourself.
Maybe overload? Maybe bandwidth restriction / constraints on their side? Memory issues?
Not yourfault. Nor moOde's.

[Falco]

Hello,

The pi3 with moodeaudio runs like a charm since two years.
Thanks to @Tim Curtis and all the team that makes it happens. You're the best / really!

I would like to share an issue I have since a few days.
env:
- HW: pi3 with 1Go of memory
- OS: Debian GNU/Linux 12 (bookworm)
- USB Key: Creative Technology, Ltd Creative BT-W4
- with moode-player=9.0.8-1moode1

suddenly the sounds stops at the wifi system, with a message on moode web interface about MPD hum (see screenshot hereafter)

looking at with command

moodeutl -t

last line is:

20240903 181736 watchdog: Error: MPD restarted (check syslog for messages)

journalctl -S "2024-09-03 18:00:00"
Sep 03 18:14:13 moodeaudio kernel: hwmon hwmon1: Undervoltage detected!
Sep 03 18:14:19 moodeaudio kernel: hwmon hwmon1: Voltage normalised
Sep 03 18:16:42 moodeaudio kernel: hwmon hwmon1: Undervoltage detected!
Sep 03 18:16:46 moodeaudio kernel: hwmon hwmon1: Voltage normalised
Sep 03 18:16:48 moodeaudio kernel: hwmon hwmon1: Undervoltage detected!
Sep 03 18:16:54 moodeaudio kernel: hwmon hwmon1: Voltage normalised
Sep 03 18:17:08 moodeaudio dbus-daemon[358]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.2314' (uid=0 pid=120766>
Sep 03 18:17:08 moodeaudio systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Sep 03 18:17:09 moodeaudio dbus-daemon[358]: [system] Successfully activated service 'org.freedesktop.timedate1'
Sep 03 18:17:09 moodeaudio systemd[1]: Started systemd-timedated.service - Time & Date Service.
Sep 03 18:17:36 moodeaudio systemd[1]: mpd.service: Main process exited, code=killed, status=11/SEGV
Sep 03 18:17:36 moodeaudio systemd[1]: mpd.service: Failed with result 'signal'.
Sep 03 18:17:36 moodeaudio systemd[1]: mpd.service: Consumed 1h 36min 14.207s CPU time.
Sep 03 18:17:36 moodeaudio systemd[1]: Starting mpd.service - Music Player Daemon...
Sep 03 18:17:37 moodeaudio mpd[1207846]: Ignoring the 'pid_file' setting in systemd mode
Sep 03 18:17:37 moodeaudio systemd[1]: Started mpd.service - Music Player Daemon.

oups I noticed:

Undervoltage detected

I search for, since the last two months:

journalctl -S "2024-07-03 18:00:00"|grep "Undervoltage detected"

one occurency on Aug 25
one occurency on Aug 26
15 occurencies on Aug 29
one occurency on Aug 30
35 occurencies on Sep 03

I think the power for the pi should changed however there is this popup and if I choose another station, the sound is ok.
see there: https://ibb.co/b6Z26Px
I checked at the same time no "Undervoltage detected"  in log.


I also found a nice script to monitor voltage, see there: https://gist.github.com/Paraphraser/17fb...86e1207c7e

./vcgencmd_power_report.sh
vcgencmd get_throttled (0x50000)
  under-voltage has occurred since last reboot
  throttling has occurred since last reboot
vcgencmd measure_volts:
     core volt=1.3188V
  sdram_c volt=1.2000V
  sdram_i volt=1.2000V
  sdram_p volt=1.2250V
Temperature: temp=53.2'C

sumup, there is two problems:
-the radio station sometimes has issue. it explains the 502 code
-the pi starts to have a power issue

Am i right?

Thanks for your advises and feedbacks
Best regards
Phil

Regarding the radio station, not sure which one it is but you might be able to find it in radio-browser.info catalogue. That site checks the lively-hood of the streams so you might be able to find a more stable stream of your radio station.

Regarding the power issue. I've had that as well with my RPi 3B+, with a IFI iPower and with an Allo Nirvana power supply. Now I just use the RPi original power supply and the issues are gone. Not sure what happens, but it did not effect the sound either so all good with the RPi PSU.... What power supply do you use? And any other peripherals connected? Another solution is to connect these via a powered USB hub. Then the usb peripheral does not draw power via de RPi.

[Phil35]

Hi,

I use an official Power for pi

today, there are these messages in log

Sep 11 19:02:54 moodeaudio systemd[1]: mpd.service: Main process exited, code=killed, status=11/SEGV
Sep 11 19:02:54 moodeaudio systemd[1]: mpd.service: Failed with result 'signal'.
Sep 11 19:02:54 moodeaudio systemd[1]: mpd.service: Consumed 1h 58min 43.937s CPU time.
Sep 11 19:02:57 moodeaudio systemd[1]: Starting mpd.service - Music Player Daemon...
Sep 11 19:02:58 moodeaudio mpd[371838]: Ignoring the 'pid_file' setting in systemd mode
Sep 11 19:02:58 moodeaudio systemd[1]: Started mpd.service - Music Player Daemon.

@Tim Curtis may be you should like some detail about "11/SEGV" ,  tell me what you should want.

[Phil35]

-the radio station sometimes has issue. it explains the 502 code

Every error in the 500 range is on the SERVER (that is: the "radio" station) side: you cannot do anything to fix it yourself.
Maybe overload? Maybe bandwidth restriction / constraints on their side? Memory issues?
Not yourfault. Nor moOde's.

Hi @Nutul
I agree, it is the conclusion I made, following some searchs on the internet.

Thanks

[Tim Curtis]

Hi,

I use an official Power for pi

today, there are these messages in log

Sep 11 19:02:54 moodeaudio systemd[1]: mpd.service: Main process exited, code=killed, status=11/SEGV
Sep 11 19:02:54 moodeaudio systemd[1]: mpd.service: Failed with result 'signal'.
Sep 11 19:02:54 moodeaudio systemd[1]: mpd.service: Consumed 1h 58min 43.937s CPU time.
Sep 11 19:02:57 moodeaudio systemd[1]: Starting mpd.service - Music Player Daemon...
Sep 11 19:02:58 moodeaudio mpd[371838]: Ignoring the 'pid_file' setting in systemd mode
Sep 11 19:02:58 moodeaudio systemd[1]: Started mpd.service - Music Player Daemon.

@Tim Curtis may be you should like some detail about "11/SEGV" ,  tell me what you should want.

Is this a fresh 908 image?

[Phil35]

Hi Tim,

Yes I had fully reinstalled it with moode 9
I wrote a post there: https://moodeaudio.org/forum/showthread.php?tid=6659
-
moode-player 9.0.8-1moode1
-

on this pi 3 the only application running is moode

Phil

[Tim Curtis]

SEGV error means the program which in this case is MPD has crashed due to a memory access issue. This suggests a hardware issue with the Pi.

[Phil35]

Thank you Tim.
Since the installation,  this error occurs two times.
Will see if the frequency increases.

$ journalctl -S "2024-06-01 00:00:00" | grep MPD | grep SEGV
Sep 03 18:17:36 moodeaudio systemd[1]: mpd.service: Main process exited, code=killed, status=11/SEGV
Sep 11 19:02:54 moodeaudio systemd[1]: mpd.service: Main process exited, code=killed, status=11/SEGV

[Tim Curtis]

Just remember that under normal circumstance a SEGV should never appear!

I would suggest trying another Pi.