@ChuckPa any info on the link that I mentioned about the statistics table being the culprit?
Unfortunately no. I don’t get into depth.
That’s also rather extreme too
There was a recent update to PMS (since 1.24.3.5033) which corrects all those extra records.
You might want to update to current and lt it clean the junk back out
I opened a new thread not noticing this one was already here, but getting a load of this too on a brand new install.
Server was installed from scratch on a docker container and a new library was added.
Logs attached.
@ChuckPa
Im still having locking issues. I just updated to 1.25.05220 and seeing plenty of:
- waited for a whole second for a busy database
- took to long to start a transaction
- failed to begin transaction database is locked
Some of the log entries are saying they are waiting as high as 11 seconds.
Prior to installing the latest beta build I did an offline disk defrag and full window update.
After installing the update I did a clean bundles and a database optimization and Im still seeing these errors. I currently have 0 users watching content and nothing being recorded and Im seeing this slowness in the logs. My Plex database and metadata directory are on a RAID 1 Enterprise SAS SSD.
Personally?
Back down to previous stable. This group of betas have issues
I cant remember what version that was now. Better yet…what is the ETA for this issue being fixed?
ETA? Given the time of year and upcoming holiddays, I would ETA – January 2022. (being realistic)
I would go back to build 5173. You still do have those install files ?
This is the time when you want the machine stable — Priority 1.
There are some vague reports of 5246 fixing certain problems but I don’t know which issues were fixed.
this one? 1.24.5.5173-8dcc73a59
checking
Yes, that one – OR –
My production server is running 1.24.2.4973-2b1b51db9
can you send me the link for 1.24.2.4973-2b1b51db9?
@ChuckPa do you have an updated ETA on when this will be fixed? I see that there have been several releases since the version that I started having issues with. None of the new releases mention database lock issues being resolved.
Sorry i didn’t get notified.
There is a new work being done now to clean up the database which is the problem here.
We’re testing it with a few users . It is looking very promising.
If the progress is as I think, Engineering will probably release it to everyone when they return after the holiday
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
