Plex 1.16.5 unable to start service after reboot

Server Version#: 1.16.5.1554-1e5ff713d_amd64
Player Version#: chromium

Hello
Following a reboot the launch of the plex service is impossible.
I see that there is an error in “service plexmediaserver status” and “journalctl -xe” but I do not understand what’s wrong.
Can you help me please ?

service plexmediaserver status :

● plexmediaserver.service - Plex Media Server
   Loaded: loaded (/lib/systemd/system/plexmediaserver.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2019-09-16 13:01:45 CEST; 16s ago
  Process: 21346 ExecStart=/bin/sh -c  PLEX_MEDIA_SERVER_INFO_VENDOR="$(grep ^NAME= /etc/os-release | awk 
  Process: 21342 ExecStartPre=/bin/sh -c /usr/bin/test -d "${PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR}" |
 Main PID: 21346 (code=exited, status=255)

sept. 16 13:01:39 streaming systemd[1]: plexmediaserver.service: Unit entered failed state.
sept. 16 13:01:39 streaming systemd[1]: plexmediaserver.service: Failed with result 'exit-code'.
sept. 16 13:01:45 streaming systemd[1]: plexmediaserver.service: Service hold-off time over, scheduling re
sept. 16 13:01:45 streaming systemd[1]: Stopped Plex Media Server.
sept. 16 13:01:45 streaming systemd[1]: plexmediaserver.service: Start request repeated too quickly.
sept. 16 13:01:45 streaming systemd[1]: Failed to start Plex Media Server.
sept. 16 13:01:45 streaming systemd[1]: plexmediaserver.service: Unit entered failed state.
sept. 16 13:01:45 streaming systemd[1]: plexmediaserver.service: Failed with result 'exit-code'.

journalctl -xe:

Sep 16 13:43:11 streaming systemd[1]: plexmediaserver.service: Unit entered failed state.
Sep 16 13:43:11 streaming systemd[1]: plexmediaserver.service: Failed with result 'exit-code'.
Sep 16 13:43:13 streaming sudo[2186]:    k1000 : TTY=pts/0 ; PWD=/home/k1000 ; USER=root ; COMMAND=/usr/sbin/service plexmediaserver status
Sep 16 13:43:13 streaming sudo[2186]: pam_unix(sudo:session): session opened for user root by k1000(uid=0)
Sep 16 13:43:16 streaming sudo[2186]: pam_unix(sudo:session): session closed for user root
Sep 16 13:43:16 streaming systemd[1]: plexmediaserver.service: Service hold-off time over, scheduling restart.
Sep 16 13:43:16 streaming systemd[1]: Stopped Plex Media Server.
-- Subject: Unit plexmediaserver.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit plexmediaserver.service has finished shutting down.
Sep 16 13:43:16 streaming systemd[1]: plexmediaserver.service: Start request repeated too quickly.
Sep 16 13:43:16 streaming systemd[1]: Failed to start Plex Media Server.
-- Subject: Unit plexmediaserver.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit plexmediaserver.service has failed.
-- 
-- The result is failed.
Sep 16 13:43:16 streaming systemd[1]: plexmediaserver.service: Unit entered failed state.
Sep 16 13:43:16 streaming systemd[1]: plexmediaserver.service: Failed with result 'exit-code'.
Sep 16 13:43:19 streaming sudo[2193]:    k1000 : TTY=pts/0 ; PWD=/home/k1000 ; USER=root ; COMMAND=/usr/sbin/service plexmediaserver status
Sep 16 13:43:19 streaming sudo[2193]: pam_unix(sudo:session): session opened for user root by k1000(uid=0)
Sep 16 13:43:21 streaming sudo[2193]: pam_unix(sudo:session): session closed for user root
Sep 16 13:43:26 streaming sudo[2200]:    k1000 : TTY=pts/0 ; PWD=/home/k1000 ; USER=root ; COMMAND=/bin/journalctl -xe
Sep 16 13:43:26 streaming sudo[2200]: pam_unix(sudo:session): session opened for user root by k1000(uid=0)

I am having this exact same issue. Fresh VMWare install of Ubuntu 18.04 LTS and fresh install of Plex 1.16.6.1592.

在 2019年9月21日週六 下午3:34,TKampy via Plex Forum plex@discoursemail.com 寫道:

Restart the linux computer, and 10 min after PMS has started or failed to start, then gather up the Log Files directory, zip it up, and attach it with your next reply.

Before you upload it, though, check if it’s full of DEBUG messages, indicating that PMS is running in debug mode. That’s what we want to have. If it is not using DEBUG mode, then edit your Preferences.xml file when PMS is not running, and add the field for debug as explained in Advanced Hidden Settings.

Include many details about your hardware and network configuration: how PMS has run for you in the past, what changed when it stopped working right, how did you go about installing PMS, and are there any VMs or Dockers?

Settings - Server - General - Show Advanced will also allow turning VERBOSE off and DEBUG on again if it was altered from the defaults.

Mine was a brand new install of Ubuntu 18.04.3 LTS headless running as a VM on ESXi. The only logs I could find complained about a database corruption.
I don’t think Plex ever actually ran.

I tried another install on another Ubuntu install, this one a desktop version. That install appeared to complete, but caused the system to hang at max CPU until I terminated it about 20 minutes later.

I have moved on to CentOS where everything is going MUCH smoother.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.