When Push Notifications are enabled, the server locks up

Server Version#: 1.31.2.6715 (running this version because of the ongoing issues in this thread, but regardless it affects all builds of Plex I’ve tried in the last few years)
Player Version#: (doesn’t matter)

Issue described pretty well by this reddit user and replicated by several others. This has been the only workaround for the lockup issue, I’ve been looking for one for a long time!

If you are like me and have been dealing with servers becoming unresponsive, database deadlocks and long running queries - try disabling Push Notifications

Basically what I experience is, whenever any somewhat large amount of media is added or rescanned, a single thread will be loaded (visible with e.g. top command) and the rest of the plex services will be starved of resources, barely using any CPU when they should be using way more. Due to the single thread load and correlation with media being added, it would seemingly be due to sqlite db locking + slow single thread task, but I have no idea if that is actually the culprit and surely those with access to the notifications code can tell haha.

I have logs I can send to any plex rep via PM. When I experienced the lockup issue, I unchecked the setting (in General > Push Notifications) as suggested by the reddit post and the server returned to a usable state, then I clicked Download Logs.

PM sent.

1 Like

Hi there,

On my server, this is off since day one, so unfortunately, it will not solve my issue, but thanks for sharing! :wink:

1 Like

Haha yes, that is true Franck! If you already have it disabled then I don’t think it will help. Are you affected by this as well even with that setting off, where one thread is under 100% load and the plex ui is unresponsive?

We need be careful here. “… long running queries…”

There is a bug with Plex/web.

If the first word in the search is “The”. “A”. etc (determiner words), the search will not return results unless you wait “forever”

Drop “the” from the search and results are immediate.

Yes, there are definitely issues with search haha, such as the display saying there are no results and then waiting a bit longer only for them to appear!

That quote from the linked reddit user describes how they experienced improvements to those problems by disabling notifications. For me the main issue of those that I’ve experienced is the one about Plex becoming unresponsive. That seems to correlate with a single thread being loaded inexplicably sometimes, and disabling the notifications option also seems to help.

H,

No, Plex was never unresponsive “so to say” but I noticed since the beginning of this thread Plex being in high CPU usage when I was asking for a movie/serie in Web client. But it was transcoder process that was taking all the CPU (despite I have a GPU).

Regarding the transcoding running —

Please look at the priority of the process.

Foreground jobs are run at 20.

Background jobs are run lower (25+)

Please let me know what you find.

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