Sponsored Content
Top Forums Shell Programming and Scripting s3cmd works on command line not on cron Post 302477136 by qwerty20 on Friday 3rd of December 2010 10:34:39 AM
Old 12-03-2010
s3cmd works on command line not on cron

Ubuntu 9.10 is my linux distro
Based on forums they say that the problem is with environment .

here is my case:
login as user, then sudo -s
using this command: s3cmd put file s3://bucket >>worked!
now here is the simple script intended for testing:
#! /bin/bash
env >/tmp/cronjob.log
s3cmd put file s3://bucket
issuing the command crontab -e
* * * * * /opt/script 2>&1 | logger

Then using tail to syslogs
Dec 3 23:22:01 ubuntu CRON[10795]: (root) CMD (/opt/script 2>&1 | logger)

But by verifying it on s3Fox Organizer, the file is not uploaded.

(I tried changing the #! /bin/sh (no effect), putting crons on /etc/crontab (no effect), setting HOME=/home/user (no effect)

What are other options to try? or other ways to debug this problem.

Thanks
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

script works on command line, not in cron job

Hey there, I'm a total newbie unix guy here and just picking this stuff up. Have a very small script I put together that works fine from the command line but not once I put it in a cron job. Searched and found this thread and am wondering it it has something to do with setting variables, though the... (7 Replies)
Discussion started by: JackTheTripper
7 Replies

2. Shell Programming and Scripting

Cron job fails, but works fine from command line

I have a very basic script that essentially sends a log file, via FTP, to a backup server. My cron entry to run this every night is: 55 23 * * * /usr/bin/archive_logs The script runs perfectly when executed manually, and actually worked via cron for about three weeks. However, it mysteriously... (3 Replies)
Discussion started by: cdunavent
3 Replies

3. Shell Programming and Scripting

Zgrep works at command line but not in script?

Hi all- I'm trying to search through some .gz log files to verify certain feeds have passed through our app. I have a small script that I wrote in hopes that I could automate the checking but haven't been able to get the zgrep to work. When I copy it to the command line directly it works... (2 Replies)
Discussion started by: Cailet
2 Replies

4. UNIX for Dummies Questions & Answers

Works on command line but not in script

Hey guys. Hopefully this is an easy one but having reference similar problems on the web I still can't fix it. I am doing a recursive find and replace from a script. Of course I could just run the damn thing from the command line but it's bugging me now and want to get it working. grep -rl... (4 Replies)
Discussion started by: anthonyjstewart
4 Replies

5. Windows & DOS: Issues & Discussions

Command works on CMD line but not in batch?

Hi All, This command works when I type it on but when I run the batch file it doesn't..any ideas why? attrib.exe * | find /c /v "" >filecount.txt (1 Reply)
Discussion started by: Grueben
1 Replies

6. Shell Programming and Scripting

SH script, variable built command fails, but works at command line

I am working with a sh script on a solaris 9 zone (sol 10 host) that grabs information to build the configuration command line. the variables Build64, SSLopt, CONFIGopt, and CC are populated in the script. the script includes CC=`which gcc` CONFIGopt=' --prefix=/ --exec-prefix=/usr... (8 Replies)
Discussion started by: oly_r
8 Replies

7. Shell Programming and Scripting

Works on command line but not in script

OSX 10.9 I am building a script that evaluates the difference between 2 files. Here is a command that does not work transparently. Running this command in Terminal yields great results; however when I put that line in a .sh script, I get the errors shown below. Am I doing something silly? ... (1 Reply)
Discussion started by: sudo
1 Replies

8. 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

9. Shell Programming and Scripting

Cp command works on command line but not in bash

The below command moves all the .vcf files into the directory. cp /home/cmccabe/Desktop/test/vcf/overall/stats/*.vcf /home/cmccabe/Desktop/NGS/annovar When I use a bash wrapper the target.txt gets created but the text files do not get copied. All the paths are the same, but not sure why... (2 Replies)
Discussion started by: cmccabe
2 Replies

10. Shell Programming and Scripting

Command works at command line but not from cron

Oracle Linux 6. Trying to set up a simple monitoring of memory usage. This command does exactly what I want at the command line: echo $(date +%Y-%m-%d" "%H:%M:%S) $(grep PageTables /proc/meminfo) >> /home/oracle/meminfo.logBut when I put it in my crontab: * * * * * echo $(date +%Y-%m-%d"... (2 Replies)
Discussion started by: edstevens
2 Replies
PBUILDER-DIST(1)					      General Commands Manual						  PBUILDER-DIST(1)

NAME
pbuilder-dist, cowbuilder-dist - multi-distribution pbuilder/cowbuilder wrapper SYNOPSIS
pbuilder-dist distribution [architecture] operation [options] [...] cowbuilder-dist distribution [architecture] operation [options] [...] DESCRIPTION
pbuilder-dist is a wrapper that makes it easy to use pbuilder with many different versions of Ubuntu and/or Debian. It is common to symlink this script in order to give it many names in the form of pbuilder-distribution or pbuilder-distribution-architec- ture, like for example pbuilder-feisty, pbuilder-sid, pbuilder-gutsy-i386, etc. The same applies to cowbuilder-dist, which uses cowbuilder. The main difference between both is that pbuilder compresses the created chroot as a a tarball, thus using less disc space but needing to uncompress (and possibly compress) its contents again on each run, and cowbuilder doesn't do this. USAGE
There are many arguments listed on the synopsis; each of them, if used, has to be used exactly in the same order as it appears there. In case you renamed the script to pbuilder-distribution, do not use the distribution parameter; same with i386 / amd64 if the name also con- tains -architecture. distribution Replace this with the codename of the version of Ubuntu or Debian you want to use. architecture This optional parameter will attempt to construct a chroot in a foreign architecture. For some architecture pairs (e.g. i386 on an amd64 install), the chroot will be created natively. For others (e.g. armel on an i386 install), qemu-user-static will be used. Note that some combinations (e.g. amd64 on an i386 install) require special separate kernel handling, and may break in unexpected ways. operation Replace this with the action you want pbuilder to do (create, update, build, clean, login or execute). If you don't specify any action, but the next argument is a .dsc file, it will assume that it should build. Check its manpage for more details. [...] Replace this with other parameters, if needed. For example, if build is the option, you will need to also specify a .dsc file. As a special feature, if you specify a .dsc file you can skip the build option and this script will automatically assume that building is the action you want to do. OPTIONS
--main-only (deprecated: mainonly) If you specify this option, only packages from the main (in Debian) or main and restricted (in Ubuntu) components will be used. By default, all official components are enabled. This only has effect when creating a new environment. --debug-echo The generated pbuilder/cowbuilder command will be printed to the standard output instead of being executed. This is useful for debugging. --buildresult DIRECTORY (pbuilder-dist only) If this option is specified, the resultant files of the pbuilder build are placed in DIRECTORY. --release-only Only use the release pocket. Default for development releases. --security-only Only use the release and security pockets. Suitable environment for preparing security updates. --updates-only Only use the release, security, and updates pocket. Not the proposed-updates pocket. EXAMPLES
pbuilder-dist gutsy create Creates a pbuilder environment for Ubuntu Gutsy, with all components enabled. pbuilder-sid --main-only create Creates a pbuilder environment for Debian Sid, with only the main component. pbuilder-feisty build ./sample_1.0-0ubuntu1.dsc Builds the specified package on an already existing Ubuntu Feisty environment. pbuilder-dist feisty withlog build ./sample_1.0-0ubuntu1.dsc Same as above, but stores pbuilder's output on a file. pbuilder-etch i386 update Updates an existing i386-architecture Debian Etch environment on an amd64 system. cowbuilder-experimental create Creates a cowbuilder environment for Debian Experimental. FILES AND ENVIRONMENT VARIABLES
By default, pbuilder-dist will store all the files it generates in ~/pbuilder/. This can be changed by setting the PBUILDFOLDER environment variable. If the directory doesn't exist, it will be created on the run. A file with the log of the last operation, called last_operation.log, will be saved in the results subdirectory of each build environment. The default authentication method is sudo. You can change this by setting the PBUILDAUTH variable. By default, pbuilder-dist use the master Debian and Ubuntu mirrors. The pbuilder MIRRORSITE and OTHERMIRROR variables are supported, as are the standard ubuntu-dev-tools variables: UBUNTUTOOLS_DEBIAN_MIRROR, PBUILDER_DIST_DEBIAN_MIRROR, UBUNTUTOOLS_DEBSEC_MIRROR, PBUILDER_DIST_DEBSEC_MIRROR, UBUNTUTOOLS_UBUNTU_MIRROR, PBUILDER_DIST_UBUNTU, UBUNTUTOOLS_UBUNTU_PORTS_MIRROR, and PBUILDER_DIST_UBUNTU_PORTS_MIRROR. See ubuntu-dev-tools (5) for details. You may also want to know that pbuilder-dist exports DIST and ARCH environment variables to the invoked process, containing the name of the distribution and the architecture targeted by the current build. You can make use of them, for example, in pbuilderrc. BUGS
If you experience any problem with this script contact me on rainct@ubuntu.com or file a bug at https://bugs.launch- pad.net/ubuntu/+source/ubuntu-dev-tools. Please ensure first that the problem is really this script and not an issue with pbuilder or cowbuilder themselves. SEE ALSO
pbuilder(1), pbuilderrc(5), cowbuilder(1), ubuntu-dev-tools(5). AUTHORS
pbuilder-dist and this manual page were written by Siegfried-A. Gevatter <rainct@ubuntu.com>, with contributions from Iain Lane <iain@orangesquash.org.uk>, Emmet Hikory <persia@ubuntu.com> and others. pbuilder-dist is released under the GNU General Public License, version 2 or later. ubuntu-dev-tools January 10, 2008 PBUILDER-DIST(1)
All times are GMT -4. The time now is 01:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy