I’ve recently started using trakt-scrobbler and its error log shows a lot of this message:
PMS is currently running startup maintenance tasks
503 Server Error: Service Unavailable for url: http://localhost:32400/status/sessions
The scrobbler stops monitoring Plex when it sees this error and I need to manually restart it. Any idea what this error is and how I can avoid it? I’m running PMS 1.29.0.6244 on Mac OS 10.13.6.
Wait ! Leave PMS running, and don’t use it. It is migrating databases. Try in a few hours or tomorrow.
You have nothing wrong … yet 
To clarify, when I say “manually restart” I’m referring to the trakt-scrobbler. I never touch PMS - it runs problem-free and reliably. It’s only the scrobbler that’s throwing errors.
Understood
those two messages are the exact ones displayed when migrating the db after a server upgrade. If scrobbler is wrong I’m not sure what to do, but if it’s right then just wait till it stops saying that to use PMS.
Another thing to mention, 1.29.0 was very much beta, and 1.29.1 is a significant upgrade to the transcoder and HW acceleration. You’ll want to upgrade as soon as practical.
Hmm. Looking further back through the log, those messages are appearing at one or two-day intervals, at nearly the exact same time of day.
Maybe worth mentioning that the scrobbler had been running well until the password breach issue. Perhaps it’s a coincidence, but these errors only started after resetting my password (after which I needed to reclaim my server). I reauthorized the scrobbler with my updated credentials of course, and it works MOST of the time - but when it doesn’t, it’s because of this error.
Okay now I understand. Every indication is that your server works fine, except in Scrobbler which crashes.
If I were you after I’m sure PMS is idle, I’d restart it and wait 5min, then I’d troubleshooting → Download Logs, zip and drop them into this topic so we can check for errors.
After that I would upgrade PMS because the new version is pretty epic, and completely uninstall then reinstall Scrobbler while waiting for the PMS db migration to finish.
That sound like a plan?
They don’t… but I just realized that I have an ages old cron job that restarts the server every morning at 4:30 - which is when the errors happen. That job must be the source of the scrobbler error. I feel silly for not remembering this earlier, but thanks for triggering my memory by asking about the schedule lol.
