Can't enable Sickbeard. Python, Quotaon issues

RS1 · 2. Januar 2017

Hi there, I'm having a challenging time getting sick-beard/sick rage up and running since swapping out hard drives and upgrading to the new OMV build. I also enabled the union/mergerfs plugin. Any help would be appreciated. The error messages I receive when trying to enable the plugin are below. From what I can tell, I have a problem with Python and Quotas?

I'm very new to linux, so I could very well be wrong about my inclination. Feedback would be great.

Thank you

Error message when enabling plugin

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl start sickbeard.service 2>&1' with exit code '1': Job for sickbeard.service failed. See 'systemctl status sickbeard.service' and 'journalctl -xn' for details

Contents of systemctl:

Code

● sickbeard.service - SickBeard Daemon
   Loaded: loaded (/lib/systemd/system/sickbeard.service; enabled)
   Active: failed (Result: exit-code) since Mon 2017-01-02 04:27:38 GMT; 1min 24s ago
  Process: 12748 ExecStart=/usr/bin/python /opt/sickbeard/SickBeard.py --quiet --daemon --datadir /var/opt/sickbeard/ (code=exited, status=216/GROUP)


Jan 02 04:27:38 NAS systemd[12748]: Failed at step GROUP spawning /usr/bin/python: No such process
Jan 02 04:27:38 NAS systemd[1]: sickbeard.service: control process exited, code=exited status=216
Jan 02 04:27:38 NAS systemd[1]: Failed to start SickBeard Daemon.
Jan 02 04:27:38 NAS systemd[1]: Unit sickbeard.service entered failed state.
root@NAS:/#

Alles anzeigen

Contents of journalctl:

Code

root@NAS:/# journalctl -xn 
-- Logs begin at Fri 2016-12-30 20:49:28 GMT, end at Mon 2017-01-02 04:35:40 GMT. --
Jan 02 04:35:40 NAS quotaon[13733]: quotaon: cannot find /media/cbe1e2d4-0fad-472e-97a2-8f4dc3979687/aquota.group on /dev/sda1 [/media/cbe1e2d4-0fad-472e-97a2-8f4
dc3979687]
Jan 02 04:35:40 NAS quotaon[13733]: quotaon: cannot find /media/cbe1e2d4-0fad-472e-97a2-8f4dc3979687/aquota.user on /dev/sda1 [/media/cbe1e2d4-0fad-472e-97a2-8f4d
c3979687]
Jan 02 04:35:40 NAS systemd[1]: quotaon.service: main process exited, code=exited, status=6/NOTCONFIGURED
Jan 02 04:35:40 NAS systemd[1]: Failed to start Enable File System Quotas.
-- Subject: Unit quotaon.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit quotaon.service has failed.
-- 
-- The result is failed.
Jan 02 04:35:40 NAS systemd[1]: Unit quotaon.service entered failed state.
Jan 02 04:35:40 NAS systemd[1]: Starting SickBeard Daemon...
-- Subject: Unit sickbeard.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit sickbeard.service has begun starting up.
Jan 02 04:35:40 NAS systemd[13736]: Failed at step GROUP spawning /usr/bin/python: No such process
-- Subject: Process /usr/bin/python could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The process /usr/bin/python could not be executed and failed.
-- 
-- The error number returned while executing this process is 3.
Jan 02 04:35:40 NAS systemd[1]: sickbeard.service: control process exited, code=exited status=216
Jan 02 04:35:40 NAS systemd[1]: Failed to start SickBeard Daemon.
-- Subject: Unit sickbeard.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit sickbeard.service has failed.
-- 
-- The result is failed.
Jan 02 04:35:40 NAS systemd[1]: Unit sickbeard.service entered failed state.
root@NAS:/#

Alles anzeigen

RS1 · 2. Januar 2017

I managed to find the sickbeard config.ini file; however there was no reference to my old hard drive in there. I'm not sure whether there are remnants from an old install lurking around.

Is there a way of completely removing sickbeard and then starting from scratch?

RS1 · 2. Januar 2017

I disabled the unionfilesystems plugin, thinking that perhaps that has a part to play in my 'quota' error in journalctl. Unfortunately, that did not resolve the issue. I'm totally out of ideas..

RS1 · 2. Januar 2017

I think that I'm going to go back to OMV 2.1 for now..

ryecoaaron · 2. Januar 2017

If not too late, I would disable the quota service - systemctl disable quaton

RS1 · 2. Januar 2017

Thank you for the suggestion. Unfortunately, that didn't do the trick:

sickbeard.service

Code

root@NAS:/# systemctl status sickbeard.service
● sickbeard.service - SickBeard Daemon
   Loaded: loaded (/lib/systemd/system/sickbeard.service; enabled)
   Active: failed (Result: exit-code) since Mon 2017-01-02 22:04:56 GMT; 11s ago
  Process: 3401 ExecStart=/usr/bin/python /opt/sickbeard/SickBeard.py --quiet --daemon --datadir /var/opt/sickbeard/ (code=exited, status=216/GROUP)


Jan 02 22:04:56 NAS systemd[3401]: Failed at step GROUP spawning /usr/bin/python: No such process
Jan 02 22:04:56 NAS systemd[1]: sickbeard.service: control process exited, code=exited status=216
Jan 02 22:04:56 NAS systemd[1]: Failed to start SickBeard Daemon.
Jan 02 22:04:56 NAS systemd[1]: Unit sickbeard.service entered failed state.

Alles anzeigen

journalctl

Code

root@NAS:/# journalctl -xn
-- Logs begin at Mon 2017-01-02 21:59:36 GMT, end at Mon 2017-01-02 22:12:26 GMT. --
Jan 02 22:12:26 NAS quotaon[5157]: quotaon: cannot find /media/cbe1e2d4-0fad-472e-97a2-8f4dc3979687/aquota.group on /dev/sda1 [/media/cbe1e2d4-0fad-472e-97a2-8f4dc3979687]
Jan 02 22:12:26 NAS quotaon[5157]: quotaon: cannot find /media/cbe1e2d4-0fad-472e-97a2-8f4dc3979687/aquota.user on /dev/sda1 [/media/cbe1e2d4-0fad-472e-97a2-8f4dc3979687]
Jan 02 22:12:26 NAS systemd[1]: quotaon.service: main process exited, code=exited, status=6/NOTCONFIGURED
Jan 02 22:12:26 NAS systemd[1]: Failed to start Enable File System Quotas.
-- Subject: Unit quotaon.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit quotaon.service has failed.
-- 
-- The result is failed.
Jan 02 22:12:26 NAS systemd[1]: Unit quotaon.service entered failed state.
Jan 02 22:12:26 NAS systemd[1]: Starting SickBeard Daemon...
-- Subject: Unit sickbeard.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit sickbeard.service has begun starting up.
Jan 02 22:12:26 NAS systemd[5160]: Failed at step GROUP spawning /usr/bin/python: No such process
-- Subject: Process /usr/bin/python could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The process /usr/bin/python could not be executed and failed.
-- 
-- The error number returned while executing this process is 3.
Jan 02 22:12:26 NAS systemd[1]: sickbeard.service: control process exited, code=exited status=216
Jan 02 22:12:26 NAS systemd[1]: Failed to start SickBeard Daemon.
-- Subject: Unit sickbeard.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit sickbeard.service has failed.
-- 
-- The result is failed.
Jan 02 22:12:26 NAS systemd[1]: Unit sickbeard.service entered failed state.

Alles anzeigen

I repeated the process several times, just to ensure quotas is disabled, but I get the same error in journalctl

RS1 · 2. Januar 2017

I could try a fresh install of OMV3 as I upgraded from 2.xx..

RS1 · 3. Januar 2017

For anyone else who may experience issues with plugins etc - a fresh install of OMV3.xx sorted my particular problem out. I'm not exactly sure what the issue was before; however, I did mess around with the build quite a bit and also followed an upgrade path opposed to a clean install.

jhmiller · 3. Januar 2017

Happy to hear you got it going.

Jetzt mitmachen!