Ubuntu Server Needs Constant Restarting to Access Plex

Plex Media Server Desktops & Laptops
1

Server Version#: 1.21.1.3795

I’m having to constantly reboot my Ubuntu Plex server to access the content. Usually daily. I don’ t know what’s going on. I troubleshooted using some suggestions on the forums like optimizing the database and cleaning up bundles. At this point, I don’t know what I should do. Any suggestions would be appreciative. Ubuntu seems fine, just Plex isn’t showing up. My network drives are still mounted and accessible (content is on a network NAS).

(File removed)

2

Have you added “sudo service plexmediaserver start” to the /etc/rc.local file? This will ensure plex automatically starts when the server is started. I know that when you reboot all is well, however is there something that is timing out your connection on the NAS or elsewhere on your network?

3

@jp2558

The correct command, which does not require any modification to rc.local is:

sudo systemctl enable plexmediaserver

With it enabled, it will autostart at system boot.

4

@abrown

Looking at your logs now.

I will edit this post in a few minutes.

EDIT:

There are no obvious errors in your logs.

If the primary issue was that PMS would not restart after a system boot, enable the service will correct the problem.

Please advise if I’ve misunderstood/missed something.

5

No the exact opposite. I lose the ability to connect to my Plex Server almost daily. I have to reboot to regain access. It’s always available after rebooting.

I just tried to access the server again and it is unavailable. I remoted in and checked the NFS mount. The NAS is available on the mounted folder.

I accessed the server from the network address (192.168.1.XXX:32400/web…) and the Plex website is accessible but it does not show the files or the media server in the settings. Just my Shield’s server shows up.

I deleted my Shield server and removed it from my account to see if that did anything. I had it disabled, but weirdly it showed up available in the settings of my Ubuntu server. Maybe its getting confused about what server is what.

Updated logs after I reset the server:
(File removed)

6

Thanks for the updated logs.

  1. I can see it restart
  2. I can see it becoming available for Remote Access

Would you mind, when it next becomes unavailble;

  1. Restart
  2. Wait 2 minutes
  3. Download the logs ZIP again
  4. Attach here for me to see how it got into that state?
7

Sure, I can try to wait two minutes after restarting next time it becomes unavailable.

8

Thanks.

By waiting those 2 minutes, I can see both the failure state and how it recovers.

9

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