Hi,
I had Mopidy with pirate audio on a Pi 4 running sweetly until my SD card failed.
I started from scratch with a new card and did the same as my first install using the Pirate Audio install.sh
However Mopidy fails to start and systemctl status give the output below.
Any thoughts on what has gone wrong?
Tom
pi@mopidy:~ $ sudo systemctl status mopidy
● mopidy.service - Mopidy music server
Loaded: loaded (/lib/systemd/system/mopidy.service; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Wed 2020-11-11 16:36:52 GMT; 3min 39s ago
Process: 581 ExecStartPre=/bin/mkdir -p /var/cache/mopidy (code=exited, status=0/SUCCESS)
Process: 584 ExecStartPre=/bin/chown mopidy:audio /var/cache/mopidy (code=exited, status=0/SUCCESS)
Process: 591 ExecStart=/usr/bin/mopidy --config /usr/share/mopidy/conf.d:/etc/mopidy/mopidy.conf (code=killed, signal=SEGV)
Main PID: 591 (code=killed, signal=SEGV)
Nov 11 16:36:47 mopidy systemd[1]: Starting Mopidy music server…
Nov 11 16:36:47 mopidy systemd[1]: Started Mopidy music server.
Nov 11 16:36:52 mopidy systemd[1]: mopidy.service: Main process exited, code=killed, status=11/SEGV
Nov 11 16:36:52 mopidy systemd[1]: mopidy.service: Failed with result ‘signal’.
Not sure if this helps but when I run
pi@mopidy:/etc/mopidy $ sudo mopidyctl --config /etc/mopidy/mopidy.conf -vvv
I get the following
Running “/usr/bin/mopidy --config /usr/share/mopidy/conf.d:/etc/mopidy/mopidy.conf --config /etc/mopidy/mopidy.conf -vvv” as user mopidy
Segmentation fault
I tried sudo apt-get reinstall mopidy and it reinstalled cleanly but still the same fault.
I also re-ran the install.sh but no change to the problem
Tom
Hi Tom,
Can you try disabling all the extensions by setting their enabled = false in your /etc/mopidy/mopidy.conf. I would start with the pidi extension.
[pidi]
enabled = false
Then also set your logging to debug (3) or even trace (4) verbosity with:
[logging]
verbosity = 3
Then restart Mopidy service the normal way using sudo systemctl restart mopidy and view the log with sudo journalctl -u mopidy -b
Also if you could provide the output of sudo mopidyctl deps that’d help.
Hi,
Thanks for helping.
My /etc/mopidy/mopidy config is as follows:
pi@mopidy:/etc/mopidy $ sudo cat mopidy.conf
[raspberry-gpio]
enabled = false
bcm5 = play_pause,active_low,250
bcm6 = volume_down,active_low,250
bcm16 = next,active_low,250
bcm20 = volume_up,active_low,250
bcm24 = volume_up,active_low,250
[file]
enabled = true
media_dirs = /home/pi/Music
show_dotfiles = false
excluded_file_extensions =
.directory
.html
.jpeg
.jpg
.log
.nfo
.pdf
.png
.txt
.zip
follow_symlinks = false
metadata_timeout = 1000
[pidi]
enabled = false
display = st7789
rotation = 90
[mpd]
hostname = 0.0.0.0
[http]
hostname = 0.0.0.0
[audio]
mixer_volume = 40
output = alsasink device=hw:sndrpihifiberry
[spotify]
enabled = false
username =
password =
client_id =
client_secret =
[logging]
verbosity = 3
I have set everything, other than files to false.
when I run
sudo mopidyctl deps, I get
Running “/usr/bin/mopidy --config /usr/share/mopidy/conf.d:/etc/mopidy/mopidy.conf deps” as user mopidy
Segmentation fault
It still fails to start.
Tom
Starting Mopidy results in the following:
pi@mopidy:/etc/mopidy $ sudo systemctl restart mopidy
pi@mopidy:/etc/mopidy $ sudo journalctl -u mopidy -b
– Logs begin at Wed 2020-11-11 16:36:31 GMT, end at Wed 2020-11-11 18:26:07 GMT. –
Nov 11 16:36:47 mopidy systemd[1]: Starting Mopidy music server…
Nov 11 16:36:47 mopidy systemd[1]: Started Mopidy music server.
Nov 11 16:36:52 mopidy systemd[1]: mopidy.service: Main process exited, code=killed, status=11/SEGV
Nov 11 16:36:52 mopidy systemd[1]: mopidy.service: Failed with result ‘signal’.
Nov 11 16:57:34 mopidy systemd[1]: Starting Mopidy music server…
Nov 11 16:57:34 mopidy systemd[1]: Started Mopidy music server.
Nov 11 16:57:35 mopidy systemd[1]: mopidy.service: Main process exited, code=killed, status=11/SEGV
Nov 11 16:57:35 mopidy systemd[1]: mopidy.service: Failed with result ‘signal’.
Nov 11 18:08:38 mopidy systemd[1]: Starting Mopidy music server…
Nov 11 18:08:38 mopidy systemd[1]: Started Mopidy music server.
Nov 11 18:08:39 mopidy systemd[1]: mopidy.service: Main process exited, code=killed, status=11/SEGV
Nov 11 18:08:39 mopidy systemd[1]: mopidy.service: Failed with result ‘signal’.
Nov 11 18:10:23 mopidy systemd[1]: Starting Mopidy music server…
Nov 11 18:10:23 mopidy systemd[1]: Started Mopidy music server.
Nov 11 18:10:24 mopidy systemd[1]: mopidy.service: Main process exited, code=killed, status=11/SEGV
Nov 11 18:10:24 mopidy systemd[1]: mopidy.service: Failed with result ‘signal’.
Nov 11 18:10:59 mopidy systemd[1]: Starting Mopidy music server…
Nov 11 18:10:59 mopidy systemd[1]: Started Mopidy music server.
Nov 11 18:11:00 mopidy systemd[1]: mopidy.service: Main process exited, code=killed, status=11/SEGV
Nov 11 18:11:00 mopidy systemd[1]: mopidy.service: Failed with result ‘signal’.
Nov 11 18:11:44 mopidy systemd[1]: Starting Mopidy music server…
Nov 11 18:11:44 mopidy systemd[1]: Started Mopidy music server.
Nov 11 18:11:46 mopidy systemd[1]: mopidy.service: Main process exited, code=killed, status=11/SEGV
Nov 11 18:11:46 mopidy systemd[1]: mopidy.service: Failed with result ‘signal’.
Nov 11 18:14:01 mopidy systemd[1]: Starting Mopidy music server…
Nov 11 18:14:01 mopidy systemd[1]: Started Mopidy music server.
Nov 11 18:14:02 mopidy systemd[1]: mopidy.service: Main process exited, code=killed, status=11/SEGV
Nov 11 18:14:02 mopidy systemd[1]: mopidy.service: Failed with result ‘signal’.
Nov 11 18:26:03 mopidy systemd[1]: Starting Mopidy music server…
Nov 11 18:26:03 mopidy systemd[1]: Started Mopidy music server.
Nov 11 18:26:05 mopidy systemd[1]: mopidy.service: Main process exited, code=killed, status=11/SEGV
Nov 11 18:26:05 mopidy systemd[1]: mopidy.service: Failed with result ‘signal’.
I blanked the SD card and started again. I am not sure why but it works now -
Tom