Can't start calibre-server on Linux (ubuntu)

Awfki · 08-17-2015, 08:47 PM

It was working (not sure what version, probably something a few months old), then I upgraded to 2.35 and the service starts but quits after a few seconds.

The only thing showing up in the main syslog is:

console-kit-daemon[1291]: GLib-CRITICAL: Source ID 144 was not found when attempting to remove it

I downgraded to 2.34 and have the same issue.

If there more logs I can post just let me know where to find them. In the mean time I'm going to try backing up a few more versions to 2.32.1.

Add: Same result with 2.32.1.

eschwartz · 08-17-2015, 09:06 PM

There's nothing wrong with calibre itself, or at least I cannot duplicate your problem

on ArchLinux.
Google says that error is just general warnings -- i.e. log pollution. https://stackoverflow.com/questions/...g-to-remove-it

"the service starts" -- calibre ships no services, are you running this from the command-line, or via a systemd/upstart service unit?

Awfki · 08-19-2015, 04:37 PM

I found that StackOverflow post as well but that was the only thing showing up in the logs.

The problem is fixed and appears to have been the calibre-server was already running and what was failing was a second copy that I was trying to start via an init.d script (the "service").

I don't know where the running copy came from but it was using the same options as my init script. Anyway it was late and I was very sleepy (or at least that's the excuse I'm going with).

Thanks

eschwartz · 08-19-2015, 05:58 PM

If you use --daemonize then calibre-server will persist after you think you've killed it.

Excellent test for running server -- try to contact it.

Dunno what an upstart service should look like, but a working systemd unit should look like this:

Code:

[eschwartz@arch ~]$ cat ~/.config/systemd/user/calibre-server.service
[Unit]
Description=Main calibre server
After=network.target

[Service]
Type=forking
PIDFile=/%t/calibre.pid
ExecStart=/usr/bin/calibre-server \
    --daemonize \
    --port=8080 \
    --pidfile=/%t/calibre.pid \
    --with-library /media/PORTABLEAPP/PortableApps/calibrePortable/Data/Amazon \
    --restriction contentserve

[Install]
WantedBy=default.target

kovidgoyal · 08-19-2015, 10:21 PM

@eschwartz: IIRC, you dont actually need --daemonize and --pidfile with systemd, since systemd takes care of that for you. Remember to also get rid of Type=Forking and PIDFile

Of course the re-written server supports systemd socket activation, which is much nicer and supports logging to stdout/stderr so that it works with the systemd journal

eschwartz · 08-19-2015, 10:54 PM

Oh, well, there are worse things than redundancy.

I actually just copy-pasted other peoples' examples and then got down to the part that interested me: templating it and using %i.conf EnvironmentFile's.

I suppose I will just have to wait for the new server, then. Goodness knows it sounds like it will have all sorts of goodies.

08-17-2015, 08:47 PM	#1
Awfki Member Posts: 24 Karma: 43434 Join Date: Apr 2010 Device: Moon+ Reader (ePub)	Can't start calibre-server on Linux (ubuntu) It was working (not sure what version, probably something a few months old), then I upgraded to 2.35 and the service starts but quits after a few seconds. The only thing showing up in the main syslog is: console-kit-daemon[1291]: GLib-CRITICAL: Source ID 144 was not found when attempting to remove it I downgraded to 2.34 and have the same issue. If there more logs I can post just let me know where to find them. In the mean time I'm going to try backing up a few more versions to 2.32.1. Add: Same result with 2.32.1. Last edited by Awfki; 08-17-2015 at 08:50 PM.

08-19-2015, 05:58 PM	#4
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	If you use --daemonize then calibre-server will persist after you think you've killed it. Excellent test for running server -- try to contact it. Dunno what an upstart service should look like, but a working systemd unit should look like this: Code: [eschwartz@arch ~]$ cat ~/.config/systemd/user/calibre-server.service [Unit] Description=Main calibre server After=network.target [Service] Type=forking PIDFile=/%t/calibre.pid ExecStart=/usr/bin/calibre-server \ --daemonize \ --port=8080 \ --pidfile=/%t/calibre.pid \ --with-library /media/PORTABLEAPP/PortableApps/calibrePortable/Data/Amazon \ --restriction contentserve [Install] WantedBy=default.target Last edited by eschwartz; 08-19-2015 at 06:08 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Calibre will not shut down on ubuntu linux	audeojude	Calibre	3	01-07-2013 09:11 AM
Calibre start at boot on Ubuntu 12.04 ?	user68	Calibre	2	06-08-2012 05:12 PM
Cannot start calibre on Ubuntu	astrodad	Calibre	4	07-25-2011 09:20 PM
How Do I Uninstall Calibre Off Linux Ubuntu?	MorganM	Devices	10	03-12-2011 05:51 PM
Calibre 0.6.27 does not start on Ubuntu Karmic (9.10)	dmandala	Calibre	7	12-15-2009 12:46 AM

08-17-2015, 09:06 PM	#2
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	There's nothing wrong with calibre itself, or at least I cannot duplicate your problem on ArchLinux. Google says that error is just general warnings -- i.e. log pollution. https://stackoverflow.com/questions/...g-to-remove-it "the service starts" -- calibre ships no services, are you running this from the command-line, or via a systemd/upstart service unit?

08-19-2015, 04:37 PM	#3
Awfki Member Posts: 24 Karma: 43434 Join Date: Apr 2010 Device: Moon+ Reader (ePub)	I found that StackOverflow post as well but that was the only thing showing up in the logs. The problem is fixed and appears to have been the calibre-server was already running and what was failing was a second copy that I was trying to start via an init.d script (the "service"). I don't know where the running copy came from but it was using the same options as my init script. Anyway it was late and I was very sleepy (or at least that's the excuse I'm going with). Thanks

08-19-2015, 10:21 PM	#5
kovidgoyal creator of calibre Posts: 45,295 Karma: 27111240 Join Date: Oct 2006 Location: Mumbai, India Device: Various	@eschwartz: IIRC, you dont actually need --daemonize and --pidfile with systemd, since systemd takes care of that for you. Remember to also get rid of Type=Forking and PIDFile Of course the re-written server supports systemd socket activation, which is much nicer and supports logging to stdout/stderr so that it works with the systemd journal

08-19-2015, 10:54 PM	#6
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	Oh, well, there are worse things than redundancy. I actually just copy-pasted other peoples' examples and then got down to the part that interested me: templating it and using %i.conf EnvironmentFile's. I suppose I will just have to wait for the new server, then. Goodness knows it sounds like it will have all sorts of goodies.

Advert

Advert