Plex timeouts connecting to "PubSubManager"

Plex Media Server Desktops & Laptops
1

Hello,
as stated in the object, after restarting Plex after hanging without any reasons, I checked the Media Server.log file and there seems to be some problems with the connection to some “SubManager”. Plus the web interface keeps loading without showing any page.
Here’s the relevant part of the log:

Jul 24, 2018 11:35:26.117 [0x7f02bc7fe700] WARN - PubSubManager: Connection to 82.94.168.55 failed: Connection timed out.
Jul 24, 2018 11:35:26.117 [0x7f02bc7fe700] WARN - PubSubManager: Connection to 50.116.44.223 failed: Connection timed out.
Jul 24, 2018 11:35:26.117 [0x7f02bc7fe700] WARN - PubSubManager: Connection to 45.79.11.43 failed: Connection timed out.
Jul 24, 2018 11:35:26.117 [0x7f02bc7fe700] WARN - PubSubManager: Connection to 172.104.24.90 failed: Connection timed out.
Jul 24, 2018 11:35:26.117 [0x7f02bc7fe700] WARN - PubSubManager: Connection to 172.104.133.220 failed: Connection timed out.
Jul 24, 2018 11:35:26.117 [0x7f02bc7fe700] WARN - PubSubManager: Connection to 139.162.115.125 failed: Connection timed out.
Jul 24, 2018 11:35:26.117 [0x7f02bc7fe700] WARN - PubSubManager: Connection to 178.79.150.155 failed: Connection timed out.
Jul 24, 2018 11:35:26.117 [0x7f02bc7fe700] WARN - PubSubManager: Connection to 172.104.173.210 failed: Connection timed out.
Jul 24, 2018 11:35:26.117 [0x7f02bc7fe700] WARN - PubSubManager: Connection to 184.105.148.98 failed: Connection timed out.
Jul 24, 2018 11:35:26.117 [0x7f02bc7fe700] WARN - PubSubManager: Connection to 82.94.168.60 failed: Connection timed out.
Jul 24, 2018 11:38:16.150 [0x7f02a6bf9700] ERROR - Timeout or error reading status line from plug-in pipe [com.plexapp.agents.imdb], we’re killing it.
Jul 24, 2018 11:38:16.150 [0x7f02a6bf9700] ERROR - Error received reading configuration for com.plexapp.agents.imdb
Jul 24, 2018 11:38:16.151 [0x7f02a6bf9700] ERROR - downloadContainer: expected MediaContainer element, found html
Jul 24, 2018 11:38:16.151 [0x7f02a6bf9700] ERROR - IVA: failed to get IMDB prefs

Plex is running on a Debian dedicated server with a 1Gbit full-duplex connection without any restriction. No UPnP problems as all ports are, like every dedicated servers, open.

Thanks to whoever can help.

2

May I have the complete log file containing those errors?
There is more information to go with it which is in the vicinity

In a nutshell, gateway / default adapter outbound path is missing somewhere

3

Here’s the full log before I restarted it:

Jul 24, 2018 16:35:48.429 [0x7fbcf03fe700] INFO - Plex Media Server v1.13.4.5271-200287a06 - ubuntu PC x86_64 - build: linux-ubuntu-x86_64 ubuntu - GMT 02:00
Jul 24, 2018 16:35:48.429 [0x7fbcf03fe700] INFO - Linux version: 4.9.0-7-amd64 (#1 SMP Debian 4.9.110-1 (2018-07-05)), language: en-US
Jul 24, 2018 16:35:48.429 [0x7fbcf03fe700] INFO - Processor Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
Jul 24, 2018 16:35:48.430 [0x7fbcf03fe700] INFO - /usr/lib/plexmediaserver/Plex Media Server
Jul 24, 2018 16:35:48.480 [0x7fbcfc487800] INFO - OCSP: Successfully retrieved response from cache.
Jul 24, 2018 16:35:48.482 [0x7fbcfc487800] INFO - OCSP: Successfully retrieved response from cache.
Jul 24, 2018 16:35:49.745 [0x7fbcda7fe700] INFO - LibraryUpdateManager path watching is disabled
Jul 24, 2018 16:35:49.972 [0x7fbcd87fd700] WARN - Sync: Couldn't get sync lists without subscription.
Jul 24, 2018 16:35:58.542 [0x7fbcfc487800] WARN - Timed out waiting for server to finish.
Jul 24, 2018 16:35:58.543 [0x7fbce5fff700] ERROR - Error issuing curl_easy_perform(handle): 52
Jul 24, 2018 16:35:58.543 [0x7fbce5fff700] WARN - HTTP error requesting POST http://127.0.0.1:32600/devices/discover (0, No error) (Empty reply from server)
Jul 24, 2018 16:35:58.543 [0x7fbce5fff700] ERROR - Error parsing content.
Jul 24, 2018 16:35:58.543 [0x7fbce5fff700] ERROR - Error parsing XML.
Jul 24, 2018 16:35:58.544 [0x7fbccdff9700] ERROR - Timeout or error reading status line from plug-in pipe [com.plexapp.agents.imdb], we're killing it.
Jul 24, 2018 16:35:58.544 [0x7fbccdff9700] ERROR - Error received reading configuration for com.plexapp.agents.imdb
Jul 24, 2018 16:35:58.544 [0x7fbccdff9700] ERROR - downloadContainer: expected MediaContainer element, found html
Jul 24, 2018 16:35:58.544 [0x7fbccdff9700] ERROR - IVA: failed to get IMDB prefs
Jul 24, 2018 16:35:59.542 [0x7fbcfc487800] WARN - Timed out waiting for server to finish.
Jul 24, 2018 16:36:00.162 [0x7fbce3ffe700] WARN - PubSubManager: Connection to 172.104.217.190 failed: Connection timed out.
Jul 24, 2018 16:36:00.162 [0x7fbce3ffe700] WARN - PubSubManager: Connection to 172.104.245.130 failed: Connection timed out.
Jul 24, 2018 16:36:00.162 [0x7fbce3ffe700] WARN - PubSubManager: Connection to 139.162.117.249 failed: Connection timed out.
Jul 24, 2018 16:36:00.162 [0x7fbce3ffe700] WARN - PubSubManager: Connection to 151.236.217.85 failed: Connection timed out.
Jul 24, 2018 16:36:00.162 [0x7fbce3ffe700] WARN - PubSubManager: Connection to 139.162.21.199 failed: Connection timed out.
Jul 24, 2018 16:36:00.162 [0x7fbce3ffe700] WARN - PubSubManager: Connection to 184.105.148.101 failed: Connection timed out.
Jul 24, 2018 16:36:00.162 [0x7fbce3ffe700] WARN - PubSubManager: Connection to 82.94.168.60 failed: Connection timed out.
Jul 24, 2018 16:36:00.162 [0x7fbce3ffe700] WARN - PubSubManager: Connection to 82.94.168.54 failed: Connection timed out.
Jul 24, 2018 16:36:00.162 [0x7fbce3ffe700] WARN - PubSubManager: Connection to 173.230.131.250 failed: Connection timed out.
Jul 24, 2018 16:36:00.162 [0x7fbce3ffe700] WARN - PubSubManager: Connection to 45.33.118.95 failed: Connection timed out.

Detailed log: https://pastebin.com/MRCz9SSy

4

Where is the section where PMS shows the ethernet adapters it finds in its startup scan?
Minimally it will report the loopback (lo) adapter at 127.0.0.1.

That’s missing.

Can you just go to Settings - Server - Help - Download Logs and attach the ZIP it gives you?

I’ll have the full view. It’ll be a lot easier than looking at snippets

5

Sure!
Plex Media Server Logs_2018-07-24_19-03-09.zip (616.0 KB)

Thank you

6

Thank you, that’s got it. :slight_smile:

I see two WAN IP addresses (Public Internet) defined. One is eth0, and the second is the alias address on eth0.1.

I’m also seeing Verbose logging. Can you turn that off please? We only use Verbose logging when there is need to see each individual mouse click or block of data sent to a player . It’s insanely verbose causing a lot of debugging data loss.

If this machine is in a datacenter (VPS, dedicated host, etc) then PMS is getting confused because of the routing (netstat -r).

PMS can’t decide, or has decided prematurely to select the wrong adapter due to startup delays of the host, nor is there any way to tell it, which adapter to use right now. One might be the hosting company’s internal net with no public route to pubsub (Publication Subsystem – how your server is registered as active in Plex.tv)

There is a change coming out in this next version which will finally give us that control in PMS. You will be able to tell it which ethernet adapter.

Do you find that sometimes it’s ok and other times it’s not?

7

Nice, that’s wonderful news.

Yes. Sometimes it just hangs, sometimes it streams just fine, sometimes it buffers, sometimes it’s unavailable from external network (red badge in the Network tab, although it’s perfectly accessible).

I’ll wait for the big change to come, hopefully it will fix all the issues i’m encountering!

Thank you very much.

8

You’re very welcome.

As FYI, I just got the latest build (checking a NAS issue prior to release). It’s that close to coming out to you in Plex Pass beta.

9

Nice! Can’t wait for it :slight_smile:

10

Any news for the coming update? Like, any ETA? Days? Weeks? Any page I can check for new releases and changelogs?

Thank you :slight_smile:

11

Yes.

PMS 1.13.5 has been released to Plex Pass.

12

Hello,
I’m sorry to tell you that even after the update, without any 2nd IP addresses, the problem persists and I can’t access Plex nor locally or remotely.

Same problem as already notified:

Aug 02, 2018 22:34:01.084 [0x7fed2dbfe700] WARN - PubSubManager: Connection to 139.162.115.125 failed: Connection timed out.
Aug 02, 2018 22:34:01.084 [0x7fed2dbfe700] WARN - PubSubManager: Connection to 139.162.195.42 failed: Connection timed out.
Aug 02, 2018 22:34:01.084 [0x7fed2dbfe700] WARN - PubSubManager: Connection to 139.162.54.192 failed: Connection timed out.
Aug 02, 2018 22:34:01.085 [0x7fed2dbfe700] WARN - PubSubManager: Connection to 184.105.148.102 failed: Connection timed out.
Aug 02, 2018 22:34:01.085 [0x7fed2dbfe700] WARN - PubSubManager: Connection to 82.94.168.47 failed: Connection timed out.
Aug 02, 2018 22:34:01.085 [0x7fed2dbfe700] WARN - PubSubManager: Connection to 82.94.168.55 failed: Connection timed out.
Aug 02, 2018 22:34:01.085 [0x7fed2dbfe700] WARN - PubSubManager: Connection to 45.79.197.109 failed: Connection timed out.
Aug 02, 2018 22:34:01.085 [0x7fed2dbfe700] WARN - PubSubManager: Connection to 45.33.118.95 failed: Connection timed out.
Aug 02, 2018 22:34:01.085 [0x7fed2dbfe700] WARN - PubSubManager: Connection to 172.104.216.121 failed: Connection timed out.
Aug 02, 2018 22:34:01.085 [0x7fed2dbfe700] WARN - PubSubManager: Connection to 172.104.133.220 failed: Connection timed out.
13

Would you be kind enough to do the following?

  1. Enable DEBUG logging (but not VERBOSE)
  2. Restart PMS to recreate / recapture the issue
  3. Gather and submit the ZIP file again?

I ask this because we made changes at PubSub and since you have 2 WAN addresses directly connected, I need to see how that works. You might need to use the new PMS 1.13.5 ‘bind’ feature to select only 1 ( It prevents this situation from happening)

14

Currently there is no way for me to access the server via web interface, as it simply won’t load (restarted server, pms service, etc). Any way to enable the DEBUG logging via console?

Thank you.

15

SSH-tunnel is your last remaining hope.

ssh -L 8888:127.0.0.1:32400 -l username_to_sign_in_as ip.addr.of.server

Once signed in, let the ssh session sit there.

In your browser, open http://127.0.0.1:8888/web

The SSH tunnel will redirect you to the loopback adapter on the server.

If you have trouble connecting / utilizing the console this way, you have a network issue at a much more basic level

16

I tunneled the port with PuTTY, PMS won’t answer and times out.
After 57 restarts of PMS I managed to enable the DEBUG logs, but I can’t download them.
I’ll just tar the “Logs” folder from the console and upload it.

Logs.tar (6.8 MB)

17

I ended up downgrading to the older version, 1.13.4.5271-200287a06 until you fix the issue.

Thank you very much for your help.

18

Your earlier logs were also 1.13.4.5271.

If the pubsub timeouts you posted previously are from 1.13.4, we’d like to see them.
We do prefer you use 1.13.5 which has several changes including the ability to select which adapter to use when communicating with Plex.tc

19

Will you please PM me your Prefereces.xmlfile?

We see a change and would like to confirm what your configuration actually is.

20

@t0rz

I’ve been going over your logs in greater detail.

I am concerned about the validity of the certificate you’re trying to install.

If you attempt to replace PMS’s cert with your own, PMS won’t work.
If you ADD your cert to PMS, validating both, it will work.

Can you validate your cert installation ?

Aug 03, 2018 01:16:31.422 [0x7f3a2ae49800] DEBUG - CERT: Installed certificate with fingerprint f9:85:54:bb:1b:8f:cb:66:fa:8d:82:ff:03:5e:9c:14:ac:b9:ef:7a.
Aug 03, 2018 01:16:31.422 [0x7f3a2ae49800] DEBUG - CERT: Installed new private key.
Aug 03, 2018 01:16:31.422 [0x7f3a2ae49800] DEBUG - CERT: Subject name is /C=US/ST=CA/L=Los Gatos/O=Plex, Inc./CN=*.dc346de1a61e4663a3a36ef907ec1954.plex.direct
Aug 03, 2018 01:16:31.422 [0x7f3a2ae49800] DEBUG - CERT: OCSP requests for stapling will be made to 'http://ocspx.digicert.com/'.
Aug 03, 2018 01:16:31.422 [0x7f3a2ae49800] INFO - OCSP: Successfully retrieved response from cache.
Aug 03, 2018 01:16:31.422 [0x7f3a2ae49800] DEBUG - CERT: Installed intermediate certificate.
Aug 03, 2018 01:16:31.423 [0x7f3a2ae49800] DEBUG - CERT: Loaded a user-provided certificate.
Aug 03, 2018 01:16:31.423 [0x7f3a2ae49800] WARN - CERT: Missing cert or issuer; skipping OCSP stapling
Aug 03, 2018 01:16:31.424 [0x7f3a2ae49800] DEBUG - HttpServer: Listening on port 32400 with queue of 128 connections.
Aug 03, 2018 01:16:31.424 [0x7f3a2ae49800] DEBUG - HttpServer: Listening on port 32401 with queue of 128 connections.
Aug 03, 2018 01:16:31.427 [0x7f3a1afff700] DEBUG - DVR:Grabber: Cleaning up orphaned grabs.
Aug 03, 2018 01:16:31.427 [0x7f3a2ae49800] DEBUG - Media Provider: Registering provider com.plexapp.plugins.library
Aug 03, 2018 01:16:31.427 [0x7f3a2ae49800] DEBUG - Auth: Refreshing tokens inside the token-based authentication filter.
Aug 03, 2018 01:16:31.427 [0x7f3a2ae49800] DEBUG - Relay: read 10 cached entries from hosts file

I’m wondering if PMS might not be handling certification failure fallback