Lost access to Sabnzbd. [proxmox, Sabnzbd LXC]

[DukeOfAwesome]

System:
Proxmox Host 8.2.4
Sabnzbd LXC installed via tteck's sabnzbd-lxc script.

It's a relatively new setup, been up and running for 2 weeks. This morning i all of a sudden lost access to sabnzbd. Sonarr has about 40 files in queue but since then has lost connection to the service.

when i run netstat i dont see the service running. short of deleting the ini file and starting fresh what can i do to try to revive the system?

Code: Select all

root@sabnzbd:~# netstat -apon | grep -i LISTEN | grep -vi listening
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      317/master           off (0.00/0/0)
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1/init               off (0.00/0/0)
root@sabnzbd:~# 

[sander]

start sabnzbd?

[DukeOfAwesome]

start sabnzbd?

Shouldn't it start automatically upon reboot?
I dont know what command to send to force start it.

[sander]

> Shouldn't it start automatically upon reboot?

Depends on how you configured it.

> I dont know what command to send to force start it.

Depends how you installed it.

[sander]

I've put [proxmox, Sabnzbd LXC] into the title. Maybe that attracts some people who know proxmox

I tried proxmox for an hour and then gave up: too difficult for my simple mind.

[DukeOfAwesome]

Thank you sander.
I've messed around with it a bit more.
I've created multiple new containers and all of them startup for the initial boot. However when i reboot the machine after adding mounted drives for it to use it fails to start properly. This happens on a freshly built container everytime. After a reboot the service fails to start.

Code: Select all

root@sabnzbd:~# systemctl status sabnzbd
× sabnzbd.service - SABnzbd
     Loaded: loaded (/etc/systemd/system/sabnzbd.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Tue 2024-08-13 17:16:35 CDT; 1min 57s ago
   Duration: 602ms
    Process: 297 ExecStart=python3 SABnzbd py -s 0.0.0.0:7777 (code=exited, status=2)                     //I had to delete the period before py because i'm not allowed to post links...??
   Main PID: 297 (code=exited, status=2)
        CPU: 593ms

Aug 13 17:16:35 sabnzbd systemd[1]: sabnzbd.service: Scheduled restart job, restart counter is at 5.
Aug 13 17:16:35 sabnzbd systemd[1]: Stopped sabnzbd.service - SABnzbd.
Aug 13 17:16:35 sabnzbd systemd[1]: sabnzbd.service: Start request repeated too quickly.
Aug 13 17:16:35 sabnzbd systemd[1]: sabnzbd.service: Failed with result 'exit-code'.
Aug 13 17:16:35 sabnzbd systemd[1]: Failed to start sabnzbd.service - SABnzbd.

[sander]

"python3 SABnzbd py -s 0.0.0.0 7777" I don't think that startup parameters are allowed.

This is allowed:

"python3 SABnzbd py -s 0.0.0.0:7777"

BTW: 7777 is not the default SABnzbd port; that's 8080. So: did you change that yourself? Of is that proxmox / LXC behaviour?

[DukeOfAwesome]

Sorry i was trying to figure out what in that was causing the site to deny my post because i couldn't post links. Turns out it was the SABnzbd.py
I corrected the output of the status prompt. And that's the default port in the script. And yes that's the port i'm trying to access in the browser.

[sander]

Ah, yes.

Then I can't help. I can only see/guess: your system tries to start SABnzbd (5 times?), but that fails.

You already said you tried fresh installs, which didn't help. Then I don't know. Maybe there is more logging on your proxmox, but as said: I don't know proxmox.

[DukeOfAwesome]

Is there a log somewhere that i can check to see why it's exiting?

[sander]

Yes: sabnzbd.log

And linux: syslog and journal

[DukeOfAwesome]

I managed to get a workaround
changing

Code: Select all

python3 SABnzbd py -s 0.0.0.0:7777

to

Code: Select all

python3 SABnzbd py -s 192.168.1.91:7777

works. for some reason when binding to all interfaces it fails