-
-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Cron Schedule not working in v0.8.0 #602
Comments
Just to add my two pennies worth, seeing similar here, my container updated on the 14th March and has not pulled data from the drives since that date. I do not have the CRON schedule set so should be running on the default midnight schedule. My older Unraid install from February is working. |
this is probably related to #596 Debian messed around with the filesystem ( /bin vs /usr/bin ) |
Encountering the same problem. Is there any workaround now that can make cron work. thanks |
hello |
I just started using Scrutiny with version |
same issue here with 0.8.0 |
Stupid question, but how do I revert to Edit: leaving this here for other n00bs like me: Edit2: Setting a different cron schedule in docker compose by putting
still does not seem to work though. |
Hello, Try using simple quote:
|
I already did that too, unfortunately it does not make a difference for me. It also should show up like that in
|
Updated s6overlay to v3 Note: xz-utils was added as a requirement for s6-overlay (using safe 5.4.1 instead of compromised 5.6.x versions)
Hey all, sorry for the delay fixing this issue - life happened. I've updated the version of s6-overlay and verified the image locally. I'd appreciate it if you could all try it on your machines and confirm below. |
Once the Docker images in https://github.com/AnalogJ/scrutiny/actions/runs/8575689484 finish building, you can pull the latest image. |
Hey, I pulled master-collector:latest again and now it works! Thanks for the fix! :) |
Hello, The build of the omnibus docker failed. Cheers |
@SirOch27 yeah, but the subsequent build passed. Can you pull the latest image and confirm Cron worked? |
Hi @AnalogJ |
👍 closing! |
running the latest 0.8.1 via podman and cron still isnt working for me, connecting to the container and manually running sudo podman container run \
--detach \
--replace \
--name scrutiny \
--volume `pwd`/scrutiny:/opt/scrutiny/config:Z \
--volume /run/udev:/run/udev:ro \
--mount type=volume,dst=/opt/scrutiny/influxdb \
--publish 8085:8080/tcp \
--device /dev/sda:/dev/sda:rwm \
--device /dev/sdb:/dev/sdb:rwm \
--device /dev/sdc:/dev/sdc:rwm \
--device /dev/sdd:/dev/sdd:rwm \
--device /dev/sde:/dev/sde:rwm \
--device /dev/sdf:/dev/sdf:rwm \
--device /dev/sdg:/dev/sdg:rwm \
--device /dev/sdh:/dev/sdh:rwm \
--device /dev/sdi:/dev/sdi:rwm \
--device /dev/nvme0:/dev/nvme0:rwm \
--cap-add SYS_RAWIO \
--cap-add SYS_ADMIN \
--restart always \
--pull newer \
ghcr.io/analogj/scrutiny:latest |
Describe the bug
Cron Schedule stop working after upgrade to v0.8.0
Expected behavior
Cron Schedule should executed as normal
AnalogJ/scrutiny/metrics doesn't start as planned by cron
The text was updated successfully, but these errors were encountered: