Closed adude00 closed 4 days ago
I think plex pulls down a zip when it starts and unpacks it. There isn't anything we can do there.
What I can suggest is upgrading to 24.10 which uses docker instead of kubernetes. Not sure if the issue lies there, but you can try.
Remember to check truenas release notes before upgrading.
Considering kubernetes apps system is deprecated, I'm going to close this now.
Sometimes (20-30% of the times?) Plex container/pod (unsure of the correct nomenclature here) won't start. Logs shows the container is unable to find the Plex executable and then gets stuck in an infinite loop.
Here is an extract of the logs when it's not starting.
This goes on and on and on.
When it does starts correctly it looks like it's downloading it from the internet (full logs here)
Again it's happening not all the time and I haven't found any reliable steps to reproduce it.
I turn my NAS off after using it, when I turn it on again, maybe one or three days later, most of the times Plex starts fine but sometimes it won't.
Restarting the app fixes it, all the time.
I use a CLI script that first run a
ssh root@opti midclt call chart.release.scale plex \'{\"replica_count\": 0}\'
then assh root@opti midclt call chart.release.scale plex \'{\"replica_count\": 1}\'
To fix it from my home automation.
I noticed that if I wait long enough (20, maybe 30 minutes?) the container eventually gets restarted, maybe after it reaches some kind of timeout?
I'm running Dragonfish-24.04.2.5. It has been this way forever so I'm not sure is related to TrueNAS version.
I notice that when it does not work it looks like it's not able to get the updated version. Is that a network error? If so, why would it need to always download the new version? Can't it use the version that it's already downloaded locally and only upgrade it when an actual upgrade is performed in TrueNAS GUI?
As a workaround, is there any way to reduce this timeout?