Calibre server doesn't start on Ubuntu server 16.10 with systemd











up vote
0
down vote

favorite












I am trying to get Calibre server to start automatic during startup.
I have used this tutorial.
Then I've used this script:



[Unit]
Description=Calibre Service
After=network.target

[Service]
User=calibre
Group=calibre
ExecStart=/usr/bin/calibre-server
--daemonize
--max-cover=600x800
--max-opds-items=30
--max-opds-ungrouped-items=100
--username=calibre
--port=9000
--pidfile=/var/run/calibre-server.pid
--with-library=/jan/home/calibre-library/

[Install]
WantedBy=multi-user.target


to create an auto startup in systemd.
If I manualy startup with: systemctl start calibre.service
It seems to execute.
If I give the command: systemctl status calibre.service, I get the following result:



● calibre.service - Calibre Service
Loaded: loaded (/lib/systemd/system/calibre.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Thu 2017-05-25 21:55:51 CEST; 45s ago
Process: 1887 ExecStart=/usr/bin/calibre-server --daemonize --max-cover=600x800 --max-opds-items=30 --max-opds-ungrouped-items=100 --username=calibre --port=
Main PID: 1887 (code=exited, status=0/SUCCESS)

May 25 21:55:50 FileServer systemd[1]: Started Calibre Service.
May 25 21:55:50 FileServer calibre-server[1887]: No write acces to


/home/calibre/.config/calibre using a temporary dir instead



But when I look in my browser there is no calibre home page on http://192.168.0.100:9000, this is my home server.
Does anyone have a clue?










share|improve this question
























  • Add Type=forking to the [Service] section and retry lets see what happens!
    – George Udosen
    May 25 '17 at 20:17















up vote
0
down vote

favorite












I am trying to get Calibre server to start automatic during startup.
I have used this tutorial.
Then I've used this script:



[Unit]
Description=Calibre Service
After=network.target

[Service]
User=calibre
Group=calibre
ExecStart=/usr/bin/calibre-server
--daemonize
--max-cover=600x800
--max-opds-items=30
--max-opds-ungrouped-items=100
--username=calibre
--port=9000
--pidfile=/var/run/calibre-server.pid
--with-library=/jan/home/calibre-library/

[Install]
WantedBy=multi-user.target


to create an auto startup in systemd.
If I manualy startup with: systemctl start calibre.service
It seems to execute.
If I give the command: systemctl status calibre.service, I get the following result:



● calibre.service - Calibre Service
Loaded: loaded (/lib/systemd/system/calibre.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Thu 2017-05-25 21:55:51 CEST; 45s ago
Process: 1887 ExecStart=/usr/bin/calibre-server --daemonize --max-cover=600x800 --max-opds-items=30 --max-opds-ungrouped-items=100 --username=calibre --port=
Main PID: 1887 (code=exited, status=0/SUCCESS)

May 25 21:55:50 FileServer systemd[1]: Started Calibre Service.
May 25 21:55:50 FileServer calibre-server[1887]: No write acces to


/home/calibre/.config/calibre using a temporary dir instead



But when I look in my browser there is no calibre home page on http://192.168.0.100:9000, this is my home server.
Does anyone have a clue?










share|improve this question
























  • Add Type=forking to the [Service] section and retry lets see what happens!
    – George Udosen
    May 25 '17 at 20:17













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I am trying to get Calibre server to start automatic during startup.
I have used this tutorial.
Then I've used this script:



[Unit]
Description=Calibre Service
After=network.target

[Service]
User=calibre
Group=calibre
ExecStart=/usr/bin/calibre-server
--daemonize
--max-cover=600x800
--max-opds-items=30
--max-opds-ungrouped-items=100
--username=calibre
--port=9000
--pidfile=/var/run/calibre-server.pid
--with-library=/jan/home/calibre-library/

[Install]
WantedBy=multi-user.target


to create an auto startup in systemd.
If I manualy startup with: systemctl start calibre.service
It seems to execute.
If I give the command: systemctl status calibre.service, I get the following result:



● calibre.service - Calibre Service
Loaded: loaded (/lib/systemd/system/calibre.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Thu 2017-05-25 21:55:51 CEST; 45s ago
Process: 1887 ExecStart=/usr/bin/calibre-server --daemonize --max-cover=600x800 --max-opds-items=30 --max-opds-ungrouped-items=100 --username=calibre --port=
Main PID: 1887 (code=exited, status=0/SUCCESS)

May 25 21:55:50 FileServer systemd[1]: Started Calibre Service.
May 25 21:55:50 FileServer calibre-server[1887]: No write acces to


/home/calibre/.config/calibre using a temporary dir instead



But when I look in my browser there is no calibre home page on http://192.168.0.100:9000, this is my home server.
Does anyone have a clue?










share|improve this question















I am trying to get Calibre server to start automatic during startup.
I have used this tutorial.
Then I've used this script:



[Unit]
Description=Calibre Service
After=network.target

[Service]
User=calibre
Group=calibre
ExecStart=/usr/bin/calibre-server
--daemonize
--max-cover=600x800
--max-opds-items=30
--max-opds-ungrouped-items=100
--username=calibre
--port=9000
--pidfile=/var/run/calibre-server.pid
--with-library=/jan/home/calibre-library/

[Install]
WantedBy=multi-user.target


to create an auto startup in systemd.
If I manualy startup with: systemctl start calibre.service
It seems to execute.
If I give the command: systemctl status calibre.service, I get the following result:



● calibre.service - Calibre Service
Loaded: loaded (/lib/systemd/system/calibre.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Thu 2017-05-25 21:55:51 CEST; 45s ago
Process: 1887 ExecStart=/usr/bin/calibre-server --daemonize --max-cover=600x800 --max-opds-items=30 --max-opds-ungrouped-items=100 --username=calibre --port=
Main PID: 1887 (code=exited, status=0/SUCCESS)

May 25 21:55:50 FileServer systemd[1]: Started Calibre Service.
May 25 21:55:50 FileServer calibre-server[1887]: No write acces to


/home/calibre/.config/calibre using a temporary dir instead



But when I look in my browser there is no calibre home page on http://192.168.0.100:9000, this is my home server.
Does anyone have a clue?







server systemd calibre






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 25 '17 at 20:38









DeeJayh

230217




230217










asked May 25 '17 at 20:00









Jan Peetoom

12




12












  • Add Type=forking to the [Service] section and retry lets see what happens!
    – George Udosen
    May 25 '17 at 20:17


















  • Add Type=forking to the [Service] section and retry lets see what happens!
    – George Udosen
    May 25 '17 at 20:17
















Add Type=forking to the [Service] section and retry lets see what happens!
– George Udosen
May 25 '17 at 20:17




Add Type=forking to the [Service] section and retry lets see what happens!
– George Udosen
May 25 '17 at 20:17










2 Answers
2






active

oldest

votes

















up vote
0
down vote













You are using --pidfile=/var/run/calibre-server.pid which tell calibre to write the pid file to /var/run. Most likely the user running the process User=calibre does not have access to write there. I'd suggest you remove --pidfile since you're not using it.



If you do want to use it, change the path to a writeable directory by the calibre user and add PIDFile=/dir/with/pidfile/calibre-server.pid before your ExecStart line, and as mentioned above also add Type=forking






share|improve this answer




























    up vote
    0
    down vote













    I am running a Calibre server successfully on 18.04, so hopefully these suggestions apply to your distribution as well.



    I would change the Type to "oneshot" and remove the "--daemonize" tag because it doesn't need to be there since you're running it from systemd anyway. If you are running the current version of calibre then you need to remove the "--with-library" tag and just leave the last line as "/path/to/calibre/library".



    Additionally, you specify a username but no password. Not sure if that causes problems, but it might be better to create a user database and then pass the option "--enable-auth" to your server command to activate your users (see the calibre user manual) along with "--userdb /path/to/users.sqlite". If you need more information on how to do this I can expand.



    Lastly, since it hasn't been mentioned yet, please make sure the port you are using is allowed through your firewall and forwarded by your router properly.






    share|improve this answer





















      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "89"
      };
      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',
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      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%2faskubuntu.com%2fquestions%2f918920%2fcalibre-server-doesnt-start-on-ubuntu-server-16-10-with-systemd%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      0
      down vote













      You are using --pidfile=/var/run/calibre-server.pid which tell calibre to write the pid file to /var/run. Most likely the user running the process User=calibre does not have access to write there. I'd suggest you remove --pidfile since you're not using it.



      If you do want to use it, change the path to a writeable directory by the calibre user and add PIDFile=/dir/with/pidfile/calibre-server.pid before your ExecStart line, and as mentioned above also add Type=forking






      share|improve this answer

























        up vote
        0
        down vote













        You are using --pidfile=/var/run/calibre-server.pid which tell calibre to write the pid file to /var/run. Most likely the user running the process User=calibre does not have access to write there. I'd suggest you remove --pidfile since you're not using it.



        If you do want to use it, change the path to a writeable directory by the calibre user and add PIDFile=/dir/with/pidfile/calibre-server.pid before your ExecStart line, and as mentioned above also add Type=forking






        share|improve this answer























          up vote
          0
          down vote










          up vote
          0
          down vote









          You are using --pidfile=/var/run/calibre-server.pid which tell calibre to write the pid file to /var/run. Most likely the user running the process User=calibre does not have access to write there. I'd suggest you remove --pidfile since you're not using it.



          If you do want to use it, change the path to a writeable directory by the calibre user and add PIDFile=/dir/with/pidfile/calibre-server.pid before your ExecStart line, and as mentioned above also add Type=forking






          share|improve this answer












          You are using --pidfile=/var/run/calibre-server.pid which tell calibre to write the pid file to /var/run. Most likely the user running the process User=calibre does not have access to write there. I'd suggest you remove --pidfile since you're not using it.



          If you do want to use it, change the path to a writeable directory by the calibre user and add PIDFile=/dir/with/pidfile/calibre-server.pid before your ExecStart line, and as mentioned above also add Type=forking







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Aug 30 '17 at 18:17









          JD Frias

          1011




          1011
























              up vote
              0
              down vote













              I am running a Calibre server successfully on 18.04, so hopefully these suggestions apply to your distribution as well.



              I would change the Type to "oneshot" and remove the "--daemonize" tag because it doesn't need to be there since you're running it from systemd anyway. If you are running the current version of calibre then you need to remove the "--with-library" tag and just leave the last line as "/path/to/calibre/library".



              Additionally, you specify a username but no password. Not sure if that causes problems, but it might be better to create a user database and then pass the option "--enable-auth" to your server command to activate your users (see the calibre user manual) along with "--userdb /path/to/users.sqlite". If you need more information on how to do this I can expand.



              Lastly, since it hasn't been mentioned yet, please make sure the port you are using is allowed through your firewall and forwarded by your router properly.






              share|improve this answer

























                up vote
                0
                down vote













                I am running a Calibre server successfully on 18.04, so hopefully these suggestions apply to your distribution as well.



                I would change the Type to "oneshot" and remove the "--daemonize" tag because it doesn't need to be there since you're running it from systemd anyway. If you are running the current version of calibre then you need to remove the "--with-library" tag and just leave the last line as "/path/to/calibre/library".



                Additionally, you specify a username but no password. Not sure if that causes problems, but it might be better to create a user database and then pass the option "--enable-auth" to your server command to activate your users (see the calibre user manual) along with "--userdb /path/to/users.sqlite". If you need more information on how to do this I can expand.



                Lastly, since it hasn't been mentioned yet, please make sure the port you are using is allowed through your firewall and forwarded by your router properly.






                share|improve this answer























                  up vote
                  0
                  down vote










                  up vote
                  0
                  down vote









                  I am running a Calibre server successfully on 18.04, so hopefully these suggestions apply to your distribution as well.



                  I would change the Type to "oneshot" and remove the "--daemonize" tag because it doesn't need to be there since you're running it from systemd anyway. If you are running the current version of calibre then you need to remove the "--with-library" tag and just leave the last line as "/path/to/calibre/library".



                  Additionally, you specify a username but no password. Not sure if that causes problems, but it might be better to create a user database and then pass the option "--enable-auth" to your server command to activate your users (see the calibre user manual) along with "--userdb /path/to/users.sqlite". If you need more information on how to do this I can expand.



                  Lastly, since it hasn't been mentioned yet, please make sure the port you are using is allowed through your firewall and forwarded by your router properly.






                  share|improve this answer












                  I am running a Calibre server successfully on 18.04, so hopefully these suggestions apply to your distribution as well.



                  I would change the Type to "oneshot" and remove the "--daemonize" tag because it doesn't need to be there since you're running it from systemd anyway. If you are running the current version of calibre then you need to remove the "--with-library" tag and just leave the last line as "/path/to/calibre/library".



                  Additionally, you specify a username but no password. Not sure if that causes problems, but it might be better to create a user database and then pass the option "--enable-auth" to your server command to activate your users (see the calibre user manual) along with "--userdb /path/to/users.sqlite". If you need more information on how to do this I can expand.



                  Lastly, since it hasn't been mentioned yet, please make sure the port you are using is allowed through your firewall and forwarded by your router properly.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 22 at 7:09









                  MysticEagle

                  184




                  184






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Ask Ubuntu!


                      • 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.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • 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%2faskubuntu.com%2fquestions%2f918920%2fcalibre-server-doesnt-start-on-ubuntu-server-16-10-with-systemd%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

                      mysqli_query(): Empty query in /home/lucindabrummitt/public_html/blog/wp-includes/wp-db.php on line 1924

                      How to change which sound is reproduced for terminal bell?

                      Can I use Tabulator js library in my java Spring + Thymeleaf project?