in reply to Re^2: Net::OpenSSH killing script
in thread Net::OpenSSH killing script

It seems that you are using spawn in order to create detached processes on the remote host, but it doesn't work that way.

spawn forks a new local ssh process that continues running on the background until the remote process exits and you have to take care of reaping those ssh processes with waitpid, otherwise zombies will pile up and at some point the OS will refuse to fork new processes... and that is probably the reason for your script failing.

The right way to do that is to run the remote command with nohup:

$ssh->system("nohup ./script.pl &");
Though, as it seems that the remote command is actually a Perl script, you can also convert it into a daemon letting it take the responsibility of going into the background. There are several CPAN modules that allow to do that (i.e. Proc::Daemon).

Besides that, there are other places where you can improve your Net::OpenSSH usage:

# Read File on remote machine ( $DATA, $ERR ) = $SSH->capture2( "cat <file on remote machine" ); # Write/Append $DATA to loca file <write data to loca file>
...can just be written as...
$ssh->system({stdout_file => ['>>', $local_file]}, cat => $remote_file).
And in...
my $PROC = $SSH->capture( "ps aux | grep <process_name> | grep -v grep + | wc -l | sed 's/ *//'" ); if( $PROC == 0 ) {...
you should check that the command did not fail due to some SSH error. Otherwise, you could end running several instances of ./script.pl.

Replies are listed 'Best First'.
Re^4: Net::OpenSSH killing script
by jaiieq (Novice) on Feb 07, 2011 at 15:09 UTC

    Just wanted to thank you for the assistance. Using...

    $ssh->system("nohup ./script.pl &");

    ...fixed my problem. You were correct in your assumption of how I thought 'spawn' worked. Thank you!!