More information.
"sudo service calibre-server status" returns this:
Quote:
● calibre-server.service - calibre content server
Loaded: loaded (/etc/systemd/system/calibre-server.service; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Mon 2018-10-15 16:25:55 EDT; 9s ago
Process: 1437 ExecStart=/usr/bin/calibre-server /var/www/calibre --url-prefix /calibre --port 8080 --userdb /srv/calibre/users.sqlite --enable-auth --auth-mode=basic
Main PID: 1437 (code=killed, signal=ABRT)
Oct 15 16:25:52 teetui systemd[1]: Started calibre content server.
Oct 15 16:25:55 teetui calibre-server[1437]: qt.qpa.plugin: Could not find the Qt platform plugin "headless" in "/usr/lib/calibre/calibre/plugins"
Oct 15 16:25:55 teetui calibre-server[1437]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Oct 15 16:25:55 teetui calibre-server[1437]: Available platform plugins are: headless (from /usr/lib/calibre/calibre/plugins), eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
Oct 15 16:25:55 teetui systemd[1]: calibre-server.service: Main process exited, code=killed, status=6/ABRT
Oct 15 16:25:55 teetui systemd[1]: calibre-server.service: Unit entered failed state.
Oct 15 16:25:55 teetui systemd[1]: calibre-server.service: Failed with result 'signal'.
|
If I turn the Raspbian desktop back on and run the Content Server from the calibre desktop application and reverse proxy that through my apache2 server, it works.
In the following bug report...
https://bugs.launchpad.net/calibre/+bug/1627494
...Kovid suggests recompiling the headless plugin. Perhaps that needs to be done for the Raspbian build.
Any suggestions?