systemd service failing












4















For no reason I can think of Nzbget has stopped running. I have changed nothing and the service just stopped and refused to restart.



 sudo systemctl status nzbget -l
* nzbget.service - NZBGet Daemon
Loaded: loaded (/etc/systemd/system/nzbget.service; enabled)
Active: failed (Result: start-limit) since Sun 2016-05-01 06:23:27 BST; 2min 46s ago
Process: 596 ExecStop=/opt/nzbget/nzbget -Q (code=exited, status=0/SUCCESS) Process: 586 ExecStart=/opt/nzbget/nzbget -c /opt/nzbget/nzbget.conf -D (code=exited, status=0/SUCCESS)
Main PID: 588 (code=killed, signal=ABRT)

May 01 06:23:27 osmc systemd[1]: Unit nzbget.service entered failed state.
May 01 06:23:27 osmc systemd[1]: nzbget.service start request repeated too quickly, refusing to start.
May 01 06:23:27 osmc systemd[1]: Failed to start NZBGet Daemon.
May 01 06:23:27 osmc systemd[1]: Unit nzbget.service entered failed state.


Here is the log;



osmc@osmc:~/Downloads$ 
cat nzbget.log
Sun May 1 06:38:44 2016 INFO nzbget 16.4 daemon-mode
Sun May 1 06:38:44 2016 INFO nzbget 16.4 daemon-mode
Sun May 1 06:38:45 2016 INFO nzbget 16.4 daemon-mode
Sun May 1 06:38:45 2016 INFO nzbget 16.4 daemon-mode
Sun May 1 06:38:46 2016 INFO nzbget 16.4 daemon-mode


Here's the service;



[Unit]
Description=NZBGet Daemon
After=network.target
RequiresMountsFor=/mnt/

[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









share|improve this question
















bumped to the homepage by Community 3 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Does the service log somewhere other than stdout?

    – jordanm
    May 1 '16 at 5:39






  • 2





    journalctl _PID=588...

    – jasonwryan
    May 1 '16 at 6:11











  • Can you post systemctl cat nzbget.service?

    – zhenech
    May 1 '16 at 6:29
















4















For no reason I can think of Nzbget has stopped running. I have changed nothing and the service just stopped and refused to restart.



 sudo systemctl status nzbget -l
* nzbget.service - NZBGet Daemon
Loaded: loaded (/etc/systemd/system/nzbget.service; enabled)
Active: failed (Result: start-limit) since Sun 2016-05-01 06:23:27 BST; 2min 46s ago
Process: 596 ExecStop=/opt/nzbget/nzbget -Q (code=exited, status=0/SUCCESS) Process: 586 ExecStart=/opt/nzbget/nzbget -c /opt/nzbget/nzbget.conf -D (code=exited, status=0/SUCCESS)
Main PID: 588 (code=killed, signal=ABRT)

May 01 06:23:27 osmc systemd[1]: Unit nzbget.service entered failed state.
May 01 06:23:27 osmc systemd[1]: nzbget.service start request repeated too quickly, refusing to start.
May 01 06:23:27 osmc systemd[1]: Failed to start NZBGet Daemon.
May 01 06:23:27 osmc systemd[1]: Unit nzbget.service entered failed state.


Here is the log;



osmc@osmc:~/Downloads$ 
cat nzbget.log
Sun May 1 06:38:44 2016 INFO nzbget 16.4 daemon-mode
Sun May 1 06:38:44 2016 INFO nzbget 16.4 daemon-mode
Sun May 1 06:38:45 2016 INFO nzbget 16.4 daemon-mode
Sun May 1 06:38:45 2016 INFO nzbget 16.4 daemon-mode
Sun May 1 06:38:46 2016 INFO nzbget 16.4 daemon-mode


Here's the service;



[Unit]
Description=NZBGet Daemon
After=network.target
RequiresMountsFor=/mnt/

[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









share|improve this question
















bumped to the homepage by Community 3 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Does the service log somewhere other than stdout?

    – jordanm
    May 1 '16 at 5:39






  • 2





    journalctl _PID=588...

    – jasonwryan
    May 1 '16 at 6:11











  • Can you post systemctl cat nzbget.service?

    – zhenech
    May 1 '16 at 6:29














4












4








4








For no reason I can think of Nzbget has stopped running. I have changed nothing and the service just stopped and refused to restart.



 sudo systemctl status nzbget -l
* nzbget.service - NZBGet Daemon
Loaded: loaded (/etc/systemd/system/nzbget.service; enabled)
Active: failed (Result: start-limit) since Sun 2016-05-01 06:23:27 BST; 2min 46s ago
Process: 596 ExecStop=/opt/nzbget/nzbget -Q (code=exited, status=0/SUCCESS) Process: 586 ExecStart=/opt/nzbget/nzbget -c /opt/nzbget/nzbget.conf -D (code=exited, status=0/SUCCESS)
Main PID: 588 (code=killed, signal=ABRT)

May 01 06:23:27 osmc systemd[1]: Unit nzbget.service entered failed state.
May 01 06:23:27 osmc systemd[1]: nzbget.service start request repeated too quickly, refusing to start.
May 01 06:23:27 osmc systemd[1]: Failed to start NZBGet Daemon.
May 01 06:23:27 osmc systemd[1]: Unit nzbget.service entered failed state.


Here is the log;



osmc@osmc:~/Downloads$ 
cat nzbget.log
Sun May 1 06:38:44 2016 INFO nzbget 16.4 daemon-mode
Sun May 1 06:38:44 2016 INFO nzbget 16.4 daemon-mode
Sun May 1 06:38:45 2016 INFO nzbget 16.4 daemon-mode
Sun May 1 06:38:45 2016 INFO nzbget 16.4 daemon-mode
Sun May 1 06:38:46 2016 INFO nzbget 16.4 daemon-mode


Here's the service;



[Unit]
Description=NZBGet Daemon
After=network.target
RequiresMountsFor=/mnt/

[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









share|improve this question
















For no reason I can think of Nzbget has stopped running. I have changed nothing and the service just stopped and refused to restart.



 sudo systemctl status nzbget -l
* nzbget.service - NZBGet Daemon
Loaded: loaded (/etc/systemd/system/nzbget.service; enabled)
Active: failed (Result: start-limit) since Sun 2016-05-01 06:23:27 BST; 2min 46s ago
Process: 596 ExecStop=/opt/nzbget/nzbget -Q (code=exited, status=0/SUCCESS) Process: 586 ExecStart=/opt/nzbget/nzbget -c /opt/nzbget/nzbget.conf -D (code=exited, status=0/SUCCESS)
Main PID: 588 (code=killed, signal=ABRT)

May 01 06:23:27 osmc systemd[1]: Unit nzbget.service entered failed state.
May 01 06:23:27 osmc systemd[1]: nzbget.service start request repeated too quickly, refusing to start.
May 01 06:23:27 osmc systemd[1]: Failed to start NZBGet Daemon.
May 01 06:23:27 osmc systemd[1]: Unit nzbget.service entered failed state.


Here is the log;



osmc@osmc:~/Downloads$ 
cat nzbget.log
Sun May 1 06:38:44 2016 INFO nzbget 16.4 daemon-mode
Sun May 1 06:38:44 2016 INFO nzbget 16.4 daemon-mode
Sun May 1 06:38:45 2016 INFO nzbget 16.4 daemon-mode
Sun May 1 06:38:45 2016 INFO nzbget 16.4 daemon-mode
Sun May 1 06:38:46 2016 INFO nzbget 16.4 daemon-mode


Here's the service;



[Unit]
Description=NZBGet Daemon
After=network.target
RequiresMountsFor=/mnt/

[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






systemd






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 1 '16 at 6:57







eekfonky

















asked May 1 '16 at 5:32









eekfonkyeekfonky

177520




177520





bumped to the homepage by Community 3 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 3 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Does the service log somewhere other than stdout?

    – jordanm
    May 1 '16 at 5:39






  • 2





    journalctl _PID=588...

    – jasonwryan
    May 1 '16 at 6:11











  • Can you post systemctl cat nzbget.service?

    – zhenech
    May 1 '16 at 6:29



















  • Does the service log somewhere other than stdout?

    – jordanm
    May 1 '16 at 5:39






  • 2





    journalctl _PID=588...

    – jasonwryan
    May 1 '16 at 6:11











  • Can you post systemctl cat nzbget.service?

    – zhenech
    May 1 '16 at 6:29

















Does the service log somewhere other than stdout?

– jordanm
May 1 '16 at 5:39





Does the service log somewhere other than stdout?

– jordanm
May 1 '16 at 5:39




2




2





journalctl _PID=588...

– jasonwryan
May 1 '16 at 6:11





journalctl _PID=588...

– jasonwryan
May 1 '16 at 6:11













Can you post systemctl cat nzbget.service?

– zhenech
May 1 '16 at 6:29





Can you post systemctl cat nzbget.service?

– zhenech
May 1 '16 at 6:29










1 Answer
1






active

oldest

votes


















0














Weird one. I removed all files in the following folders;



Nzb, intermediate, queue



Restarted the service and that did the trick. No idea why but it's now all working again






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "106"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f280321%2fsystemd-service-failing%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Weird one. I removed all files in the following folders;



    Nzb, intermediate, queue



    Restarted the service and that did the trick. No idea why but it's now all working again






    share|improve this answer




























      0














      Weird one. I removed all files in the following folders;



      Nzb, intermediate, queue



      Restarted the service and that did the trick. No idea why but it's now all working again






      share|improve this answer


























        0












        0








        0







        Weird one. I removed all files in the following folders;



        Nzb, intermediate, queue



        Restarted the service and that did the trick. No idea why but it's now all working again






        share|improve this answer













        Weird one. I removed all files in the following folders;



        Nzb, intermediate, queue



        Restarted the service and that did the trick. No idea why but it's now all working again







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered May 1 '16 at 19:43









        eekfonkyeekfonky

        177520




        177520






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f280321%2fsystemd-service-failing%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            CARDNET

            Boot-repair Failure: Unable to locate package grub-common:i386

            濃尾地震