ive been using plex docker for some time no with no issues. a few months ago it started timing out whenever I did library updates(it had a higher chance of timing out if I did a full library update over just doing once specific category).

 

I tried changing to the new official plex docker and migrated my files over to it so I wouldn't have to reimport, the problem persisted, so I then wiped all the plex docker files and started fresh. still having same issue. when I check the logs all it shows is

 

Sqlite3: Sleeping for 200ms to retry busy DB.

 

and it keeps printing/scrolling that message until I restart the plex docker.

 

any ideas?

 

note: Issues started on 6.2, persisted to 6.3 as well

 

 

You will probably have to take this to the support thread of the docker you are using or to the plex forums for support.  This is the general unRAID support section.....

the issue happens across 2 different plex dockers so thought maybe someone here might know if its actually the docker or not

ive been using the linuxserver.io plex docker for some time no with no issues. a few months ago it started timing out whenever I did library updates(it had a higher chance of timing out if I did a full library update over just doing once specific category).

 

I tried changing to the new official plex docker and migrated my files over to it so I wouldn't have to reimport, the problem persisted, so I then wiped all the plex docker files and started fresh. still having same issue. when I check the logs all it shows is

 

Sqlite3: Sleeping for 200ms to retry busy DB.

 

and it keeps printing/scrolling that message until I restart the plex docker.

 

any ideas?

 

note: Issues started on 6.2, persisted to 6.3 as well

ive been using the linuxserver.io plex docker for some time no with no issues. a few months ago it started timing out whenever I did library updates(it had a higher chance of timing out if I did a full library update over just doing once specific category).

 

I tried changing to the new official plex docker and migrated my files over to it so I wouldn't have to reimport, the problem persisted, so I then wiped all the plex docker files and started fresh. still having same issue. when I check the logs all it shows is

 

Sqlite3: Sleeping for 200ms to retry busy DB.

 

and it keeps printing/scrolling that message until I restart the plex docker.

 

any ideas?

 

note: Issues started on 6.2, persisted to 6.3 as well

Unlikely to be an issue with this docker, especially since you say you have the same problem with another plex docker. Maybe an issue with the plex code itself, but more likely you have some other problem such as disk I/O issues, filesystem corruption, or underperforming hardware. We would have to see a diagnostic.

ive been using the linuxserver.io plex docker for some time no with no issues. a few months ago it started timing out whenever I did library updates(it had a higher chance of timing out if I did a full library update over just doing once specific category).

 

I tried changing to the new official plex docker and migrated my files over to it so I wouldn't have to reimport, the problem persisted, so I then wiped all the plex docker files and started fresh. still having same issue. when I check the logs all it shows is

 

Sqlite3: Sleeping for 200ms to retry busy DB.

 

and it keeps printing/scrolling that message until I restart the plex docker.

 

any ideas?

 

note: Issues started on 6.2, persisted to 6.3 as well

 

So which version are you currently using?  Although I agree 100% with trurl's comments above.

currently using the official plex docker. the hardware is decent, ive deleted the whole file system and started over, issue persists.

 

possible the cache drive is going bad i suppose, its just weird that the issue is ONLY when i click update on plex

 

is there a unraid diag tool that works from within unraid, or should i just run dft on the drive?

 

Intel® Xeon® Processor E5620

supermicro x8dti-f motherboard

(12M Cache, 2.40 GHz, 5.86 GT/s Intel® QPI)

24gb memory

 

 

currently using the official plex docker. the hardware is decent, ive deleted the whole file system and started over, issue persists.

 

possible the cache drive is going bad i suppose, its just weird that the issue is ONLY when i click update on plex

 

is there a unraid diag tool that works from within unraid, or should i just run dft on the drive?

 

Intel® Xeon® Processor E5620

supermicro x8dti-f motherboard

(12M Cache, 2.40 GHz, 5.86 GT/s Intel® QPI)

24gb memory

 

Like trurl says it's likely to be a problem with your system rather than the Plex docker, also we don't support the official container, only our own version.  Post some diagnostics here, and if that shows issues then probably best to open a thread in the general section.

cool thanks, i just figured since the issue happened on both versions, might be a better chance of someone else have experienced it here over the newer docker from plex. i have been wanting to replace the cache drive with an SSD...maybe its time to try that

 

Don't just replace hardware empirically, figure out the issue first.

I have merged your posts from the linuxserver.io plex thread back into this one since it isn't really about a particular docker.

 

is there a unraid diag tool that works from within unraid, or should i just run dft on the drive?

 

The diagnostics we have been asking for is the complete zip file you get when you go to Tools - Diagnostics.