hello world cron job not working

You may need to arrange for the terminal to stay open after the command exits - either through its preferences, or by adding a command such as read a to the bottom of your script (so that the shell blocks waiting for user input).,Setting all asterisks * * * * * tells crontab to run the command every minute of every day of every week of every month. You have to specify the times when you want to run the script:,This is my first time playing with cron jobs and I can't figure out what's wrong. I've read the three most upvoted questions on this but it still won't work.,A shell on its own has no way to interact with the user's desktop - it needs to be attached to a terminal device of some kind. For example:

* * * * * DISPLAY =: 0 gnome - terminal--/home/user / sayhello.sh

* * * * * DISPLAY =: 0 xterm - e / home / user / sayhello.sh

# To define the time you can provide concrete values
for
# minute(m), hour(h), day of month(dom), month(mon),
   # and day of week(dow) or use '*' in these fields(
      for 'any').
#
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
   # 0 5 * * 1 tar - zcf /
   var / backups / home.tgz / home /

I had a strange behavior in Ubuntu 20.04 cron job:,Connect and share knowledge within a single location that is structured and easy to search., How did Joysticks with more than 4 buttons and all those extra features work on a Game Port? , By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

service cron restart

Tested cron by writing a script to echo helloworld, wrote a crontab to run it every minute and waited around for 15 minutes while nothing happened., Thanks for the answer! I haven't thought about this problem or needed to use cron in quite a while. Now I have to recreate the situation and learn a bit more about in depth troubleshooting – Yitzchak Jun 23, 2013 at 15:05 ,If it doesn't, where does it look for cron files? Is your user allowed to create crontabs? Is the file in the directory the crond is looking in?,I have a cron job that is supposed to run a script every 15 minutes.

*/15 * * * * /path / to / script.sh

0, 30 * * * * /path/to / script.sh

You should see that the cron job hello successfully scheduled a job at the time specified in LAST SCHEDULE. There are currently 0 active jobs, meaning that the job has completed or failed.,Now you've seen one running job scheduled by the "hello" cron job. You can stop watching the job and view the cron job again to see that it scheduled the job:,If the .spec.startingDeadlineSeconds field is set (not null), the CronJob controller measures the time between when a job is expected to be created and now. If the difference is higher than that limit, it will skip this execution.,Note that concurrency policy only applies to the jobs created by the same cron job. If there are multiple cron jobs, their respective jobs are always allowed to run concurrently.

apiVersion: batch / v1
kind: CronJob
metadata:
   name: hello
spec:
   schedule: "* * * * *"
jobTemplate:
   spec:
   template:
   spec:
   containers:
   -name: hello
image: busybox: 1.28
imagePullPolicy: IfNotPresent
command:
   -/bin/sh -
   -c -
   date;
echo Hello from the Kubernetes cluster
restartPolicy: OnFailure

kubectl create - f https: //k8s.io/examples/application/job/cronjob.yaml

apiVersion: batch / v1
kind: CronJob
metadata:
   name: hello
spec:
   schedule: "* * * * *"
jobTemplate:
   spec:
   template:
   spec:
   containers:
   -name: hello
image: busybox: 1.28
imagePullPolicy: IfNotPresent
command:
   -/bin/sh -
   -c -
   date;
echo Hello from the Kubernetes cluster
restartPolicy: OnFailure

kubectl create - f https: //k8s.io/examples/application/job/cronjob.yaml

cronjob.batch / hello created

kubectl get jobs--watch

kubectl get cronjob hello

kubectl get cronjob hello

kubectl get jobs--watch

# Replace "hello-4111706356"
with the job name in your system
pods = $(kubectl get pods--selector = job - name = hello - 4111706356--output = jsonpath = {
   .items[ * ].metadata.name
})