Sponsored Content
Full Discussion: Cronjob is NOT working
Top Forums Shell Programming and Scripting Cronjob is NOT working Post 302932659 by rbatte1 on Friday 23rd of January 2015 06:27:10 AM
Old 01-23-2015
You have to be aware that the environment that cron fires up is not the same that you get when you log on. There could be differences in the PATH and other variables that mean this doesn't work. Perhaps you could schedule a script that does the following:-
Code:
env > /tmp/my.cron.env
set > /tmp/my.cron.set

If you can also do this on the command line:
Code:
env > /tmp/my.login.env
set > /tmp/my.login.set

... then you can compare the two and see what you need to add to your scheduled script to make the environments the same.

There are already numerous threads with similar issues, so we're all fallen over then at some point. Hopefully the other threads will also have more advice that will get you sorted out.



Robin


Robin
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

sftp not working as cronjob

hi, I have a script that will automatically login into a server and get a file. it is working fine if i run it on a command line. however, when i tried to run it as a cron job, it is not working. what should i do? set timeout -1 spawn /usr/bin/sftp user1@server1 match_max 100000 expect... (3 Replies)
Discussion started by: tungaw2004
3 Replies

2. UNIX for Advanced & Expert Users

cronjob not working

I created a file in /u01/oradata directory as cronjb.ksh which contains following script 30 12 * * * /export/home/oracle/u01/oradata/rman.ksh '/export/home/oracle' is my root directory. I then moved cronjb.ksh file to my '/export/home/oracle' directory. i typed crontab cronjb.ksh. However my... (8 Replies)
Discussion started by: manna
8 Replies

3. Solaris

cronjob not working

I am trying to schedule a job via cronjob. Not sure what the problem is. below is my script and the error. 45 10 * * * /u01/app/oracle/jpark/sched_exp_mis.sh Error received. Your "cron" job on tama /u01/app/oracle/jpark/sched_exp_mis.sh produced the following output: ... (19 Replies)
Discussion started by: mrx1350
19 Replies

4. Solaris

cronjob not working

Hi All , I have a cron jobs that is not working while put inside cron. But on executing from manually, it works fine, Pl anyone find if there is anything wrong in the script. 30 22 * * 1-5 cd /home/ab90737/introscope/util/bin; ./batchgenerateReport.pl ../config/reps.config >... (1 Reply)
Discussion started by: jegaraman
1 Replies

5. UNIX for Advanced & Expert Users

cronjob not working intermittently

Hi there I have a cronjob running on a sol 10 U6 server which runs every 15 minutes. The cronjob is a perl script. But I have noticed that after every few weeks the job stops running all of a sudden. There are other cronjobs running on the system from the same user and from other users which... (3 Replies)
Discussion started by: sinfuldips
3 Replies

6. Shell Programming and Scripting

Cronjob not working from user's crontab

Hi All, I am trying to execute a python script from a user's crontab. /home/user1/UDE/scripts/UdeManager.py I am at /home/user1. If I run the command "/home/user1UDE/scripts/UdeManager.py" from the users home directory its working fine. But when I try to run from user's cron tab its... (3 Replies)
Discussion started by: Tuxidow
3 Replies

7. Shell Programming and Scripting

while loop not working in cronjob

Hi , While loop is not working when running script as cronjob. #!/usr/bin/bash xyz sleep 30 var=0 while do xyz commands done This script is working if I run it manually. (7 Replies)
Discussion started by: ankush_mehra
7 Replies

8. UNIX for Dummies Questions & Answers

Cronjob not working

Hi, I am trying to run a script through crontab but it doesn't run. The script sends an email of the logfile created.When I reun through command line it works perfectly but doesn't send any email through cron. There are othe jobs in cron wich runs perfectly. Please let me know if I am doing... (3 Replies)
Discussion started by: Rossdba
3 Replies

9. Shell Programming and Scripting

Cronjob not working as intended

I have a shell script that I have scheduled using cron using a command: 0 10 * * * /directory/Script.sh > /directory/log/output.log The script is scheduled to run at 10 AM everyday. The script executes but produces output files only with headers, no content is there. The script produces... (11 Replies)
Discussion started by: Palak Sharma
11 Replies

10. Shell Programming and Scripting

PHP cronjob not working but manual working

Hi, Can anyone help me on my PHP cron not working, but when i do the manual it work. # manual run working /usr/local/bin/php /root/dev/test.php # crontab not working 55 8 * * * /usr/local/bin/php /root/dev/test.php Thank in advances Regards, FSPalero Please use CODE tags as... (2 Replies)
Discussion started by: fspalero
2 Replies
env(1)							      General Commands Manual							    env(1)

NAME
env, printenv - Displays or sets the current environment, or displays the values of environment variables SYNOPSIS
Current Syntax env [-i] [name=value...] [command] [args...] printenv [name] Obsolescent Syntax env [-] [name=value...] [command] [args...] STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: env: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
Invokes utility with exactly the environment specified by the arguments; the inherited environment is ignored completely. Changes are in effect only while the specified command is running. Dash is equivalent to -i option. OPERANDS
Changes in the form name=value are added to the current environment before the command is run. [Tru64 UNIX] Name of an environment vari- able to be printed. Name of a command to be invoked with the modified environment. Arguments to be passed to command when it is executed. DESCRIPTION
The env command lets you get and change your current environment, and then run the specified command with the changed environment. If the -i option is used, the current environment is ignored and the command runs with only the changed environment. Changes are only in effect while the specified command is running. If command is not specified, env displays your current environment, one name=value pair per line. [Tru64 UNIX] The printenv command displays the values of the variables in the environment. If name is specified, only its value is printed. If name is not the name of a currently set environment variable, only a blank line is printed, no error is reported. If name is not specified, printenv displays the current environment, one name=value per line. EXIT STATUS
If command is invoked, the exit status of env is the exit status of command; otherwise, the env utility exits with one of the following values: The env utility completed successfully. An error occurred in the env utility. The command specified by command was found but could not be invoked. The command specified by command could not be found. EXAMPLES
To add a shell variable to the environment for the duration of one command (sh only), enter: TZ=MST7MDT date env TZ=MST7MDT date Each of these commands displays the current date and time in Mountain Standard Time. The two commands shown are equivalent. When date is finished, the previous value of TZ takes effect again. To replace the environment with another one, enter: env -i PATH=$PATH IDIR=/u/jim/include LIBDIR=/u/jim/lib make This runs make in an environment that consists only of these definitions for PATH, IDIR, and LIBDIR. You must redefine PATH so that the shell can find the make command. When make is finished, the previous environment takes effect again. To find the current setting of the TERM environment variable, enter: printenv TERM The command returns the value for the TERM environment variable. ENVIRONMENT VARIABLES
The following environment variables affect the execution of env: Provides a default value for the internationalization variables that are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari- ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale for the for- mat and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of LC_MESSAGES. SEE ALSO
Commands: csh(1), ksh(1), Bourne shell sh(1b), POSIX shell sh(1p) Functions: exec(2) Standards: standards(5) env(1)
All times are GMT -4. The time now is 06:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy