I’m just installing DietPi for the first time on my Ras Pi 4.
All of the software installations seem to go fine but then SABnzbd gets stuck at the configuration stage. No errors, it just sticks.
Any ideas?
DietPi-Software
─────────────────────────────────────────────────────
Mode: Configuring SABnzbd: nzb download manager[ INFO ] DietPi-Software | Generating initial config, please wait…
hmm strange, I tried it on my VM system right now without issues
DietPi-Software
─────────────────────────────────────────────────────
Mode: Configuring SABnzbd: nzb download manager
[ INFO ] DietPi-Software | Generating initial config, please wait...
[ OK ] DietPi-Software | Setting in /etc/sabnzbd/sabnzbd.ini adjusted: download_dir = /mnt/dietpi_userdata/downloads/incomplete
[ OK ] DietPi-Software | Setting in /etc/sabnzbd/sabnzbd.ini adjusted: complete_dir = /mnt/dietpi_userdata/downloads/complete
[ OK ] DietPi-Software | Setting in /etc/sabnzbd/sabnzbd.ini adjusted: nzb_backup_dir = /mnt/dietpi_userdata/downloads/sabnzbd_nzb_backup
[ OK ] DietPi-Software | Setting in /etc/sabnzbd/sabnzbd.ini adjusted: admin_dir = /mnt/dietpi_userdata/downloads/sabnzbd_admin
[ OK ] DietPi-Software | Setting in /etc/sabnzbd/sabnzbd.ini adjusted: log_dir = /var/log/sabnzbd
[ OK ] DietPi-Software | Setting in /etc/sabnzbd/sabnzbd.ini adjusted: log_level = 0
[ OK ] DietPi-Software | Setting in /etc/sabnzbd/sabnzbd.ini adjusted: refresh_rate = 2
[ OK ] DietPi-Software | Setting in /etc/sabnzbd/sabnzbd.ini adjusted: host = 0.0.0.0
[ OK ] DietPi-Software | Setting in /etc/sabnzbd/sabnzbd.ini adjusted: permissions = 0775
[ OK ] DietPi-Software | Desired setting in /etc/sabnzbd/sabnzbd.ini was already set: auto_browser = 0
[ OK ] DietPi-Software | python2.7 tools/make_mo.py
did you tried to reboot und retry?
Hi,
Yeah I tried that a couple of times.
In the end I just went and installed it manually from the PPA so at least I’ve got it working but something’s up with the installer.
Are there any logs I could send over that might help?
well the installer was working fine for me. So there is no general issue.
I actually encountered a same problem on raspberry pi 4.
Install gets stuck at the same point, after restart SABnzbd fails to install or start.
I did notice a error message during the install informing something about old/wrong python version (2.7 vs >3).
Here is systemd status log for the SABnzbd (if that helps at all…):
● sabnzbd.service - SABnzbd (DietPi)
│ Loaded: loaded (/etc/systemd/system/sabnzbd.service; disabled; vendor
│ preset: enabled)
│ Active: failed (Result: exit-code) since Mon 2020-03-09 08:30:28 GMT;
│ 1min 13s ago
│ Docs: https://sabnzbd.org/wiki/
│ Process: 855 ExecStart=/usr/bin/python2.7 -OO /etc/sabnzbd/SABnzbd.py -b 0
│-f /etc/sabnzbd/sabnzbd.ini (code=exited, status=1/FAILURE)
│ Main PID: 855 (code=exited, status=1/FAILURE)
│
│ Mar 09 08:30:28 DietPi systemd[1]: sabnzbd.service: Service RestartSec=100ms
│ expired, scheduling restart.
│ Mar 09 08:30:28 DietPi systemd[1]: sabnzbd.service: Scheduled restart job,
│ restart counter is at 5.
│ Mar 09 08:30:28 DietPi systemd[1]: Stopped SABnzbd (DietPi).
│ Mar 09 08:30:28 DietPi systemd[1]: sabnzbd.service: Start request repeated
│ too quickly.
│ Mar 09 08:30:28 DietPi systemd[1]: sabnzbd.service: Failed with result
│ 'exit-code'.
│ Mar 09 08:30:28 DietPi systemd[1]: Failed to start SABnzbd (DietPi).
can you check journalctl if there are some error messages listed?
Here you go (errors only) 
-- Logs begin at Mon 2020-03-09 09:00:11 GMT, end at Mon 2020-03-09 12:25:02 GMT. --
Mar 09 09:00:11 DietPi kernel: bcm2708_fb soc:fb: Unable to determine number of FB's. Assuming 1
Mar 09 09:00:11 DietPi kernel: raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001
Mar 09 09:00:11 DietPi kernel: bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22)
Mar 09 09:00:11 DietPi kernel: bcm2708_fb soc:fb: probe failed, err -22
Mar 09 09:00:11 DietPi kernel: vc_vchi_sm_init: failed to open VCHI service (-1)
Mar 09 09:00:11 DietPi kernel: [vc_sm_connected_init]: failed to initialize shared memory service
Mar 09 09:00:11 DietPi kernel: vc_sm_cma_vchi_init: failed to open VCHI service (-1)
Mar 09 09:00:11 DietPi kernel: [vc_sm_connected_init]: failed to initialize shared memory service
Mar 09 09:00:58 DietPi systemd[1]: Failed to start SABnzbd (DietPi).
-- Subject: A start job for unit sabnzbd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit sabnzbd.service has finished with a failure.
--
-- The job identifier is 612 and the job result is failed.
Mar 09 10:25:21 DietPi kernel: CIFS VFS: Autodisabling the use of server inode numbers on \\192.168.86.24\tv. This s
erver doesn't seem to support them properly. Hardlinks will not be recognized on this mount. Consider mounting with the "noserverino" option
to silence this message.
hmm not sure if they are related but seems you have an issue to initialize shared memory service next to sabnzbd.service failing.
So let’s try to get rid of shared memory stuff. Can you have a look to /Dietpi/config.txt. There should be a GPU Memory area. I guess it’s set to 16. Maybe you can try setting it to 32 and reboot your system. At least it should clean these messages I hope 
Reagrding SABnzbd, can you check SABnzbd Log file? Maybe there are some useful information
cat /var/log/sabnzbd/sabnzbd.log
Thanks for investigating this error I updated the mem settings and the error changed a bit, but still majority remains.
-- Logs begin at Mon 2020-03-09 16:33:26 GMT, end at Mon 2020-03-09 16:34:51 GMT. --
Mar 09 16:33:26 DietPi kernel: bcm2708_fb soc:fb: Unable to determine number of FB's. Assuming 1
Mar 09 16:33:26 DietPi kernel: raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001
Mar 09 16:33:26 DietPi kernel: bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22)
Mar 09 16:33:26 DietPi kernel: bcm2708_fb soc:fb: probe failed, err -22
Mar 09 16:34:13 DietPi systemd[1]: Failed to start SABnzbd (DietPi).
-- Subject: A start job for unit sabnzbd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit sabnzbd.service has finished with a failure.
--
-- The job identifier is 612 and the job result is failed.
I don’t seem to have the directory “sabnzbd” or the log file in “log” directory. This could be a problem in it self? Every other software I have installed seem to have a log file present (openvpn, sonarr)
BTW: I don’t know why it would matter but this is a 4GB version of the RPI 4.
as I said, I don’t think the GPU stuff is related to sabnzbd.
anyway, if don’t use the screen you could try to set the following in /Dietpi/config.txt to get rig of the GPU error message.
hdmi_blanking=1
regarding sabnzbd. can you have a look into /etc/sabnzbd/sabnzbd.ini. There you should find these 2 entries
log_dir = /var/log/sabnzbd
log_level = 0
try to increase the log level and restart sabnzbd service. I tried to check sabnzbd documentation to find out what the debugging value would be.
Hmm… I increased the log level to 1 and then 2 (found some documentation saying 0 is least and 2 most). Still no logs sadly 
it will be hard to continue without logs, as we don’t know why SABnzbd is failing. Probably it would be good if you can raise the issue at SABnzbd Forum. Maybe these guys will have an idea why SABnzbd is failing and did not have logs
Maybe you can try to start it manually by running the following command. Hopefully it will give some error messages
/usr/bin/python2.7 -OO /etc/sabnzbd/SABnzbd.py -b 0 -f /etc/sabnzbd/sabnzbd.ini
Ahaa! Manually starting seemed to give something new: “The Python module Cheetah is required”. Should that been automatically included?
Compiling a new python with Cheetah is getting too complicated for me at the moment
Thanks for help! I’ll try to manage!
Hi,
I found this one somewhere on the internet. But I have not tested it
/usr/bin/python2.7 -m pip install cheetah
Thanks
Sadly no dice: “ERROR: Package ‘Markdown’ requires a different Python: 2.7.16 not in ‘>=3.5’”
Seems Cheetah needs Markdown and it needs newer Python… (I’m not too familiar with Linux packages etc.)
strange issue, because SABnzbd requires Python 2.7 according /etc/sabnzbd/SABnzbd.py file. Hmm seems a new version of Markdown was released in Feb 2020.
https://pypi.org/project/Markdown/#history
so what you can try it is to install a lower version of Markdown manually.
pip install Markdown==3.1.1
afterwards you could try to re-install SABnzbd as follow
dietpi-software reinstall 139
Yes!
After older Markdown it actually worked! And I got SABnzbd installed and it’s running! btw: I had to install from “scratch”, the re-install said nothing to reinstall (because of the failed initial install I guess)
Thanks!
ok cool we could have it solved for you.