Nssm install CalibreServer "C:\Program Files\Calibre2\calibre-server.exe" -enable-auth B:\Calibre-Bibliothek -ssl-certfile B:\Calibre-Bibliothek\calibre-crt.pem -ssl-keyfile B:\Calibre-Bibliothek\ -disable-use-bonjour -max-jobs 64 -worker-count 64 -max-job-time 600 -timeout 600 I guess it won't kill me to log in, but I might try AlwaysUp if it becomes a problem. I'm theorizing that NSSM simply doesn't like that some of the parameters are now simply flags and not name/value pairs.įor now, I'm just using the built in auto-start server that comes with the UI, and I simply placed Calibre in the start-up group. I even tried to get it running in other folders to make it simpler, but no dice. Does anyone have an idea why this isn't working? Is there a similar service wrapper that works better? What I'm trying to accomplish is an automatic service start that doesn't require me logging onto the server.įWIW, I was not able to make this work with NSSM and any version of the folder name or permissions changes. I've tried about a dozen ways to say "D:\Full" but none of them work. but when I use those same parameters in NSSM, and try to start the resulting service, the error shows: I can start the service manually with this command:Ĭalibre-server -port 9999 -enable-auth "D:\Full" Unfortunately, I keep failing with an error that it can't find my library.
So I rebuilt my service using the new parameter and I thought I'd be good. I checked out the documentation, and it quickly became obvious that the calibre-server interface had changed. This week, I upgraded to 3.6 and those services were no longer functional. I've been using NSSM to wrap the command and register the service and it's been working great.
I've been running Calibre as a service on my Windows server.
0 kommentar(er)
