SOLVED Error starting sabnzbd from previously working setup

[Matt K]

Hey all,

I upgraded to truenas corbia some months ago and had a working sabnzbd setup.
today I noticed an error from my docker connecting to the newsgroup servers showing a connection timeout when starting ssl.
I restarted the app, then the server, but now I can't get the app to actually start up anymore.

The kubernetes history shows the following:
2023-12-30 21:00:43 MountVolume.SetUp failed for volume "kube-api-access-8r752" : object "ix-sabnzbd"/"kube-root-ca.crt" not registered
2023-12-30 21:00:40 MountVolume.SetUp failed for volume "kube-api-access-ln4g4" : object "ix-sabnzbd"/"kube-root-ca.crt" not registered
2023-12-30 21:00:37 Predicate TaintToleration failed
2023-12-30 21:00:34 Predicate TaintToleration failed
2023-12-30 20:55:12 Container runtime did not kill the pod within specified grace period.
2023-12-30 20:53:03 Scaled down replica set sabnzbd-ix-chart-bd9f6bd5f to 0 from 1
2023-12-30 20:53:03 Deleted pod: sabnzbd-ix-chart-bd9f6bd5f-l5p9f
2023-12-30 20:39:44 Pulling image "linuxserver/sabnzbd:latest"
2023-12-30 20:39:41 Add eth0 [172.16.0.41/16] from ix-net

Now there are two things that I changed recently.
1) I updated my expired wildcard ssl certificate, the new one is 4096 bits instead of 2048.
2) I made some changes to my network setup by adding an aggregation switch into the mix. No policy changes.

The other dockers, like nginx (which actually uses my cert) sonarr, radarr, and plex all seem to be working fine. I don't know what else I can do here, so any guidance would be appreciated.

sabnzbd just says "deploying" forever.

To be clear - these are linuxserver.io docker images NOT truecharts. though i think the kube-root-ca.crt error is not related to the app since I have no config referencing it
Truenas is TrueNAS-SCALE-23.10.1

Thank you in advance
Matt

 

[Matt K]

My next step is going to be deleting the docker config and setting it back up again. I'll report back if this is successful

 

[Matt K]

what a mess...
https://imgur.com/a/D4su98U - sonarr running but not really
https://imgur.com/2PmYh70 - nginx now has the cert error

I guess i'm going to go scorched earth like this guy did =/

kube-root-ca.crt not registered after setting a new pool for applications

I recently decided to move my application pool onto my primary data pool, as the mirrored SSDs I put them on were performing horribly. The steps I performed: 1. Back up ix-applications directory using cp -a from the app pool. 2. Unset the pool in the Applications screen in the Truenas GUI. 3...

www.truenas.com

 

[Matt K]

Well I unselected the pool to use for docker, nuked the data set, and re-selected it.

When I reselect the pool I get this error:
Failed to sync TRUENAS catalog: [EFAULT] Failed to clone 'https://github.com/truenas/charts.git' repository at '/mnt/Wolverine/ix-applications/catalogs/github_com_truenas_charts_git_master' destination: [EFAULT] Failed to clone 'https://github.com/truenas/charts.git' repository at '/mnt/Wolverine/ix-applications/catalogs/github_com_truenas_charts_git_master' destination: Cloning into '/mnt/Wolverine/ix-applications/catalogs/github_com_truenas_charts_git_master'... error: RPC failed; curl 56 GnuTLS recv error (-9): Error decoding the received TLS packet. error: 3089 bytes of body are still expected fetch-pack: unexpected disconnect while reading sideband packet fatal: early EOF fatal: fetch-pack: invalid index-pack output

And I can't add my own dockers because of this failure. What the ever loving heck is going on here..
date shows the right time:
Sun Dec 31 21:21:16 MST 2023

 

[Matt K]

Ok - I found my problem. and I'm embarassed to say it was a bad DAC cable linking my udm pro to the new aggregation switch. Once I replaced it with an ethernet cable and a transceiver it started working normally. Fortunately I already have an order in for one so i'll have it in a few days. Sorry for the spam =)