please @sa2000 can i have the dev build?
Yes I can see that your server has been getting these crashes
Added you to the set of users trying out 1.16.0.1181
could i have the dev build as well server is crashing every couple of days
same crashes
done
The one that was fixed in the last PMS update. Unfortunately I can’t use that version because it crashes even more.
Yes I do. I run three seperate bare bones Ubuntu 18.04 installations that only run PMS and Plex crashes on all of them randomly.
You’ve received plenty of logs from customers unable to use your product in its current guise.
I can’t see the harm in the Plex Devs spinning up PMS on a variety of OS’s, so they can experience the issue directly, rather than obligating your paying customers to beta test your software and submit logs.
Relying on your customers as the sole beta testers of your software software is fine for free Open Source, but for a private company charging for their proprietary product? A bit of proactive investigation wouldn’t go astray.
Particularly when the product is in such a state that it can’t be used at all without crashing multiple times a day.
Yes I do. I run three seperate bare bones Ubuntu 18.04 installations that only run PMS and Plex crashes on all of them randomly.
The crash is triggered by random circumstances aligning involving multiple users, streaming from multiple devices, at multiple times, from multiple locations. The crash doesn’t happen to an idle server. A small team of developers can’t test for every imaginable scenario that could trigger a crash. The only way to get that kind of data is through real world usage. Even Tesla has to kill a few of their drivers before the Autopilot bugs are all sorted out. Even Boeing had to fly a couple of passenger airliners into the ground to fix their software bugs.
I can’t see the harm in the Plex Devs spinning up PMS on a variety of OS’s, so they can experience the issue
Yeah I’m sure nobody at Plex uses or tests their software. /s
obligating your paying customers to beta test your software
Paying a paltry amount of money for a few extra features in a freemium software does not entitle you any kind of SLA. Get real buddy.
private company charging for their proprietary product
Puh-lease. Their “proprietary product” is free and I would wager that less than 10% of their total users actually pay anything to Plex inc. Bugs have always existed in the software. Did you think that paying for Plex Pass features would suddenly prevent future bugs?
2 Likes
I am also having the same issue, only on a Fedora 29 system. Just collected a set of logs from the system after restarting. I’d enjoy testing the dev build too.
One thing that would also be very nice to have is that the PMS process exit after a crash so that systemd can restart it, as it’s listed in the current unit file. It seems that since the parent process, “Plex Media Server” doesn’t actually die when the crash happens, systemd is unable to restart it, which the unit file indicates that is what will happen when the process exits, segfaults, etc.
1 Like
Lets agree to disagree. Getting off topic.
Hopefully Plex fixes the Linux PMS soon.
yes - similar crashes. Info sent to you
I’m having similar crashes too. I’m running on Ubuntu 18.10.
Had been running lovely for a couple of months, until a few weeks ago - potentially when it updated from 1.14.x to 1.15.x ?
I have confirmed you had the same crashes
Sent you info for 1.16.0.1181-9505422cd
1 Like
@sa2000 as a side note, whilst experiencing these crashes I found the CrashUploader process also caused me more issues post-crash.
Is there a way (for Plex devs) to fully detach the CrashUploader process so that systemctl commands still work to stop/start the process without waiting for/affecting the CrashUploader process?
I ended up forcably killing all processes and spawning my own CrashUploader with the logs independently, but it would be nice if Plex did this itself
Blockquote double free or corruption (!prev)
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.15.8.1163-005053bb5/PLEX MEDIA SERVER/272749e2-7b41-43f0-705ccebc-764c2f5c.dmp
Connection to xxx.xxx.xx.xxx closed by remote host.
Connection to xxx.xxx.xxx.xx closed by remote host.
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
s6-svwait: fatal: timed out
[s6-finish] sending all processes the TERM signal.
Critical: libusb_init failed
[s6-finish] sending all processes the KILL signal and exiting.> Blockquote
Had another crash. It at least took a while this time. I check that file that it says the crash report wrote to but it is a 0kb file. Please let me know if I can provide you with any more info to help get this resolved.
The logs with debug enabled before hand would show if it crashed soon after coming to an end of a transcoded playback - which would be circumstancial evidence that it is the same issue that is being addressed
I am having the same issues on Unraid. Several crashes a dayPlex Media Server Logs_2019-06-07_06-11-28.zip (3.8 MB)
I can see similar crashes. As we have not had any repeats from users running a development build, this should be fixed in release 1.16.0.xxx which is currently in QA
As you are using a docker image, it would not be straightforward to offer you and get you to install a pre release build
I’ve got this problem too, is there already a fix for it?
I can confirm that your server had these crashes
I think it is fixed as i have not seen a repeat yet from the users testing out latest development builds for this.
I have added you to the message with the link to the 1.16.0.1181 .deb download for linux ubuntu
I rolled back to an older version (1.14.1.5488) to address these crashes. Do I need to go back to the buggy version to have access to the beta build?
Confirming that you had these crashes. I have added you to the set of users trying the fix in 1.16.0.1181
