- Minor
despite putting --no-healthchecks being added to the containers advanced settings I am still having to restart Plex so many times a day to get it working for 5 or 10 min
the cache pool is on ZFS and these issues have started since converting to ZFS on 6.12.2 and persist in 6.12.3 whats going on please help.
this is driving me crazy as I am out and about and have to remote in to restart it when family and friends tell me it is not working again
docker logs for plex are useless and say nothing is wrong here is what is coming through while its down uptime kuma and paid service uptime robot do not detect out on port 32400 through its monitoring service
[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] 45-plex-hw-transcode-and-connected-tuner: executing...
[cont-init.d] 45-plex-hw-transcode-and-connected-tuner: exited 0.
[cont-init.d] 50-plex-update: executing...
[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting Plex Media Server.
[services.d] done.
Dolby, Dolby Digital, Dolby Digital Plus, Dolby TrueHD and the double D symbol are trademarks of Dolby Laboratories.
Critical: libusb_init failed