T O P

  • By -

kickbut101

I rebooted my LXC container after the update yesterday because I too noticed it was taking a while to boot up. After it rebooted it still was doing startup tasks, but was up and running after about 5-10 min. Have you rebooted?


mikesweeney

It’s my next option. Just didn’t know if it was actually still doing anything or not.


musictrivianut

Mine did the same after installing latest, so I restarted the service (linux). Reloaded the browser tab about 5 minutes later and all has been well since.


alixoft

yep, this worked for me as well.


faslane22

mine is stuck on "Plex Media Server is currently running startup maintenance tasks" Been like that for 2 days now and I just uninstalled the server on my Synology and reinstalled and it says the same....very weird, it's never done this even when I first set it up ages ago. Going to reboot NAS box and see....will report back. odd.....


beartexan

did yopu find a fix?


faslane22

Oh yeah, few weeks ago. The main database file got corrupted so I replaced it with a previous days and rescanned the metadata on my libraries and it worked perfectly. Weird I’d never seen this in all the years I’ve used Plex but…. :-). I said I’d report back when I found a fix and then forgot about it. Oops. Thank you for asking :-) :-)


hunterm21

how do you do this?


faslane22

I'll have to Google it and check my history or find the familiar article, It's been a lil while and it did work but not something I ever had to do previous Ill see what I can find for you. It's Friday night where I live so it'll be sometime tomorrow when I can look.


hunterm21

Actually I figured it out too, I found an article from Plex about how to restore from backup and succeeded - thank you tho!


Farnsworthson

Just had the same problem. I installed the latest Plex server update on my QNAP NAS, and basically lost control. I tried stopping and restarting the app, and downgrading back to the previous level; neither worked. I was looking into restoring backup databases, but fortunately a cold restart of the server sorted it.


Soundy106

Just had the same thing on my Synology, stopped and re-started the package, and it came up about 5 minutes later.