Server Version#: 1.25.4.5426
Player Version#: 4.66.1
I can’t figure out why, but it seems that PLEX stops itself every night with no obvious explanation. I’ve tried both versions of PMS on TrueNAS (PMS, and PMS Beta) and both have given me the same issue. I’ve tried searching the web for some of the critical errors in the logs, but have so far come up empty handed with solutions. I’ve also attempted uninstall and re-installs, to no avail.
Does anyone else have any ideas?
PMS runs as a TrueNAS 12.0 plugin
Truenas runs as a ProxMox VM
I’m a TrueNAS fan myself, and that’s a valid choice, but I’m curious.
If you’re using ProxMox, why not run Plex as an LXC? There are some potential advantages to the Linux version of Plex, mostly around automatic change detection, hardware support for transcoding & tone mapping, and support for Sonic Analysis.
Sadly, there’s absolutely no indication of PMS stopping, but I do see a huge gap in the times of logging, and they happens right after PMS claims it lost the network
Feb 01, 2022 02:30:51.982 [0x80ea91400] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 22.589715 seconds: 192.168.0.11 (Wink Hub 2)
Feb 01, 2022 02:30:51.983 [0x80ea91400] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 20.844756 seconds: 192.168.0.50 (Living Room TV)
Feb 01, 2022 02:30:51.984 [0x80ea91400] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 22.527918 seconds: 192.168.0.98 (Exterior front)
Feb 01, 2022 02:30:51.984 [0x80ea91400] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 22.602369 seconds: 192.168.0.101 (OctoPrint instance on octopi)
Feb 01, 2022 02:31:20.411 [0x807282400] DEBUG - Completed after connection close: [99.246.143.74:27727] 200 GET /:/eventsource/notifications (4 live) TLS 9283480ms 20196 bytes
Feb 01, 2022 02:31:33.099 [0x80a9ad300] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 60.973344 seconds: 192.168.0.1 (CODA-4582)
Feb 01, 2022 02:31:33.138 [0x80a9ad300] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 61.115976 seconds: 192.168.0.1 (WANDevice:1)
Feb 01, 2022 02:31:33.165 [0x80a9ad300] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 61.142672 seconds: 192.168.0.1 (WANConnectionDevice:1)
Feb 01, 2022 02:31:41.161 [0x80b2af000] DEBUG - NetworkServiceBrowser: Parsing SSDP schema for http://192.168.0.1:45514/agent.xml
Feb 01, 2022 02:31:41.233 [0x80b2af000] DEBUG - HTTP requesting GET http://192.168.0.1:45514/agent.xml
Feb 01, 2022 02:31:41.288 [0x80b2af000] ERROR - Error issuing curl_easy_perform(handle): 56
Feb 01, 2022 02:31:41.288 [0x80b2af000] WARN - HTTP error requesting GET http://192.168.0.1:45514/agent.xml (56, Failure when receiving data from the peer) (Recv failure: Connection reset by peer)
Feb 01, 2022 02:31:41.288 [0x80b2af000] ERROR - SSDP: Error parsing device schema for http://192.168.0.1:45514/agent.xml
Feb 01, 2022 02:31:42.974 [0x8085d6700] ERROR - Error issuing curl_easy_perform(handle): 28
Feb 01, 2022 02:31:43.003 [0x8085d6700] DEBUG - HTTP simulating 408 after curl timeout
Feb 01, 2022 02:31:43.041 [0x8085d6700] DEBUG - MyPlex: using cached data for request for https://plex.tv/api/v2/server/access_tokens?auth_token=xxxxxxxxxxxxxxxxxxxx
Feb 01, 2022 02:31:43.273 [0x8085d6700] DEBUG - MyPlex: updating with 14 access tokens
Feb 01, 2022 02:32:12.043 [0x80b2af000] DEBUG - NetworkServiceBrowser: Parsing SSDP schema for https://192.168.0.11:8888
Feb 01, 2022 02:32:12.145 [0x807282900] DEBUG - [EventSourceClient/pubsub] Failure in IdleTimeout (0 - No error: 0).
Feb 01, 2022 02:32:12.188 [0x807282900] DEBUG - [EventSourceClient/pubsub] MyPlex: We appear to have lost Internet connectivity, resetting device URL cache.
Feb 01, 2022 02:32:12.360 [0x807282900] ERROR - [EventSourceClient/pubsub] Retrying in 15 seconds.
So I would check the OS log around that time to see if it logged something, and nope, not a TrueNas guy
