Package Details: sabnzbd 4.3.3-1

Git Clone URL: https://aur.archlinux.org/sabnzbd.git (read-only, click to copy)
Package Base: sabnzbd
Description: A web-interface based binary newsgrabber with NZB file support
Upstream URL: http://www.sabnzbd.org
Keywords: network usenet
Licenses: GPL
Submitter: esh
Maintainer: fryfrog
Last Packager: fryfrog
Votes: 270
Popularity: 0.61
First Submitted: 2007-11-09 16:21 (UTC)
Last Updated: 2024-08-21 15:57 (UTC)

Latest Comments

« First ‹ Previous 1 .. 33 34 35 36 37 38 39 40 41 42 43 .. 64 Next › Last »

<deleted-account> commented on 2012-11-07 23:07 (UTC)

@brando56894 @Revelation60 I ran into the same problem. The ,pid file reference in "/etc/systemd/system/sabnzbd.service" didn't contain the right port number because it seems to have been overwritten in a update.

Revelation60 commented on 2012-11-04 16:21 (UTC)

Well, this is a completely different issue, because sabnzbd.service is found and executed, only execution fails. Are you using custom settings, like custom ports, etc? Have you read the wiki (https://wiki.archlinux.org/index.php/SABnzbd)?

brando56894 commented on 2012-11-04 16:08 (UTC)

Didn't fix anything [bran@ra ~]$ sudo systemctl --system daemon-reload [sudo] password for bran: [bran@ra ~]$ sudo systemctl start sabnzbd Job for sabnzbd.service failed. See 'systemctl status sabnzbd.service' and 'journalctl -n' for details. [bran@ra ~]$ sudo systemctl status sabnzbd.service sabnzbd.service - SABnzbd binary newsreader Loaded: loaded (/usr/lib/systemd/system/sabnzbd.service; enabled) Active: failed (Result: exit-code) since Sun, 2012-11-04 07:05:34 EST; 23s ago Process: 562 ExecStart=/bin/sh/ -c python2 ${SABNZBD_DIR}/SABnzbd.py ${SABNZBD_ARGS} --pid /run/sabnzbd (code=exited, status=2) CGroup: name=systemd:/system/sabnzbd.service Nov 04 07:05:34 ra systemd[1]: Failed to start SABnzbd binary newsreader. Nov 04 07:05:34 ra systemd[1]: Unit sabnzbd.service entered failed state [bran@ra ~]$ journalctl -n Unprivileged users can't see messages unless persistent log storage is enabled. Users in the group 'adm' can always see messages. [bran@ra ~]$ sudo journalctl -n -- Logs begin at Sat, 2012-11-03 18:44:01 EDT, end at Sun, 2012-11-04 07:06:42 EST. -- Nov 04 07:05:34 ra systemd[1]: Starting SABnzbd binary newsreader... Nov 04 07:05:34 ra systemd[1]: sabnzbd.service: control process exited, code=exited status=2 Nov 04 07:05:34 ra systemd[1]: Failed to start SABnzbd binary newsreader. Nov 04 07:05:34 ra systemd[1]: Unit sabnzbd.service entered failed state Nov 04 07:05:34 ra sudo[559]: pam_unix(sudo:session): session closed for user root Nov 04 07:05:58 ra sudo[623]: bran : TTY=pts/2 ; PWD=/home/bran ; USER=root ; COMMAND=/usr/bin/systemctl status sabnzbd.service Nov 04 07:05:58 ra sudo[623]: pam_unix(sudo:session): session opened for user root by (uid=0) Nov 04 07:05:58 ra sudo[623]: pam_unix(sudo:session): session closed for user root Nov 04 07:06:42 ra sudo[708]: bran : TTY=pts/2 ; PWD=/home/bran ; USER=root ; COMMAND=/usr/bin/journalctl -n Nov 04 07:06:42 ra sudo[708]: pam_unix(sudo:session): session opened for user root by (uid=0)

Revelation60 commented on 2012-11-04 11:11 (UTC)

Probably systemd caches all the files. Have you tried running 'systemctl --system daemon-reload'?

brando56894 commented on 2012-11-04 02:55 (UTC)

the SABnzbd target doesn't seem to exist in the right places or something since when I try to do "systemctl start <tab complete>" nothing shows up as shown here: [bran@ra ~]$ sudo systemctl start alsa-restore.service systemd-fsck@dev-disk-by\x2duuid-27df0f80\x2d1b79\x2d4bf1\x2dac89\x2d1dc0eb68a149.service alsa-store.service systemd-fsck@dev-disk-by\x2duuid-30cd911b\x2dfb5d\x2d4f41\x2d9067\x2d39444c4726d6.service auditd.service systemd-fsck@dev-disk-by\x2duuid-450fec66\x2dbe30\x2d4245\x2db81e\x2d857e6169a113.service emergency.service systemd-fsck@dev-disk-by\x2duuid-5fb000cd\x2dd8cb\x2d4474\x2d8457\x2de7f5ebdae05b.service emergency.target systemd-fsck@dev-disk-by\x2duuid-761c9327\x2dd247\x2d43ce\x2d8d93\x2db58e14d977d3.service nss-user-lookup.target systemd-fsck@dev-disk-by\x2duuid-b2e2cf8d\x2d1cbe\x2d4b6c\x2daa52\x2d45eb5b93cec3.service plymouth-quit-wait.service systemd-fsck-root.service plymouth-start.service systemd-initctl.service proc-sys-fs-binfmt_misc.mount systemd-journal-flush.service rc-local.service systemd-random-seed-load.service rescue.service systemd-random-seed-save.service rescue.target systemd-readahead-collect.service sshdgenkeys.service systemd-readahead-done.service sys-kernel-config.mount systemd-readahead-done.timer syslog.service systemd-readahead-replay.service syslog.socket systemd-shutdownd.service syslog.target systemd-tmpfiles-clean.service systemd-ask-password-console.service systemd-update-utmp-runlevel.service systemd-ask-password-wall.service systemd-update-utmp-shutdown.service systemd-binfmt.service but it does exist as seen here: [bran@ra ~]$ locate .service|grep -i sabnzbd /etc/systemd/system/multi-user.target.wants/sabnzbd.service /usr/lib/systemd/system/sabnzbd.service Maybe I'm doing something wrong since I just migrated from sysvinit to systemd about a week or so ago and I'm still trying to understand it fully. I copied /usr/lib/tmpfiles.d/sabnzbd.conf to /etc/tmpfiles.d/sabnzbd.conf since it wouldn't start on boot for me.

robotanarchy commented on 2012-10-25 18:16 (UTC)

Could you make xdg-utils optional? It pulls xorg dependencies on headless machines. Thanks for the PKGBUILD!

terminalmage commented on 2012-10-24 03:21 (UTC)

@splippity: Please review the systemd wiki page. /etc/systemd and /etc/tmpfiles.d take precedence over the files installed by the package.

splippity commented on 2012-10-24 01:45 (UTC)

I too have the same issue. I also have to keep changing my /usr/lib/systemd/system/sabnzbd.service to reflect the correct user. I just took the advice about copying the conf file from /lib/tmpfiles.d to /etc/tmpfiles.d so hopefully that stabilizes that issue. thanks

« First ‹ Previous 1 .. 33 34 35 36 37 38 39 40 41 42 43 .. 64 Next › Last »