Those errors are likely red herrings, but really annoying. We’ve been trying to figure out what on earth is constantly trying to run / connect to dbus, but not managed to isolate it this time around.
Following http://docs.mopidy.com/en/latest/troubleshooting/#debug-logging or /var/log/mopidy/mopidy.log contents would help with pointing you in the right direction as this currently isn’t enough info to say anything at all. Oh and mopidy deps output while you are at it
Hmm, this is really strange, logs have no indication of what is going on. For something calling “sys.exit” there would be some trace in the logs. So it is likely a crash, but without any hints from the logs there isn’t much to be done.
I assume this is running as a system service? Any chance /var/log/messages or one of the other system logs contains some trace of what happend?
Otherwise you could perhaps try to narrow down by disabling extensions. If you can reproduce with a barebone mopidy that at least would exclude quite a bit of responsibilities.
Finally, running with GST_DEBUG_FILE=/path/to/log/file/for/gstreamer and GST_DEBUG=3 in the environment of mopidy might uncover if we are crashing somewhere in gstreamer.
