Joseph Huckaby

@care2DavidDPD I have moved this to [#618](https://github.com/jhuckaby/Cronicle/issues/618), as it is unrelated to the current issue at hand.

@ybitso I received your data export (thank you), and installed it on a VM. I see that almost all of your events are either disabled, or run on demand only:...

@Altersoundwork just checking with you one more time. Would it be possible for you to send me that data export which reproduces the problem described in this issue? Note: You...

@Altersoundwork I just noticed that you're using Node v12.22.9. This is really old at this point. Can you please try upgrading to v16 or v18? That might solve the issue...

@ybitso Very odd. I cannot seem to reproduce that. Note that your "Test" event does nothing except echo "Hi" to STDOUT, so it's difficult to tell if it really ran....

Cronicle [v0.9.24](https://github.com/jhuckaby/Cronicle/releases/tag/v0.9.24) was just released, which ships with transactions enabled by default (however you'll need to manually enable them for existing installs), as well as a new storage repair script....

I've never heard of this happening before, but it sounds like your server is running out of memory, and the kernel is killing the Cronicle service. Check your dmesg log:...

See: https://github.com/jhuckaby/Cronicle/issues/465

Sorry, I am having trouble understanding you. The Cronicle logs are already in 24 hour notation, localized to whatever your server's timezone is. Example: ``` [1534384981.784][2018-08-15 19:03:01][joedark.local][Cronicle][debug][1][Cronicle v0.8.23 Starting Up][]...

Ah, thank you. Understood. I'll add this to the TODO list, and make it configurable per user. Thanks!