|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
A command in a script not running in Crontab.
Post 302330644 by mystition on Thursday 2nd of July 2009 01:46:19 AM
07-02-2009
A command in a script not running in Crontab.
Hi,
I made this script for TRU Unix 5.1 OS based Node.
When the script was run manually all the commands were running properly. But when it was run from Crontab, one command is not running.
This command is not running when the script is running from Crontab:
# /usr/mg2/svi/svicom/svistatjo.x -j 20090702 -f stat_log_temp
(This is a application based command used ti fetch certain statistics of that application depending on the date)
I am using /bin/ksh shell in the script.The crontab I am using is for root user, and the command is also run by root
[ Following are the fixes that I have tried till now, but it has not done any good:
Fix 1:
I tried to find the directory from which the command is executing by the following way:
# cd /usr/mg2/svi/svicom
# which svistatjo.x
Output: /usr/mg2/svi/svicom/svistatjo.x
If the command 'which svistatjo.x' is executed from any other path, no ouput is obtained.
This is the reason the command i gave above was with the full path.
Fix 2:
I used the command this way in the script too, but it is still not runnng through crontab.
#su -c "svistatjo.x -j 20090702 -f stat_log_temp"
Also, Whenever I am running the script from Crontab, an error is coming in mail, something like :
"stty: tcgetattr: Not a typewriter
stty: tcgetattr: Not a typewriter
Not a terminal
Ambiguous output redirect. ", but I am not sure how this error is related to the command.
]
Please suggest modifications so that this command can be run from crontab also.
\\ Thanks in anticipation
I made this script for TRU Unix 5.1 OS based Node.
When the script was run manually all the commands were running properly. But when it was run from Crontab, one command is not running.
This command is not running when the script is running from Crontab:
# /usr/mg2/svi/svicom/svistatjo.x -j 20090702 -f stat_log_temp
(This is a application based command used ti fetch certain statistics of that application depending on the date)
I am using /bin/ksh shell in the script.The crontab I am using is for root user, and the command is also run by root
[ Following are the fixes that I have tried till now, but it has not done any good:
Fix 1:
I tried to find the directory from which the command is executing by the following way:
# cd /usr/mg2/svi/svicom
# which svistatjo.x
Output: /usr/mg2/svi/svicom/svistatjo.x
If the command 'which svistatjo.x' is executed from any other path, no ouput is obtained.
This is the reason the command i gave above was with the full path.
Fix 2:
I used the command this way in the script too, but it is still not runnng through crontab.
#su -c "svistatjo.x -j 20090702 -f stat_log_temp"
Also, Whenever I am running the script from Crontab, an error is coming in mail, something like :
"stty: tcgetattr: Not a typewriter
stty: tcgetattr: Not a typewriter
Not a terminal
Ambiguous output redirect. ", but I am not sure how this error is related to the command.
]Please suggest modifications so that this command can be run from crontab also.
\\ Thanks in anticipation
|
|
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am facing a strange issue while running a script(eg A) from the crontab entry
the script calls one more script(eg B) within it
now when i run the script A manually(with nohup) it also executes the script B (embedded inside it) as expected.
but when i run the script A from the crontab entry... (7 Replies)
Discussion started by: mad_man12
7 Replies
2. UNIX for Dummies Questions & Answers
Hi all,
I wrote small script for Solaris and when I am running it through command prompt its ok, but when I trying to run it using crontab, i am getting error like:
ld.so.1: dbloader: fatal: libACE.so: open failed: No such file or directory
/tmp/file.sh: line 5: 8304 Killed ... (4 Replies)
Discussion started by: nypreH
4 Replies
3. Shell Programming and Scripting
I am trying to use the CRON utility in Fedora 11 & CentOS...
I intend to run a script which pops up a warning message every hour and i made the following entry using "CRONTAB -e "
* * * * * sh /bin/myscript.sh
But this does not seem to be running.
Another thing to note is that,... (4 Replies)
Discussion started by: Vabiosis
4 Replies
4. Shell Programming and Scripting
Hi,
Can someone please help me here with this one.
This is my script:
# more tosh.sh
#!/usr/bin/ksh
clear
. /home/oracle/.profile
echo "Good morning, world."
export ORACLE_HOME=/u01/app/oracle/product/9.0.1
export PATH=$ORACLE_HOME/bin:/usr/local/bin
export ORACLE_SID=xxxx
... (11 Replies)
Discussion started by: santoshpayal
11 Replies
5. Shell Programming and Scripting
Hi, I posted this in the Solaris forum but I think this one would be more appropriate.
I created a script starting with the following lines:
#!/usr/bin/ksh
flag=n
export flag
typeset -i quant=0
(...)
When running it I'm getting the following 2 errors:
/tmp/tstscript/testfail.ksh:... (9 Replies)
Discussion started by: Cvg
9 Replies
6. UNIX for Advanced & Expert Users
Hi,
I have created the below script,
set -x
# Set the Path of Environment file
ENV_FILE_DIR=/opt/app/p1trp1c1/sybase/ecdwqdm/xrbid/QDM_Prod/bin
LOG_DIR=/opt/app/p1trp1c1/sybase/ecdwqdm/xrbid/QDM_Prod/log
export ENV_FILE_DIR
export LOG_DIR
# Set Audit Environment
. ${ENV_FILE_DIR}/QDM.env... (8 Replies)
Discussion started by: yohasini
8 Replies
7. UNIX for Dummies Questions & Answers
Hi All,
I am having the below script to be run from crontab, it it doesnt run.
1 * * * * /home/cobr_ext/test.sh > /home/cobr_ext/temp.txt
when i run i manally it runs without any issues.
Could please help me as to why doesnt it run the script.:( (7 Replies)
Discussion started by: abhi_123
7 Replies
8. Shell Programming and Scripting
I am facing an issue where sometimes crontab is running script with some delay.
Below is the stmt in script and it is the only stmt in script.
echo "running at `date` " >> CRONCHECK.log
Below is the cron entry.
0 11 * * * CRONCHECK.sh
Below is the time of run each day.
running at Fri... (8 Replies)
Discussion started by: Nishant Singh
8 Replies
9. Solaris
Hi guys!
I created a backup script that works fine when I run manually, but when I put a crontab job to execute it the result are not the expected. (not a time problem).
Here is my script:
bash-3.00# cat /bk_tool/backup2.sh
#!/usr/bin/csh
clear
set DIR_HOST='SCP08'
... (3 Replies)
Discussion started by: andredemartini
3 Replies
10. UNIX for Dummies Questions & Answers
Hi!
I'm using a RaspberryPi with standard Raspbian.
Currently I'm working on some sort of weather station.
For now I have three python scripts - one which is updating txt files for website - update1m.py ( it will not be necessary in few next days so I'll delete it) , second one for updating... (4 Replies)
Discussion started by: bartocham
4 Replies
LEARN ABOUT HPUX
queuedefs
queuedefs(4) Kernel Interfaces Manual queuedefs(4) NAME
queuedefs - queue description file for at, batch, and crontab SYNOPSIS
DESCRIPTION
The file describes the characteristics of the queues managed by (see cron(1M)). Each non-comment line in this file describes one queue. The format of the lines are as follows: [njob[nice[nwait The fields in this line are: q The name of the queue, such that is the default queue for jobs started by (see at(1)), is the queue for jobs started by (see at(1)), and is the queue for jobs run from a file (see crontab(1)). Queue names through designate user-defined queues. njob The maximum number of jobs that can be run simultaneously in that queue. Although any number can be specified here, (see cron(1M)) by default limits the number of jobs that can be run on all the queues to 100. This limitation can be removed by setting the variable to 1 in the file. nice The value to give to all jobs in that queue that are not run with a user ID of super-user (see nice(1)). The default value is 2. nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's queue, or because more than 100 jobs were running in all the queues (see njob above). EXAMPLES
Consider the following file: The file is interpreted as follows: The queue, for jobs (see at(1)), can have up to 4 jobs running simultaneously, and those jobs will be run with a value of 1. Since no nwait value is given, if a job cannot be run because too many other jobs are running, will wait 60 seconds before trying again to run it (see cron(1M)). The queue, for jobs (see at(1)), can have up to 2 jobs running simultaneously. Those jobs will be run with a value of 2. If a job cannot be run because too many other jobs are running, will wait 90 seconds before trying again to run it. All other queues can have up to 100 jobs running simultaneously. They will be run with a value of 2, and if a job cannot be run because too many other jobs are running, will wait 60 seconds before trying again to run it. SEE ALSO
at(1), nice(1), crontab(1), cron(1M), proto(4). STANDARDS CONFORMANCE
queuedefs(4)