Amit Sharma amit_...@... writes:
Lets See!
One more thing to check is that in console mode and in cron mode the file
transferred across is in bin mode. In the script, for the EOT here-doc stick in
bin in before you put the file. In console mode use type to check the
status (or just type bin
On 12/02/2009 10:01 AM, Amit Sharma amit_...@yahoo.com wrote:
Any pointers?
If a script runs from the console but not from cron, 99% of the time
it's one of these two things -
1. The user which executes the cron script is not the same
But the scripts runs for say 18Gb and then
Any pointers?
If a script runs from the console but not from cron, 99% of the time
it's one of these two things -
1. The user which executes the cron script is not the same
But the scripts runs for say 18Gb and then gives the 'not enough disk space
error'
Do any of your
On 12/02/2009 06:06 PM, Amit Sharma amit_...@yahoo.com wrote:
Any pointers?
If a script runs from the console but not from cron, 99% of the time
it's one of these two things -
1. The user which executes the cron script is not the same
But the scripts runs for say 18Gb and then
Amit Sharma amit_...@... writes:
Same Script is able to successfully transfer (FTP) 40GB data when run as user
root in command prompt. When
same script is scheduled in cron for 2345 hrs (weekly), script runs and
transfer say 18GB of data and
terminates with error
426 Connection closed;
I asked the question to ascertain if there's a particular partition, say /tmp
which has around 18GB of disk space and the file is temporarily transferred
there. Since the disk space is limited to ~18GB, the file being transferred
there temporarily isn't copied completely, and instantly gives
On Wednesday 02 Dec 2009, Amit Sharma wrote:
Same Script is able to successfully transfer (FTP) 40GB data when run
as user root in command prompt. When same script is scheduled in cron
for 2345 hrs (weekly), script runs and transfer say 18GB of data and
terminates with error
426 Connection
426 Connection closed; Not Enough Disk Space. Aborting..
Hope this clarifies the issue.
Not really, the error message is clear enough saying the fs is out of
space :(. Perhaps there is some other job (on the ftp server) that
comes by and cleans up the fs and when you try it manually,
On 12/01/2009 11:18 AM, Amit Sharma wrote:
Hi,
Some questions...
a) Is the destination directory the same as when you run it from terminal
yes, script is the same
b) How frequently does the cron script run?
Once a week
c) Is the destination actually running out of space?
No, if I run the
Any pointers?
If a script runs from the console but not from cron, 99% of the time
it's one of these two things -
1. The user which executes the cron script is not the same
But the scripts runs for say 18Gb and then gives the 'not enough disk
space error'
2. The script depends on
On Tue, Dec 1, 2009 at 7:30 PM, Sawrub luckysharm...@gmail.com wrote:
On 12/01/2009 11:18 AM, Amit Sharma wrote:
Hi,
Some questions...
a) Is the destination directory the same as when you run it from terminal
yes, script is the same
b) How frequently does the cron script run?
Once a week
Since most of the pointers are going towards the permissions but all in
vain. Can u please pass on the script to the list so that people can try
out.
--
Saurabh Sharma
Linux user number: 490644
http://sawrub-blog.blogspot.com/
Open your doors...It's time to look beyond Windows
Can you emphasize the term script, i mean what did you do exactly?
regards
rakesh
On Mon, Nov 30, 2009 at 1:03 PM, Amit Sharma amit_...@yahoo.com wrote:
Hi
I have facing a strange problem while uploading data file using FTP in
cron.
I have made a script to upload 40GB approx tar.gz file to
On Monday 30 Nov 2009, Amit Sharma wrote:
Any pointers?
Are you logging in to the FTP server using the same userid/passwd in
both cases?
--
Arun Khan
___
ilugd mailinglist -- ilugd@lists.linux-delhi.org
On 11/30/2009 11:28 PM, Arun Khan wrote:
On Monday 30 Nov 2009, Amit Sharma wrote:
Any pointers?
Are you logging in to the FTP server using the same userid/passwd in
both cases?
+1 for Arun, the issue is most probably with the user who is firing the
script.
--
Saurabh Sharma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Amit Sharma writes:
Hi
I have facing a strange problem while uploading data file using FTP in cron.
I have made a script to upload 40GB approx tar.gz file to a FTP location.
When I run the script in console, it works fine and uploads the file
[snip]
When I schedule it in cron and make it run automatically, FTP upload fails
with error :
426 Connection closed; Not Enough Disk Space. Aborting..
Are you sure the FTP user accounts being used for uploading the file in both
cases are same ? Also you can try enabling verbose login on
--- On Tue, 1/12/09, Amit Sharma amit_...@yahoo.com wrote:
From: Amit Sharma amit_...@yahoo.com
When I schedule it in cron and make it run
automatically, FTP upload fails with error :
Why is it that it works fine from command prompt and breaks
in between with error when I run the
Hi,
Some questions...
a) Is the destination directory the same as when you run it from terminal
yes, script is the same
b) How frequently does the cron script run?
Once a week
c) Is the destination actually running out of space?
No, if I run the script as is from commabd prompt, it just runs
On Mon, Nov 30, 2009 at 1:03 PM, Amit Sharma amit_...@yahoo.com wrote:
Hi
I have facing a strange problem while uploading data file using FTP in cron.
I have made a script to upload 40GB approx tar.gz file to a FTP location.
When I run the script in console, it works fine and uploads the
Hi
I have facing a strange problem while uploading data file using FTP in cron.
I have made a script to upload 40GB approx tar.gz file to a FTP location.
When I run the script in console, it works fine and uploads the file without
any issue.
When I schedule it in cron and make it run
21 matches
Mail list logo