andy@vault:/$ sudo journalctl -xe -u plexmediaserver
░░ The job identifier is 845 and the job result is done.
Apr 17 13:38:15 vault systemd[1]: plexmediaserver.service: Start request repeated too quickly.
Apr 17 13:38:15 vault systemd[1]: plexmediaserver.service: Failed with result ‘exit-code’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ The unit plexmediaserver.service has entered the ‘failed’ state with result ‘exit-code’.
Apr 17 13:38:15 vault systemd[1]: Failed to start plexmediaserver.service - Plex Media Server.
░░ Subject: A start job for unit plexmediaserver.service has failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit plexmediaserver.service has finished with a failure.
░░
░░ The job identifier is 845 and the job result is failed.
Apr 17 14:39:31 vault systemd[1]: Starting plexmediaserver.service - Plex Media Server…
░░ Subject: A start job for unit plexmediaserver.service has begun execution
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit plexmediaserver.service has begun execution.
░░
░░ The job identifier is 5174.
Apr 17 14:39:31 vault systemd[1]: Started plexmediaserver.service - Plex Media Server.
░░ Subject: A start job for unit plexmediaserver.service has finished successfully
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit plexmediaserver.service has finished successfully.
░░
░░ The job identifier is 5174.
Apr 17 14:39:59 vault [38429]: Critical: libusb_init failed
Apr 17 14:39:59 vault Plex Media Server[38429]: Critical: libusb_init failed
lines 138-171/171 (END)
░░ The job identifier is 845 and the job result is done.
Apr 17 13:38:15 vault systemd[1]: plexmediaserver.service: Start request repeated too quickly.
Apr 17 13:38:15 vault systemd[1]: plexmediaserver.service: Failed with result ‘exit-code’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ The unit plexmediaserver.service has entered the ‘failed’ state with result ‘exit-code’.
Apr 17 13:38:15 vault systemd[1]: Failed to start plexmediaserver.service - Plex Media Server.
░░ Subject: A start job for unit plexmediaserver.service has failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit plexmediaserver.service has finished with a failure.
░░
░░ The job identifier is 845 and the job result is failed.
Apr 17 14:39:31 vault systemd[1]: Starting plexmediaserver.service - Plex Media Server…
░░ Subject: A start job for unit plexmediaserver.service has begun execution
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit plexmediaserver.service has begun execution.
░░
░░ The job identifier is 5174.
Apr 17 14:39:31 vault systemd[1]: Started plexmediaserver.service - Plex Media Server.
░░ Subject: A start job for unit plexmediaserver.service has finished successfully
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit plexmediaserver.service has finished successfully.
░░
░░ The job identifier is 5174.
Apr 17 14:39:59 vault [38429]: Critical: libusb_init failed
Apr 17 14:39:59 vault Plex Media Server[38429]: Critical: libusb_init failed
I think it has sorted itself over night. But would like to know what caused this. i’ve got the logs but don’t think debug is turned on. logs.tar.gz (1.1 MB)
i tried everything i could think of to get it working yesterday and this morning hey presto its functioning.
Yes no idea what happened I certainly didn’t change any permissions (as I would probably have to research how to do that!)
At least it’s working again now.
Thanks @ChuckPa for looking into it for me
Hi ChuckPA,
i have reinstalled the Plex server and manual added all the Libarys again. thank good the played movies and tv shows are still there just the server hast to update all its data again and sucks it into the database…what a mess …but everything runs so far.
It fails to start because it cannot write to its files.
Did you recently place media/other files in the Plex shared folder ?
How this works:
Don’t put media in the Plex shared folder when you’re using DSM 6.
Equally don’t put media in the PlexMediaServer shared folder when you’re using DSM 7. You CAN put media in the unused Plex shared folder AFTER upgrading to DSM 7.
DSM 6
The Plex shared folder and all contents are owned by username Plex
The assigned group is users
DSM 7
The Plex shared folder is no longer used
The PlexMediaServer shared folder now holds all the metadata and server info
The PlexMediaServer shared folder is owned by System Internal User PlexMediaServer
The assigned group is PlexMediaServer
(Synology completely changed how the users & system services are separated with DSM 7)
That is the only change i’ve made recently as you asked me to do. Otherwise no change has been made. The issue isn’t a can’t write to but the service start request failed with “exit-code”. saying the start request was repeated too quickly.
Apr 17 13:38:15 vault systemd[1]: plexmediaserver.service: Start request repeated too quickly.
Apr 17 13:38:15 vault systemd[1]: plexmediaserver.service: Failed with result ‘exit-code’.