Server Version#: 1.41.3.9314
Player Version#: 4.141.0
My Plex Media Server is running in docker using a compose file. It is stable and robust.
My feature request is to implement an environment variable LOG_LEVEL that supports the standard values - CRITICAL, ERROR, WARN, INFO, DEBUG - for logging to the standard docker log.
I can access the Plex specific logs under plex/config/Library/Application Support/Plex Media Server/Logs/ thanks to the volume mapping in my compose file, but my docker logs are a mixture of container and application details.
For example, the last few days of logs looks like this:
A few days of logs
$ docker compose --file /srv/plex/compose.yaml logs | tail
plex | No data written!
plex | udc input failed with 1011
plex | udc input failed with 1011
plex | udc input failed with 1011
plex | udc input failed with 1011
plex | udc input failed with 1011
plex | udc input failed with 1011
plex | udc input failed with 1011
plex | udc input failed with 1001
plex | udc input failed with 1011
plex | udc input failed with 1011
plex | decoder returned no data
plex | No data written!
plex | The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.
plex | The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.
plex | The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.
plex | The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.
plex | The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.
plex | The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.
plex | The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.
plex | The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.
plex | The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.
If I restart the container, I actually see the container logs I care about:
After restart
$ docker compose --file /srv/plex/compose.yaml logs
plex | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
plex | [s6-init] ensuring user provided files have correct perms...exited 0.
plex | [fix-attrs.d] applying ownership & permissions fixes...
plex | [fix-attrs.d] done.
plex | [cont-init.d] executing container initialization scripts...
plex | [cont-init.d] 40-plex-first-run: executing...
plex | Plex Media Server first run setup complete
plex | [cont-init.d] 40-plex-first-run: exited 0.
plex | [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: executing...
plex | [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: exited 0.
plex | [cont-init.d] 50-plex-update: executing...
plex | [cont-init.d] 50-plex-update: exited 0.
plex | [cont-init.d] done.
plex | [services.d] starting services
plex | Starting Plex Media Server.
plex | [services.d] done.
plex | Critical: libusb_init failed
It would be very useful if PMS could follow the container standards and honour the log level as well. I realise this may be a low priority but it would make monitoring the server easier.
Thank you for the consideration.
