3.33 headless still doesn't work, but it gets a little farther than 3.32. When I first start the service, it's active (running), but as soon as I access a library page it's back to 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 Wed 2018-10-24 12:21:47 EDT; 2min 9s ago
Process: 14712 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: 14712 (code=killed, signal=ABRT)
Oct 24 12:21:39 teetui systemd[1]: Started calibre content server.
Oct 24 12:21:47 teetui calibre-server[14712]: qt.qpa.plugin: Could not find the Qt platform plugin "headless" in "/usr/lib/calibre/calibre/plugins"
Oct 24 12:21:47 teetui calibre-server[14712]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Oct 24 12:21:47 teetui calibre-server[14712]: Available platform plugins are: headless (from /usr/lib/calibre/calibre/plugins), eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
Oct 24 12:21:47 teetui systemd[1]: calibre-server.service: Main process exited, code=killed, status=6/ABRT
Oct 24 12:21:47 teetui systemd[1]: calibre-server.service: Unit entered failed state.
Oct 24 12:21:47 teetui systemd[1]: calibre-server.service: Failed with result 'signal'.
|
Isn't anyone else suffering from this? I can work around it by turning the desktop back on and leaving the desktop app running with the content server, but I'd much rather have the headless server that I can start and stop from the command line. Is there anything I could be doing wrong?