jhuckaby/Cronicle

Cronicle doesn't start on boot

Fradd747 opened this issue · 6 comments

Summary

Cronicle won't start on boot. I followed https://github.com/jhuckaby/Cronicle/blob/master/docs/CommandLine.md#server-startup and still doesn't work. When I reboot my machine cronicle status is 'not running'.

Steps to reproduce the problem

Setup server using https://github.com/jhuckaby/Cronicle/blob/master/docs/Setup.md#setup, then enable run on boot in https://github.com/jhuckaby/Cronicle/blob/master/docs/CommandLine.md#server-startup.

Your Setup

Basic server install, single machine, local disk db.

Operating system and version?

Ubuntu 22.04.4 LTS

0.9.53

Are you using a multi-server setup, or just a single server?

single server

Are you using the filesystem as back-end storage, or S3/Couchbase?

back-end storage

Can you reproduce the crash consistently?

yes

Log Excerpts

Please check the Cronicle logs after a reboot, to see if systemd attempted to start it and failed, or didn't attempt it at all. Specifically this log: /opt/cronicle/logs/Cronicle.log

And also /opt/cronicle/logs/crash.log if it exists.

Thank you.

Thanks for quick reply. crash.log doesn't exist and Cronicle.log is empty.

Hmm, I don't know what else to try. What does systemctl status cronicle output for you?

Thank you, systemctl actually hepled. It says /opt/cronicle/bin/control.sh: 70: node: not found, so I created symlink to /usr/bin using sudo ln -sf $(nvm which 20.13.1) /usr/bin/node, reboot machine and now it works perfect.