Plex Media Server "manually stopping"

Plex Media Server NAS & Devices
1

Server Version#:1.41.5.9626-72009626

Plex Media Server Logs_2025-12-20_13-07-53.zip (1.3 MB)

Hello!

I had uploaded some media to my Plex server a few days ago and then suddenly I couldn’t connect to it. It will open for a short period of time (maybe 3 seconds) before the status in the package center says “Manually Stopped”. I’ve been using Plex for a few years now and have never encountered this issue.

I have tried updating to the most recent version (v.1.42.2.10156-f737b826c), uninstalling/reinstalling Plex, I’ve updated my Synology firmware to DSM 7.2.2-72806 Update 5, I’ve deleted my cache and nothing has done the trick.

I’m at a loss. Really in love with my Plex server so I would really appreciate some help :).

Thank you in advance!

2

Logs state there’s no space left on the device (referring to /volume2 and /volume3 of your NAS).

3

Also check the number of folders the NAS can monitor. See FAQ 16: Increase the number of folders Plex can monitor.

4

Thank you for your reply!

That’s odd because it states in my storage manager that /volume2 has 551.6 GB free and /volume3 has 4.4 TB free?

5

You’ve exceeded the number of folders that the NAS can monitor (a Linux limitation). When this happens it appears in the Plex logs as Notify errors stating no space is left on the device.

From Plex Media Server.log:
Dec 20, 2025 13:07:36.842 [140204767423288] ERROR - [Notify] Failed to add watch for "/volume2/Media 2/Movies/Horror/Hide And Go Shriek (1988)" (28: No space left on device)

See the FAQ in my earlier post to resolve the issue.

Note: As it is a Linux issue, you may have to re-apply the fix after future DSM updates (DSM is Synology’s customized version of Linux).

6

Ok thank you very much for your response! I’ll try this now

7

The example in the FAQ shows only one volume. You’ve multiple volumes, so add up the folders for all volumes, then add 32768, etc.

1 Like
8

Hi, sorry to bug you,

when it comes to this script:

Remove any previous s2s_watches_max entries (avoid clutter)

sed -i ‘s/^s2s_watches_max=.$//’ /etc/synoinfo.conf
sed -i 's/^s2s_watches_max=.$//’ /etc.defaults/synoinfo.conf

This is an example only. Use your actual result below to add the new value

echo ‘s2s_watches_max=262144’ >> /etc/synoinfo.conf
echo ‘s2s_watches_max=262144’ >> /etc.defaults/synoinfo.conf

my number came to 65536. I’m assuming I would write that as:

Remove any previous s2s_watches_max entries (avoid clutter)

sed -i ‘s/^s2s_watches_max=.$//’ /etc/synoinfo.conf
sed -i 's/^s2s_watches_max=.$//’ /etc.defaults/synoinfo.conf

This is an example only. Use your actual result below to add the new value

echo ‘s2s_watches_max=65536’ >> /etc/synoinfo.conf
echo ‘s2s_watches_max=65536’ >> /etc.defaults/synoinfo.conf

Do I leave everything else as is?

9

Yes. Looks good.

10

So I did try this. It hasn’t seemed to have worked. I right clicked the task and hit Run, nothing happened so I figured that it was an instant kind of thing and I restarted my NAS and it’s the same issue. I’ve tried running the task again but am just waiting now. Will I get an alert it’s completed?

Sorry for all the questions. I’m very new to this stuff. Thank you for your time.

11

That task runs very quickly, just a couple of seconds. It is editing a file. “sed” is a Linux text editor.

What happens when you try to start Plex Media Server? Does it still show manually stopped?

If Plex Media Server is still not running…

  1. Configure the task and DSM to send notifications (see below).
  2. Re-run the task.
  3. Assuming it completes OK, restart the NAS.
  4. Then try to start Plex Media Server.

Write back if the task does not complete successfully or if Plex Media Server will not start.

If PMS still does not start, post a new set of server log files. If needed, manually pull the log files: Stop Plex if running. In File Station, navigate to the Plex Data Folder (/PlexMediaServer/…). Right click on the Logs directory and choose Compress to Logs.zip. Download the zip file and post to the thread.


Notifications

  1. Synology Control Panel → Notification → Email tab.
    Configure both the Synology Account and Email sections to send notifications to the desired e-mail address.

  2. Make sure the task is configured to send notifications.
    Edit the task, Task Settings tab, check the box to send details and enter your e-mail address.


This is the e-mail I receive when running the task on my DS918+:

Task Scheduler has completed a scheduled task.

Task: Linux Notify Table Increase for Plex
Start time: Sat, 20 Dec 2025 17:39:03 -0600
Stop time: Sat, 20 Dec 2025 17:39:04 -0600
Current status: 0 (Normal)
Standard output/error:
13

A few extra questions when you get a minute.

Increasing the folder count uses additional RAM, and if set too high the NAS will ignore the new setting. Just want to double check the calculations.

  • How much RAM in the NAS? Control Panel → Info Center → Total Physical Memory

  • What was the total folder account for all volumes?

  • The new limit is still 65536 (as in your earlier post), correct?

Thanks.

14

Once again, thank you for your response.

I tried again and did as you said and got the confirmation e-mail that the script did actually run, however PMS initially runs but stops as soon as I try and access Plex via the web app.

Here are the new logs -

Logs.zip (1.2 MB)

To answer your additional questions:

  • 4096 MB
  • volume1 = 6050, volume2 = 7836, volume3 = 3268 for a total of 17154
  • Yes. after adding 32768, then dividing 32768 I get 1.52. I didn’t round up, maybe that’s it? If I don’t round and add 1, that’s 2 x 32768 = 65536. If rounded I get 98304. Could that be the issue?

THANK YOU!

15

(DSM must be restarted for changes to be effective)

17000 folders should easily fit in 65535.

I will review the logs

EDIT: The logs do not show “No space left on device” errors.

16

Hello!

I did restart after running the script via Options → Restart unless I’m missing something else?

17

Is Plex running now?

If not, go to Package Center and start it. What happens?

I do not see anything in the log files that would keep it from running.

19

I can start it and it will run, but as soon as I connect to it with the web app it disconnects and says “manually stopped” :frowning:

Here’s the logs after the most recent crash

Logs.zip (1.2 MB)

Thanks again everyone