Everything will work fine for a few minutes, then it freezes. I’m wondering if the problem is because the /tmp folder still has some old permissions or DB locks. I just rebooted the server. I’m hoping that’s it. I’ll provide logs if it happens again.
I feel so stupid. I think Plex was optimizing database shortly after Plex was restarted.
When I viewed the logs just now with tail -f, I could see it was trying to optimize the database. It was just taking forever before, and that’s why it was frozen for so long. After I ran the DBRepair the optimization ran a little faster. It basically unfroze when the optimization was done.
Now I know better that I need to check the Plex logs directly instead of just journalctl. It would be nice if the progress to a database optimization or database migration was outputted into syslog/journalctl.
Haha, no, actually, the local browser for 32400 was completely frozen. It wasn’t migrating. It was optimizing, and I suppose it only shows the maintenance message when it’s migrating.
I’m sure this was never a concern normally because this optimization would only last a few seconds. But for very large databases it can lock everything up for a few minutes until it’s completed.
But, yeah! I should have checked the plex logs. I swear I waited! I knew that sometimes it performs some maintenance tasks when plex starts, but it was taking too long, and everything was frozen. If I just checked the logs itself I would’ve seen that it was doing stuff! Haha, I’m just relieved it’s working!
you do have a choice which you can set in the override.conf
There is one caveat… If you switch to using syslog/journal, then the burden of providing CLEAN plex logs is on you. We won’t sit there and filter through the pile of messages for you LOL
lol )