• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 322
  • Last Modified:

cron does not run files at scheduled times

I have a SUN T2000 SOLARIS 10 and have been trying to get just a simple script to run in cron.
Nothing happens.  I do a ps -ef |grep cron
 # ps -ef |grep cron
    root   384     1   0   Sep 21 ?           0:03 /usr/sbin/cron
so it appears to be running.
Any suggestions as to why nothing is executed from cron?
I just put a script in there that simple echos a few lines to a file but that does not happen.
On my production T2000 SOLARIS 10 this same script runs fine.

Thanks
0
bkreynolds48
Asked:
bkreynolds48
  • 5
  • 4
  • 2
  • +1
2 Solutions
 
si_shamilCommented:
What is the output of "crontab -l" command?
0
 
Brian UtterbackPrinciple Software EngineerCommented:
You are not giving us much to go on, are you? I think you need to be more specific about your particular issue. Right now all we have is
"cron is running. My script isn't. Why?"

What does your script look like? Which crontab is it in? What does the entry look like?  Have you looked in the cron log file under /var/cron?
0
 
bkreynolds48Author Commented:
# FORMAT: Minute Hours Day Month Day-of-Week Script-to-Execute
#
# -- Remember to code all time in GMT not CST ---
#------------------------------------------------------------
00 01 * * 5 /export/home/oracle/bev/bin/cleanup_logs.sh
40 15 * * * /export/home/oracle/bev/bin/cleanup_arcs.sh
00 05 * * 5 /export/home/oracle/bev/bin/bcklistener.sh
00 07 * * 5 /export/home/oracle/bev/bin/bckcron.sh
18 17 * * 1-6 /usr/bin/sh /var/tmp/b.sh  2>&1 >/var/tmp/b.log

oracle /240 cat /var/tmp/b.sh
#######################################################################
#
#!/bin/sh
#
DBA1='breynolds@cymtec.com';export DBA1
#
PATH=$PATH:/usr/bin:/usr/sbin/:/sbin:/bin:/usr/opt/networker/bin; export PATH
LOGPATH=/var/tmp; export LOGPATH
#
DATED=`date "+%m%d%y"`
TP=`date "+%m-%d-%y"`
LOGFILE=$LOGPATH/bev.$DATED; export LOGFILE
#
echo Start: `date +"%d/%m/%y %H:%M"` > $LOGFILE 2>&1
echo $DATED >>$LOGFILE
echo $TP >>$LOGFILE
#
####################### End of Script #################################
 
0
Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

 
si_shamilCommented:
The script will run only on 17:18 every day except sunday.

Are you in the time window,  to check if it working?
0
 
bkreynolds48Author Commented:
I keep changing the time trying to get it executed.
This script is just for testing because nothing is running from cron.
I did a svcs -a |grep cron and the service is online.
I did a svcadm restart cron as well but nothing runs.
0
 
bkreynolds48Author Commented:
One thing I forgot to mention is that I had to change /etc/TIMEZONE to be GMT - it was CDT - I just vi ed the file to make the change  - is that a problem?
0
 
si_shamilCommented:
change the line on to this:

* * * * /usr/bin/sh /var/tmp/b.sh  2>&1 >/var/tmp/b.log

it will run script every minute

then check your log "/var/tmp/b.log"
and check also cron log...
0
 
bkreynolds48Author Commented:
that ran
* * * * /usr/bin/sh /var/tmp/b.sh  2>&1 >/var/tmp/b.log

Does that mean something is messed up on the time because I changed the TIMEZONE file?
0
 
si_shamilCommented:
TIMEZONE can affect the schedule. but it still will run.
Also you should read the crontab format manual to understand how to create cron scheduled jobs
0
 
Brian UtterbackPrinciple Software EngineerCommented:
How are you editing the crontab file? Are you using the crontab -e command to do it?
0
 
omarfaridCommented:
try to stop and start the cron daemon? changing timezone might have confused cron.

0
 
omarfaridCommented:
If I remember correctly, changing the system time use to cause cron to misbehave in earlier versions of solaris
0
 
bkreynolds48Author Commented:
a reboot fixed the problem
Thanks
0

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 5
  • 4
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now