Plex and Jellyfin apps won't start

[sgt_jamez]

I'm running TrueNAS-SCALE-22.12-MASTER-20220711-072905 nightly, and I'm not sure when this issue started.

Both Plex and Jellyfin apps are stuck on "DEPLOYING", while the UniFi controller and TrueCommand apps are up and running.

Log from Plex:
{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"container \"plex\" in pod \"plex-6dfc955df6-9lf5l\" is waiting to start: CreateContainerError","reason":"BadRequest","code":400}

Log from Jellyfin:
{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"container \"jellyfin\" in pod \"jellyfin-ffb69f4b6-m5zw4\" is waiting to start: PodInitializing","reason":"BadRequest","code":400}

What can I do from here?

Edit:
I rolled back to TrueNAS-SCALE-22.12-MASTER-20220626-072905 and all the apps start. A couple updates back the CPU and Memory display panels stopped working and that's still the case. And I notice under the Jobs icon, alert.process_alerts stays active.

 

[truecharts]

Considering the Apps you listed, you are most-likely using TrueCharts Apps.
Please be aware we're not related to iX-Systems and handle our support only on our own discord and Github.

 

[sgt_jamez]

Sorry for not clarifying that. Plex is the official app and Jellyfin is of course TrueCharts. So one of each.

Something about the update that it didn’t like and there hasn’t been a new nightly in a good number of days. I guess I will just wait for the next nightly to drop and if that doesn’t work I’ll roll back to my current version.

 

[MAndreato]

I just had the same issue with NextCloud (official catalog) but only when adding an "Nextcloud Extra Host Path Volumes" with a dataset of my pool...
Resolved reverting to TrueNAS-22.12-MASTER-20220616-020038; so I also guess that another TrueNAS nightly may fix it.

 

[sgt_jamez]

Has anyone been able to resolve this on a current version of the nightly? I was happy to see new ones posted, but so far the issue remains. The most recent update that works for me is TrueNAS-SCALE-22.12-MASTER-20220626-072905.

 

[MAndreato]

I tried just few hours ago but had to revert to TrueNAS-SCALE-22.12-MASTER-20220626 again.

 

[sgt_jamez]

Yeah, even the most current version, TrueNAS-SCALE-22.12-MASTER-20220820-092905, has this issue for me still.

 

[sp3tsnaz]

Interested to hear if either of you end up figuring out a solution. I am not tech savvy enough to troubleshoot myself, but have had the exact same issue (except that mine is with Emby rather than Jellyfin/Plex) and just sticking to an older build for now which seem to work fine. I am using the TrueCharts version of the app, but I tried to get the official one to test out with the new build and was getting the same error being stuck on deploying.

 

[sgt_jamez]

I'm with you. I don't know how to troubleshoot this. Especially since one of my apps (Plex) is official and the other is not. All I can do is keep testing new nightlies as they surface and hope for the best.

 

[rs_taylor]

I'm having same issue with Jellyfin being stuck "Deploying".
It seemed to have an issue with me using an SMB share with the same path as i was exposting in Jellyfin (bizarre right?).

Anyway i disabled all my SMB shares. Stopped JellyFin, Started JellyFin, once it became Active i reenabled the SMB shares.

 

[ImMrTea]

Issue with any app using host paths that are shares (smb or nfs) or scheduled for snapshots. This started for me around the 711 update I believe, or the first one after the long break.

 

[sgt_jamez]

@rs_taylor How did you disable the shares? I booted back to the most current update, stopped the Plex and Jellyfin app, turned of the SMB service slider, and then attempted to restart the apps. Still stuck at "deploying" with the "bad request 400" in the logs. Rebooted back to the 626 environment and all's well.

 

[rs_taylor]

Turning the SMB servicce off for me didn't help, i had to Disabled all the shares individually.
Then STOPPED the APP (if still stuck "Deploying") and then Start it again & it became "Active", then i re-enabled all the shares again.

I have to do this again each time i want to start Jellyfin (upgrade, server reboot etc)

 

[rs_taylor]

 

[sgt_jamez]

Ok cool. I will try that this evening. Hopefully this gets squared away before too long.

 

[rs_taylor]

FYI TrueNAS-SCALE-22.12-MASTER-20220826-222905 is still busted

 

[rs_taylor]

Newer nightlies no longer have this "bug"

 

[sgt_jamez]

I still get it though the error message in the log is different.

{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Get \"https://192.168.2.230:10250/contain...true\u0026tailLines=500\u0026timestamps=true\": x509: certificate is valid for 127.0.0.1, 0.0.0.0, not 192.168.2.230","code":500}

Clicking on Application Events for the app gives me a log of errors:

2022-08-28 6:49:58
Error: Error response from daemon: invalid volume specification: '/mnt/main_vault/media:/media': Invalid mount path. /mnt/main_vault/media. Following service(s) uses this path: `SMB Share`.
2022-08-28 6:49:22
Container image "plexinc/pms-docker:1.28.1.6104-788f82488" already present on machine
2022-08-28 6:48:58
Successfully assigned ix-plex/plex-8467955d6f-j594x to ix-truenas
2022-08-28 6:48:53
Created pod: plex-8467955d6f-j594x
2022-08-28 6:48:53
0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
2022-08-28 6:48:45
MountVolume.SetUp failed for volume "kube-api-access-cr95d" : object "ix-plex"/"kube-root-ca.crt" not registered
2022-08-28 6:48:42
MountVolume.SetUp failed for volume "plex-probe-check" : object "ix-plex"/"plex-probe-check" not registered
2022-08-28 6:48:42
MountVolume.SetUp failed for volume "plex-probe-check" : object "ix-plex"/"plex-probe-check" not registered
2022-08-28 6:48:42
MountVolume.SetUp failed for volume "kube-api-access-xrkkf" : object "ix-plex"/"kube-root-ca.crt" not registered
2022-08-28 6:48:40
Predicate TaintToleration failed

 

[rs_taylor]

yes sorry, my mistake they didnt fix it

 

[sgt_jamez]

Something else I noticed in the newest nightly is that despite being connected to my AD domain, my ACL editor does not list the domain users and groups.