I am seeing this issue immediately after upgrading to Version 1.5.0.3501. This behavior is not seen in prior versions.
I believe this is a minor issue. After upgrading to the 1.5.0.3501 release in the official plexinc/pms-docker:plexpass docker image, The following is recorded in the container logs:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 40-plex-first-run: executing...
[cont-init.d] 40-plex-first-run: exited 0.
[cont-init.d] 50-plex-update: executing...
Attempting to upgrade to: 1.5.0.3501-3b8374a5c
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 177 100 177 0 0 224 0 --:--:-- --:--:-- --:--:-- 224
100 100M 100 100M 0 0 561k 0 0:03:03 0:03:03 --:--:-- 769k
(Reading database ... 10923 files and directories currently installed.)
Preparing to unpack /tmp/plexmediaserver.deb ...
/var/lib/dpkg/info/plexmediaserver.prerm: 13: /var/lib/dpkg/info/plexmediaserver.prerm: stop: not found
Unpacking plexmediaserver (1.5.0.3501-3b8374a5c) over (1.4.4.3495-edef59192) ...
Setting up plexmediaserver (1.5.0.3501-3b8374a5c) ...
Processing triggers for systemd (229-4ubuntu13) ...
[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Starting Plex Media Server.
**Critical: libusb_init failed**
It does not appear, so far, that this actually affects plex operation, however my monitoring tools caught this, so I figured reporting it would be a good thing. I will post an update if I find it actually causes problems.
We are investigating this internally but for now it looks like there shouldn’t be much concern with the error message. It’s part of the system that handles USB-based HD HomeRun devices.
I’m getting this error now on the lateset plexpass docker on freenas corral, it won’t let me play most files via my amazon fire TV (some files work for some reason?) I can play most things through my browser, but other times not and plex just crashes.
[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Starting Plex Media Server.
Dolby, Dolby Digital, Dolby Digital Plus, Dolby TrueHD and the double D symbol are trademarks of Dolby Laboratories.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
Critical: libusb_init failed
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
that’s all that was in my log, which led me here and nowhere else really.
anyway, the latest plexpass version seems broken playing large >1gb files (or maybe certain file types? mkv?) it just stopped working after the last update. I’m running a normal Plex container along side it pointing to the same config locations so I can just switch between them when plexpass works again / doesn’t
i found in my log the same error message: “[s6-init] ensuring user provided files have correct perms.
…exited 0”
Sorry and i created for a view seconds this thread Click
@xic044 do you found an solution on your FreeNAS system?
I dont know how i can change the the tag from plexpass to the latest and back
It is not the update channel, in the PMS server settings?
Pukinator claims to have correct it by changing the Plex Container mode from plexinc/pms-docker:plexpass to plexinc/pms-docker:latest and back to plexinc/pms-docker:plexpass . What I didn’t figured out is how and where we should edit that…
Pukinator, can you describe how you edit that ( Forget I am in Freenas)… Most of us are very fresh to Docker containers…
@xic044 we are not in the correct forum
In the section FreeBSD i found something. The normal plex container will possible work and only the plexpass container has this issue.
The freenas image can only be change if u create a new container -.-
@x-Timmey-x said: @xic044 we are not in the correct forum
In the section FreeBSD i found something. The normal plex container will possible work and only the plexpass container has this issue.
The freenas image can only be change if u create a new container -.-
Thanks for the info… But the Docker host in the freenas is Ubuntu based (VM)… So if we knew how to edit the file as Pukinator did could solve the issue…
@x-Timmey-x said: @xic044 we are not in the correct forum
In the section FreeBSD i found something. The normal plex container will possible work and only the plexpass container has this issue.
The freenas image can only be change if u create a new container -.-
