Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Getting error when running script through crontab Post 302365878 by methyl on Wednesday 28th of October 2009 09:01:07 AM
Old 10-28-2009
Further to zaxxon. A agree, you are probably missing an environment variable which points to a Library Path.
To see the difference in environments:
Write a small script containing just your shebang and a "set" command and an "env" command.
1) Submit the script as an "at" job from your normal prompt.
2) Submit the script as a "cron" job.
3) Compare the output.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

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: #... (2 Replies)
Discussion started by: mystition
2 Replies

2. Shell Programming and Scripting

issue with running script with crontab

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

3. Red Hat

Problems with script running with crontab

Hi, I'm trying the backup a few information commands of my Check Point FW (it's on a SPLAT linux machine). This is the script I wrote: #!/bin/bash cd /var/tmp/ file1=netstat_`/bin/date +%d%m%y`.txt file2=ifconfig_`/bin/date +%d%m%y`.txt file3=cpstatos_`/bin/date +%d%m%y`.txt... (2 Replies)
Discussion started by: nirsh
2 Replies

4. Shell Programming and Scripting

Crontab not running a script

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

5. UNIX for Advanced & Expert Users

Particular script not running through crontab

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

6. UNIX for Dummies Questions & Answers

crontab not running script

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

7. Shell Programming and Scripting

Delay in running script from crontab

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

8. UNIX for Advanced & Expert Users

Error while running Rsync through Crontab

hi All, i have implemented Rsync in my source and destination server. while running through command prompt it is working fine: ksh rsync_bravo_db.ksh usa0300uz1252.apps.mc.xerox.com /uv1402/u207/home/bravodba/bin/rsync-3.0.9/config/mrsx_rsync.cfg but later on i created a another ksh and... (4 Replies)
Discussion started by: lovelysethii
4 Replies

9. Solaris

Script problem when running on crontab

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

CRONTAB - one python script is not running

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
GLOBUS-JOB-SUBMIT(1)						  GRAM5 Commands					      GLOBUS-JOB-SUBMIT(1)

NAME
globus-job-submit - Submit a batch job using GRAM SYNOPSIS
globus-job-submit [-dumprsl] [-dryrun] [-verify] [-file ARGUMENT_FILE] SERVICE_CONTACT [-np PROCESSES | -count PROCESSES] [-m MAX_TIME | -maxtime MAX_TIME] [-p PROJECT | -project PROJECT] [-q QUEUE | -queue QUEUE] [-d DIRECTORY | -directory DIRECTORY] [-env NAME=VALUE]... [-stdin [-l | -s] STDIN_FILE] [-stdout [-l | -s] STDOUT_FILE] [-stderr [-l | -s] STDERR_FILE] [-x RSL_CLAUSE] [-l | -s] EXECUTABLE [ARGUMENT...] globus-job-submit [-help] [-usage] [-version] [-versions] DESCRIPTION
The globus-job-submit program constructs a job description from its command-line options and then submits the job to the GRAM service running at SERVICE_CONTACT. The executable and arguments to the executable are provided on the command-line after all other options. Note that the -dumprsl, -dryrun, -verify, and -file command-line options must occur before the first non-option argument, the SERVICE_CONTACT. The globus-job-submit provides similar functionality to globusrun in that it allows batch submission of GRAM jobs. However, unlike globusrun, it uses command-line parameters to define the job instead of RSL expressions. To retrieve the output and error streams of the job, use the program globus-job-get-output. To reclaim resources used by the job by deleting cached files and job state, use the program globus-job-clean. To cancel a batch job submitted by globus-job-submit, use the program globus-job-cancel. OPTIONS
The full set of options to globus-job-submit are: -help, -usage Display a help message to standard error and exit. -version Display the software version of the globus-job-submit program to standard output. -versions Display the software version of the globus-job-submit program including DiRT information to standard output. -dumprsl Translate the command-line options to globus-job-submit into an RSL expression that can be used with tools such as globusrun. -dryrun Submit the job request to the GRAM service with the dryrun option enabled. When this option is used, the GRAM service prepares to execute the job but stops before submitting the job to the LRM. This can be used to diagnose some problems such as missing files. -verify Submit the job request to the GRAM service with the dryrun option enabled and then without it enabled if the dryrun is successful. -file ARGUMENT_FILE Read additional command-line options from ARGUMENT_FILE. -np PROCESSES, -count PROCESSES Start PROCESSES instances of the executable as a single job. -m MAX_TIME, -maxtime MAX_TIME Schedule the job to run for a maximum of MAX_TIME minutes. -p PROJECT, -project PROJECT Request that the job use the allocation PROJECT when submitting the job to the LRM. -q QUEUE, -queue QUEUE Request that the job be submitted to the LRM using the named QUEUE. -d DIRECTORY, -directory DIRECTORY Run the job in the directory named by DIRECTORY. Input and output files will be interpreted relative to this directory. This directory must exist on the file system on the LRM-managed resource. If not specified, the job will run in the home directory of the user the job is running as. -env NAME=VALUE Define an environment variable named by NAME with the value VALUE in the job environment. This option may be specified multiple times to define multiple environment variables. -stdin [-l | -s] STDIN_FILE Use the file named by STDIN_FILE as the standard input of the job. If the -l option is specified, then this file is interpreted to be on a file system local to the LRM. If the -s option is specified, then this file is interpreted to be on the file system where globus-job-submit is being executed, and the file will be staged via GASS. If neither is specified, the local behavior is assumed. -stdout [-l | -s] STDOUT_FILE Use the file named by STDOUT_FILE as the destination for the standard output of the job. If the -l option is specified, then this file is interpreted to be on a file system local to the LRM. If the -s option is specified, then this file is interpreted to be on the file system where globus-job-submit is being executed, and the file will be staged via GASS. If neither is specified, the local behavior is assumed. -stderr [-l | -s] STDERR_FILE Use the file named by STDERR_FILE as the destination for the standard error of the job. If the -l option is specified, then this file is interpreted to be on a file system local to the LRM. If the -s option is specified, then this file is interpreted to be on the file system where globus-job-submit is being executed, and the file will be staged via GASS. If neither is specified, the local behavior is assumed. -x RSL_CLAUSE Add a set of custom RSL attributes described by RSL_CLAUSE to the job description. The clause must be an RSL conjunction and may contain one or more attributes. This can be used to include attributes which can not be defined by other command-line options of globus-job-submit. -l When included outside the context of -stdin, -stdout, or -stderr command-line options, -l option alters the interpretation of the executable path. If the -l option is specified, then the executable is interpreted to be on a file system local to the LRM. -s When included outside the context of -stdin, -stdout, or -stderr command-line options, -l option alters the interpretation of the executable path. If the -s option is specified, then the executable is interpreted to be on the file system where globus-job-run is being executed, and the file will be staged via GASS. If neither is specified, the local behavior is assumed. ENVIRONMENT
If the following variables affect the execution of globus-job-submit. X509_USER_PROXY Path to proxy credential. X509_CERT_DIR Path to trusted certificate directory. SEE ALSO
globusrun(1), globus-job-run(1), globus-job-clean(1), globus-job-get-output(1), globus-job-cancel(1) University of Chicago 03/18/2010 GLOBUS-JOB-SUBMIT(1)
All times are GMT -4. The time now is 01:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy