Current Optimal Set Up on Synology

Plex Media Server NAS & Devices
21

Dave,

By turning off DEBUG, there is nothing which can be seen / used

Sep 21, 2022 22:00:48.990 [0x7f92685e3b00] INFO - Plex Media Server v1.29.0.6219-b1b4d4871 - Docker Docker Container x86_64 - build: linux-x86_64 debian - GMT 00:00
Sep 21, 2022 22:00:48.990 [0x7f92685e3b00] INFO - Linux version: 4.4.180+, language: en-US
Sep 21, 2022 22:00:48.990 [0x7f92685e3b00] INFO - Processor: 4-core Intel(R) Celeron(R) J4125 CPU @ 2.00GHz
Sep 21, 2022 22:00:48.990 [0x7f92685e3b00] INFO - Compiler is - Clang 11.0.1 (https://plex.tv 9b997da8e5b47bdb4a9425b3a3b290be393b4b1f)
Sep 21, 2022 22:00:48.990 [0x7f92685e3b00] INFO - /usr/lib/plexmediaserver/Plex Media Server
Sep 21, 2022 22:00:49.018 [0x7f926c2d97c0] INFO - [CERT/OCSP] Successfully retrieved response from cache.
Sep 21, 2022 22:00:49.074 [0x7f926c2d97c0] INFO - Running migrations. (EPG 0)
Sep 21, 2022 22:00:49.497 [0x7f926c2d97c0] INFO - Running migrations. (EPG 0)
Sep 21, 2022 22:00:50.150 [0x7f92650b7b00] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: availability
Sep 21, 2022 22:00:50.150 [0x7f92650b7b00] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: availability-platforms
Sep 21, 2022 22:00:50.150 [0x7f92650b7b00] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: markers
Sep 21, 2022 22:00:50.173 [0x7f9265b38b00] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: availability
Sep 21, 2022 22:00:50.173 [0x7f9265b38b00] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: availability-platforms
Sep 21, 2022 22:00:50.173 [0x7f9265b38b00] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: markers
Sep 21, 2022 22:00:52.325 [0x7f9263258b00] INFO - Refreshing paths watched by LibraryUpdateManager
Sep 21, 2022 22:00:52.874 [0x7f926c2d97c0] WARN - [DatabaseFixups] Held transaction for too long (/data/jenkins/server/3534229725/Library/DatabaseFixups.cpp:375): 0.440000 seconds
Sep 21, 2022 22:00:53.119 [0x7f9267f83b00] WARN - [EventSourceClient/pubsub/50.116.51.249:443] MyPlex: attempted a reachability check but we're not yet mapped.
Sep 21, 2022 22:00:53.164 [0x7f9262240b00] INFO - Sync: downloaded 0 sync list(s) with 0 sync items(s): 0 new, 0 updated, 0 deleted
Sep 21, 2022 22:00:53.164 [0x7f9261831b00] WARN - Sync: local sync directory "/config/Library/Application Support/Plex Media Server/Cache/Transcode/Sync+" does not exist
Sep 21, 2022 22:00:57.513 [0x7f92609c8b00] INFO - [Req#45] AutoUpdate: no updates available
Sep 21, 2022 22:00:58.789 [0x7f92628a4b00] INFO - [Req#5a] [PlexRelay] Allocated port 25135 for remote forward to 127.0.0.1:32401
Sep 21, 2022 22:01:02.295 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:01:03.292 [0x7f9260145b00] ERROR - Unknown metadata type: 
Sep 21, 2022 22:01:03.340 [0x7f925ff42b00] ERROR - Unknown metadata type: 
Sep 21, 2022 22:01:18.105 [0x7f925ff42b00] WARN - Connection Tester: Error testing media server Jared's iMac in 10000 ms.
Sep 21, 2022 22:01:18.105 [0x7f9260145b00] WARN - Connection Tester: Error testing media server Jared's iMac in 10000 ms.
Sep 21, 2022 22:01:18.351 [0x7f925ff42b00] ERROR - Unknown metadata type: 
Sep 21, 2022 22:01:18.541 [0x7f9260145b00] ERROR - Unknown metadata type: 
Sep 21, 2022 22:01:23.311 [0x7f925ff42b00] ERROR - Unknown metadata type: 
Sep 21, 2022 22:01:23.435 [0x7f9260145b00] ERROR - Unknown metadata type: 
Sep 21, 2022 22:01:32.303 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:01:38.113 [0x7f925ff42b00] WARN - Connection Tester: Error testing media server MiniMe in 10000 ms.
Sep 21, 2022 22:01:38.253 [0x7f92654bdb00] ERROR - Unknown metadata type: 
Sep 21, 2022 22:01:40.027 [0x7f92654bdb00] ERROR - Unknown metadata type: 
Sep 21, 2022 22:01:40.277 [0x7f9265919b00] WARN - [HttpClient/HCl#7a] HTTP error requesting GET /media/providers (3, URL using bad/illegal format or missing URL) ()
Sep 21, 2022 22:01:40.278 [0x7f9265919b00] WARN - [HttpClient/HCl#7b] HTTP error requesting GET /media/providers (3, URL using bad/illegal format or missing URL) ()
Sep 21, 2022 22:01:40.457 [0x7f92654bdb00] ERROR - Unknown metadata type: 
Sep 21, 2022 22:01:42.082 [0x7f92654bdb00] ERROR - Unknown metadata type: 
Sep 21, 2022 22:01:45.489 [0x7f92654bdb00] ERROR - Unknown metadata type: 
Sep 21, 2022 22:01:46.060 [0x7f92654bdb00] ERROR - Unknown metadata type: 
Sep 21, 2022 22:01:51.489 [0x7f9265919b00] WARN - [HttpClient/HCl#8f] HTTP error requesting GET /media/providers (3, URL using bad/illegal format or missing URL) ()
Sep 21, 2022 22:02:02.304 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:02:32.302 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:03:02.309 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:03:32.308 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:04:02.314 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:04:32.314 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:05:02.322 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:05:32.325 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:06:02.331 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:06:32.327 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:06:54.862 [0x7f9264f54b00] WARN - [Req#19c] QueryParser: Invalid field 'sectionID' found, ignoring.
Sep 21, 2022 22:06:54.862 [0x7f9264f54b00] WARN - [Req#19c] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Sep 21, 2022 22:06:54.862 [0x7f9264f54b00] WARN - [Req#19c] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Sep 21, 2022 22:06:54.862 [0x7f92652bab00] WARN - [Req#19b] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Sep 21, 2022 22:06:54.862 [0x7f92652bab00] WARN - [Req#19b] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Sep 21, 2022 22:06:54.909 [0x7f9264f54b00] WARN - [Req#19c] QueryParser: Invalid field 'sectionID' found, ignoring.
Sep 21, 2022 22:06:54.909 [0x7f9264f54b00] WARN - [Req#19c] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Sep 21, 2022 22:06:54.909 [0x7f9264f54b00] WARN - [Req#19c] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Sep 21, 2022 22:06:54.944 [0x7f9264f54b00] WARN - [Req#19c] QueryParser: Invalid field 'sectionID' found, ignoring.
Sep 21, 2022 22:06:54.944 [0x7f9264f54b00] WARN - [Req#19c] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Sep 21, 2022 22:06:54.944 [0x7f9264f54b00] WARN - [Req#19c] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Sep 21, 2022 22:06:54.986 [0x7f92652bab00] WARN - [Req#19d] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Sep 21, 2022 22:06:54.986 [0x7f92652bab00] WARN - [Req#19d] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Sep 21, 2022 22:06:54.991 [0x7f92642a9b00] WARN - [Req#1a8] QueryParser: Invalid field 'sectionID' found, ignoring.
Sep 21, 2022 22:06:54.991 [0x7f92642a9b00] WARN - [Req#1a8] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Sep 21, 2022 22:06:54.991 [0x7f92642a9b00] WARN - [Req#1a8] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Sep 21, 2022 22:06:54.993 [0x7f9264017b00] WARN - [Req#1a9] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Sep 21, 2022 22:06:54.993 [0x7f9264017b00] WARN - [Req#1a9] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Sep 21, 2022 22:06:55.057 [0x7f9264f54b00] WARN - [Req#19c] SLOW QUERY: It took 280.000000 ms to retrieve 50 items.
Sep 21, 2022 22:07:02.333 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:07:32.329 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:08:02.341 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:08:32.338 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:09:02.337 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:09:32.346 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:10:02.351 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:10:32.352 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:11:02.353 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:11:32.362 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:12:02.364 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:12:32.361 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:13:02.361 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:13:32.367 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:13:32.997 [0x7f9261c37b00] ERROR - XML: Entity: line 1:\00
Sep 21, 2022 22:13:32.997 [0x7f9261c37b00] ERROR - XML: parser\00
Sep 21, 2022 22:13:32.997 [0x7f9261c37b00] ERROR - XML: error :\00
Sep 21, 2022 22:13:32.997 [0x7f9261c37b00] ERROR - XML: Start tag expected, '<' not found\00
Sep 21, 2022 22:13:32.997 [0x7f9261c37b00] ERROR - XML: status=ok\00
Sep 21, 2022 22:13:32.997 [0x7f9261c37b00] ERROR - XML: ^\00
Sep 21, 2022 22:13:32.997 [0x7f9261c37b00] ERROR - Error parsing content.
Sep 21, 2022 22:13:32.997 [0x7f9261c37b00] ERROR - Error parsing XML: Error parsing file.
Sep 21, 2022 22:13:32.997 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.43.156:9080
Sep 21, 2022 22:14:02.364 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:14:32.372 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:15:02.375 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:15:32.380 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:15:53.266 [0x7f9261c37b00] ERROR - XML: Entity: line 1:\00
Sep 21, 2022 22:15:53.266 [0x7f9261c37b00] ERROR - XML: parser\00
Sep 21, 2022 22:15:53.266 [0x7f9261c37b00] ERROR - XML: error :\00
Sep 21, 2022 22:15:53.266 [0x7f9261c37b00] ERROR - XML: Start tag expected, '<' not found\00
Sep 21, 2022 22:15:53.266 [0x7f9261c37b00] ERROR - XML: status=ok\00
Sep 21, 2022 22:15:53.266 [0x7f9261c37b00] ERROR - XML: ^\00
Sep 21, 2022 22:15:53.266 [0x7f9261c37b00] ERROR - Error parsing content.
Sep 21, 2022 22:15:53.266 [0x7f9261c37b00] ERROR - Error parsing XML: Error parsing file.
Sep 21, 2022 22:15:53.266 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.43.156:9080
Sep 21, 2022 22:16:02.382 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:16:32.381 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:16:33.656 [0x7f9261c37b00] ERROR - XML: Entity: line 1:\00
Sep 21, 2022 22:16:33.656 [0x7f9261c37b00] ERROR - XML: parser\00
Sep 21, 2022 22:16:33.656 [0x7f9261c37b00] ERROR - XML: error :\00
Sep 21, 2022 22:16:33.656 [0x7f9261c37b00] ERROR - XML: Start tag expected, '<' not found\00
Sep 21, 2022 22:16:33.656 [0x7f9261c37b00] ERROR - XML: status=ok\00
Sep 21, 2022 22:16:33.656 [0x7f9261c37b00] ERROR - XML: ^\00
Sep 21, 2022 22:16:33.656 [0x7f9261c37b00] ERROR - Error parsing content.
Sep 21, 2022 22:16:33.656 [0x7f9261c37b00] ERROR - Error parsing XML: Error parsing file.
Sep 21, 2022 22:16:33.656 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.43.156:9080
Sep 21, 2022 22:17:02.390 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:17:22.637 [0x7f9261c37b00] ERROR - XML: Entity: line 1:\00
Sep 21, 2022 22:17:22.637 [0x7f9261c37b00] ERROR - XML: parser\00
Sep 21, 2022 22:17:22.637 [0x7f9261c37b00] ERROR - XML: error :\00
Sep 21, 2022 22:17:22.637 [0x7f9261c37b00] ERROR - XML: Start tag expected, '<' not found\00
Sep 21, 2022 22:17:22.637 [0x7f9261c37b00] ERROR - XML: status=ok\00
Sep 21, 2022 22:17:22.637 [0x7f9261c37b00] ERROR - XML: ^\00
Sep 21, 2022 22:17:22.637 [0x7f9261c37b00] ERROR - Error parsing content.
Sep 21, 2022 22:17:22.637 [0x7f9261c37b00] ERROR - Error parsing XML: Error parsing file.
Sep 21, 2022 22:17:22.637 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.43.156:9080
Sep 21, 2022 22:17:32.384 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:18:02.392 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:18:32.391 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:18:32.572 [0x7f9261c37b00] ERROR - XML: Entity: line 1:\00
Sep 21, 2022 22:18:32.572 [0x7f9261c37b00] ERROR - XML: parser\00
Sep 21, 2022 22:18:32.572 [0x7f9261c37b00] ERROR - XML: error :\00
Sep 21, 2022 22:18:32.572 [0x7f9261c37b00] ERROR - XML: Start tag expected, '<' not found\00
Sep 21, 2022 22:18:32.572 [0x7f9261c37b00] ERROR - XML: status=ok\00
Sep 21, 2022 22:18:32.572 [0x7f9261c37b00] ERROR - XML: ^\00
Sep 21, 2022 22:18:32.572 [0x7f9261c37b00] ERROR - Error parsing content.
Sep 21, 2022 22:18:32.572 [0x7f9261c37b00] ERROR - Error parsing XML: Error parsing file.
Sep 21, 2022 22:18:32.572 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.43.156:9080
Sep 21, 2022 22:19:02.393 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:19:32.397 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:20:02.404 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:20:32.401 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:21:02.404 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:21:32.406 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:22:02.403 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:22:32.415 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:23:02.413 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:23:32.417 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:24:02.422 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:24:32.425 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:25:02.431 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:25:32.432 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:26:02.434 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:26:32.431 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:27:02.440 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:27:32.434 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:27:32.649 [0x7f9261c37b00] ERROR - XML: Entity: line 1:\00
Sep 21, 2022 22:27:32.649 [0x7f9261c37b00] ERROR - XML: parser\00
Sep 21, 2022 22:27:32.649 [0x7f9261c37b00] ERROR - XML: error :\00
Sep 21, 2022 22:27:32.649 [0x7f9261c37b00] ERROR - XML: Start tag expected, '<' not found\00
Sep 21, 2022 22:27:32.649 [0x7f9261c37b00] ERROR - XML: status=ok\00
Sep 21, 2022 22:27:32.649 [0x7f9261c37b00] ERROR - XML: ^\00
Sep 21, 2022 22:27:32.649 [0x7f9261c37b00] ERROR - Error parsing content.
Sep 21, 2022 22:27:32.662 [0x7f9261c37b00] ERROR - Error parsing XML: Error parsing file.
Sep 21, 2022 22:27:32.662 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.43.156:9080
Sep 21, 2022 22:28:02.438 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:28:32.448 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:29:02.447 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:29:12.589 [0x7f9261c37b00] ERROR - XML: Entity: line 1:\00
Sep 21, 2022 22:29:12.589 [0x7f9261c37b00] ERROR - XML: parser\00
Sep 21, 2022 22:29:12.589 [0x7f9261c37b00] ERROR - XML: error :\00
Sep 21, 2022 22:29:12.589 [0x7f9261c37b00] ERROR - XML: Start tag expected, '<' not found\00
Sep 21, 2022 22:29:12.589 [0x7f9261c37b00] ERROR - XML: status=ok\00
Sep 21, 2022 22:29:12.589 [0x7f9261c37b00] ERROR - XML: ^\00
Sep 21, 2022 22:29:12.589 [0x7f9261c37b00] ERROR - Error parsing content.
Sep 21, 2022 22:29:12.589 [0x7f9261c37b00] ERROR - Error parsing XML: Error parsing file.
Sep 21, 2022 22:29:12.589 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.43.156:9080
Sep 21, 2022 22:29:32.447 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:30:02.452 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:30:32.454 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:31:01.551 [0x7f92683c7b00] WARN - JobManager: Could not find job for handle 403
Sep 21, 2022 22:31:02.452 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:31:32.462 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:32:02.454 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:32:32.465 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:32:43.834 [0x7f9261c37b00] ERROR - XML: Entity: line 1:\00
Sep 21, 2022 22:32:43.834 [0x7f9261c37b00] ERROR - XML: parser\00
Sep 21, 2022 22:32:43.834 [0x7f9261c37b00] ERROR - XML: error :\00
Sep 21, 2022 22:32:43.834 [0x7f9261c37b00] ERROR - XML: Start tag expected, '<' not found\00
Sep 21, 2022 22:32:43.834 [0x7f9261c37b00] ERROR - XML: status=ok\00
Sep 21, 2022 22:32:43.834 [0x7f9261c37b00] ERROR - XML: ^\00
Sep 21, 2022 22:32:43.834 [0x7f9261c37b00] ERROR - Error parsing content.
Sep 21, 2022 22:32:43.834 [0x7f9261c37b00] ERROR - Error parsing XML: Error parsing file.
Sep 21, 2022 22:32:43.834 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.43.156:9080
Sep 21, 2022 22:33:02.466 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:33:32.469 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:33:32.586 [0x7f9261c37b00] ERROR - XML: Entity: line 1:\00
Sep 21, 2022 22:33:32.586 [0x7f9261c37b00] ERROR - XML: parser\00
Sep 21, 2022 22:33:32.586 [0x7f9261c37b00] ERROR - XML: error :\00
Sep 21, 2022 22:33:32.586 [0x7f9261c37b00] ERROR - XML: Start tag expected, '<' not found\00
Sep 21, 2022 22:33:32.586 [0x7f9261c37b00] ERROR - XML: status=ok\00
Sep 21, 2022 22:33:32.586 [0x7f9261c37b00] ERROR - XML: ^\00
Sep 21, 2022 22:33:32.586 [0x7f9261c37b00] ERROR - Error parsing content.
Sep 21, 2022 22:33:32.586 [0x7f9261c37b00] ERROR - Error parsing XML: Error parsing file.
Sep 21, 2022 22:33:32.586 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.43.156:9080
Sep 21, 2022 22:34:02.474 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:34:32.467 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:35:02.477 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:35:03.700 [0x7f9261c37b00] ERROR - XML: Entity: line 1:\00
Sep 21, 2022 22:35:03.700 [0x7f9261c37b00] ERROR - XML: parser\00
Sep 21, 2022 22:35:03.700 [0x7f9261c37b00] ERROR - XML: error :\00
Sep 21, 2022 22:35:03.700 [0x7f9261c37b00] ERROR - XML: Start tag expected, '<' not found\00
Sep 21, 2022 22:35:03.700 [0x7f9261c37b00] ERROR - XML: status=ok\00
Sep 21, 2022 22:35:03.700 [0x7f9261c37b00] ERROR - XML: ^\00
Sep 21, 2022 22:35:03.700 [0x7f9261c37b00] ERROR - Error parsing content.
Sep 21, 2022 22:35:03.700 [0x7f9261c37b00] ERROR - Error parsing XML: Error parsing file.
Sep 21, 2022 22:35:03.700 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.43.156:9080
Sep 21, 2022 22:35:32.472 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:36:02.483 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:36:32.486 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:37:02.485 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:37:32.492 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:37:42.668 [0x7f9261c37b00] ERROR - XML: Entity: line 1:\00
Sep 21, 2022 22:37:42.668 [0x7f9261c37b00] ERROR - XML: parser\00
Sep 21, 2022 22:37:42.668 [0x7f9261c37b00] ERROR - XML: error :\00
Sep 21, 2022 22:37:42.668 [0x7f9261c37b00] ERROR - XML: Start tag expected, '<' not found\00
Sep 21, 2022 22:37:42.668 [0x7f9261c37b00] ERROR - XML: status=ok\00
Sep 21, 2022 22:37:42.668 [0x7f9261c37b00] ERROR - XML: ^\00
Sep 21, 2022 22:37:42.668 [0x7f9261c37b00] ERROR - Error parsing content.
Sep 21, 2022 22:37:42.668 [0x7f9261c37b00] ERROR - Error parsing XML: Error parsing file.
Sep 21, 2022 22:37:42.668 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.43.156:9080
Sep 21, 2022 22:38:02.484 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:38:32.500 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:39:02.493 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:39:32.503 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:40:02.494 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:40:32.503 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:41:02.505 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:41:32.502 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:42:02.508 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:42:32.514 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:43:02.516 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:43:32.515 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:44:02.518 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:44:32.522 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:45:02.519 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:45:32.533 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:46:02.529 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:46:32.535 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:47:02.541 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:47:32.533 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:48:02.543 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:48:32.539 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:49:02.551 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:49:32.550 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:50:02.551 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:50:32.557 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:51:02.557 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:51:32.555 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:52:02.557 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:52:32.566 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:52:44.044 [0x7f9261c37b00] ERROR - XML: Entity: line 1:\00
Sep 21, 2022 22:52:44.044 [0x7f9261c37b00] ERROR - XML: parser\00
Sep 21, 2022 22:52:44.044 [0x7f9261c37b00] ERROR - XML: error :\00
Sep 21, 2022 22:52:44.044 [0x7f9261c37b00] ERROR - XML: Start tag expected, '<' not found\00
Sep 21, 2022 22:52:44.044 [0x7f9261c37b00] ERROR - XML: status=ok\00
Sep 21, 2022 22:52:44.044 [0x7f9261c37b00] ERROR - XML: ^\00
Sep 21, 2022 22:52:44.044 [0x7f9261c37b00] ERROR - Error parsing content.
Sep 21, 2022 22:52:44.044 [0x7f9261c37b00] ERROR - Error parsing XML: Error parsing file.
Sep 21, 2022 22:52:44.044 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.43.156:9080
Sep 21, 2022 22:53:02.572 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:53:32.569 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:54:02.575 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:54:32.572 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:55:02.579 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:55:32.575 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:56:02.584 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:56:32.583 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:57:02.587 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:57:32.595 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:58:02.594 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:58:32.601 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:59:02.594 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 22:59:32.603 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:00:02.603 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:00:32.607 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:01:02.603 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:01:32.614 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:01:44.679 [0x7f9261c37b00] ERROR - XML: Entity: line 1:\00
Sep 21, 2022 23:01:44.679 [0x7f9261c37b00] ERROR - XML: parser\00
Sep 21, 2022 23:01:44.679 [0x7f9261c37b00] ERROR - XML: error :\00
Sep 21, 2022 23:01:44.679 [0x7f9261c37b00] ERROR - XML: Start tag expected, '<' not found\00
Sep 21, 2022 23:01:44.679 [0x7f9261c37b00] ERROR - XML: status=ok\00
Sep 21, 2022 23:01:44.679 [0x7f9261c37b00] ERROR - XML: ^\00
Sep 21, 2022 23:01:44.679 [0x7f9261c37b00] ERROR - Error parsing content.
Sep 21, 2022 23:01:44.679 [0x7f9261c37b00] ERROR - Error parsing XML: Error parsing file.
Sep 21, 2022 23:01:44.679 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.43.156:9080
Sep 21, 2022 23:02:02.612 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:02:32.613 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:03:02.622 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:03:32.622 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:04:02.621 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:04:32.629 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:05:02.635 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:05:32.633 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:05:42.772 [0x7f9261c37b00] ERROR - XML: Entity: line 1:\00
Sep 21, 2022 23:05:42.772 [0x7f9261c37b00] ERROR - XML: parser\00
Sep 21, 2022 23:05:42.772 [0x7f9261c37b00] ERROR - XML: error :\00
Sep 21, 2022 23:05:42.772 [0x7f9261c37b00] ERROR - XML: Start tag expected, '<' not found\00
Sep 21, 2022 23:05:42.772 [0x7f9261c37b00] ERROR - XML: status=ok\00
Sep 21, 2022 23:05:42.772 [0x7f9261c37b00] ERROR - XML: ^\00
Sep 21, 2022 23:05:42.772 [0x7f9261c37b00] ERROR - Error parsing content.
Sep 21, 2022 23:05:42.773 [0x7f9261c37b00] ERROR - Error parsing XML: Error parsing file.
Sep 21, 2022 23:05:42.773 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.43.156:9080
Sep 21, 2022 23:06:02.632 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:06:12.860 [0x7f9261c37b00] ERROR - XML: Entity: line 1:\00
Sep 21, 2022 23:06:12.860 [0x7f9261c37b00] ERROR - XML: parser\00
Sep 21, 2022 23:06:12.860 [0x7f9261c37b00] ERROR - XML: error :\00
Sep 21, 2022 23:06:12.860 [0x7f9261c37b00] ERROR - XML: Start tag expected, '<' not found\00
Sep 21, 2022 23:06:12.860 [0x7f9261c37b00] ERROR - XML: status=ok\00
Sep 21, 2022 23:06:12.860 [0x7f9261c37b00] ERROR - XML: ^\00
Sep 21, 2022 23:06:12.860 [0x7f9261c37b00] ERROR - Error parsing content.
Sep 21, 2022 23:06:12.860 [0x7f9261c37b00] ERROR - Error parsing XML: Error parsing file.
Sep 21, 2022 23:06:12.860 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.43.156:9080
Sep 21, 2022 23:06:32.642 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:06:53.152 [0x7f9261c37b00] ERROR - XML: Entity: line 1:\00
Sep 21, 2022 23:06:53.152 [0x7f9261c37b00] ERROR - XML: parser\00
Sep 21, 2022 23:06:53.152 [0x7f9261c37b00] ERROR - XML: error :\00
Sep 21, 2022 23:06:53.152 [0x7f9261c37b00] ERROR - XML: Start tag expected, '<' not found\00
Sep 21, 2022 23:06:53.152 [0x7f9261c37b00] ERROR - XML: status=ok\00
Sep 21, 2022 23:06:53.152 [0x7f9261c37b00] ERROR - XML: ^\00
Sep 21, 2022 23:06:53.152 [0x7f9261c37b00] ERROR - Error parsing content.
Sep 21, 2022 23:06:53.152 [0x7f9261c37b00] ERROR - Error parsing XML: Error parsing file.
Sep 21, 2022 23:06:53.152 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.43.156:9080
Sep 21, 2022 23:07:02.642 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:07:32.646 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:08:02.654 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:08:32.655 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:09:02.655 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:09:32.652 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:09:33.661 [0x7f9261c37b00] ERROR - XML: Entity: line 1:\00
Sep 21, 2022 23:09:33.661 [0x7f9261c37b00] ERROR - XML: parser\00
Sep 21, 2022 23:09:33.661 [0x7f9261c37b00] ERROR - XML: error :\00
Sep 21, 2022 23:09:33.661 [0x7f9261c37b00] ERROR - XML: Start tag expected, '<' not found\00
Sep 21, 2022 23:09:33.661 [0x7f9261c37b00] ERROR - XML: status=ok\00
Sep 21, 2022 23:09:33.661 [0x7f9261c37b00] ERROR - XML: ^\00
Sep 21, 2022 23:09:33.661 [0x7f9261c37b00] ERROR - Error parsing content.
Sep 21, 2022 23:09:33.661 [0x7f9261c37b00] ERROR - Error parsing XML: Error parsing file.
Sep 21, 2022 23:09:33.661 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.43.156:9080
Sep 21, 2022 23:10:02.664 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:10:22.797 [0x7f9261c37b00] ERROR - XML: Entity: line 1:\00
Sep 21, 2022 23:10:22.797 [0x7f9261c37b00] ERROR - XML: parser\00
Sep 21, 2022 23:10:22.797 [0x7f9261c37b00] ERROR - XML: error :\00
Sep 21, 2022 23:10:22.797 [0x7f9261c37b00] ERROR - XML: Start tag expected, '<' not found\00
Sep 21, 2022 23:10:22.797 [0x7f9261c37b00] ERROR - XML: status=ok\00
Sep 21, 2022 23:10:22.797 [0x7f9261c37b00] ERROR - XML: ^\00
Sep 21, 2022 23:10:22.797 [0x7f9261c37b00] ERROR - Error parsing content.
Sep 21, 2022 23:10:22.797 [0x7f9261c37b00] ERROR - Error parsing XML: Error parsing file.
Sep 21, 2022 23:10:22.797 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.43.156:9080
Sep 21, 2022 23:10:32.663 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:11:02.665 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:11:32.667 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:12:02.673 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:12:32.676 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:13:02.675 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:13:32.680 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:14:02.682 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:14:32.685 [0x7f9261c37b00] ERROR - SSDP: Error parsing device schema for http://192.168.42.12:8080/upnp
Sep 21, 2022 23:15:00.043 [0x7f9261c37b00] ERROR - Network Service: Error in advertiser handle read: 125 (Operation canceled) socket=-1
Sep 21, 2022 23:15:00.119 [0x7f92683c7b00] WARN - JobManager: Could not find job for handle 325
Sep 21, 2022 23:15:00.143 [0x7f9261c37b00] INFO - Network Service: Abandoning advertise socket, it was closed.

I now need you to stop PMS.

Using the Synology Text Editor app, add logDebug="1" logVerbose="0" to Preferences.xml before the closing /> on the last line of it.

Start PMS…

Capture the log again.

(You’re not saving anything by turning off DEBUG but are making it tougher to diagnose and lose time when diagnosing)

22

Sure thing and, again, thank you!

PlexDockerFailure2-Logs.zip (661.5 KB)

Thanks for the tip. I’m so used to debug logs only being needed for debugging—and filling up the drive the rest of the time—that I simply turn them off by default when presented with the option. I appreciate the heads-up that this isn’t the case with Plex, and will leave them on going forward. Thanks!

23

Regardless of the logging level:

  1. There are 6 files; the current log file and 5 rollover logs
  2. The maximum size of a log file is 10.5 MB.
  3. When the log rolls over, the oldest falls off the end.

You’ll never have more than logNumFiles="x" logfiles so why not leave it in the default Debug ON, Verbose OFF logging settings.

I’m not seeing any errors in the log.
I see it scanning & adding media.

I do find one very odd , completely out of place entry.

Sep 22, 2022 00:45:39.241 [0x7f5a4a0f3b00] DEBUG - Request: [[::1]:45674 (Loopback)] GET /identity (13 live) #37d Signed-in
Sep 22, 2022 00:45:39.241 [0x7f5a51a12b00] DEBUG - Completed: [[::1]:45674] 200 GET /identity (13 live) 0ms 398 bytes (pipelined: 1)

This entry is checking to see if the server is claimed. IMHO, that makes it suspicious.

Plex doesn’t use IPv6 in this form.
All PMS internal is via 127.0.0.1 (IPv4 stack)

Your LAN is IPv4 primary

Sep 22, 2022 00:43:57.236 [0x7f5a55d687c0] DEBUG - Detected primary interface: 192.168.42.48
Sep 22, 2022 00:43:57.236 [0x7f5a55d687c0] DEBUG - Network interfaces:
Sep 22, 2022 00:43:57.236 [0x7f5a55d687c0] DEBUG -  * 1 lo (127.0.0.1) (00-00-00-00-00-00) (loopback: 1)
Sep 22, 2022 00:43:57.236 [0x7f5a55d687c0] DEBUG -  * 3 eth2 (169.254.65.7) (00-11-32-D4-19-B3) (loopback: 0)
Sep 22, 2022 00:43:57.236 [0x7f5a55d687c0] DEBUG -  * 6 eth3 (169.254.48.185) (00-11-32-D4-19-B4) (loopback: 0)
Sep 22, 2022 00:43:57.236 [0x7f5a55d687c0] DEBUG -  * 7 bond0 (192.168.42.48) (00-11-32-D4-19-B1) (loopback: 0)
Sep 22, 2022 00:43:57.236 [0x7f5a55d687c0] DEBUG -  * 1 lo (::1) (00-00-00-00-00-00) (loopback: 1)
Sep 22, 2022 00:43:57.236 [0x7f5a55d687c0] DEBUG -  * 7 bond0 (fd87:644f:cec:491b:211:32ff:fed4:19b1) (00-11-32-D4-19-B1) (loopback: 0)

Might you have something else going on ? Tautulli or something ?

24

Hmmm, no, I’m not running that (and now I know what it is). I checked to make sure IPv6 is disabled (it is), and I disabled Tailscale just to make sure that wasn’t causing any issues (same launch error).

This DiskStation was just brought into service a couple of weeks ago to be used primarily as a Plex server because my DS1522+ doesn’t have a GPU for hardware transcoding. Docker was installed today solely for this. There’s very little running on this server other than Plex (ChannelsDVR also is here, VideoStation is installed, and as of yesterday so is Emby, though I don’t see any immediate appeal of using that!).

Happy to troubleshoot other things, of course, but not sure what else it would be?

My network is “bonded” as you can probably see from the logs. Not sure if that would be an issue.

25

You might find, as most of us did, VideoStation, AudioStation, (at least) and possibly PhotoStation, to be very lackluster as compared to Plex.

What you’ll learn quickly is how they interfere with PMS.

If you ever place media in any of the Synology-provided default shared folders, they will , sooner or later, block PMS from seeing the files.

It seems, Synology has a nasty habit (Since DSM 5 days at least) of forcibly setting permissions when it suits them.

26

Interesting. I’ve been running VideoStation and AudioStation alongside Plex for (many) years, with no obvious issues. PhotoStation was replaced by Moments which was replaced by Synology Photos, the latter of which (finally) has some utility.

In any event, I don’t store anything in Synology-provided default shared folders. Everything is in custom folders, most of which are stored in NFS shares on my DS1522+.

All that said (and aside), should I uninstall VideoStation?

It seems weird that the Dockerized Plex will happily run with “sudo docker start Plex” but won’t run when I launch it in the Docker app. Was I wrong to use “sudo” when creating the Plex docker? Is that my issue? Should I have done it with my user account (which is in the Administrators group)?

27

If you’ve achieve stability, there is no need to change.
My comment was based on what I’ve seen with the forum where folks would put media in the Synology-defined shared folders.

Now for the silly question.

  1. With PMS and Docker both stopped
  2. DSM restarted
  3. How does it play when you then start Docker and the PMS container?
28

I get the same message. I looked in the Docker GUI in DSM and saw this error about the /config/Library/Application Support mapping.

I realize there are good reasons why we had to create the container from the command line, but this was interesting. Relevant, or no?

image
image872×573 36.8 KB

29

DS1522+ with DSM 7.

I’m not really fond of using the Docker UI. Synology has some pretty severe limitations. They don’t handle the Application Support part of the definition.

I’d rather you not use their GUI like that. It’ll mess it up every time.

May I see your docker run config?

It should be like mine here except localization

docker run \
-d \
--name Plex \
--network=host \
-e TZ="EST" \
-e LANG="en_US.UTF-8" \
-e PUID=297536 \
-e PGID=297536 \
-e PLEX_UID=297536 \
-e PLEX_GID=297536 \
-h dockerplex \
-v /volume1/PlexMediaServer/AppData:"/config/Library/Application Support" \
-v /volume1/PlexMediaServer/AppData/tmp:/tmp \
-v /volume1/PlexMediaServer/AppData/tmp:/transcode \
-v /volume1:/volume1 \
-v /volume2:/volume2 \
--device=/dev/dri:/dev/dri \
plexinc/pms-docker:plexpass

# Set to automatically restart unless stopped
docker update --restart=unless-stopped Plex```
30

My data is stored on a DS1522+, but Plex is running on my DS1520+, since the latter has a GPU for hardware transcoding.

I’m happy to show you my docker run config… except I can’t for the life of me figure out how to display that! :wink: What’s the right command to run? I know the container ID, of course.

31

How did you define the container?

Did you use my FAQ ?

To show what you have, a simple copy/paste here using </> code formatting (top of the reply window) will work.

Looks like this when typing:
```
It will look like this when done
```

It will look like this when done
32

I used your FAQ, yes, but instead of running it as a Scheduled Command, I just logged in and pasted it at the command line (with sudo, as admin/root). It fired right up.

33

Yep. that will work too.

If you used the container, as written, then all paths to the media on the DS1522+

will have been through the NFS mount point on the DS1520+ – which is 100% OK as long as the permissions on the other side of the NFS are right.

I don’t understand why the DS1520+ docker control is having problems with Run/Stop.

Stupid question time… You do have PMS installed on the DS1520+ and you keep it in the Stopped status?

I"m trying to figure out what’s happening because I’ve never seen Docker fail to start/stop one of its own containers.

It’s starting to feel like a Docker app bug.

What gets me is that if you can use docker start / docker stop and it’s fine – that wreaks of an app bug, doesn’t it?

34

It kinda does, yes! I mean… what else is the Synology Docker GUI app doing other than issuing docker start Plex when I tell it to start? It’s kinda bizarre.

For grins, I did delete and recreate the container using your method 100%, including the two Scheduled Tasks. Same end result. ¯\_(ツ)_/¯

Is there somewhere I can look to see the failure logs that we haven’t otherwise looked?

35

as root cat /var/log/messages

dmesg is useless given the proprietary kernel.

36

Hmmm… neither /var/log/messages nor dmesg shows anything when I try this. Super bizarre.

37

Don’t know what else to tell you other than the classic:

  1. Uninstall docker
  2. Reboot the NAS
  3. Reinstall docker
  4. Redefine the containers (since the data is held safe in the file system)
1 Like
38

Thanks, @ChuckPa! I appreciate your willingness to dig in and try, my friend. I’m probably going to leave it as is for now and long term either:

  • Hope that a DSM update addresses this
  • Move back to the native Plex package (because I can’t see a lick of difference with HDR transcoding on/off)
  • Just let Portainer or something else manage that package. :slight_smile:
39

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