Sabnzbd in Portainer starts fine then nothing
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Sabnzbd in Portainer starts fine then nothing
The container starts fine but for some reason looks like it's on port 8080 rather than the defined 9090
2021-12-13 06:09:54,176::INFO::[SABnzbd:1437] Starting web-interface on :::8080
...
2021-12-13 06:09:59,398::INFO::[ssdp:108] Serving SSDP on 10.35.0.26 as SABnzbd
Any assistance is GREATLY appreciated!
Cheers StefWill
2021-12-13 06:09:54,176::INFO::[SABnzbd:1437] Starting web-interface on :::8080
...
2021-12-13 06:09:59,398::INFO::[ssdp:108] Serving SSDP on 10.35.0.26 as SABnzbd
Any assistance is GREATLY appreciated!
Cheers StefWill
Re: Sabnzbd in Portainer starts fine then nothing
What is your question?
Re: Sabnzbd in Portainer starts fine then nothing
Sorry.
I can't load the Web interface.
The logs are not any help at all.
I can't load the Web interface.
The logs are not any help at all.
Re: Sabnzbd in Portainer starts fine then nothing
I tried to post my logs and docker-compose but the forum won't let me post text containing URLs but I'll try again.
When I start the container, Portainer reports it as Running (green) The logs look OK to me except that it is starting on port 8080 rather than the 9090 that I have specified.
I'm accessing it using the server's IP:9090
This is the Log from Portainer for my Sabnzbd container (Edited to obfuscate links)
This is my sabnzbd.yml (Edited to obfuscate links)
When I start the container, Portainer reports it as Running (green) The logs look OK to me except that it is starting on port 8080 rather than the 9090 that I have specified.
I'm accessing it using the server's IP:9090
This is the Log from Portainer for my Sabnzbd container (Edited to obfuscate links)
Code: Select all
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 01-migrations: executing...
[migrations] started
[migrations] no migrations found
[cont-init.d] 01-migrations: exited 0.
[cont-init.d] 10-adduser: executing...
usermod: no changes
-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/
Brought to you by linuxserver . io
-------------------------------------
To support the app dev(s) visit:
SABnzbd: h-t-t-p-s-:-/-/-sabnzbd_org/donate
To support LSIO projects visit:
h-t-t-p-s-:-/-/-www . linuxserver . io/donate/
-------------------------------------
GID/UID
-------------------------------------
User uid: 1001
User gid: 100
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-scripts: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2021-12-13 06:09:54,125::INFO::[SABnzbd:1180] --------------------------------
2021-12-13 06:09:54,126::INFO::[SABnzbd:1181] SABnzbd . py-3.4.2
2021-12-13 06:09:54,126::INFO::[SABnzbd:1191] Commit = cc831e16d87d12fe4d7bbcc71b9ff579eb1335ff
2021-12-13 06:09:54,126::INFO::[SABnzbd:1193] Full executable path = /app/sabnzbd/SABnzbd . py
2021-12-13 06:09:54,126::INFO::[SABnzbd:1194] Arguments = "/app/sabnzbd/SABnzbd . py" "--config-file" "/config" "--server" "::"
2021-12-13 06:09:54,127::INFO::[SABnzbd:1195] Python-version = 3.8.10 (default, Sep 28 2021, 16:10:42)
[GCC 9.3.0]
2021-12-13 06:09:54,127::INFO::[SABnzbd:1196] Dockerized = True
2021-12-13 06:09:54,127::INFO::[SABnzbd:1197] CPU architecture = x86_64
2021-12-13 06:09:54,142::INFO::[SABnzbd:1200] Platform = posix - Linux-5.10.60-qnap-x86_64-with-glibc2.29
2021-12-13 06:09:54,143::INFO::[SABnzbd:1206] Preferred encoding = UTF-8
2021-12-13 06:09:54,143::INFO::[SABnzbd:1218] SSL version = OpenSSL 1.1.1f 31 Mar 2020
2021-12-13 06:09:54,144::INFO::[SABnzbd:1227] Certifi version = 2021.10.08
2021-12-13 06:09:54,144::INFO::[SABnzbd:1228] Loaded additional certificates from /usr/local/lib/python3.8/dist-packages/certifi/cacert.pem
2021-12-13 06:09:54,145::INFO::[SABnzbd:1248] Using INI file /config/sabnzbd.ini
2021-12-13 06:09:54,146::INFO::[postproc:135] Loading postproc queue
2021-12-13 06:09:54,147::INFO::[scheduler:190] Scheduling RSS interval task every 60 min (delay=26)
2021-12-13 06:09:54,147::INFO::[scheduler:201] Scheduling VersionCheck on day 5 at 14:57
2021-12-13 06:09:54,147::INFO::[scheduler:215] Setting schedule for midnight BPS reset
2021-12-13 06:09:54,148::INFO::[scheduler:218] Setting schedule for server expiration check
2021-12-13 06:09:54,148::INFO::[scheduler:223] Setting scheduler for server quota check
2021-12-13 06:09:54,155::INFO::[config:905] Writing settings to INI file /config/sabnzbd.ini
2021-12-13 06:09:54,158::INFO::[__init__:334] All processes started
2021-12-13 06:09:54,159::INFO::[SABnzbd:344] Template location for Glitter is /app/sabnzbd/interfaces/Glitter
2021-12-13 06:09:54,159::INFO::[SABnzbd:344] Template location for Config is /app/sabnzbd/interfaces/Config
2021-12-13 06:09:54,160::INFO::[misc:1098] [N/A] Running external command: ['/usr/bin/unrar']
2021-12-13 06:09:54,166::INFO::[misc:1098] [N/A] Running external command: ['/usr/bin/par2', '-h']
2021-12-13 06:09:54,173::INFO::[SABnzbd:431] SABYenc module (v4.0.2)... found!
2021-12-13 06:09:54,174::INFO::[SABnzbd:450] Cryptography module (v36.0.0)... found!
2021-12-13 06:09:54,174::INFO::[SABnzbd:455] par2 binary... found (/usr/bin/par2)
2021-12-13 06:09:54,174::INFO::[SABnzbd:462] UNRAR binary... found (/usr/bin/unrar)
2021-12-13 06:09:54,174::INFO::[SABnzbd:472] UNRAR binary version 6.00
2021-12-13 06:09:54,175::INFO::[SABnzbd:480] 7za binary... found (/usr/bin/7za)
2021-12-13 06:09:54,175::INFO::[SABnzbd:491] nice binary... found (/usr/bin/nice)
2021-12-13 06:09:54,175::INFO::[SABnzbd:495] ionice binary... found (/usr/bin/ionice)
2021-12-13 06:09:54,176::INFO::[SABnzbd:1437] Starting web-interface on :::8080
2021-12-13 06:09:54,176::INFO::[_cplogging:213] [13/Dec/2021:06:09:54] ENGINE Bus STARTING
/usr/local/lib/python3.8/dist-packages/cherrypy/process/servers . py:416: UserWarning: Unable to verify that the server is bound on 8080
warnings.warn(msg)
2021-12-13 06:09:59,298::INFO::[_cplogging:213] [13/Dec/2021:06:09:59] ENGINE Serving on h-t-t-p-://:::8080
2021-12-13 06:09:59,298::INFO::[_cplogging:213] [13/Dec/2021:06:09:59] ENGINE Bus STARTED
2021-12-13 06:09:59,298::INFO::[SABnzbd:1473] Starting SABnzbd . py-3.4.2
2021-12-13 06:09:59,299::INFO::[postproc:233] Completed Download Folder /config/Downloads/complete is not on FAT
2021-12-13 06:09:59,300::INFO::[dirscanner:117] Dirscanner starting up
2021-12-13 06:09:59,301::INFO::[panic:239] Launching browser with h-t-t-p-://127.0.0.1:8080/sabnzbd
2021-12-13 06:09:59,306::INFO::[notifier:122] Sending notification: SABnzbd - SABnzbd 3.4.2 started (type=startup, job_cat=None)
2021-12-13 06:09:59,398::INFO::[zconfig:61] No bonjour/zeroconf support installed
2021-12-13 06:09:59,398::INFO::[ssdp:108] Serving SSDP on 10.35.0.26 as SABnzbd
Code: Select all
version: "3"
services:
sabnzbd:
cap_add:
- AUDIT_WRITE
- CHOWN
- DAC_OVERRIDE
- FOWNER
- FSETID
- KILL
- MKNOD
- NET_BIND_SERVICE
- NET_RAW
- SETFCAP
- SETGID
- SETPCAP
- SETUID
- SYS_CHROOT
cap_drop:
- AUDIT_CONTROL
- BLOCK_SUSPEND
- DAC_READ_SEARCH
- IPC_LOCK
- IPC_OWNER
- LEASE
- LINUX_IMMUTABLE
- MAC_ADMIN
- MAC_OVERRIDE
- NET_ADMIN
- NET_BROADCAST
- SYSLOG
- SYS_ADMIN
- SYS_BOOT
- SYS_MODULE
- SYS_NICE
- SYS_PACCT
- SYS_PTRACE
- SYS_RAWIO
- SYS_RESOURCE
- SYS_TIME
- SYS_TTY_CONFIG
- WAKE_ALARM
container_name: sabnzbd
entrypoint:
- /init
environment:
- HOME=/config
- LANG=en_US.UTF-8
- LANGUAGE=en_US.UTF-8
- PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
- PGID=100
- PUID=1001
- PYTHONIOENCODING=utf-8
- TERM=xterm
hostname: d0d84019f3e1
image: docker . io/linuxserver/sabnzbd:latest
ipc: private
labels:
build_version: 'Linuxserver . io version:- 3.4.2-ls46 Build-date:- 2021-11-12T11:09:36+01:00'
com.qnap.qcs.gpu: False
com.qnap.qcs.network.mode: nat
maintainer: thelamer
org.opencontainers.image.authors: linuxserver . io
org.opencontainers.image.created: 2021-11-12T11:09:36+01:00
org.opencontainers.image.description: "[Sabnzbd](h-t-t-p-:-/-/-sabnzbd . org/) makes\
\ Usenet as simple and streamlined as possible by automating everything we\
\ can. All you have to do is add an .nzb. SABnzbd takes over from there, where\
\ it will be automatically downloaded, verified, repaired, extracted and filed\
\ away with zero human interaction."
org.opencontainers.image.documentation: h-t-t-p-s-:-/-/-docs . linuxserver . io/images/docker-sabnzbd
org.opencontainers.image.licenses: GPL-3.0-only
org.opencontainers.image . ref . name: 225dd4efe81661b7ffa8757776ca5f247097eaac
org.opencontainers.image.revision: 225dd4efe81661b7ffa8757776ca5f247097eaac
org.opencontainers.image.source: h-t-t-p-s-:-/-/-github . com/linuxserver/docker-sabnzbd
org.opencontainers.image.title: Sabnzbd
org.opencontainers.image.url: h-t-t-p-s-:-/-/-github . com/linuxserver/docker-sabnzbd/packages
org.opencontainers.image.vendor: linuxserver . io
org.opencontainers.image.version: 3.4.2-ls46
logging:
driver: json-file
options:
max-file: 10
max-size: 10m
mac_address: XX:XX:XX:XX:XX:XX
ports:
- 9090:9090/tcp
restart: always
stdin_open: true
tty: true
ulimits:
- Hard: 65535
Name: nofile
Soft: 65535
volumes:
- /share/appdata/sabnzbd:/config
- /share/usenet:/usenet
- /share/usenet/incomplete:/usenet/incomplete
networks: {}
Re: Sabnzbd in Portainer starts fine then nothing
Your sabnzbd.yml says
ports:
- 9090:9090/tcp
Your sab container is listening on port 8080. And that port is not exposed to the host ...only 9090 is ...
So ... no match.
ports:
- 9090:9090/tcp
Your sab container is listening on port 8080. And that port is not exposed to the host ...only 9090 is ...
So ... no match.
Re: Sabnzbd in Portainer starts fine then nothing
@sander
But why is it listening on port 8080 when I'm defining port 9090?
The web interface for my NAS runs on 8080
But why is it listening on port 8080 when I'm defining port 9090?
The web interface for my NAS runs on 8080
Re: Sabnzbd in Portainer starts fine then nothing
Does the lsio docker listen/obey to that yaml file at all?
If so, what if you define 9090:8080 ? So 9090 on the host, connected to 8080 inside the docker container.
Re: Sabnzbd in Portainer starts fine then nothing
Thanks I'll try 9090:8080
How would I check if the lsio docker listen/obey to that yaml file?
How would I check if the lsio docker listen/obey to that yaml file?
Re: Sabnzbd in Portainer starts fine then nothing
If it did, you would expect the port number to be passed to sabnzbd as a command line argument. But in the not-so-useless log, the --server option only specifies a host ("::") without a port number:
Mapping 9090 outside to 8080 inside the container is probably the easiest fix.
Re: Sabnzbd in Portainer starts fine then nothing
Thanks for all the help.
Mapping the other port fixed the issue now it's all running as expected.
Mapping the other port fixed the issue now it's all running as expected.
