11-10-2011
cron error
Hi all,
I am brand new in linux and i have a cron lon error which i am trying to locate if anyone has any ideas that would be really appreciated
################### Logwatch 7.3.6 (05/19/07) ####################
Processing Initiated: Thu Nov 10 06:25:26 2011
Date Range Processed: yesterday
( 2011-Nov-09 )
Period is day.
Detail Level of Output: 0
Type of Output/Format: mail / text
Logfiles for Host: jupiter
##################################################################
--------------------- Cron Begin ------------------------
Errors when running cron:
grandchild #9218 failed with exit status 1: 2 Time(s)
---------------------- Cron End -------------------------
thanks in advance i tried googling the error number but no luck i am tasked to just locate where the error is coming from
thanks again
Last edited by pludi; 11-10-2011 at 02:28 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am running a script through cron but keep getting this message in unix mail:
Subject: cron
Not a terminal
stty: : Not a typewriter
stty: : Not a typewriter
logout
The script appears to run successfully. Any ideas what this message is and how I can stop it? (1 Reply)
Discussion started by: Bab00shka
1 Replies
2. Filesystems, Disks and Memory
Hey Guys,
Ive got a script which when run from the command prompt works exactly as planned. However when this script is scheduled to run from the crontab (using the same user ID) it brings up a series of mmap errors...
+ /opt/cobol/bin/rebuild /cybtirl/data/file02 -k:4+32 -e -i -v
Error... (1 Reply)
Discussion started by: Bicks
1 Replies
3. UNIX for Dummies Questions & Answers
I am using the following cron entry to run a cron job every 4 hours and
it is rejecting it:
0 */4 * * * /home/location/scriptname
When I put this entry in cron is errors with: 0481-079 reached a symbol that is not expected.
This is an AIX 5.3 system
Any ideas?
Thanks (4 Replies)
Discussion started by: capeme
4 Replies
4. Shell Programming and Scripting
I am using the following cron entry to run a cron job every 4 hours and
it is rejecting it:
0 */4 * * * /home/location/scriptname
When I put this entry in cron is errors with: 0481-079 reached a symbol that is not expected.
This is an AIX 5.3 system
Any ideas?
Thanks (6 Replies)
Discussion started by: capeme
6 Replies
5. Shell Programming and Scripting
Hi All,
please help me out with this problem.
While running my mail_out_original.ksh in CRT window, it disconnects from the server saying not connected
Here is my code : (please see the attachment)
____________________________________________________________
#!/bin/ksh
## Load... (1 Reply)
Discussion started by: shruthinagaraj
1 Replies
6. Shell Programming and Scripting
HI
am having a script file which is ok if i run from the server manually
like
<root@hostname:/space/canvas/home/lbs/current/internalcdrbackup/LES_CDR_Configuration/0/MSISDNcdrCount > /space/canvas/home/lbs/current/internalcdrbackup/LES_CDR_Configuration/0/MSISDNcdrCount.txt
the... (2 Replies)
Discussion started by: aemunathan
2 Replies
7. UNIX for Dummies Questions & Answers
I am attempting to run a cron job, however, I receive this cron output error:
Error: of parameter : xxxxx does not make a valid output file.
What causes this? (4 Replies)
Discussion started by: AM1234
4 Replies
8. Shell Programming and Scripting
I am running the following cron job:
SHELL=/usr/bin/ksh; export SHELL; . $HOME/.profile; xxx.sh > xxx.out 2>&1
and I am getting mail with the folloinwg message mailed to me when I login as this user: stty: tcgetattr: Not a typewriter
I am running on an AIX 6.1 machine
oslevel -s... (4 Replies)
Discussion started by: BeefStu
4 Replies
9. UNIX for Dummies Questions & Answers
Hi all,
I am brand new in linux and not sure where to post this i posted it also on debian but i think this place would have been better. I have a cron log error which i am trying to locate if anyone has any ideas that would be really appreciated
################### Logwatch 7.3.6... (3 Replies)
Discussion started by: stav40
3 Replies
10. UNIX for Dummies Questions & Answers
Hi all, I write from 'Italy (sorry for my english)
I have a joomla site, some days I get an error with cronjobs
I do not know how to fix it (I'm not an expert)
I kindly ask you to help you who are more experienced
the error is this:
Status: 403 Forbidden
Set-Cookie: =... (1 Reply)
Discussion started by: arredoannunci
1 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)