This probably isn't a c.l.p.m. issue, but I'll ask anyway.
I have a script that's run for years, part of which runs pscp to
download and upload files to a remote server several times a day. This
functionality is part of an essential process, and my organization's
activities would come to a screeching halt if this ever failed. The
machines are Windows servers.
The call looks something like this:
sub get_app_file
{
my $success =3D system './pscp -p -pw password username@12.34.56.78/
directory/path/filename*.txt .';
if ($success =3D=3D 0) { $log .=3D "Successfully downloaded application
file.\n"; }
else { $log .=3D "PROBLEM WITH downloaded application file.\n"; }
}
The hardware guys are updating the servers, and I am in the process of
moving these scripts to a new machine. A week ago, the download
function worked, and today I can run it by hand -- BUT the script
fails with this error message:
=91Fatal: Network error: Connection timed out=92
The hardware guys claim that they have made no change whatsoever to
the system, but we have automatic updates, which have run.
Any clues as to what might cause the problem? And maybe how to
diagnose the failure? I'm not a hardware guy or a network guy, and I
don't have any idea where to begin.
Thanks, CC.
|
|
0
|
|
|
|
Reply
|
cartercc (423)
|
3/23/2011 7:52:12 PM |
|
On 2011-03-23, ccc31807 <cartercc@gmail.com> wrote:
> The call looks something like this:
> sub get_app_file
> {
> my $success = system './pscp -p -pw password username@12.34.56.78/
> directory/path/filename*.txt .';
> if ($success == 0) { $log .= "Successfully downloaded application
> file.\n"; }
> else { $log .= "PROBLEM WITH downloaded application file.\n"; }
> }
>
> The hardware guys are updating the servers, and I am in the process of
> moving these scripts to a new machine. A week ago, the download
> function worked, and today I can run it by hand -- BUT the script
> fails with this error message:
> ‘Fatal: Network error: Connection timed out’
Maybe they've done something with ssh?
What happens if you, from the command line, "ssh username@[dottedquad]"?
I would expect a very similar error.
Can you still ping that IP?
I'm no newtwork expert, but that's what I'd start with.
If you can't ssh into the box then you're not going to be able to scp
either, pscp is just an scp wrapper/clone (PuTTY for anyone not
familiar). At least you'll have something with which to go to the
hardware guys, and put the problem back in their court.
Justin.
--
Justin C, by the sea.
|
|
0
|
|
|
|
Reply
|
Justin
|
3/24/2011 9:22:48 AM
|
|
On Mar 24, 5:22=A0am, Justin C <justin.1...@purestblue.com> wrote:
> Maybe they've done something with ssh?
According to 'them' (the network guys) they've done nothing to the
server.
> What happens if you, from the command line, "ssh username@[dottedquad]"?
> I would expect a very similar error.
I have three machines, my desktop, the current server, and the new
server. I can hit the remote box with WinSCP on my desktop and the
current server and the current server, but not the new server.
I can't ping the remote site and never have been, but that's never
been a problem.
> Can you still ping that IP?
I can't ping the remote site and never have been, but that's never
been a problem.
> If you can't ssh into the box then you're not going to be able to scp
> either, pscp is just an scp wrapper/clone (PuTTY for anyone not
> familiar). At least you'll have something with which to go to the
> hardware guys, and put the problem back in their court.
This morning, I ran three different test on all three machines,
documented the results, turned it over to the network guys, and washed
my hands of the problem. My code works, and the software works -- it's
the machine that doesn't work.
CC.
|
|
0
|
|
|
|
Reply
|
ccc31807
|
3/24/2011 2:05:14 PM
|
|
On Mar 23, 3:52=A0pm, ccc31807 <carte...@gmail.com> wrote:
> Any clues as to what might cause the problem? And maybe how to
> diagnose the failure? I'm not a hardware guy or a network guy, and I
> don't have any idea where to begin.
One of the cowboys, playing on the server, made some changes he
shouldn't have and didn't tell anybody ... AFTER he swore up and down
that no one made any changes.
Unfortunately, his name is Boss.
CC.
|
|
0
|
|
|
|
Reply
|
ccc31807
|
3/24/2011 10:39:06 PM
|
|
|
3 Replies
168 Views
(page loaded in 1.162 seconds)
|