Getting nzbget to autorun

Hi,

Have followed the tutorial here ([HOW-TO] Install NZBGet on Raspberry Pi) and all seems to install and set up fine but it won’t auto run. I can usually run it manually but recently have got this message when trying-

osmc@HTPC:~$ sudo systemctl start nzbget
Job for nzbget.service failed because the control process exited with error code.
See “systemctl status nzbget.service” and “journalctl -xe” for details.
osmc@HTPC:~$

Any ideas? Ta

What’s the output from these 2 commands?

first is:

nzbget.service - NZBGet
Loaded: loaded (/etc/systemd/system/nzbget.service; enabled; vendor preset: e
Active: failed (Result: exit-code) since Mon 2019-01-07 20:03:33 GMT; 12min a
Process: 2453 ExecStop=/opt/nzbget/nzbget -Q (code=exited, status=1/FAILURE)
Process: 2450 ExecStart=/opt/nzbget/nzbget -c /opt/nzbget/nzbget.conf -D (code
Main PID: 2445 (code=exited, status=1/FAILURE)

Jan 07 20:03:33 HTPC systemd[1]: Failed to start NZBGet.
Jan 07 20:03:33 HTPC systemd[1]: nzbget.service: Unit entered failed state.
Jan 07 20:03:33 HTPC systemd[1]: nzbget.service: Failed with result ‘exit-code’.
Jan 07 20:03:33 HTPC systemd[1]: nzbget.service: Service hold-off time over, sch
Jan 07 20:03:33 HTPC systemd[1]: Stopped NZBGet.
Jan 07 20:03:33 HTPC systemd[1]: nzbget.service: Start request repeated too quic
Jan 07 20:03:33 HTPC systemd[1]: Failed to start NZBGet.
Jan 07 20:03:33 HTPC systemd[1]: nzbget.service: Unit entered failed state.
Jan 07 20:03:33 HTPC systemd[1]: nzbget.service: Failed with result ‘exit-code’.
lines 1-16/16 (END)…skipping…

  • nzbget.service - NZBGet
    Loaded: loaded (/etc/systemd/system/nzbget.service; enabled; vendor preset: enabled)
    Active: failed (Result: exit-code) since Mon 2019-01-07 20:03:33 GMT; 12min ago
    Process: 2453 ExecStop=/opt/nzbget/nzbget -Q (code=exited, status=1/FAILURE)
    Process: 2450 ExecStart=/opt/nzbget/nzbget -c /opt/nzbget/nzbget.conf -D (code=exited, status=0/SUCCESS)
    Main PID: 2445 (code=exited, status=1/FAILURE)

Jan 07 20:03:33 HTPC systemd[1]: Failed to start NZBGet.
Jan 07 20:03:33 HTPC systemd[1]: nzbget.service: Unit entered failed state.
Jan 07 20:03:33 HTPC systemd[1]: nzbget.service: Failed with result ‘exit-code’.
Jan 07 20:03:33 HTPC systemd[1]: nzbget.service: Service hold-off time over, scheduling restart.
Jan 07 20:03:33 HTPC systemd[1]: Stopped NZBGet.
Jan 07 20:03:33 HTPC systemd[1]: nzbget.service: Start request repeated too quickly.
Jan 07 20:03:33 HTPC systemd[1]: Failed to start NZBGet.
Jan 07 20:03:33 HTPC systemd[1]: nzbget.service: Unit entered failed state.
Jan 07 20:03:33 HTPC systemd[1]: nzbget.service: Failed with result ‘exit-code’.

second is:
Jan 07 20:16:35 HTPC sshd[3023]: Server listening on 0.0.0.0 port 22.
Jan 07 20:16:35 HTPC sshd[3023]: Server listening on :: port 22.
Jan 07 20:16:39 HTPC sshd[3019]: Failed password for root from 218.92.1.179 port 44400 ssh2
Jan 07 20:16:40 HTPC sshd[3019]: Failed password for root from 218.92.1.179 port 44400 ssh2
Jan 07 20:16:40 HTPC sshd[3019]: Failed password for root from 218.92.1.179 port 44400 ssh2
Jan 07 20:16:41 HTPC sshd[3019]: Failed password for root from 218.92.1.179 port 44400 ssh2
Jan 07 20:16:42 HTPC sshd[3019]: Failed password for root from 218.92.1.179 port 44400 ssh2
Jan 07 20:16:43 HTPC sshd[3019]: Failed password for root from 218.92.1.179 port 44400 ssh2
Jan 07 20:16:43 HTPC sshd[3019]: Disconnecting: Too many authentication failures for root [preauth]
Jan 07 20:16:52 HTPC sshd[3034]: Failed password for root from 218.92.1.179 port 60079 ssh2
Jan 07 20:16:53 HTPC sshd[3034]: Failed password for root from 218.92.1.179 port 60079 ssh2
Jan 07 20:16:53 HTPC sshd[3034]: Failed password for root from 218.92.1.179 port 60079 ssh2
Jan 07 20:16:54 HTPC sshd[3034]: Failed password for root from 218.92.1.179 port 60079 ssh2
Jan 07 20:16:55 HTPC sshd[3034]: Failed password for root from 218.92.1.179 port 60079 ssh2
Jan 07 20:16:56 HTPC sshd[3034]: Failed password for root from 218.92.1.179 port 60079 ssh2
Jan 07 20:16:56 HTPC sshd[3034]: Disconnecting: Too many authentication failures for root [preauth]
Jan 07 20:17:01 HTPC CRON[3051]: pam_unix(cron:session): session opened for user root by (uid=0)
Jan 07 20:17:01 HTPC CRON[3058]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 07 20:17:01 HTPC CRON[3051]: pam_unix(cron:session): session closed for user root
Jan 07 20:17:04 HTPC sshd[3045]: Failed password for root from 218.92.1.179 port 10673 ssh2
Jan 07 20:17:05 HTPC sshd[3045]: Failed password for root from 218.92.1.179 port 10673 ssh2
Jan 07 20:17:06 HTPC sshd[3045]: Failed password for root from 218.92.1.179 port 10673 ssh2
Jan 07 20:17:06 HTPC sshd[3045]: Failed password for root from 218.92.1.179 port 10673 ssh2
Jan 07 20:17:07 HTPC sshd[3045]: Failed password for root from 218.92.1.179 port 10673 ssh2
Jan 07 20:17:08 HTPC sshd[3045]: Failed password for root from 218.92.1.179 port 10673 ssh2
Jan 07 20:17:08 HTPC sshd[3045]: Disconnecting: Too many authentication failures for root [preauth]
Jan 07 20:17:15 HTPC sshd[3073]: Received disconnect from 218.92.1.145: 11: [preauth]

But I can also see there are invalid dir as I have formatted and renamed drives since

osmc@HTPC:~$ sudo journalctl -u nzbget
– Logs begin at Mon 2019-01-07 19:58:27 GMT, end at Mon 2019-01-07 20:17:53 GMT. –
Jan 07 19:58:28 HTPC systemd[1]: Starting NZBGet…
Jan 07 19:58:28 HTPC nzbget[379]: media/New Volume/temp/nzbget-2019-01-07.log: No such file or directory
Jan 07 19:58:28 HTPC nzbget[379]: nzbget.conf(55): Invalid value for option “TempDir” (media/New Volume/temp/media/New Volume/temp): could not create directory media/Ne
Jan 07 19:58:28 HTPC nzbget[379]: nzbget.conf(52): Invalid value for option “QueueDir” (media/New Volume/temp/media/New Volume/temp/queue): could not create directory m
Jan 07 19:58:28 HTPC systemd[1]: Started NZBGet.
Jan 07 19:58:28 HTPC systemd[1]: nzbget.service: Main process exited, code=exited, status=1/FAILURE
Jan 07 19:58:28 HTPC nzbget[489]: media/New Volume/temp/nzbget-2019-01-07.log: No such file or directory
Jan 07 19:58:28 HTPC nzbget[489]: media/New Volume/temp/nzbget-2019-01-07.log: No such file or directory
Jan 07 19:58:28 HTPC nzbget[489]: nzbget.conf(55): Invalid value for option “TempDir” (media/New Volume/temp/media/New Volume/temp): could not create directory media/Ne
Jan 07 19:58:28 HTPC nzbget[489]: nzbget.conf(52): Invalid value for option “QueueDir” (media/New Volume/temp/media/New Volume/temp/queue): could not create directory m
Jan 07 19:58:28 HTPC systemd[1]: nzbget.service: Control process exited, code=exited status=1
Jan 07 19:58:28 HTPC systemd[1]: nzbget.service: Unit entered failed state.
Jan 07 19:58:28 HTPC systemd[1]: nzbget.service: Failed with result ‘exit-code’.
Jan 07 19:58:28 HTPC systemd[1]: nzbget.service: Service hold-off time over, scheduling restart.
Jan 07 19:58:28 HTPC systemd[1]: Stopped NZBGet.
Jan 07 19:58:28 HTPC systemd[1]: Starting NZBGet…
Jan 07 19:58:28 HTPC nzbget[537]: media/New Volume/temp/nzbget-2019-01-07.log: No such file or directory
Jan 07 19:58:28 HTPC nzbget[537]: media/New Volume/temp/nzbget-2019-01-07.log: No such file or directory
Jan 07 19:58:28 HTPC nzbget[537]: media/New Volume/temp/nzbget-2019-01-07.log: No such file or directory
Jan 07 19:58:28 HTPC nzbget[537]: media/New Volume/temp/nzbget-2019-01-07.log: No such file or directory
Jan 07 19:58:28 HTPC nzbget[537]: nzbget.conf(55): Invalid value for option “TempDir” (media/New Volume/temp/media/New Volume/temp): could not create directory media/Ne
Jan 07 19:58:28 HTPC nzbget[537]: nzbget.conf(52): Invalid value for option “QueueDir” (media/New Volume/temp/media/New Volume/temp/queue): could not create directory m
Jan 07 19:58:28 HTPC nzbget[537]: nzbget.conf(46): Invalid value for option “NzbDir” (media/New Volume/temp/media/New Volume/temp): could not create directory media/New
Jan 07 19:58:28 HTPC nzbget[541]: media/New Volume/temp/nzbget-2019-01-07.log: No such file or directory
Jan 07 19:58:28 HTPC nzbget[541]: media/New Volume/temp/nzbget-2019-01-07.log: No such file or directory
Jan 07 19:58:28 HTPC nzbget[541]: nzbget.conf(55): Invalid value for option “TempDir” (media/New Volume/temp/media/New Volume/temp): could not create directory media/Ne
Jan 07 19:58:28 HTPC nzbget[541]: nzbget.conf(52): Invalid value for option “QueueDir” (media/New Volume/temp/media/New Volume/temp/queue): could not create directory m
Jan 07 19:58:28 HTPC nzbget[541]: nzbget.conf(46): Invalid value for option “NzbDir” (media/New Volume/temp/media/New Volume/temp): could not create directory media/New
Jan 07 19:58:28 HTPC nzbget[541]: Unable to send request to nzbget-server at 127.0.0.1 (port 6789)
Jan 07 19:58:28 HTPC systemd[1]: nzbget.service: Control process exited, code=exited status=1
Jan 07 19:58:28 HTPC systemd[1]: Failed to start NZBGet.
Jan 07 19:58:28 HTPC systemd[1]: nzbget.service: Unit entered failed state.
Jan 07 19:58:28 HTPC systemd[1]: nzbget.service: Failed with result ‘exit-code’.
Jan 07 19:58:28 HTPC systemd[1]: nzbget.service: Service hold-off time over, scheduling restart.
Jan 07 19:58:28 HTPC systemd[1]: Stopped NZBGet.
Jan 07 19:58:28 HTPC systemd[1]: Starting NZBGet…
Jan 07 19:58:29 HTPC nzbget[575]: media/New Volume/temp/nzbget-2019-01-07.log: No such file or directory
Jan 07 19:58:29 HTPC nzbget[575]: media/New Volume/temp/nzbget-2019-01-07.log: No such file or directory
Jan 07 19:58:29 HTPC nzbget[575]: nzbget.conf(55): Invalid value for option “TempDir” (media/New Volume/temp/media/New Volume/temp): could not create directory media/Ne
Jan 07 19:58:29 HTPC nzbget[575]: nzbget.conf(52): Invalid value for option “QueueDir” (media/New Volume/temp/media/New Volume/temp/queue): could not create directory m
Jan 07 19:58:29 HTPC nzbget[578]: media/New Volume/temp/nzbget-2019-01-07.log: No such file or directory
Jan 07 19:58:29 HTPC nzbget[578]: media/New Volume/temp/nzbget-2019-01-07.log: No such file or directory

What’s your /etc/systemd/system/nzbget.service file contents?

It’s your one from the tutorial; however, I did amend it using the tutorial on nzbget site, which didn’t work, so deleted content and added yours back. My concern is that when I wrote out I appended. Would that keep both file contents?

That being said, when I open it up , I only see the text from your tutorial

Why are you using a user called nzbget? If the contents of /etc/systemd/system/nzbget.service are looking for group and user osmc it won’t work with another user

Saw it on a forum post where you had posted previously and thought it might reveal something useful.

What do I need to do then? Ta

So paste the output from sudo systemctl status nzbget.service and sudo journalctl -xe

Also try the nzbget.log file which is probably in the main directory you set in the nzbget setup

Loaded: loaded (/etc/systemd/system/nzbget.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2019-01-07 20:32:54 GMT; 4min 37s ago
Process: 617 ExecStop=/opt/nzbget/nzbget -Q (code=exited, status=1/FAILURE)
Process: 606 ExecStart=/opt/nzbget/nzbget -c /opt/nzbget/nzbget.conf -D (code=exited, status=0/SUCCESS)
Main PID: 614 (code=exited, status=1/FAILURE)

Jan 07 20:32:54 HTPC systemd[1]: nzbget.service: Control process exited, code=exited status=1
Jan 07 20:32:54 HTPC systemd[1]: nzbget.service: Unit entered failed state.
Jan 07 20:32:54 HTPC systemd[1]: nzbget.service: Failed with result ‘exit-code’.
Jan 07 20:32:54 HTPC systemd[1]: nzbget.service: Service hold-off time over, scheduling restart.
Jan 07 20:32:54 HTPC systemd[1]: Stopped NZBGet.
Jan 07 20:32:54 HTPC systemd[1]: nzbget.service: Start request repeated too quickly.
Jan 07 20:32:54 HTPC systemd[1]: Failed to start NZBGet.
Jan 07 20:32:54 HTPC systemd[1]: nzbget.service: Unit entered failed state.
Jan 07 20:32:54 HTPC systemd[1]: nzbget.service: Failed with result ‘exit-code’

osmc@HTPC:~$ journalctl -xe

– Unit systemd-update-utmp-runlevel.service has begun starting up.
Jan 07 20:34:23 HTPC systemd[1]: Started Update UTMP about System Runlevel Changes.
– Subject: Unit systemd-update-utmp-runlevel.service has finished start-up
– Defined-By: systemd
– Support: Debian -- Support

– Unit systemd-update-utmp-runlevel.service has finished starting up.

– The start-up result is done.
Jan 07 20:34:23 HTPC systemd[1]: Startup finished in 3.476s (kernel) + 1min 31.815s (userspace) = 1min 35.292s.
– Subject: System start-up is now complete
– Defined-By: systemd
– Support: Debian -- Support

– All system services necessary queued for starting at boot have been
– successfully started. Note that this does not mean that the machine is
– now idle as services might still be busy with completing start-up.

– Kernel start-up required 3476612 microseconds.

– Initial RAM disk start-up required INITRD_USEC microseconds.

– Userspace start-up required 91815968 microseconds.
Jan 07 20:34:24 HTPC systemd[1]: ssh.service: Service hold-off time over, scheduling restart.
Jan 07 20:34:24 HTPC systemd[1]: Stopped OpenBSD Secure Shell server.
– Subject: Unit ssh.service has finished shutting down
– Defined-By: systemd
– Support: Debian -- Support

– Unit ssh.service has finished shutting down.
Jan 07 20:34:24 HTPC systemd[1]: Starting OpenBSD Secure Shell server…
– Subject: Unit ssh.service has begun start-up
– Defined-By: systemd
– Support: Debian -- Support

– Unit ssh.service has begun starting up.
Jan 07 20:34:24 HTPC sshd[2165]: Server listening on 0.0.0.0 port 22.
Jan 07 20:34:24 HTPC sshd[2165]: Server listening on :: port 22.
Jan 07 20:34:24 HTPC sshd[2149]: Failed password for root from 218.92.1.179 port 28175 ssh2
Jan 07 20:34:25 HTPC sshd[2149]: Failed password for root from 218.92.1.179 port 28175 ssh2
Jan 07 20:34:25 HTPC sshd[2149]: Failed password for root from 218.92.1.179 port 28175 ssh2
Jan 07 20:34:25 HTPC sshd[2149]: Disconnecting: Too many authentication failures for root [preauth]
lines 1092-1134/1134 (END)

– Unit systemd-update-utmp-runlevel.service has begun starting up.
Jan 07 20:34:23 HTPC systemd[1]: Started Update UTMP about System Runlevel Changes.
– Subject: Unit systemd-update-utmp-runlevel.service has finished start-up
– Defined-By: systemd
– Support: Debian -- Support

– Unit systemd-update-utmp-runlevel.service has finished starting up.

– The start-up result is done.
Jan 07 20:34:23 HTPC systemd[1]: Startup finished in 3.476s (kernel) + 1min 31.815s (userspace) = 1min 35.292s.
– Subject: System start-up is now complete
– Defined-By: systemd
– Support: Debian -- Support

– All system services necessary queued for starting at boot have been
– successfully started. Note that this does not mean that the machine is
– now idle as services might still be busy with completing start-up.

– Kernel start-up required 3476612 microseconds.

– Initial RAM disk start-up required INITRD_USEC microseconds.

– Userspace start-up required 91815968 microseconds.
Jan 07 20:34:24 HTPC systemd[1]: ssh.service: Service hold-off time over, scheduling restart.
Jan 07 20:34:24 HTPC systemd[1]: Stopped OpenBSD Secure Shell server.
– Subject: Unit ssh.service has finished shutting down
– Defined-By: systemd
– Support: Debian -- Support

– Unit ssh.service has finished shutting down.
Jan 07 20:34:24 HTPC systemd[1]: Starting OpenBSD Secure Shell server…
– Subject: Unit ssh.service has begun start-up
– Defined-By: systemd
– Support: Debian -- Support

– Unit ssh.service has begun starting up.
Jan 07 20:34:24 HTPC sshd[2165]: Server listening on 0.0.0.0 port 22.
Jan 07 20:34:24 HTPC sshd[2165]: Server listening on :: port 22.
Jan 07 20:34:24 HTPC sshd[2149]: Failed password for root from 218.92.1.179 port 28175 ssh2
Jan 07 20:34:25 HTPC sshd[2149]: Failed password for root from 218.92.1.179 port 28175 ssh2
Jan 07 20:34:25 HTPC sshd[2149]: Failed password for root from 218.92.1.179 port 28175 ssh2
osmc@HTPC:~$ sudo systemctl status nzbget.service

  • nzbget.service - NZBGet
    Loaded: loaded (/etc/systemd/system/nzbget.service; enabled; vendor preset: enabled)
    Active: failed (Result: exit-code) since Mon 2019-01-07 20:32:54 GMT; 4min 37s ago
    Process: 617 ExecStop=/opt/nzbget/nzbget -Q (code=exited, status=1/FAILURE)
    Process: 606 ExecStart=/opt/nzbget/nzbget -c /opt/nzbget/nzbget.conf -D (code=exited, status=0/SUCCESS)
    Main PID: 614 (code=exited, status=1/FAILURE)

Jan 07 20:32:54 HTPC systemd[1]: nzbget.service: Control process exited, code=exited status=1
Jan 07 20:32:54 HTPC systemd[1]: nzbget.service: Unit entered failed state.
Jan 07 20:32:54 HTPC systemd[1]: nzbget.service: Failed with result ‘exit-code’.
Jan 07 20:32:54 HTPC systemd[1]: nzbget.service: Service hold-off time over, scheduling restart.
Jan 07 20:32:54 HTPC systemd[1]: Stopped NZBGet.
Jan 07 20:32:54 HTPC systemd[1]: nzbget.service: Start request repeated too quickly.
Jan 07 20:32:54 HTPC systemd[1]: Failed to start NZBGet.
Jan 07 20:32:54 HTPC systemd[1]: nzbget.service: Unit entered failed state.
Jan 07 20:32:54 HTPC systemd[1]: nzbget.service: Failed with result ‘exit-code’.
osmc@HTPC:~$ sudo journalctl -xe
Jan 07 20:37:33 HTPC sshd[2301]: Failed password for root from 218.92.1.179 port 1513 ssh2
Jan 07 20:37:33 HTPC sshd[2301]: Failed password for root from 218.92.1.179 port 1513 ssh2
Jan 07 20:37:34 HTPC sshd[2301]: Failed password for root from 218.92.1.179 port 1513 ssh2
Jan 07 20:37:34 HTPC sshd[2301]: Disconnecting: Too many authentication failures for root [preauth]
Jan 07 20:37:34 HTPC sshd[2308]: Received disconnect from 218.92.1.145: 11: [preauth]
Jan 07 20:37:43 HTPC sshd[2328]: Failed password for root from 218.92.1.179 port 15774 ssh2
Jan 07 20:37:43 HTPC sshd[2328]: Failed password for root from 218.92.1.179 port 15774 ssh2
Jan 07 20:37:44 HTPC mono[387]: [Info] RssSyncService: Starting RSS Sync
Jan 07 20:37:44 HTPC sshd[2328]: Failed password for root from 218.92.1.179 port 15774 ssh2
Jan 07 20:37:45 HTPC sshd[2328]: Failed password for root from 218.92.1.179 port 15774 ssh2
Jan 07 20:37:46 HTPC sshd[2328]: Failed password for root from 218.92.1.179 port 15774 ssh2
Jan 07 20:37:46 HTPC sshd[2328]: Failed password for root from 218.92.1.179 port 15774 ssh2
Jan 07 20:37:46 HTPC sshd[2328]: Disconnecting: Too many authentication failures for root [preauth]
Jan 07 20:37:48 HTPC mono[387]: [Info] DownloadDecisionMaker: Processing 300 releases
Jan 07 20:37:48 HTPC systemd[1]: Starting Report anonymous OSMC install statistics…
– Subject: Unit osmc-report-stats.service has begun start-up
– Defined-By: systemd
– Support: Debian -- Support

– Unit osmc-report-stats.service has begun starting up.
Jan 07 20:37:49 HTPC systemd[1]: Started Report anonymous OSMC install statistics.
– Subject: Unit osmc-report-stats.service has finished start-up
– Defined-By: systemd
– Support: Debian -- Support

– Unit osmc-report-stats.service has finished starting up.

– The start-up result is done.
Jan 07 20:37:55 HTPC mono[387]: [Info] RssSyncService: RSS Sync Completed. Reports found: 300, Reports grabbed: 0
Jan 07 20:37:56 HTPC sshd[2373]: Failed password for root from 218.92.1.179 port 29773 ssh2
Jan 07 20:37:57 HTPC sshd[2373]: Failed password for root from 218.92.1.179 port 29773 ssh2
Jan 07 20:37:57 HTPC sshd[2373]: Failed password for root from 218.92.1.179 port 29773 ssh2
Jan 07 20:37:58 HTPC sshd[2373]: Failed password for root from 218.92.1.179 port 29773 ssh2
Jan 07 20:37:59 HTPC sshd[2373]: Failed password for root from 218.92.1.179 port 29773 ssh2
Jan 07 20:38:00 HTPC sshd[2373]: Failed password for root from 218.92.1.179 port 29773 ssh2
Jan 07 20:38:00 HTPC sshd[2373]: Disconnecting: Too many authentication failures for root [preauth]
Jan 07 20:38:08 HTPC sshd[2385]: Failed password for root from 218.92.1.179 port 44783 ssh2
Jan 07 20:38:09 HTPC sshd[2385]: Failed password for root from 218.92.1.179 port 44783 ssh2
Jan 07 20:38:10 HTPC sshd[2385]: Failed password for root from 218.92.1.179 port 44783 ssh2
Jan 07 20:38:10 HTPC sshd[2385]: Failed password for root from 218.92.1.179 port 44783 ssh2
Jan 07 20:38:11 HTPC sudo[2389]: osmc : TTY=pts/0 ; PWD=/home/osmc ; USER=root ; COMMAND=/bin/journalctl -xe
Jan 07 20:38:11 HTPC sudo[2389]: pam_unix(sudo:session): session opened for user root by osmc(uid=0)

Can’t find a log in /opt/nzbget

Only these

7za ChangeLog cacert.pem install-update.sh license-7zip.txt nzbget pubkey.pem unrar
COPYING README downloads installer.cfg license-unrar.txt nzbget.conf scripts webui

Is your external storage mounted here? Have you let OSMC auto-mount it?

Am I supposed to edit with a drive name there as I had just pasted your contents directly?

Well, it’s started up. I edited the config file and removed those obsolete entries.

But it doesn’t survive a reboot, have to manually start

Please paste the contents of;
ls /media

osmc@HTPC:~$ ls /media
README disk1 disk2 disk3

Which disk is the media on?

Movies on two drives, Tv on another

OK, try this;

sudo systemctl list-units --type=mount

Output for me is this; (I only have one external HD mounted)

UNIT                    LOAD   ACTIVE SUB     DESCRIPTION                                                                                                                                                        
* -.mount                 error  active mounted Root Mount                                                                                                                                                           
dev-mqueue.mount        loaded active mounted POSIX Message Queue File System                                                                                                                                      
media-externalHD.mount  loaded active mounted /media/externalHD                                                                                                                                                    
proc-fs-nfsd.mount      loaded active mounted NFSD configuration filesystem                                                                                                                                        
run-rpc_pipefs.mount    loaded active mounted RPC Pipe File System                                                                                                                                                 
run-user-1000.mount     loaded active mounted /run/user/1000                                                                                                                                                       
sys-kernel-config.mount loaded active mounted Configuration File System                                                                                                                                            
sys-kernel-debug.mount  loaded active mounted Debug File System

I am interested in the 3rd line media-externalHD.mount loaded active mounted /media/externalHD as this is where my drive is mounted. You’ll be looking for the mounts with /media/disk1 /media/disk2 /media/disk3.

Add these to the file /etc/systemd/system/nzbget.service in the After block. See Below for whole file I am using;

[Unit]
Description=NZBGet
After=network.target media-externalHD.mount

[Service]
User=osmc
Group=osmc
Type=forking
ExecStart=/opt/nzbget/nzbget -c /opt/nzbget/nzbget.conf -D
ExecStop=/opt/nzbget/nzbget -Q
ExecReload=/opt/nzbget/nzbget -O
KillMode=process
Restart=on-failure

[Install]
WantedBy=multi-user.target

Of course you’ll need to append After=network.target with your outputs that are relevant to you.

Save & quit

Reload the systemctl daemon;
sudo systemctl daemon-reload

Now reboot to see if it restarts at boot

Sorry, when you say to add after=network.target media-externalHD.mount
are all entries to be added on the same line with just a space between each?

Ta