I installed Version 1.15.1.707 earlier today and it is doing the same thing as *659… The server will just exit… and when trying to reboot it, it’s hit or miss if it reloads… (sigh). I run servers on two seperate machines setup the same way and they both do the same thing…
The question is, can I roll back to a version that wasn’t troublesome?
I am having the same issues where plex crashes between 1am-5am… I thought it was the scheduled tasks so i moved them to 9a-1pm… it still crashes randomly…
I updated the latest beta last night this morning it crashed about 445 (I have tautulli that shows the time something last played)
this is the logs during that time
Feb 22, 2019 03:39:29.331 [0x70000859a000] ERROR - [Transcoder] [mpeg4 @ 0x7fd1ef014c00] Either hw_frames_ctx or hw_device_ctx must be set.
Feb 22, 2019 03:39:29.332 [0x700008517000] ERROR - [Transcoder] [mpeg4 @ 0x7fd1ef014c00] Failed setup for format videotoolbox_vld: hwaccel initialisation returned error.
Feb 22, 2019 03:39:31.709 [0x700006d8d000] ERROR - EventSource: Retrying in 120 seconds.
Feb 22, 2019 03:57:48.188 [0x700008a35000] WARN - SLOW QUERY: It took 250.000000 ms to retrieve 1 items.
Feb 22, 2019 04:00:31.556 [0x7000068f2000] WARN - Got a request to stop a transcode session without a session GUID (or with an invalid one).
Feb 22, 2019 04:22:11.062 [0x700008517000] WARN - SLOW QUERY: It took 550.000000 ms to retrieve 33 items.
Feb 22, 2019 04:22:11.078 [0x7000068f2000] WARN - SLOW QUERY: It took 650.000000 ms to retrieve 41 items.
Feb 22, 2019 04:34:08.872 [0x70000732e000] ERROR - Failed to delete session directory (boost::filesystem::remove: No such file or directory: "/Users/sandd/transtemp/Transcode/Sessions/plex-transcode-4C2D6DB3-DC5A-48D1-BE7C-4374D773C346-0f7ba3e2-3eff-4a2a-bbfd-a57674768045/media-01089.ts")
Feb 22, 2019 04:39:24.387 [0x70000732e000] WARN - NAT: PMP, got an error: Not Supported by gateway.
Feb 22, 2019 04:39:25.897 [0x700006f16000] WARN - NAT: PMP, got an error: Not Supported by gateway.
Feb 22, 2019 04:40:37.905 [0x700007ff9000] WARN - SLOW QUERY: It took 290.000000 ms to retrieve 33 items.
Feb 22, 2019 04:40:37.923 [0x70000807c000] WARN - SLOW QUERY: It took 290.000000 ms to retrieve 50 items.
Feb 22, 2019 04:43:44.190 [0x700008829000] WARN - SLOW QUERY: It took 290.000000 ms to retrieve 41 items.
Feb 22, 2019 04:50:38.697 [0x7000086a0000] WARN - Waited one whole second for a busy database.
Feb 22, 2019 04:50:39.880 [0x7000086a0000] ERROR - Failed to begin transaction (../Statistics/StatisticsManager.h:201) (tries=1): Cannot begin transaction. database is locked
Feb 22, 2019 04:50:42.181 [0x7000086a0000] WARN - Waited one whole second for a busy database.
Feb 22, 2019 04:50:43.352 [0x7000086a0000] ERROR - Failed to begin transaction (../Statistics/StatisticsManager.h:201) (tries=2): Cannot begin transaction. database is locked
Feb 22, 2019 04:50:45.148 [0x7000086a0000] WARN - Waited one whole second for a busy database.
Feb 22, 2019 04:50:46.324 [0x7000086a0000] ERROR - Failed to begin transaction (../Statistics/StatisticsManager.h:201) (tries=3): Cannot begin transaction. database is locked
Feb 22, 2019 04:50:48.059 [0x7000086a0000] WARN - Waited one whole second for a busy database.
Feb 22, 2019 04:50:49.183 [0x7000086a0000] ERROR - Failed to begin transaction (../Statistics/StatisticsManager.h:201) (tries=4): Cannot begin transaction. database is locked
Feb 22, 2019 04:50:50.758 [0x7000086a0000] WARN - Waited one whole second for a busy database.
Feb 22, 2019 04:50:51.880 [0x7000086a0000] ERROR - Failed to begin transaction (../Statistics/StatisticsManager.h:201) (tries=5): Cannot begin transaction. database is locked
Feb 22, 2019 04:50:54.113 [0x7000086a0000] WARN - Waited one whole second for a busy database.
Feb 22, 2019 04:50:55.251 [0x7000086a0000] ERROR - Failed to begin transaction (../Statistics/StatisticsManager.h:201) (tries=6): Cannot begin transaction. database is locked
Feb 22, 2019 04:50:56.909 [0x7000086a0000] WARN - Waited one whole second for a busy database.
Feb 22, 2019 04:50:58.049 [0x7000086a0000] ERROR - Failed to begin transaction (../Statistics/StatisticsManager.h:201) (tries=7): Cannot begin transaction. database is locked
Feb 22, 2019 04:50:59.491 [0x7000086a0000] WARN - Waited one whole second for a busy database.
Feb 22, 2019 04:51:00.620 [0x7000086a0000] ERROR - Failed to begin transaction (../Statistics/StatisticsManager.h:201) (tries=8): Cannot begin transaction. database is locked
Feb 22, 2019 04:51:02.669 [0x7000086a0000] WARN - Waited one whole second for a busy database.
Feb 22, 2019 04:51:03.771 [0x7000086a0000] ERROR - Failed to begin transaction (../Statistics/StatisticsManager.h:201) (tries=9): Cannot begin transaction. database is locked
Feb 22, 2019 04:51:05.938 [0x7000086a0000] WARN - Waited one whole second for a busy database.
Feb 22, 2019 04:51:07.083 [0x7000086a0000] ERROR - Failed to begin transaction (../Statistics/StatisticsManager.h:201) (tries=10): Cannot begin transaction. database is locked
Feb 22, 2019 04:51:07.084 [0x7000086a0000] ERROR - Thread: Uncaught exception running async task which was spawned by thread 0x7000067ec000: Cannot begin transaction. database is locked
Well, sadly enough I woke up to one crashed server – Brainbuntu ■■■■ the bed during the morning. BearcubII is still working on the consolidated Classical library, not sure if it’s stuck with the Gracenote database again – the last time I built a big library, though, it took a while.
Logs for Brain attached. I haven’t even had my morning cuppa, yet (and I’m wishing I had hot chocolate, as we had a minor blizzard here in Tucson.)
Brainbuntu Plex Media Server 1511707.zip (270.7 KB)
And in case I do have the sticky library thing again, here’s logs for BearcubII as well.
Plex Media (8.4 MB)
These daily crashes are becoming quite annoying… Any movement on a fix? Installed 707 last night but it didn’t help…
1 Like
Yes, just run uninstall on 707, and then install 1.14.'s last non-Plex Pass version.
707 just crashed quietly on BearcubII. Interesting to me is that I was having it scan the BBC Classic library after I moved a folder from Classical to BBC Classical (where it really belonged.) It appeared to have gotten stuck scanning what is a small library, and then it quietly expired.
1 Like
Brainbuntu just crashed, right on time – seems to have gone down right after scheduled tasks started at 2am.Plex Media Server Logs_2019-02-23_02-40-46.zip (4.2 MB) (Edit to add: as soon as the logs were downloaded, down it went again. I’m turning scheduled tasks off.)Plex Media Server Logs_2019-02-23_02-50-44.zip (3.7 MB)
Over at Brainbuntu, meanwhile, things are presently stuck, again, on the Classical library (the consolidated one.) This may just be slow motion grrrrriiiiinnnnndddddding through, though after twelve hours of nothing happening, I’m getting antsy.
1 Like
…if uninstalling 707 and installing 1.14, will it impact all the configuration and libraries, meaning would I have to start from scratch building the server? If so, that would suck the wind out of the sails…
installed when it released - had a crash at 1 am
Definitely isn’t as bad as the old version but definitely going down
I believe mine went down at scheduled tasks also
No, all the configuration and library data persists, so 1.14 will pick it right up. I just did a rollback myself (followed by updating to 707.)
One more person here reporting 1.15.1.707 on Windows 7 was crashing. I downgraded to 1.14.1.5488 and it’s stable so far. I would like to note that thousands of new library files were added under 1.15.1.707 because it seems to disregard previously working “.plexignore” files.
1 Like
BearcubII went down during the night, after I stopped Classical’s library scan and let it move to Classical II, which also thrashed without seeming to do much of anything. Looking at the Task Manager, the Plex Media Scanner was still up (though I’d had a crash alert saying it had stopped), the usual Plex Script Host entries, and…Plex Transcoder, sucking up 48% of the CPU cycles. Not sure why it was thrashing like that, but I suspect something in Zmisc tried to eat it.
1 Like
it does appear to point to an issue injected in the Plex Media Scanner after the 12/18 PMS release linked with database wait occurrences; hoping data provided to Plex Devs will help to resolve ASAP.
note; able to cause a crash on demand by manual starting a library scan and the subsequent database waits that come with it…
BearcubII fell down went boom when starting a library scan of Classical, after completing a scan of Classical II. Logs are logged.
1 Like
The “Music: Classical” library is definitely refusing to update, so I’m taking the drastic step of deleting it altogether and replacing it with “Music: Classical I” to see if that does any better.
I’m wondering if there’s an upper limit to the number of entries an individual library can sustain…
Hmmm, well my Photo library currently has 24223 entries…
Correction…my Photo library has 24391 entries…
54,391 tracks in my various artists library.
I’ll have a readout on Classical I when it’s done updating, but it may be a while.
The more examples I see of the crashes the better. So please logs with debug logging enabled beforehand and logs downloaded after restarting following a crash together with export of Windows Application Event Log export of all Event IDs 1000 and 1001 and giving me the date and time of either the last or first exported event
