that is for every Monday at three different times.
but, first job executes well, later ones do not. I checked my scrip result at 14:05 hrs, and it was not executed, i change the job to 14:08 and it executed well at the specified time, then checked at 18:21 hrs for the output, again it didnt execute, and i changed the time to few more minutes and it executed at that time. All i noticed is, that if i change the time to few minutes, it executes, but it do not execute for big intervals.
Can anybody tell the problem and the respective solution
Mentionable:- I hav the checked the basic cron forums, so find my issue lil different from the mentioned.. Using centOS 5.3 system.
from big intervals i mean, like wen i change the schedule with just minutes, it do work, but if the next schedule is after few hours, as i mentioned in my crontab example, it do not run the script
And, m sorry m new to Cron as well as Linux, and m not sure how to set the rest of the attirbutes, and wat exactly do they require for..
and if these attributes do effect, then i believe the cron job shud not work for the rest of jobs as well, that i run if i change the same to minutes.
There is no such thing as if you have crontab scheduled after long time.
Above is your misunderstanding.
Something else is the mistake....
Definitely environment, or your script permissions or some thing else ... when you check at 18:21 and scheduling it later .. i hope you are doing something .. which makes the script to execute.
The above is assumption only.
Check your /var/log/syslog to identify this problem. ( in debian )
Check the same in your OS.
m using CentOS and it is not having that syslog fiel, where else can i get that file ??
---------- Post updated at 03:33 PM ---------- Previous update was at 03:14 PM ----------
I hav checked the log
it was in var/log/cron
it shows that it is taking the script, then why the hell is it not working
i just changed the time to next 2 mins to execute, and it executed perfectly, now its time to execute is at 18:20 and m sure, it will not execute, n i really dont know why...
and the job executed well at 15:30 hrs, giving me the backup of sepcified time, if there wud b any issue of environment variable or anything else, then it shud not hav been executed...
What we need to see is what happened around the time that the jobs should have executed and didn't. I suggests that you set up a crontab. When it fails, post the part of the log that covers 1 hour before the failure time to the end of the file.
