Login or Register to Ask a Question and Join Our Community


UNIX for Advanced & Expert Users

Cron Issue

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users Cron Issue
# 1  
Old 09-29-2011
Cron Issue
I have written a custom cron. This cron executes a rake task every 5 minutes. I also log the trace of this execution in a file locally on my server. The whole process seems to execute seamlessly every 5 minutes, but then it seems to log it in /var/log/syslog. I investigated on the syslog and found that system's critical errors, and other cron issues are logged in syslog. Has anybody faced this kind of an issue ?

Moderator's Comments:
Mod Comment Double post. Continue here.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Cron issue

i have written a script to sftp yesterday's logs from another server as below: cd /export/home/abc/xyz/tt d=`gdate -d'yesterday' +%Y%m%d` sftp abc@XXX.XX.XX.XX<<EOF cd /yyy/logs/archive mget abc.log.$d* EOF cd /export/home/abc/xyz/scripts nohup ./ss.sh PROD & it is working fine... (2 Replies)
Discussion started by: ssk250
2 Replies

2. Solaris

CRON Issue

Hello, I am running Solaris 8. I have set a cron job that runs every couple hours. If I run the script manually, it runs just fine (logged in as root). The cron however will not run. It is producing an rc=1 error. Any thoughts would be appreciated. Thanks (4 Replies)
Discussion started by: jkmtm
4 Replies

3. Ubuntu

Cron Issue

I have written a custom cron. This cron executes a rake task every 5 minutes. I also log the trace of this execution in a file locally on my server. The whole process seems to execute seamlessly every 5 minutes, but then it seems to log it in /var/log/syslog. I investigated on the syslog and found... (3 Replies)
Discussion started by: manjunath.nm89
3 Replies

4. UNIX for Dummies Questions & Answers

Cron Issue

I have written a custom cron. This cron executes a rake task every 5 minutes. I also log the trace of this execution in a file locally on my server. The whole process seems to execute seamlessly every 5 minutes, but then it seems to log it in /var/log/syslog. I investigated on the syslog and found... (0 Replies)
Discussion started by: manjunath.nm89
0 Replies

5. Shell Programming and Scripting

Issue with Cron

Hi Gurus, I need to run a script every saturday at 7:05 PM. Below command is working in x86_64. 05 19 * * 6 /apps/informatica/scripts/inf_rest.ksh However when I tried in HP-UX it is giving the below error. crontab: error on previous line; unexpected character found in line. Please... (4 Replies)
Discussion started by: svajhala
4 Replies

6. Red Hat

Cron Issue

Hey all! I'm working on setting up a script to run with cron. I have thus far been unable to get it to successfully complete. I'm hoping you gurus can lend me a hand. This is my crontab, the transfer script works fine the backup will not. The backup however does work when I execute it from the... (11 Replies)
Discussion started by: spiffyville
11 Replies

7. Shell Programming and Scripting

A Cron Issue

Hi Guys.,, This thing is driving me crazy.. I have this script which runs perfectly fine. If it is not able to connect to database it will drop a mail which it does when i ran it manually. But when i am running it from crontab, the script is not sending mail to me but to my id(login id)... (0 Replies)
Discussion started by: mac4rfree
0 Replies

8. Red Hat

cron issue

Hello, Having and issue with a job scheduled in cron. The script: #!/bin/bash 2 3 # Example shell script which can be added to roots cron job to check the 4 # Embedded Satellite disk space usage. If any table is over 90% usage, send 5 # a notice to the default email address... (2 Replies)
Discussion started by: mgb
2 Replies

9. Solaris

Cron issue

When I list whats in cron -l its fine but when I try to -e edit it...it returns a number 309 can't you not edit cron this way with solaris 10? I can do it fine in sol 8 and 9. export EDITOR="vi" is set in my profile I am using BASH $ sudo crontab -l Password: #ident "@(#)root ... (5 Replies)
Discussion started by: kingdbag
5 Replies

10. UNIX for Advanced & Expert Users

cron issue

user x has a cron job that looks in a dir and moves teh files from 1 name to another except its not working correctly. . /user/.profile # sorce the users profile for file in `ls`; do mv $file $file.`date +%Y%m%d%H%M%S``microsec` done microsec is a binary with 555 perm. on it in... (5 Replies)
Discussion started by: Optimus_P
5 Replies
Login or Register to Ask a Question

LEARN ABOUT NETBSD

cron

CRON(8) 						    BSD System Manager's Manual 						   CRON(8)

NAME

     cron -- daemon to execute scheduled commands (ISC Cron V4.1)

SYNOPSIS

     cron [-n] [-x debugflags]

DESCRIPTION

     cron is normally started during system boot by rc.d(8) framework, if cron is switched on in rc.conf(5).

     It will return immediately so you don't have to start it with '&'.

     cron searches /var/cron/tabs for crontab files which are named after accounts in /etc/passwd.  Crontabs found are loaded into memory.  cron
     also searches for /etc/crontab which is in a different format (see crontab(5)).  Finally cron looks for crontabs in /etc/cron.d if it exists,
     and executes each file as a crontab.

     When cron looks in a directory for crontabs (either in /var/cron/tabs or /etc/cron.d) it will not process files that:
	   -   Start with a '.' or a '#'.
	   -   End with a '~' or with ``.rpmsave'', ``.rpmorig'', or ``.rpmnew''.
	   -   Are of zero length.
	   -   Their length is greater than MAXNAMLEN.

     cron then wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute.  When
     executing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab,
     if such exists).

     Events such as START and FINISH are recorded in the /var/log/cron log file with date and time details.  This information is useful for a num-
     ber of reasons, such as determining the amount of time required to run a particular job.  By default, root has an hourly job that rotates
     these log files with compression to preserve disk space.

     Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab or /etc/cron.d) has changed,
     and if it has, cron will then examine the modtime on all crontabs and reload those which have changed.  Thus cron need not be restarted when-
     ever a crontab file is modified.  Note that the crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.

     The following options are available:

     -x      This  flag turns on some debugging flags.	debugflags is comma-separated list of debugging flags to turn on.  If a flag is turned on,
	     cron writes some additional debugging information to system log during its work.  Available debugging flags are:
	     sch   scheduling
	     proc  process control
	     pars  parsing
	     load  database loading
	     misc  miscellaneous
	     test  test mode - do not actually execute any commands
	     bit   show how various bits are set (long)
	     ext   print extended debugging information

     -n      Stay in the foreground and don't daemonize cron.

Daylight Saving Time and other time changes
     Local time changes of less than three hours, such as those caused by the start or end of Daylight Saving Time, are handled specially.  This
     only applies to jobs that run at a specific time and jobs that are run with a granularity greater than one hour.  Jobs that run more fre-
     quently are scheduled normally.

     If time has moved forward, those jobs that would have run in the interval that has been skipped will be run immediately.  Conversely, if time
     has moved backward, care is taken to avoid running jobs twice.

     Time changes of more than 3 hours are considered to be corrections to the clock or timezone, and the new time is used immediately.

SIGNALS

     On receipt of a SIGHUP, the cron daemon will close and reopen its log file.  This is useful in scripts which rotate and age log files.  Natu-
     rally this is not relevant if cron was built to use syslog(3).

FILES

     /var/cron/tabs  cron spool directory
     /etc/crontab    system crontab file
     /etc/cron.d/    system crontab directory
     /var/log/cron   log file for cron events

SEE ALSO

     crontab(1), crontab(5)

AUTHORS

     Paul Vixie <vixie@isc.org>

BSD
								 October 12, 2011							       BSD