Server Version#:5286 (latest)
Player Version#:
Windows version: W10 Version 21H2 (Build 19044.1348)
Plex Media Server.zip (2.2 KB)
Server seem to work… ??
I do not know why server attemps to connect to port 34400 as show in the log since the
server is not configured for using that port number…
Thank for your help…
You need to enable debug logging, otherwise only warnings and errors get logged so that is all you will see. Some of these may be harmless but can’t tell without the rest of the info. Enable the setting, restart PMS, wait 3 minutes. Grab logs.
However, if nothing appears to be wrong, these could all be harmless errors/warnings.
Bonjour,
Here is the log file with debug mode enabled… I did only enable the debug mode not the verbose… hope it’s OK…
I Do have few questions regarding the contains of the log file…
1 – line 37 : Dec 08, 2021 05:56:24.506 [7968] WARN - Couldn’t determine bundle identifier for plug-in at: “C:\Program Files (x86)\Plex\Plex Media Server\Resources\Plug-ins-34f965be8\WebClient.bundle”
I tried to fix it, but was unable… have you an idea of where should I look for to fix it…
2 – line 187 : I seem to ping my IPAD, but my IPAD was idle and no session was active and the Plex APPS is not even started on it… It try a lot to talk to it has seen in the log… strange… May be it’s OK…
3 – line 303 : Dec 08, 2021 05:56:27.213 [19224] WARN - [DatabaseFixups] Held transaction for too long (…\Library\MetadataCollection.cpp:479): 0.109375 seconds
Dec 08, 2021 05:56:27.214 [19224] DEBUG - [DatabaseFixups] Collections: Refreshed attributes for 0 collections in section 1 in 60ms.
Dec 08, 2021 05:56:27.214 [7968] WARN - Took too long (0.109375 seconds) to start a transaction on …\Plugins\PluginDatabaseState.cpp:189
Dec 08, 2021 05:56:27.214 [7968] WARN - Transaction that was running was started on thread 19224 at …\Library\MetadataCollection.cpp:306
This is a fast machine, but not the fastest 
… but I do not understand why Plex complains as it is too long… I’m trying to figure that out but with no success…
4 – line 442 : Dec 08, 2021 05:56:28.689 [23380] WARN - HTTP error requesting GET http://192.168.1.99:34400/discover.json (7, Couldn’t connect to server) (Failed to connect to 192.168.1.99 port 34400: Connection refused)
Dec 08, 2021 05:56:28.690 [23380] ERROR - DVR:Device: Error refreshing existing device device://tv.plex.grabbers.hdhomerun/2019-10-3HA4-L7O76A, marking as dead.
Dec 08, 2021 05:56:28.690 [23380] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/2019-10-3HA4-L7O76A:10 at http://192.168.1.99:34400
Dec 08, 2021 05:56:28.690 [23380] DEBUG - DVR:Device: Device device://tv.plex.grabbers.hdhomerun/2019-10-3HA4-L7O76A:10 was already known, refreshing database info
It seem trying to connect using port number 34400 — but there is no such a port number – this is not what is indicated in the configuration of the server! why did he stuck on this port number all along in the log file…?
5 – line 745 : Dec 08, 2021 05:56:36.929 [23332] DEBUG - Activity: registered new activity ff7de815-a638-4c95-be53-71eeffa5f081 - “Refreshing Sub”
Dec 08, 2021 05:56:36.930 [8220] ERROR - PlexClient::downloadContainer: expected MediaContainer element, found html
Dec 08, 2021 05:56:36.930 [8220] WARN - Subscription: No container available for /tv.plex.providers.epg.cloud:173/metadata/plex%3A%2F%2Fshow%2F5fc6982c6a2ae8002d056729
Dec 08, 2021 05:56:36.930 [8220] ERROR - Subscription: Error refreshing sub: No container found
This type of errors happen often… is this really an error… how could I fix it… don’t even know where to look for…
I fall on those errors while I was investigating problem with tuners and errors in the transcoding process… those are related to latest release(5286)… and I try to have a clean installation before reporting the problem that I have with transcoding…
Thank you for your help…
Have a nice day…
PS: My apologies for my poor English, This is not my native language.
Denys.
Plex Media Server.zip (67.8 KB)
That is strange… this is the log file just after I turn off the debug…
Plex Media Server(2).zip (2.2 KB)
and i lost the tuner…
also I did terminate Plex correctly but that was not recorded in the log… ??
I have to restart Plex again to have access to the tuner again…
strange…
1 - I’m not familiar with that error. Likely harmless.
2 - Definitely harmless. PMS scans your network for devices all the time.
3 - Plex uses an SQLite database to store certain information. A fast cpu does not necessarily mean fast database performance. This is just a warning, meaning it took longer to retrieve the information than expected. Mostly harmless.
5 - That’s PMS trying to analyze the video stream coming in. Are you using an actual tuner or XTeve? I saw a reference to that in your log. I’ve noticed IPTV streams do not always have the correct header information so PMS can’t determine what it is. You can’t fix this yourself, this information comes from whatever source you are using.
4 - PMS is looking for your tuner and not finding it. I went out of order since #5 is related to this. If you are using XTeve, PMS is not happy with it.
What are the exact issues you ae having? The best way is to reproduce the problem then we can look at the logs.
Turning off debug just hides all the normal log lines. It didn’t cause the tuner to die, it had already done that earlier. Again, if you are using XTeve, look there first. It looks like something isn’t working right. If you are not using XTeve, there is a reference to it in your logs so maybe you tried it before and never removed it. It may still be running and causing a conflict with the real tuner.
Thank for your reply.
You are right , I’m using Xteve… so
Result is exacly the same not at the same place in the log… and no XTEVE there…
So, as you said these are not errors… it is probably just Plex probing network and devices… and disk access that may become busy sometime.
Thank for you help and time. I will close this.
Have a nice day.
Denys.
