I seem to be unable to sync ‘tvshows’ onto either an iOS or Android device.
I’ve created a temp tvshow library and have the same issue. Films are fine.
Looking in the logs, I get:
Oct 18, 2019 13:20:01.989 [0x7fa3d99e9700] Error — Exception inside transaction (inside=1) (../Library/MetadataItem.cpp:779): Null value fetched and no indicator defined.
Oct 18, 2019 13:20:01.989 [0x7fa3d99e9700] Error — Thread: Uncaught exception running async task which was spawned by thread 0x7fa3bd11f700: Null value fetched and no indicator defined.
This old post explains the exact issue I have Sync failing PMS 1.17.0 however there are no comments to say how it was resolved (if it was).
Works okay here. I was able to sync two tv episodes in different formats.
One was an xvid avi that went to the iPad at Highest without conversion.
The other was an x264 mkv that got burned subtitles.
Server - 1.18.1.1973 on x64 QNAP QTS 4.3.6-1070
Player - 6.2 on a 2018 iPad running iOS 13.1.3
Then I went offline and played both episodes. I’ll try another device.
I don’t think it is an issue with PMS in general, but something to do with my instance of it. As @M1dKn1ght says, maybe a db issue?
I just find it strange it only effects libraries which are ‘TV programmes’. Even new libraries.
Oct 20, 2019 13:20:52.643 [0x7fc2c7f5b700] INFO - Plex Media Server v1.18.1.1973-0f4abfbcc - QNAP TS-1277 x86_64 - build: linux-x86_64 qnap - GMT 01:00
Oct 20, 2019 13:20:52.643 [0x7fc2c7f5b700] INFO - Linux version: QTS 4.4.1.1086, language: en-US
Oct 20, 2019 13:20:52.643 [0x7fc2c7f5b700] INFO - Processor AMD Ryzen 7 PRO 1700 Eight-Core Processor
The logs are chaotic and filled with errors like in your first post. @M1dKn1ght said the fix was a fresh database, and it does look database related but not in the usual way. The more common symptom of a db problem is an SQLITE3 error saying “database corruption” or something similar. Your logs have no ERRORs from SQLITE3 at least. The topic of checking is covered in https://support.plex.tv/articles/201100678-repair-a-corrupt-database/
One repeated problem that can be stopped temporarily is to identify and unplug this device if it’s not mandatory during testing, because your logs are filled with this error too:
Oct 20, 2019 13:23:06.192 [0x7fc2bcaf4700] ERROR - SSDP: Error parsing device schema for http://10.10.10.103:55296/
I would like to see the logs covering a PMS start.
I would reboot the QNAP and grab logs 6 min. after it’s back to a desktop,
but you’ll want to wait and see what ChuckPA asks you to do first. Good luck!
You might want to identify the network domain. PMS is treating it as Non-Local even though it’s on the same subnet. (Settings - Server - Network - Show Advanced)
I see where the client app closed the connection.
Oct 20, 2019 20:06:40.425 [0x7ff0ab159700] DEBUG - Content-Length is -1 (of total: -1).
Oct 20, 2019 20:07:00.425 [0x7ff14b8c8700] DEBUG - Completed: [10.10.10.171:53348] 200 GET /player/proxy/poll?deviceClass=pc&protocolVersion=3&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1 (12 live) TLS GZIP 20000ms 5 bytes (pipelined: 20)
Oct 20, 2019 20:07:00.480 [0x7ff14b5da700] DEBUG - WebSocket: client initiated close
Oct 20, 2019 20:07:00.481 [0x7ff14b5da700] DEBUG - NotificationStream: Removing because of close
Oct 20, 2019 20:07:00.486 [0x7ff14b8c8700] DEBUG - handleStreamRead code 2: End of file
