Mopidy fail to start as a Debian Jessie service


#1
root@rmsbox:/home# /etc/init.d/mopidy status
   mopidy.service - Mopidy music server
   Loaded: loaded (/lib/systemd/system/mopidy.service; enabled)
   Active: failed (Result: signal) since Sun 2016-07-24 11:53:30 CEST; 3min 10s ago
  Process: 3859 ExecStart=/usr/bin/mopidy --config /usr/share/mopidy/conf.d:/etc/mopidy/mopidy.conf (code=killed, signal=SEGV)
 Main PID: 3859 (code=killed, signal=SEGV)

Jul 24 11:53:28 rmsbox mopidy[3859]: INFO     Loading config from builtin defaults
Jul 24 11:53:28 rmsbox mopidy[3859]: INFO     Loading config from /etc/mopidy/mopidy.conf
Jul 24 11:53:28 rmsbox mopidy[3859]: INFO     Loading config from command line options
Jul 24 11:53:28 rmsbox mopidy[3859]: INFO     Enabled extensions: mopify, spotify, mpd, alsamixer, http, stream, m3u, softwaremixer, file, local
Jul 24 11:53:28 rmsbox mopidy[3859]: INFO     Disabled extensions: none
Jul 24 11:53:30 rmsbox mopidy[3859]: INFO     Starting Mopidy mixer: SoftwareMixer
Jul 24 11:53:30 rmsbox mopidy[3859]: INFO     Starting Mopidy audio
Jul 24 11:53:30 rmsbox mopidy[3859]: INFO     Starting Mopidy backends: SpotifyBackend, StreamBackend, M3UBackend, FileBackend, LocalBackend
Jul 24 11:53:30 rmsbox systemd[1]: mopidy.service: main process exited, code=killed, status=11/SEGV
Jul 24 11:53:30 rmsbox systemd[1]: Unit mopidy.service entered failed state.

==> /var/log/kern.log <==
Jul 24 23:07:48 rmsbox kernel: [ 1147.058711] mopidy[2291]: segfault at 0 ip 00007fbd6b67db9e sp 00007fbd5bda76e0 error 4 in libspotify.so.12.1.51[7fbd6b4e0000+25c000]

Any ideas ? I Can’t find a previous topic with this error.


#3

Solved by reinstalling everything with apt


#4

Hi,

just got the same issue. I installed mopidy incl. some extras on RaspberryPi3 powered by raspbian (jessie indeed).
First I ran it as via sudo mopidy --config /etc/mopidy/mopidy.conf to run some tests and configure my setup.
Once ready I tried to run mopidy as a service and… same error as above.
In my case here’s what I did:

  1. sudo mopidyctl --config /etc/mopidy/mopidy.conf -vvv
    this showed me that mopidy crashes on spotify module loading /var/cache/mopidy/…

  2. I checked all paths mentioned in /etc/mopidy/mopidy.conf in scope of ownership

Conclusion: because I ran previously via sudo mopidy, files and folders were created for root:root.
Solution:
sudo chown -R mopidy:audio /var/cache/mopidy
sudo chown -R mopidy:audio /var/lib/mopidy

the above did the trick. mopidy up and running, fully repleced mpd.


#5

So in conclusion, don’t run the service as the root user, it’s not designed to be used that way. And there is a need to improve the error messages so you don’t need to run with verbose logging to discover this. Thanks.