Volumio 3 Buster Beta for X86

Hermann · March 13, 2021, 1:24pm

Yes 16/44.1.

gkkpch · March 13, 2021, 9:31pm

Perhaps this is a different issue after all, i’ll get back to this when the more urgent issues are resolved. Support for bytcr and bytcht devices is still wip, rt5640/51 are working out of the box with limiting to 16bit.
Somehow es8316 has still not been initialised properly, difficult without having one one here, but needs a little patience atm.

gkkpch · March 15, 2021, 4:48pm

Located and fixed for the next version

Darmur · March 21, 2021, 9:41am

Device: Chinese No-brand device, similar to MS Surface
System Version: 3.55, installed on USB
LOG → http://logs.volumio.org/volumiobuster/L4U6fiB.html
lspci

00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 7 Series Chipset Family LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04)
01:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31)

inxi -Fxxxz

System: Host: volumio-x64 Kernel: 5.10.21 x86_64 bits: 64 compiler: N/A Console: tty 0 dm: N/A
Distro: Debian GNU/Linux 10 (buster)
Machine: Type: Laptop System: Intel product: C22 v: 0.1 serial: Chassis: type: 9 v: 0.1 serial:
Mobo: Intel model: C22 v: FAB1 serial: UEFI: Phoenix v: 72S date: 09/05/2013
Battery: ID-1: BAT0 charge: 37.5 Wh condition: 38.4/59.2 Wh (65%) volts: 8.4/7.4 model: Render type: Li-ion serial: N/A
status: Charging
CPU: Topology: Dual Core model: Intel Celeron 1037U bits: 64 type: MCP arch: Ivy Bridge rev: 9 L2 cache: 2048 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 7183
Speed: 1505 MHz min/max: 800/1800 MHz Core speeds (MHz): 1: 1651 2: 1545
Graphics: Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0156
Display: tty server: X.org 1.20.4 driver: modesetting unloaded: fbdev,vesa tty: 199x27
Message: Unable to show advanced data. Required tool glxinfo missing.
Audio: Device-1: Intel 7 Series/C216 Family High Definition Audio driver: snd_hda_intel v: kernel bus ID: 00:1b.0
chip ID: 8086:1e20
Sound Server: ALSA v: k5.10.21
Network: Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: AzureWave driver: ath10k_pci v: kernel
port: efa0 bus ID: 01:00.0 chip ID: 168c:0042
IF: wlan0 state: up mac:
Drives: Local Storage: total: 176.86 GiB used: 90.23 GiB (51.0%)
ID-1: /dev/sda vendor: Kingfast model: KingFast size: 119.24 GiB speed: 6.0 Gb/s serial: rev: 41
scheme: GPT
ID-2: /dev/sdb type: USB vendor: Lexar model: USB Flash Drive size: 57.62 GiB serial: rev: 1100
scheme: GPT
Partition: ID-1: / size: 53.00 GiB used: 63.9 MiB (0.1%) fs: overlay source: ERR-102
ID-2: /boot size: 170.8 MiB used: 58.1 MiB (34.0%) fs: vfat dev: /dev/sdb1
Sensors: Missing: Required tool sensors not installed. Check --recommends
Info: Processes: 137 Uptime: 14m Memory: 3.69 GiB used: 1.23 GiB (33.3%) Init: systemd v: 241 runlevel: 5 default: 2
Compilers: gcc: N/A Shell: bash v: 5.0.3 running in: tty 0 (SSH) inxi: 3.0.32

No issues to report so far, everything seems to work as expected. Touchscreen works also out-of-the-box.

SonosKiller · March 21, 2021, 10:06pm

Ver: 3.055
Analog output

Same isues as @Robert.Hecht and @Hermann reported
But after reboot / restart basically nothing works

Log when I start a radio channel

info: CoreCommandRouter::volumioPlay

UNSET VOLATILE
info: CoreStateMachine::play index undefined
info: CoreStateMachine::setConsumeUpdateService undefined
info: CorePlayQueue::getTrack 0
info: CoreStateMachine::startPlaybackTimer
info: CorePlayQueue::getTrack 0
info: [1616363607380] ControllerWebradio::clearAddPlayTrack

Could not load plugin /usr/lib/x86_64-linux-gnu/ntfs-3g/ntfs-plugin-8000001b.so: No such file or directory
Hint /usr/lib/x86_64-linux-gnu/ntfs-3g/ntfs-plugin-8000001b.so: cannot open shared object file: No such file or directory
process exited with code null

When clicking Next

info: CoreCommandRouter::volumioNext

info: CoreStateMachine::next
info: CoreStateMachine::stop
info: CoreStateMachine::setConsumeUpdateService undefined
UNSET VOLATILE
info: CoreStateMachine::play index undefined
info: CoreStateMachine::setConsumeUpdateService undefined
info: CorePlayQueue::getTrack 2
info: CoreStateMachine::startPlaybackTimer
info: CorePlayQueue::getTrack 2
info: [1616364810762] ControllerWebradio::clearAddPlayTrack

info: CoreStateMachine::updateTrackBlock
info: CorePlayQueue::getTrackBlock
mpd.service: Start operation timed out. Terminating.
process exited with code null

gkkpch · March 22, 2021, 12:13am

please please supply volumio logs from the dev page as you agreed by joining the beta, at this stage all info helps.

Yes, this is a showkiller at the moment, we are working hard to get things working properly. Auto scanning internal disks we did not expect to see at this rate, seem to be spoiling the show. Progress is being made but nothing for testing yet.
No sound at first is also an issue, separate, but once we get the scanning deadlock solved we will have more insights.

SonosKiller · March 22, 2021, 6:53am

Okay no problem
Basically all problems as described earlier.
No scan , can’t play any radio channel , the only sound i can hear is the startup sound

I have too many players , this is the correct log file

http://logs.volumio.org/volumiobuster/9MoFiKV.html

dvo · March 22, 2021, 7:01am

sonoskiller you got a under voltage system is having problems with that…

SonosKiller · March 22, 2021, 7:05am

Yes I know , the log was from my main player , not my Buster x86 player

dvo · March 22, 2021, 7:06am

oke just checking what’s happening … in the log…

gkkpch · March 28, 2021, 9:41pm

Dear testers,
You all noticed Volumio 3 Buster Beta for x86 has come to a halt more or less.
Following the logs @Hermann, @Robert.Hecht, @SonosKiller and others have reported, we discovered a deadlock when starting up the X86 version with internal hard disk/ssd/nvme/mmcblk devices or usb sticks (other than the one booting from) connected.
Because of this, we decided to take a different approach to handling additional disks (internal and removable) and intend to implement something similar to the way you currently add a remote (NAS) share.
In order to allow people to continue testing, we will temporarily disable scanning of internal devices.
A USB stick or disk should still work, however, you do need to hit the update button in the source menu to get the data indexed.
Once we have implemented the targeted solution, these restrictions will become obsolete.
Hope to release this temporary solution, which was already tested with @Robert.Hecht, sometime this week.

Hermann · April 4, 2021, 8:00am

Any news on temporary solution implementation?

gkkpch · April 4, 2021, 8:15am

yes, it will be published the next few days, it only needs to be verified against a PI build and then we should be good to go. It will take a couple of days because of Easter.

SonosKiller · April 10, 2021, 7:11am

on ver 3.057
Now basically everything works
Sometimes feels a bit slow and unresponsive, spontaneous “running wheels”, breaks in the stream both with webradio and tracks from the Nas, but i’m not sure to blame Volumio for all of that ,network loads from other computers and a bit weak hardware in the test rigg may cause some of the disturbance

Robert.Hecht · April 10, 2021, 10:57am

Hi them all,

my tests of the 3,057 have not been successful.

The same problems we saw at the beginning of the beta phase are still present here. The first startup after flash or after factory reset ends up in a unusable state where no playback is possible and the scan of attached volumes does not work.

1st boot after flash:

no playback is possible (webradio, tidal, local)
music lib is not being built up, scan does not work
the startup assistent is interrupted in between
http://logs.volumio.org/volumiobuster/vgSxrdR.html

volumio@volumio:~$ systemctl status mpd.service
● mpd.service - Music Player Daemon
   Loaded: loaded (/lib/systemd/system/mpd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2021-04-09 23:01:24 UTC; 25s ago
     Docs: man:mpd(1)
           man:mpd.conf(5)
 Main PID: 692 (code=exited, status=1/FAILURE)

Apr 09 23:01:21 volumio systemd[1]: Starting Music Player Daemon...
Apr 09 23:01:24 volumio mpd[692]: exception: failed to open log file "/var/log/mpd/mpd.log" (config line 39): No such file or directory
Apr 09 23:01:24 volumio systemd[1]: mpd.service: Main process exited, code=exited, status=1/FAILURE
Apr 09 23:01:24 volumio systemd[1]: mpd.service: Failed with result 'exit-code'.
Apr 09 23:01:24 volumio systemd[1]: Failed to start Music Player Daemon.
volumio@volumio:~$ systemctl status mpd.service
● mpd.service - Music Player Daemon
   Loaded: loaded (/lib/systemd/system/mpd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2021-04-09 23:01:54 UTC; 611ms ago
     Docs: man:mpd(1)
           man:mpd.conf(5)
  Process: 1796 ExecStartPre=/usr/bin/touch /var/log/mpd.log (code=exited, status=0/SUCCESS)
  Process: 1797 ExecStartPre=/bin/chown volumio /var/log/mpd.log (code=exited, status=0/SUCCESS)
  Process: 1798 ExecStart=/usr/bin/mpd --no-daemon (code=exited, status=1/FAILURE)
 Main PID: 1798 (code=exited, status=1/FAILURE)

Apr 09 23:01:54 volumio mpd[1798]: exception: failed to open log file "/var/log/mpd/mpd.log" (config line 39): No such file or directory
Apr 09 23:01:54 volumio systemd[1]: mpd.service: Main process exited, code=exited, status=1/FAILURE
Apr 09 23:01:54 volumio systemd[1]: mpd.service: Failed with result 'exit-code'.
Apr 09 23:01:54 volumio systemd[1]: Failed to start Music Player Daemon.
Apr 09 23:01:54 volumio systemd[1]: mpd.service: Start request repeated too quickly.
Apr 09 23:01:54 volumio systemd[1]: mpd.service: Failed with result 'exit-code'.
Apr 09 23:01:54 volumio systemd[1]: Failed to start Music Player Daemon.
Apr 09 23:01:54 volumio systemd[1]: mpd.service: Start request repeated too quickly.
Apr 09 23:01:54 volumio systemd[1]: mpd.service: Failed with result 'exit-code'.
Apr 09 23:01:54 volumio systemd[1]: Failed to start Music Player Daemon.
volumio@volumio:~$ systemctl status mpd.service
● mpd.service - Music Player Daemon
   Loaded: loaded (/lib/systemd/system/mpd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2021-04-09 23:01:54 UTC; 3s ago
     Docs: man:mpd(1)
           man:mpd.conf(5)
  Process: 1796 ExecStartPre=/usr/bin/touch /var/log/mpd.log (code=exited, status=0/SUCCESS)
  Process: 1797 ExecStartPre=/bin/chown volumio /var/log/mpd.log (code=exited, status=0/SUCCESS)
  Process: 1798 ExecStart=/usr/bin/mpd --no-daemon (code=exited, status=1/FAILURE)
 Main PID: 1798 (code=exited, status=1/FAILURE)

Apr 09 23:01:54 volumio mpd[1798]: exception: failed to open log file "/var/log/mpd/mpd.log" (config line 39): No such file or directory
Apr 09 23:01:54 volumio systemd[1]: mpd.service: Main process exited, code=exited, status=1/FAILURE
Apr 09 23:01:54 volumio systemd[1]: mpd.service: Failed with result 'exit-code'.
Apr 09 23:01:54 volumio systemd[1]: Failed to start Music Player Daemon.
Apr 09 23:01:54 volumio systemd[1]: mpd.service: Start request repeated too quickly.
Apr 09 23:01:54 volumio systemd[1]: mpd.service: Failed with result 'exit-code'.
Apr 09 23:01:54 volumio systemd[1]: Failed to start Music Player Daemon.
Apr 09 23:01:54 volumio systemd[1]: mpd.service: Start request repeated too quickly.
Apr 09 23:01:54 volumio systemd[1]: mpd.service: Failed with result 'exit-code'.
Apr 09 23:01:54 volumio systemd[1]: Failed to start Music Player Daemon.
volumio@volumio:~$ systemctl status mpd.service
● mpd.service - Music Player Daemon
   Loaded: loaded (/lib/systemd/system/mpd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2021-04-09 23:01:54 UTC; 14s ago
     Docs: man:mpd(1)
           man:mpd.conf(5)
  Process: 1796 ExecStartPre=/usr/bin/touch /var/log/mpd.log (code=exited, status=0/SUCCESS)
  Process: 1797 ExecStartPre=/bin/chown volumio /var/log/mpd.log (code=exited, status=0/SUCCESS)
  Process: 1798 ExecStart=/usr/bin/mpd --no-daemon (code=exited, status=1/FAILURE)
 Main PID: 1798 (code=exited, status=1/FAILURE)

Apr 09 23:01:54 volumio mpd[1798]: exception: failed to open log file "/var/log/mpd/mpd.log" (config line 39): No such file or directory
Apr 09 23:01:54 volumio systemd[1]: mpd.service: Main process exited, code=exited, status=1/FAILURE
Apr 09 23:01:54 volumio systemd[1]: mpd.service: Failed with result 'exit-code'.
Apr 09 23:01:54 volumio systemd[1]: Failed to start Music Player Daemon.
Apr 09 23:01:54 volumio systemd[1]: mpd.service: Start request repeated too quickly.
Apr 09 23:01:54 volumio systemd[1]: mpd.service: Failed with result 'exit-code'.
Apr 09 23:01:54 volumio systemd[1]: Failed to start Music Player Daemon.
Apr 09 23:01:54 volumio systemd[1]: mpd.service: Start request repeated too quickly.
Apr 09 23:01:54 volumio systemd[1]: mpd.service: Failed with result 'exit-code'.
Apr 09 23:01:54 volumio systemd[1]: Failed to start Music Player Daemon.
volumio@volumio:~$ systemctl status mpd.service
● mpd.service - Music Player Daemon
   Loaded: loaded (/lib/systemd/system/mpd.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-04-09 23:02:24 UTC; 8s ago
     Docs: man:mpd(1)
           man:mpd.conf(5)
  Process: 2467 ExecStartPre=/usr/bin/touch /var/log/mpd.log (code=exited, status=0/SUCCESS)
  Process: 2473 ExecStartPre=/bin/chown volumio /var/log/mpd.log (code=exited, status=0/SUCCESS)
 Main PID: 2481 (mpd)
   Memory: 29.5M
   CGroup: /system.slice/mpd.service
           └─2481 /usr/bin/mpd --no-daemon

Apr 09 23:02:23 smx systemd[1]: Starting Music Player Daemon...
Apr 09 23:02:24 smx mpd[2481]: Apr 09 23:02 : exception: bind to '0.0.0.0:6600' failed (continuing anyway, because binding to '[::]:6600' succeeded): Failed to bind socket: Address already in use
Apr 09 23:02:24 smx mpd[2481]: Apr 09 23:02 : exception: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg
Apr 09 23:02:24 smx mpd[2481]: Apr 09 23:02 : exception: Database corrupted
Apr 09 23:02:24 smx systemd[1]: Started Music Player Daemon.
volumio@volumio:~$ systemctl status mpd.service
● mpd.service - Music Player Daemon
   Loaded: loaded (/lib/systemd/system/mpd.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-04-09 23:02:24 UTC; 19s ago
     Docs: man:mpd(1)
           man:mpd.conf(5)
  Process: 2467 ExecStartPre=/usr/bin/touch /var/log/mpd.log (code=exited, status=0/SUCCESS)
  Process: 2473 ExecStartPre=/bin/chown volumio /var/log/mpd.log (code=exited, status=0/SUCCESS)
 Main PID: 2481 (mpd)
   Memory: 29.5M
   CGroup: /system.slice/mpd.service
           └─2481 /usr/bin/mpd --no-daemon

Apr 09 23:02:23 smx systemd[1]: Starting Music Player Daemon...
Apr 09 23:02:24 smx mpd[2481]: Apr 09 23:02 : exception: bind to '0.0.0.0:6600' failed (continuing anyway, because binding to '[::]:6600' succeeded): Failed to bind socket: Address already in use
Apr 09 23:02:24 smx mpd[2481]: Apr 09 23:02 : exception: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg
Apr 09 23:02:24 smx mpd[2481]: Apr 09 23:02 : exception: Database corrupted
Apr 09 23:02:24 smx systemd[1]: Started Music Player Daemon.
volumio@volumio:~$ systemctl status mpd.service
● mpd.service - Music Player Daemon
   Loaded: loaded (/lib/systemd/system/mpd.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-04-09 23:02:54 UTC; 37s ago
     Docs: man:mpd(1)
           man:mpd.conf(5)
  Process: 2900 ExecStartPre=/usr/bin/touch /var/log/mpd.log (code=exited, status=0/SUCCESS)
  Process: 2904 ExecStartPre=/bin/chown volumio /var/log/mpd.log (code=exited, status=0/SUCCESS)
 Main PID: 2911 (mpd)
   Memory: 8.6M
   CGroup: /system.slice/mpd.service
           └─2911 /usr/bin/mpd --no-daemon

Apr 09 23:02:51 smx systemd[1]: Starting Music Player Daemon...
Apr 09 23:02:52 smx mpd[2911]: Apr 09 23:02 : exception: bind to '0.0.0.0:6600' failed (continuing anyway, because binding to '[::]:6600' succeeded): Failed to bind socket: Address already in use
Apr 09 23:02:52 smx mpd[2911]: Apr 09 23:02 : exception: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg
Apr 09 23:02:54 smx systemd[1]: Started Music Player Daemon.
volumio@volumio:~$ systemctl status mpd.service
● mpd.service - Music Player Daemon
   Loaded: loaded (/lib/systemd/system/mpd.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-04-09 23:04:40 UTC; 954ms ago
     Docs: man:mpd(1)
           man:mpd.conf(5)
  Process: 4035 ExecStartPre=/usr/bin/touch /var/log/mpd.log (code=exited, status=0/SUCCESS)
  Process: 4049 ExecStartPre=/bin/chown volumio /var/log/mpd.log (code=exited, status=0/SUCCESS)
 Main PID: 4058 (mpd)
   Memory: 8.6M
   CGroup: /system.slice/mpd.service
           └─4058 /usr/bin/mpd --no-daemon

Apr 09 23:04:37 smx systemd[1]: Starting Music Player Daemon...
Apr 09 23:04:40 smx mpd[4058]: Apr 09 23:04 : exception: bind to '0.0.0.0:6600' failed (continuing anyway, because binding to '[::]:6600' succeeded): Failed to bind socket: Address already in use
Apr 09 23:04:40 smx mpd[4058]: Apr 09 23:04 : exception: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg
Apr 09 23:04:40 smx systemd[1]: Started Music Player Daemon.

after a second reboot everything works fine:
http://logs.volumio.org/volumiobuster/eAHb5Bt.html

Volumio Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Welcome to Volumio for x86_64 (5.10.28 x86_64)
volumio@smx:~$ systemctl status mpd.service
● mpd.service - Music Player Daemon
   Loaded: loaded (/lib/systemd/system/mpd.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-04-09 23:14:19 UTC; 51s ago
     Docs: man:mpd(1)
           man:mpd.conf(5)
 Main PID: 1375 (mpd)
   Memory: 8.9M
   CGroup: /system.slice/mpd.service
           └─1375 /usr/bin/mpd --no-daemon

Apr 09 23:14:19 smx systemd[1]: Starting Music Player Daemon...
Apr 09 23:14:19 smx mpd[1375]: Apr 09 23:14 : exception: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg
Apr 09 23:14:19 smx systemd[1]: Started Music Player Daemon.
volumio@smx:~$

This is the case independent whether a USB medium with music data is present or not.

The solution that gkkpch had implemented in between did work.
I’m sorry to say that the 3.057 does not work.

My x86 config: see my first posting in this topic.

Cheers,
Robert

volumio · April 10, 2021, 1:20pm

Hi Robert, we already identified the issue. If you save playback options it will work.
Can you please test that and let us know?

Robert.Hecht · April 10, 2021, 2:03pm

Hi Michelangelo,
sorry to say that - also saving the playback options to an other output device does not heal the situation. Playback is still not working… (Version 3.057 after 1st boot) I tried several save procedures (analog, HDMI, SPDIF)

Volumiobuster-3.057-2021-04-09-x86_amd64.img after saving “playback options” several times
http://logs.volumio.org/volumiobuster/WK5OEMW.html

Cheers,
Robert

Robert.Hecht · April 10, 2021, 2:40pm

Volumiobuster-3.058-2021-04-10-x86_amd64.img :

after first startup: no playback is possible (tidal, webradio), no scanning of the lib (local USB Stick with music data is not scanned).
The startup sound is hearable (SPDIF) !
The first config assistent is not interrupted !
Several changes in the “playback options” did not help the playback issue.

Welcome to Volumio for x86_64 (5.10.28 x86_64)
volumio@volumio:~$ systemctl status mpd.service
● mpd.service - Music Player Daemon
   Loaded: loaded (/lib/systemd/system/mpd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2021-04-10 14:27:03 UTC; 35s ago
     Docs: man:mpd(1)
           man:mpd.conf(5)
 Main PID: 693 (code=exited, status=1/FAILURE)

Apr 10 14:26:58 volumio systemd[1]: Starting Music Player Daemon...
Apr 10 14:27:02 volumio mpd[693]: exception: failed to open log file "/var/log/mpd/mpd.log" (config line 39): No such file or directory
Apr 10 14:27:03 volumio systemd[1]: mpd.service: Main process exited, code=exited, status=1/FAILURE
Apr 10 14:27:03 volumio systemd[1]: mpd.service: Failed with result 'exit-code'.
Apr 10 14:27:03 volumio systemd[1]: Failed to start Music Player Daemon.
volumio@volumio:~$ systemctl status mpd.service
● mpd.service - Music Player Daemon
   Loaded: loaded (/lib/systemd/system/mpd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2021-04-10 14:27:46 UTC; 4s ago
     Docs: man:mpd(1)
           man:mpd.conf(5)
  Process: 1800 ExecStartPre=/usr/bin/touch /var/log/mpd.log (code=exited, status=0/SUCCESS)
  Process: 1811 ExecStartPre=/bin/chown volumio /var/log/mpd.log (code=exited, status=0/SUCCESS)
  Process: 1820 ExecStart=/usr/bin/mpd --no-daemon (code=exited, status=1/FAILURE)
 Main PID: 1820 (code=exited, status=1/FAILURE)

Apr 10 14:27:46 volumio mpd[1820]: exception: failed to open log file "/var/log/mpd/mpd.log" (config line 39): No such file or directory
Apr 10 14:27:46 volumio systemd[1]: mpd.service: Main process exited, code=exited, status=1/FAILURE
Apr 10 14:27:46 volumio systemd[1]: mpd.service: Failed with result 'exit-code'.
Apr 10 14:27:46 volumio systemd[1]: Failed to start Music Player Daemon.
Apr 10 14:27:46 volumio systemd[1]: mpd.service: Start request repeated too quickly.
Apr 10 14:27:46 volumio systemd[1]: mpd.service: Failed with result 'exit-code'.
Apr 10 14:27:46 volumio systemd[1]: Failed to start Music Player Daemon.
Apr 10 14:27:49 volumio systemd[1]: mpd.service: Start request repeated too quickly.
Apr 10 14:27:49 volumio systemd[1]: mpd.service: Failed with result 'exit-code'.
Apr 10 14:27:49 volumio systemd[1]: Failed to start Music Player Daemon.
volumio@volumio:~$ systemctl status mpd.service
● mpd.service - Music Player Daemon
   Loaded: loaded (/lib/systemd/system/mpd.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2021-04-10 14:29:57 UTC; 43s ago
     Docs: man:mpd(1)
           man:mpd.conf(5)
  Process: 3626 ExecStartPre=/usr/bin/touch /var/log/mpd.log (code=exited, status=0/SUCCESS)
  Process: 3634 ExecStartPre=/bin/chown volumio /var/log/mpd.log (code=exited, status=0/SUCCESS)
 Main PID: 3642 (mpd)
   Memory: 8.6M
   CGroup: /system.slice/mpd.service
           └─3642 /usr/bin/mpd --no-daemon

Apr 10 14:29:55 smx systemd[1]: Starting Music Player Daemon...
Apr 10 14:29:57 smx mpd[3642]: Apr 10 14:29 : exception: bind to '0.0.0.0:6600' failed (continuing anyway, because binding to '[::]:6600' succeeded): Failed to bind socket: Address already in use
Apr 10 14:29:57 smx mpd[3642]: Apr 10 14:29 : exception: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg
Apr 10 14:29:57 smx systemd[1]: Started Music Player Daemon.

This could be the root cause:
exception: bind to '0.0.0.0:6600' failed (continuing anyway, because binding to '[::]:6600' succeeded): Failed to bind socket: Address already in use

After a reboot, playback of webradio, Tidal, local files works well, local media volumes are scanned, the lib is available.

volumio@smx:~$ systemctl status mpd.service
● mpd.service - Music Player Daemon
   Loaded: loaded (/lib/systemd/system/mpd.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2021-04-10 14:36:48 UTC; 43s ago
     Docs: man:mpd(1)
           man:mpd.conf(5)
 Main PID: 1937 (mpd)
   Memory: 8.6M
   CGroup: /system.slice/mpd.service
           └─1937 /usr/bin/mpd --no-daemon

Apr 10 14:36:47 smx systemd[1]: Starting Music Player Daemon...
Apr 10 14:36:48 smx mpd[1937]: Apr 10 14:36 : exception: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg
Apr 10 14:36:48 smx systemd[1]: Started Music Player Daemon.

Log after factory reset - again: no playback possible, no scan, no lib.
http://logs.volumio.org/volumiobuster/FjyU17v.html

after reboot - playback is working:
http://logs.volumio.org/volumiobuster/nP4wxOs.html

Cheers,
Robert

ashthespy · April 10, 2021, 4:08pm

Robert.Hecht:

● mpd.service - Music Player Daemon
   Loaded: loaded (/lib/systemd/system/mpd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2021-04-10 14:27:03 UTC; 35s ago
     Docs: man:mpd(1)
           man:mpd.conf(5)
 Main PID: 693 (code=exited, status=1/FAILURE)

We had a brief discussion about this - it should be sufficient to disable mpd.service during build, and have the Volumio main MPD plug-in start the service, once the correct configuration files are written.

@gkkpch, @volumio could someone test this? Could be as simple as adding to finalize.sh

systemctl disable mpd.service

Robert.Hecht:

Apr 10 14:36:47 smx systemd[1]: Starting Music Player Daemon...
Apr 10 14:36:48 smx mpd[1937]: Apr 10 14:36 : exception: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg
Apr 10 14:36:48 smx systemd[1]: Started Music Player Daemon.

This is just noise, but it it is because Pull in the latest MPD by timothyjward · Pull Request #494 · volumio/Build · GitHub requires alterations to
Volumio2/app/plugins/music_service/mpd/mpd.conf.tmpl at master · volumio/Volumio2 · GitHub for the new version…

gkkpch · April 10, 2021, 4:16pm

Yeah, the missing plugin error does not bother us.
But, as soon as MPD starts it will crash because of an invalid log location in the default mpd.conf.
This leads to a deadlock as afterwards mpd sockets appear to be blocked (no connections possible)
Today’s fix with creating an mpd.log at systemstart did not work