Removing music library path while dvr recording blocks recording

Live TV & DVR
1

Server Version#: plexmediaserver_1.18.2.2041-3d469cb32_amd64
Player Version#:

my (large) music library had multiple paths

while a dvr recording was in progress, I edited the music library and removed one of the paths (no longer used).

changes could not be saved, but I could see the log (tail -F) was destroying metadata items, and stopped showing the in progress transcoding/recording for the dvr.

additionally, plex web no longer responded.

Meanwhile the server process was still running and the log is continuing to destroy metadata items, until it stopped and started doing this repeatedly.

Nov 20, 2019 19:02:04.842 [0x7f81137fe700] DEBUG - HTTP requesting GET http://192.168.168.108:80/discover.json
Nov 20, 2019 19:02:04.844 [0x7f81137fe700] DEBUG - HTTP 200 response from GET http://192.168.168.108:80/discover.json
Nov 20, 2019 19:02:04.844 [0x7f81137fe700] DEBUG - HTTP requesting GET http://192.168.168.108:80/lineup_status.json
Nov 20, 2019 19:02:04.855 [0x7f81137fe700] DEBUG - HTTP 200 response from GET http://192.168.168.108:80/lineup_status.json
Nov 20, 2019 19:02:07.868 [0x7f81277fe700] DEBUG - HTTP requesting GET http://192.168.168.108:80/discover.json
Nov 20, 2019 19:02:07.870 [0x7f81277fe700] DEBUG - HTTP 200 response from GET http://192.168.168.108:80/discover.json
Nov 20, 2019 19:02:07.870 [0x7f81277fe700] DEBUG - HTTP requesting GET http://192.168.168.108:80/lineup_status.json
Nov 20, 2019 19:02:07.882 [0x7f81277fe700] DEBUG - HTTP 200 response from GET http://192.168.168.108:80/lineup_status.json
Nov 20, 2019 19:02:07.895 [0x7f81277fe700] DEBUG - Activity: updated activity 63e8def8-565d-404b-b37f-1c9583e4238e - completed 5.0% - Recording
Nov 20, 2019 19:02:10.895 [0x7f8112ffd700] DEBUG - HTTP requesting GET http://192.168.168.108:80/discover.json
Nov 20, 2019 19:02:10.897 [0x7f8112ffd700] DEBUG - HTTP 200 response from GET http://192.168.168.108:80/discover.json
Nov 20, 2019 19:02:10.898 [0x7f8112ffd700] DEBUG - HTTP requesting GET http://192.168.168.108:80/lineup_status.json
Nov 20, 2019 19:02:10.909 [0x7f8112ffd700] DEBUG - HTTP 200 response from GET http://192.168.168.108:80/lineup_status.json
Nov 20, 2019 19:02:13.923 [0x7f8126ffd700] DEBUG - HTTP requesting GET http://192.168.168.108:80/discover.json
Nov 20, 2019 19:02:13.925 [0x7f8126ffd700] DEBUG - HTTP 200 response from GET http://192.168.168.108:80/discover.json
Nov 20, 2019 19:02:13.925 [0x7f8126ffd700] DEBUG - HTTP requesting GET http://192.168.168.108:80/lineup_status.json
Nov 20, 2019 19:02:13.936 [0x7f8126ffd700] DEBUG - HTTP 200 response from GET http://192.168.168.108:80/lineup_status.json
Nov 20, 2019 19:02:16.950 [0x7f81267fc700] DEBUG - HTTP requesting GET http://192.168.168.108:80/discover.json
Nov 20, 2019 19:02:16.952 [0x7f81267fc700] DEBUG - HTTP 200 response from GET http://192.168.168.108:80/discover.json
Nov 20, 2019 19:02:16.952 [0x7f81267fc700] DEBUG - HTTP requesting GET http://192.168.168.108:80/lineup_status.json
Nov 20, 2019 19:02:16.963 [0x7f81267fc700] DEBUG - HTTP 200 response from GET http://192.168.168.108:80/lineup_status.json
Nov 20, 2019 19:02:19.977 [0x7f8110ff9700] DEBUG - HTTP requesting GET http://192.168.168.108:80/discover.json
Nov 20, 2019 19:02:19.978 [0x7f8110ff9700] DEBUG - HTTP 200 response from GET http://192.168.168.108:80/discover.json
Nov 20, 2019 19:02:19.979 [0x7f8110ff9700] DEBUG - HTTP requesting GET http://192.168.168.108:80/lineup_status.json

finally I stopped plex, confirmed all plex processes were gone, then started pms again.

2

CPU info?
Debug log files please?

It sounds like the database activity and the disk i/o was too much for the system to keep up with .

The logs should shine some light on this.

3

duno if these will be helpful or not, from after shutting pms down then restarting and re-attempting.

Kernel and CPU Linux 5.0.21-3-pve on x86_64
Processor information Intel® Xeon® CPU E5-2630L v2 @ 2.40GHz, 24 cores

64g ram

~200k tracks being removed from music library path

I understand that is a lot of processing, the main point is that operation blocked most everything else.

Plex Media Server Logs_2019-11-20_20-54-31.zip (6.6 MB)

4

Afraid I can’t help. Proxmox is a distro I have no experience with. It’s also not officially supported.

I can only direct you to their forums or to search here for possibly related threads.

5

proxmox is debian

6

Proxmox is a whole different mechanism.
Sorry, but it’s not supported.

Debian is. Ubuntu is. Proxmox isn’t.

I am working on a lot of packaging changes. Maybe, when I’m done, Proxmox will be supportable but I won’t know until then.

7

This is the most information I have on Proxmox.

It is user contributed.

8

proxmox is debian buster with a lts kernel for virtualization, but ok not gonna argue the differences, in any case, this doesn’t have anything to do with proxmox/debian, it has to do with how plex adds/removes items from the database.

I am not running plex in a vm or container, its running on bare metal, with the DEB from plex downloads, just like any debian install, and I’ve been running it like this for years with no support issues.