07-31-2008
cron does not appear to run
Hi everyone, I am having a problem with a cron, I am using Solaris 10 and need to run a php file every 5 minutes. I can run the file from the test user, but the cron does not seem to run. I do not see anything about it in /var/cron/log but see crons for other users running. What should I look for to correct this? I directed the cron to output to a file and the file was empty after 5+ minutes.
bash-3.00$ crontab -l
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /usr/local/bin/php /var/apache2/htdocs/test/test.php
/var/spool/cron/crontabs shows:
-rw-r--r-- 1 root test 98 Jul 31 01:12 test
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
Does anyone know why the cron job fail to run automatically ?
We have the problem with some Solaris 2.5.1 Machine !
The cron seemd to fail to submit the jobs defined at the defined time !!
Why ?
Sometime it runs OK,but sometime it fail .
We are very sure the problem is due to... (6 Replies)
Discussion started by: kerwin_hsu
6 Replies
2. Shell Programming and Scripting
test.ksh
===================
#!/usr/bin/ksh
APPLICATION=hr_app
APPLICATION_UPPER=`echo $APPLICATION | tr `
echo $APPLICATION_UPPER > /tmp/test.txt
echo $APPLICATION >> /tmp/test.txt
which tr >> /tmp/test.txt
===================
When I run this from the shell:
/home/natter> more... (6 Replies)
Discussion started by: natter
6 Replies
3. UNIX for Dummies Questions & Answers
I have a script in the same directory as some files and directories im trying to tar up and I have it run in cron. Well it runs but says it can't find the directories, you need to be in the directory where the script is for it to work. Here is my cron and script its crappy but it does the trick =).... (3 Replies)
Discussion started by: kingdbag
3 Replies
4. Linux
hi,
I am newbie,
I had set cron jobs to update something on one time very day,
I had tested the script, it run fine,
but the cron jobs seem never run.
some help?
Thanks. (4 Replies)
Discussion started by: robertsnoog
4 Replies
5. Shell Programming and Scripting
I have a perl script, when I ran manually it works perfect. I check the permissions which are fine.
How can I find out why it is not running? how can I setup a log to check.
I am running it on solaris 9.
It compares multiple files, SCP and then send out an e-mail.
As I said when I ran it... (2 Replies)
Discussion started by: amir07
2 Replies
6. Shell Programming and Scripting
Dear Experts,
I have a script defined in Cron which runs every 1 minute.
* * * * * /export/home/myscript.sh >/dev/null 2>&1
Now the issue is executing that myscript.sh sometime will take 2/3 or more minutes to finish execution.
But after 1 minute cron will invoke another... (4 Replies)
Discussion started by: thepurple
4 Replies
7. UNIX for Dummies Questions & Answers
How can I run the following command from cron?
tar -cvf /email_backup/email_bu_062110.tar /prod/email (2 Replies)
Discussion started by: nim73
2 Replies
8. Shell Programming and Scripting
Hi,
Can anyone help in editing CRON (OR) write a script to run another script every second saturday??
I tried to make use of DATE command to find the day but couldnt proceed further.
your help is highly appreciated!
Thanks,
Mahi (11 Replies)
Discussion started by: mahi_mayu069
11 Replies
9. Shell Programming and Scripting
If I run 'who -u' interactively or from a script invoked through bash in a tty on my Ubuntu 12LTS box I get an output like this:
testuser pts/0 Dec 9 02:32 . 2163 (host.xx.yy)
running the same through cron I get:
testuser pts/0 2012-12-09 02:32 00:05 2163... (2 Replies)
Discussion started by: latimer
2 Replies
10. Shell Programming and Scripting
Hi,
1)
If some job supposed to run on 1st of every month at 7 AM
In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day?
2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct)
And if 25th... (5 Replies)
Discussion started by: System Admin 77
5 Replies
cron(1M) System Administration Commands cron(1M)
NAME
cron - clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
cron starts a process that executes commands at specified dates and times.
You can specify regularly scheduled commands to cron according to instructions found in crontab files in the directory
/var/spool/cron/crontabs. Users can submit their own crontab file using the crontab(1) command. Commands which are to be executed only once
can be submitted using the at(1) command.
cron only examines crontab or at command files during its own process initialization phase and when the crontab or at command is run. This
reduces the overhead of checking for new or changed files at regularly scheduled intervals.
As cron never exits, it should be executed only once. This is done routinely by way of the svc:/system/cron:default service. The file
/etc/cron.d/FIFO file is used as a lock file to prevent the execution of more than one instance of cron.
cron captures the output of the job's stdout and stderr streams, and, if it is not empty, mails the output to the user. If the job does not
produce output, no mail is sent to the user. An exception is if the job is an at(1) job and the -m option was specified when the job was
submitted.
cron and at jobs are not executed if your account is locked. Jobs and processses execute. The shadow(4) file defines which accounts are not
locked and will have their jobs and processes executed.
Setting cron Jobs Across Timezones
The timezone of the cron daemon sets the system-wide timezone for cron entries. This, in turn, is by set by default system-wide using
/etc/default/init.
If some form of daylight savings or summer/winter time is in effect, then jobs scheduled during the switchover period could be executed
once, twice, or not at all.
Setting cron Defaults
To keep a log of all actions taken by cron, you must specify CRONLOG=YES in the /etc/default/cron file. If you specify CRONLOG=NO, no log-
ging is done. Keeping the log is a user configurable option since cron usually creates huge log files.
You can specify the PATH for user cron jobs by using PATH= in /etc/default/cron. You can set the PATH for root cron jobs using SUPATH= in
/etc/default/cron. Carefully consider the security implications of setting PATH and SUPATH.
Example /etc/default/cron file:
CRONLOG=YES
PATH=/usr/bin:/usr/ucb:
This example enables logging and sets the default PATH used by non-root jobs to /usr/bin:/usr/ucb:. Root jobs continue to use
/usr/sbin:/usr/bin.
The cron log file is periodically rotated by logadm(1M).
FILES
/etc/cron.d Main cron directory
/etc/cron.d/FIFO Lock file
/etc/default/cron cron default settings file
/var/cron/log cron history information
/var/spool/cron Spool area
/etc/cron.d/queuedefs Queue description file for at, batch, and cron
/etc/logadm.conf Configuration file for logadm
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
svcs(1), at(1), crontab(1), sh(1), logadm(1M), svcadm(1M), queuedefs(4), shadow(4), attributes(5), smf(5)
NOTES
The cron service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/cron:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
DIAGNOSTICS
A history of all actions taken by cron is stored in /var/cron/log and possibly in /var/cron/olog.
SunOS 5.10 5 Aug 2004 cron(1M)