Generic “Killed” error in PHP script
You might be triggering the Linux out-of-memory (OOM) killer. Check dmesg for messages about it. It says which process was killed when this happens.
You might be triggering the Linux out-of-memory (OOM) killer. Check dmesg for messages about it. It says which process was killed when this happens.
Here is how I run one of my cron containers. Dockerfile: FROM alpine:3.3 ADD crontab.txt /crontab.txt ADD script.sh /script.sh COPY entry.sh /entry.sh RUN chmod 755 /script.sh /entry.sh RUN /usr/bin/crontab /crontab.txt CMD [“/entry.sh”] crontab.txt */30 * * * * /script.sh >> /var/log/script.log entry.sh #!/bin/sh # start cron /usr/sbin/crond -f -l 8 script.sh #!/bin/sh # code goes … Read more
It turned out that I could not use the @Scheduled annotation, but I implemented a work-around. In the JavaDoc of the SchedulingConfigurer it is stated that: [SchedulingConfigurer is] Typically used for setting a specific TaskScheduler bean to be used when executing scheduled tasks or for registering scheduled tasks in a programmatic fashion as opposed to … Read more
Your command is fine! To run from 7.00 until 19.45, every 15 minutes just use */15 as follows: */15 07-19 * * * /path/script ^^^^ ^^^^^ That is, the content */15 in the minutes column will do something every 15 minutes, while the second column, for hours, will do that thing on the specified range … Read more
Begin the line with 0 0 * * 1,2,3,4,5 <user> <command>. The first fields are minutes and hours. In this case the command will run at midnight. The stars mean: for every day of the month, and for every month. The 1 to 5 specify the days. monday to friday. 6=saturday 0=sunday.
Change Minute to be 0. That’s it 🙂 Note: you can check your “crons” in http://cronchecker.net/ Example
Several issues that I faced while trying to get a cron job running in a docker container were: time in the docker container is in UTC not local time; the docker environment is not passed to cron; as Thomas noted, cron logging leaves a lot to be desired and accessing it through docker requires a … Read more
Try * * * * * to run every minute. Unfortunately H/1 * * * * does not work due to open defect. Defect: https://issues.jenkins-ci.org/browse/JENKINS-22129
sbin is not in the path when run via cron. Specify the full path to service. This is probably either /sbin/service or /usr/sbin/service. You can find the path on your system by running which service.
Try this-: 00 01,13 * * * it will run at 1 A.M and 1 P.M