Sponsored Content
Top Forums Shell Programming and Scripting Shell Script has different ouput via cron vs when run Manually Post 302975518 by Irishboy24 on Tuesday 14th of June 2016 05:05:38 PM
Old 06-14-2016
Shell Script has different ouput via cron vs when run Manually

Hello Lads,

I deployed a script on my mac to start and stop EC2 instances on AWS console. The script when started manually on the terminal does the expected stop and start. Problem is when i try to schedule it on a cron, it fails to recognize the AWS Keys which i set up as ENV variable by adding them to ~/ .bash_profile and throws an error of missing key.

Note that when i do printenv on terminal i can see the AWS ENV variables. I can also see them when i cat the ~/ .bash_profile file. Can any one advise on what's happening here. All other crons on my mac are working fine.

Code:
# Run Daily to Start and Stop EC2 Instances
48 15 * * 1-5 /home/Dir/Documents/Scripts/BashScripts/start-ec2.sh >> /home/Dir/Documents/Scripts/BashScripts/CronStart.txt 
45 15 * * 1-5 /home/Dir/Documents/Scripts/BashScripts/stop-ec2.sh >> /home/Dir/Documents/Scripts/BashScripts/CronStop.txt

Code:
#!/bin/bash
export PATH=$PATH:/home/Dir
export AWS_ACCESS_KEY_ID
export AWS_SECRET_ACCESS_KEY
export AWS_CREDENTIAL_FILE

/usr/local/bin/ec2-stop-instances i-xxxx --region us-west-2
/usr/local/bin/ec2-stop-instances i-xxxx --region us-west-2

Code:
Output When Starting Manually. 

./start-ec2.sh 
INSTANCE	i-xxxx	stopped	pending
INSTANCE	i-xxxx	stopped	pending

Code:
Full Error which i capture in /var/Mail/Maddy
Subject: Cron /Users/Maddy/Documents/Scripts/BashScripts/stop-ec2.sh >> /Users/Maddy/Documents/Scripts/BashScripts/CronStop.txt
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=Maddy>
X-Cron-Env: <USER=Maddy>
X-Cron-Env: <HOME=/Users/Maddy>
Date: Tue, 14 Jun 2016 16:58:03 -0400 (EDT)

Required option '-O, --aws-access-key KEY' missing (-h for usage)
Required option '-O, --aws-access-key KEY' missing (-h for usage)

Code:
My Path Variable.
echo $PATH
/Library/Frameworks/Python.framework/Versions/3.4/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin

 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Can run script Manually, but not through Cron?

Hi all, I have a main script (called OracleCleanup) that runs some sql queries. that runs off a wrapper script which contains the sources for the login information and and JOB_HOME (the script is below). When I schedule this job in the cron the log says that it cannot open my list file, which... (4 Replies)
Discussion started by: MadHatter
4 Replies

2. Shell Programming and Scripting

check in unix shell script so that no one is able to run the script manually

I want to create an automated script which is called by another maually executed script. The condition is that the no one should be able to manually execute the automated script. The automated script can be on the same machine or it can be on a remote machine. Can any one suggest a check in the... (1 Reply)
Discussion started by: adi_bang76
1 Replies

3. Solaris

SFTP errorcode 1 when run on cron but runs manually

I am trying to run a sript on cron to SFTP data to a company. Private and public keys are set up. When I run this manully it works fine, however it was failing when run on cron. I have narrowed down the problem - it fails at the code that says if the error code is 0 then continue . . . I... (2 Replies)
Discussion started by: Heidi.Ebbs
2 Replies

4. UNIX for Dummies Questions & Answers

shell script run by user or cron job ?

My shell script runs fine both as a cron job and when i issue it. However, I wish to differentiate when it runs as a cron-job so the "echo" statements are not issued (they get mailed to me, which i don't want). I tried checking $USER but since the cron was created in my user that does not... (5 Replies)
Discussion started by: sentinel
5 Replies

5. Shell Programming and Scripting

Script behaves different when run from cron vs. manually

Hey all, Just wanted to get some input on a script I am using to import files into a MySQL database. The process is pretty simple: my main server exports these files and FTPs them. I have a script that FTPs them to the machine running that runs this script. The FTP script runs without issue... (2 Replies)
Discussion started by: billtwild
2 Replies

6. Solaris

Shell Script gives error when run through cron job.

Hi, The following shell script runs without any problem when executed manulally. USED=$(df -h /arch | tail -1 | awk '{print $5}' | cut -d '%' -f 1) if then find /arch/AUBUAT/ -type f -mtime +0 | xargs rm find /arch/AUBMIG/ -type f -mtime +0 | xargs rm fi But the same gives below... (6 Replies)
Discussion started by: ksadiq79
6 Replies

7. Shell Programming and Scripting

Shell Script runs good manually but not through Cron tab

Hello Every one, I have a shell script which is running fine manually, but its giving me hard time when running tru cron job. :wall:. Am using #!/usr/bin/ksh >echo $SHELL /usr/bin/ksh Cron Job is as below, it execues but dosent do what i want it to do. 47 15 * * *... (1 Reply)
Discussion started by: naren.chowdhary
1 Replies

8. Shell Programming and Scripting

Shell script not getting called through cron job but executes fine manually.

Hi, My shell script not getting called through cron job. The same works fine when executed manually. I tried to generate logs to find if the scripts has some errors related to path using following command- trying to execute .sh file every 5 mins: */5 * * * * /home/myfolder/abc.sh... (17 Replies)
Discussion started by: Dejavu20
17 Replies

9. Shell Programming and Scripting

Output differs when run manually and when cron job executes it

I get a different output when i manually run the .sh script and when it is run by a cron job. Please help me .. TMP1="/lhome/bbuser/script/wslog/sar.t1" TMP2="/lhome/bbuser/script/wslog/sar.t2" TMP3="/lhome/bbuser/script/wslog/sar.t3" OUTPUT="/lhome/bbuser/script/wslog/sar.out"... (8 Replies)
Discussion started by: nithinankam
8 Replies

10. UNIX for Dummies Questions & Answers

Execution problem with Cron: Script works manually but not w/Cron. Why?

Hello gurus, I am making what I think is a simple db2 call from within a shell script but I am having difficulty producing the desired report when I run the script shown below from a shell script in cron. For example, my script and the crontab file setup is shown below: #!/bin/ksh db2... (3 Replies)
Discussion started by: okonita
3 Replies
Path(3pm)						User Contributed Perl Documentation						 Path(3pm)

NAME
Env::Path - Advanced operations on path variables SYNOPSIS
use Env::Path; # basic usage my $manpath = Env::Path->MANPATH; $manpath->Append('/opt/samba/man'); for ($manpath->List) { print $_, " " }; # similar to above using the "implicit object" shorthand Env::Path->MANPATH; MANPATH->Append('/opt/samba/man'); for (MANPATH->List) { print $_, " " }; # one-shot use Env::Path->PATH->Append('/usr/sbin'); # change instances of /usr/local/bin to an architecture-specific dir Env::Path->PATH->Replace('/usr/local/bin', "/usr/local/$ENV{PLATFORM}/bin"); # more complex use (different names for same semantics) my $libpath; if ($^O =~ /aix/) { $libpath = Env::Path->LIBPATH; } else { $libpath = Env::Path->LD_LIBRARY_PATH; } $libpath->Assign(qw(/usr/lib /usr/openwin/lib)); $libpath->Prepend('/usr/ucblib') unless $libpath->Contains('/usr/ucblib'); $libpath->InsertAfter('/usr/ucblib', '/xx/yy/zz'); $libpath->Uniqify; $libpath->DeleteNonexistent; $libpath->Remove('/usr/local/lib'); print $libpath->Name, ":"; for ($libpath->List) { print " $_" }; print " "; # simplest usage: bless all existing EV's as Env::Path objects use Env::Path ':all'; my @cats = PATH->Whence('cat*'); print "@cats "; DESCRIPTION
Env::Path presents an object-oriented interface to path variables, defined as that subclass of environment variables which name an ordered list of filesystem elements separated by a platform-standard separator (typically ':' on UNIX and ';' on Windows). Of course, core Perl constructs such $ENV{PATH} .= ":/usr/local/bin"; will suffice for most uses. Env::Path is for the others; cases where you need to insert or remove interior path entries, strip redundancies, operate on a pathvar without having to know whether the current platform uses ":" or ";", operate on a pathvar which may have a different name on different platforms, etc. The OO interface is slightly unusual in that the environment variable is itself the object and the constructor is Env::Path->AUTOLOAD(); thus Env::Path->MANPATH; will bless $ENV{MANPATH} into its package while leaving it otherwise unmodified (with the exception of possible autovivification). Unlike most objects, this is a scalar and thus can have only one attribute; its value. In other words, Env::Path simply defines a set of methods a path variable may call on itself without changing the variable's value or other semantics. Also, while the object reference may be assigned and used in the normal style my $path = Env::Path->CLASSPATH; $path->Append('/opt/foo/classes.jar'); a shorthand is also available: Env::Path->CLASSPATH; CLASSPATH->Append('/opt/foo/classes.jar'); I.e. the name of the path variable may be used as a proxy for its object reference. This may be done at 'use' time too: use Env::Path qw(PATH CLASSPATH); # or qw(:all) to bless all EV's CLASSPATH->Append('/opt/foo/classes.jar'); The design is intended to make use of this module as lightweight as possible. Rather than creating a new object to manage an environment variable, the environment variable is provided a set of methods for self-modification but is otherwise left undisturbed and can be used in all normal ways. CLASS METHODS o <CONSTRUCTOR> The constructor may have any name; it's assumed to name a path variable as defined above. Returns the object reference. o PathSeparator Returns or sets the platform-specific path separator character, by default : on open platforms and ; on monopolistic ones. INSTANCE METHODS Unless otherwise indicated these methods return the object reference, allowing method calls to be strung together. All methods which take lists join them together using the value of "Env::Path->PathSeparator". o Name Returns the name of the pathvar. o Contains Returns true iff the specified entry is present in the pathvar. o Assign Takes a list and sets the pathvar to that value, separated by the current PathSeparator. o List Returns the current path in list format. o Prepend For each entry in the supplied list, removes it from the pathvar if present and prepends it, thus ensuring that it's present exactly once and at the front. o Append Analogous to Prepend. o InsertBefore Takes a <dirname> and a list, inserts the list just before the first instance of the <dirname>. If dirname is not found, works just like Prepend. As with Prepend, duplicates of the supplied entries are removed. o InsertAfter Analogous to InsertBefore o Remove Removes the specified entries from the path. o Replace Takes a /pattern/ and a list. Traverses the path and replaces all entries which match the pattern with the concatenated list entries. o ListNonexistent Returns a list of all entries which do not exist as filesystem entities. o DeleteNonexistent Removes from the path all entries which do not exist as filesystem entities. o Uniqify Removes redundant entries (the 2nd through nth instances of each entry). o Whence Takes a pattern and returns an ordered list of all filenames found along the path which match it and are executable. o Shell Returns a string suitable for passing to a shell which would set and export the pathvar to its current value within the shell context. NOTES
o No provision is made for path variables which are not also environment variables, a situation which is technically possible but quite rare. o Except where necessary no assumption is made that path entries should be directories, because pathvars like CLASSPATH may contain "virtual dirs" such as zip/jar files. For instance the DeleteNonexistent method does not remove entries which are files. In Perl terms the test applied is "-e", not "-d". o The shorthand notation for pathvar FOO is implemented by hacking @FOO::ISA, so there's a slight risk of namespace collision if your code also creates packages with all-upper-case names. No packages are created unless the shorthand notation is employed. o There's some cute code in the Env module by Gregor N. Purdy for splitting pathvars into arrays using ties. I'd love to be able to take advantage of that, and it pains me to do the same thing (and not as well) here rather than using Env. Unfortunately it's a newish feature (5.6.0? 5.005? 5.6.1?) in Env and I don't want Env::Path to be "tied" to the very latest Perls. WORKS ON
UNIX and Windows. AUTHOR
David Boyce <dsbperl AT boyski.com> COPYRIGHT
Copyright (c) 2000-2001 David Boyce. All rights reserved. This Perl program is free software; you may redistribute and/or modify it under the same terms as Perl itself. SEE ALSO
perl(1), perlobj(1), Env::Array(3) perl v5.10.1 2006-11-09 Path(3pm)
All times are GMT -4. The time now is 02:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy