Joseph Huckaby

Oh dear god, of course. It thinks the latest is installed (it was "half-installed"), so it doesn't try to reinstall, UGH!!!! What a mess, I'm so sorry 😞 I think...

Can't see the error in these screenshots. Please click on one of the failed job IDs, to see what the actual error message is: ![Screenshot 2024-12-03 at 12 19 25 ...

Okay, so this looks like an issue with your `firefox-esr` program: > Error: no DISPLAY environment variable specified I don't know anything about this, but I'm guessing it's some sort...

> I keep getting this error on a script thats ran in the past. If the job ran successfully in the past, I am guessing that Cronicle was previously started...

Okay, so running out of disk space is a **catastrophically bad** error when you are using the local filesystem for storage, because the Cronicle "database" will be corrupted. **Note:** You...

I'm so sorry, but Cronicle v1 doesn't support seconds. It only goes down to minutes, similar to cron. Support running jobs on specific seconds, including every 10 seconds, is coming...

Yeah, I think so? Something like this may work: ```sh #!/bin/bash echo "Launching at second 00..." /usr/bin/your-script.sh & sleep 10; echo "Launching at second 10..." /usr/bin/your-script.sh & sleep 10; echo...

Well Cronicle isn't "crashing". It's receiving a SIGTERM signal to shut down: ``` Feb 06 11:45:14 selenoid control.sh[242790]: [1738860314.384][2025-02-06 11:45:14][selenoid][242790][Cronicle][debug][2][Caught SIGTERM][] Feb 06 11:45:14 selenoid control.sh[242790]: [1738860314.384][2025-02-06 11:45:14][selenoid][242790][Cronicle][debug][2][Shutting down][] ```...

I think you have those environment variables set somewhere else (like in the container host or container config, or even `/etc/environment`), and they're being passed down to the process. It's...

Restart the service (or reboot your server, so systemd starts Cronicle), THEN grep the log. The key is to find out what happens at startup. Check if Cronicle is forking,...