I have a large library of movies and series, and I use Plex to watch those movies and series, but most of the time Plex stops responding on most devices, and when reviewing the service on the server, we find that it is working and I wait for a lot of time, perhaps it will work again to no avail, which makes me stop Plex and restart it again Others until it works and I attached the records. Please help and thank you
Plex Media Server Logs_2023-04-23_03-02-55.zip (4.6 MB)
Plex Media Server Logs_2023-04-24_16-12-54.zip (2.9 MB)
Plex Media Server Logs_2023-04-25_21-21-56.zip (3.4 MB)
Please turn off verbose logging. Debug is sufficient. Verbose adds a lot of additional, usually unnecessary, info to the log files. As a result, they wrap too fast and the desirable information can be lost.
From Plex Media Server.log
(2023-04-24):
Apr 24, 2023 16:12:49.239 [0x7f039b3ffb38] ERROR - [Notify] Failed to add watch for "/volume1/Multimedia/Movies/English/2D/C/Crucible Of The Vampire (2019) [BluRay] [1080p] [YTS.AM]" (28: No space left on device)
You’ve exceeded the Linux inotify limit. This is common and easily rectified. Remember to reboot the NAS, not just restart PMS, after increasing the limit. It is a Linux, not Plex, limit, so the NAS must be rebooted.
See FAQ 16: Increase the number of folders Plex can monitor.
Adjust the limit and see how Plex responds. If it does not correct the situation, upload another set of log files.
FYI, if you want to see PMS hit the notify limit, look in the same file and count the DEBUG - [Notify] Now watching
entries. There are 8192, the default limit for Synology NAS.
The last entry is Apr 24, 2023 16:12:49.239 [0x7f039b3ffb38] DEBUG - [Notify] Now watching "/volume1/Multimedia/Movies/English/2D/C/Crows Explode (2014) [1080p] [BluRay] [5.1] [YTS.MX]"
.
The next line in the log file is the ERROR entry listed above.
Second issue to investigate:
Apr 24, 2023 16:12:36.219 [0x7f03a1930a90] DEBUG - Detected primary interface: 10.10.100.100
Apr 24, 2023 16:12:36.219 [0x7f03a1930a90] DEBUG - Network interfaces:
Apr 24, 2023 16:12:36.219 [0x7f03a1930a90] DEBUG - * 1 lo (127.0.0.1) (00-00-00-00-00-00) (loopback: 1)
Apr 24, 2023 16:12:36.219 [0x7f03a1930a90] DEBUG - * 3 eth0 (10.10.100.100) (00-11-32-2C-A6-03) (loopback: 0)
Apr 24, 2023 16:12:36.219 [0x7f03a1930a90] DEBUG - * 4 eth1 (10.10.3.31) (00-11-0A-66-AA-11) (loopback: 0)
Apr 24, 2023 16:12:36.219 [0x7f03a1930a90] DEBUG - * 5 eth2 (10.10.100.100) (C4-54-44-23-F0-E1) (loopback: 0)
Apr 24, 2023 16:12:36.219 [0x7f03a1930a90] DEBUG - * 6 eth3 (10.10.4.100) (C4-54-44-23-F0-E2) (loopback: 0)
Apr 24, 2023 16:12:36.219 [0x7f03a1930a90] DEBUG - * 1 lo (::1) (00-00-00-00-00-00) (loopback: 1)
eth0 and eth2 have the same IP address. Unless the interfaces are bonded or one is offline as a backup, this will also cause problems.
WOW
First, I thank you very much for helping me
I also encountered this problem with Unraid, and I had to demolish the library and re-create it again. Today I will try the solution and I will contact you again
Thank you very much
i can acces synology every time
but plex has stop responding
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.