plex server go's down every time library scans

daveftw84

Legendary Member
Original poster
Donor
Local time
11:18 PM
Jan 18, 2018
270
33
everytime my server is scaning the library , my plex server go's down for a little bit then comes back online.
 

Admin9705

Administrator
Project Manager
Local time
2:18 AM
Jan 17, 2018
4,798
1,848
everytime my server is scaning the library , my plex server go's down for a little bit then comes back online.
Ya that’s new to me. We havent changed anything in Plex. Have you run a test vm to see if you get the same issue?
 

nickeveli

Junior Member
Local time
6:18 PM
Apr 28, 2018
16
4
I'm having the same issue--when PLEX begins a library scan, streams go down and I can't access any other containers except via SSH (which is quite slow to respond as well).

PG is running on a 4-core VPS with 8GB RAM.

PS I love PG! :)
 
  • Like
Reactions: Admin9705

Admin9705

Administrator
Project Manager
Local time
2:18 AM
Jan 17, 2018
4,798
1,848
I'm having the same issue--when PLEX begins a library scan, streams go down and I can't access any other containers except via SSH (which is quite slow to respond as well).

PG is running on a 4-core VPS with 8GB RAM.

PS I love PG! :)
Try a custom tag to see if it's a version issue.
 

daveftw84

Legendary Member
Original poster
Donor
Local time
11:18 PM
Jan 18, 2018
270
33
increasing the open file limit helped but im still seeing this in log and my server went down once today..

Sqlite3: Sleeping for 200ms to retry busy DB.,
Sqlite3: Sleeping for 200ms to retry busy DB.,
Sqlite3: Sleeping for 200ms to ret[cont-finish.d] executing container finish scripts...,
[cont-finish.d] done.,
[s6-finish] syncing disks.,
[s6-finish] sending all processes the TERM signal.,
Critical: libusb_init failed,
[s6-finish] sending all processes the KILL signal and exiting.,
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.,
[s6-init] ensuring user provided files have correct perms...exited 0.,
[fix-attrs.d] applying ownership & permissions fixes...,
[fix-attrs.d] done.,
[cont-init.d] executing container initialization scripts...,
[cont-init.d] 40-plex-first-run: executing... ,
[cont-init.d] 40-plex-first-run: exited 0.,
[cont-init.d] 50-plex-update: executing... ,
[cont-init.d] 50-plex-update: exited 0.,
[cont-init.d] done.,
[services.d] starting services,
[services.d] done.,
Starting Plex Media Server.,
Dolby, Dolby Digital, Dolby Digital Plus, Dolby TrueHD and the double D symbol are trademarks of Dolby Laboratories.,

---- Automatically Merged Double Post ----

the log is filled with 100s of these
Sqlite3: Sleeping for 200ms to retry busy DB.,
Sqlite3: Sleeping for 200ms to retry busy DB.,
 
Last edited:

Admin9705

Administrator
Project Manager
Local time
2:18 AM
Jan 17, 2018
4,798
1,848
increasing the open file limit helped but im still seeing this in log and my server went down once today..

Sqlite3: Sleeping for 200ms to retry busy DB.,
Sqlite3: Sleeping for 200ms to retry busy DB.,
Sqlite3: Sleeping for 200ms to ret[cont-finish.d] executing container finish scripts...,
[cont-finish.d] done.,
[s6-finish] syncing disks.,
[s6-finish] sending all processes the TERM signal.,
Critical: libusb_init failed,
[s6-finish] sending all processes the KILL signal and exiting.,
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.,
[s6-init] ensuring user provided files have correct perms...exited 0.,
[fix-attrs.d] applying ownership & permissions fixes...,
[fix-attrs.d] done.,
[cont-init.d] executing container initialization scripts...,
[cont-init.d] 40-plex-first-run: executing... ,
[cont-init.d] 40-plex-first-run: exited 0.,
[cont-init.d] 50-plex-update: executing... ,
[cont-init.d] 50-plex-update: exited 0.,
[cont-init.d] done.,
[services.d] starting services,
[services.d] done.,
Starting Plex Media Server.,
Dolby, Dolby Digital, Dolby Digital Plus, Dolby TrueHD and the double D symbol are trademarks of Dolby Laboratories.,

---- Automatically Merged Double Post ----

the log is filled with 100s of these
Sqlite3: Sleeping for 200ms to retry busy DB.,
Sqlite3: Sleeping for 200ms to retry busy DB.,
---- Automatically Merged Double Post ----

@daveftw84 u might have to the linxserver server io team or plex. I don't have this issue, but it's plex related. I did some light research, but nothing comes from our part.

---- Automatically Merged Double Post ----

@daveftw84 u might have to the linxserver server io team or plex. I don't have this issue.

can check this https://forums.plex.tv/discussion/296424/unraid-plex-crashing-with-sqlite3-sleeping-for-200ms-to-retry-busy-db
 
Last edited:

wuffers

Junior Member
Local time
2:18 AM
Dec 30, 2018
8
5
Sorry to necro this old thread.. but I think I found the issue.

Plex would sometimes die on me in my deployment, and logs would show this:
[s6-finish] sending all processes the TERM signal.
Critical: libusb_init failed
[s6-finish] sending all processes the KILL signal and exiting.


So the important thing here is the "Critical: libusb_init failed", which sends a KILL signal to Plex.

OP did not mention which Plex version he's using, but I suspect everyone here is using the "latest" tag for Plex, and not using "plexpass" version, and won't see the issue at all. I am using plexpass version, and the tuner service is enabled by default, which uses libusb.

I disabled the tuner and killed the service by just renaming the folder:
Bash:
docker exec plex mv -f "/usr/lib/plexmediaserver/Plex Tuner Service" "/usr/lib/plexmediaserver/Plex Tuner Service DISABLED"
kill $(docker top plex | grep 'Plex Tuner Service' | awk '{print $2}')
This might be some script code you add if the user selects plexpass (or an additional option for it). Is anyone using a docker deployment of plex and using a tuner? I believe the port that it starts is 32600 and it's not even mapped on the plex container.
 

fr0sty

Senior Member
Staff
Donor
Local time
5:18 PM
Jul 8, 2018
135
33
Australia
So libusb_init failed happened to me today. Never see this before and do run the plexpass tag.

Bash:
docker exec plex mv -f "/usr/lib/plexmediaserver/Plex Tuner Service" "/usr/lib/plexmediaserver/Plex Tuner Service DISABLED"
kill $(docker top plex | grep 'Plex Tuner Service' | awk '{print $2}')
I can run the first line ok but the second line with sudo throws

Got permission denied while trying to connect to the Docker daemon socket at uni x:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/plex/top: dial unix /var/run/docker.sock: connect: permission denied

I dont have a tuner so this "feature" (bug) is not required
What is the difference between /latest and /plexpass tags? If i reinstall will i loose any other function or features?
 

eclipseserena

Full Member
Local time
2:18 AM
Oct 25, 2018
45
3
I am running into this today same critical error libusb_init failed using plexpass version
 

hooper

Legendary Member
Staff
Donor
Local time
11:18 PM
Aug 1, 2018
310
116
Sorry to necro this old thread.. but I think I found the issue.

Plex would sometimes die on me in my deployment, and logs would show this:
[s6-finish] sending all processes the TERM signal.
Critical: libusb_init failed
[s6-finish] sending all processes the KILL signal and exiting.


So the important thing here is the "Critical: libusb_init failed", which sends a KILL signal to Plex.

OP did not mention which Plex version he's using, but I suspect everyone here is using the "latest" tag for Plex, and not using "plexpass" version, and won't see the issue at all. I am using plexpass version, and the tuner service is enabled by default, which uses libusb.

I disabled the tuner and killed the service by just renaming the folder:
Bash:
docker exec plex mv -f "/usr/lib/plexmediaserver/Plex Tuner Service" "/usr/lib/plexmediaserver/Plex Tuner Service DISABLED"
kill $(docker top plex | grep 'Plex Tuner Service' | awk '{print $2}')
This might be some script code you add if the user selects plexpass (or an additional option for it). Is anyone using a docker deployment of plex and using a tuner? I believe the port that it starts is 32600 and it's not even mapped on the plex container.
use sudo and the commands should work
 

ThomasDev

Junior Member
Local time
2:18 AM
Jan 14, 2019
13
7
This happened to me on my Hetzner dedicated server.

I re-installed, disabled software raid completely and mounted my second hard drive under /mnt as documented how in the wiki. I have not had any problems since.

2nd HD option wiki
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads


Members online

Maintenance Donations

Recommend NewsGroups

      Up To a 58% Discount!

Trending