Plex 1.13.5.5332 Crashing 1-2 times a Day on Synology DS918+

i do not see a Plex library in file station

Okay, not sure which account to use with to install then. i only have the 1 account i created to login and out of the system

i just checked the permissions on my Plex shared folder my user was not added, only the plex user had permissions

I see the folder now

Here are the logs you Requested @ChuckPa

Logs.zip (6.2 MB)

@trumpy81

Is there a reason i should be on 6.2 update 2?

I’m a big believer of if it aint broke don’t fix it

@ChuckPa i have installed 13.2 successfully after uninstalling 13.5 and Plex is up and running

i will monitor to see the stability of this version

i agree with you on the security aspect with the security patches they release in newer versions

Now that i am temporarily running Plex 13.2 i will hold off updating to 6.2 update 2 until the kinks can be worked out, and will most likely upgrade DSM when the latest Plex version is shown to work with the latest DSM version

well there seems to be a kernel issue, so there may be something else amiss here

This may be very unpleasant to do but will rule out a corrupt kernel.

  1. Backup the system’s configuration
  2. Make a list of your installed applications (which you added)
  3. Reset & Reinstall DSM
    https://www.synology.com/en-global/knowledgebase/DSM/tutorial/General/How_to_reset_my_Synology_NAS

You will want Mode 2: which is Step 3.

Remember to export (backup ) the configuration from Control Panel - Backup and Restore before you do.

Afterwards, reinstall your apps including PMS. The PMS installer will find your existing Library and continue to use it uninterrupted.

oh man, how long you think that will take. Not a whole lot of time in the near future for something like this

Is there something else to try before this nuclear option?

surprisingly, it takes me, on 25 Mbps DSL, about 30 minutes to backup, reset, reinstall everything, and reboot that last time after everything is installed. It’s nothing like the nuclear (Reload the volume) step

Let it wait If you don’t have the time. If you rush, you’ll mess up.

Alright, i’ll give it a go.

May i ask why this is needed?

I’m not convinced it is but little makes sense.

We can try one last step

Item 1. See if UDEV is corrupted (part of the OS Plex uses for video)

  1. SSH into the box
  2. sudo -su root
  3. ls -la /dev/dri

Item 2. Have it do a full scrub (the background task) and up the priority - scrub rate

This makes sense to do if you’ve had an abrupt power off/outage… Such an outage can corrupt the OS tables.

Did you add any non-Synology memory to the box?

No i just added a second 4GB stick, purchased from Synology. Total of 8GB

here is the output from those 2 commands. Did you want me to do a scrub?

Did this problem begin right after adding memory?

If so, do you hear where I’m going? I’m wondering if it seated correctly. Some machines don’t even have enough for two fingers to get in there. Not to be insulting or pedantic, do you remember hearing both sides ‘click’ as they locked into place ?

i installed the second stick before setting up DSM initially
i bought it and the unit with the hard drives all at once

I do remember hearing that (fyi i’ve installed RAM into other machines previously)

Cool. Just asking (some have never done it so we never really know if “one click or two” haha)

For now, you’re on 1.13.2, which I know is very stable on all the DS boxes.

If you’re ok with this, let’s rule out software and any/all hardware we can by seeing how long it runs.

Should this crash, we need to go grab the kernel log itself.

  1. SSH into it
  2. sudo -su root
  3. cat /var/log/messages (capture it all)

i’m curious if DSM would’ve recognized the full 8GB of RAM if it was not installed properly