Looks like your system isn't automatically resuming interrupted system calls.¹

You could try modifying the module's code in order to do it manually.  Resuming a system call manually means to simply call it again if $! is EINTR or ERESTART.  In this particular case, look for line 755 in OpenSSH.pm

    $r = waitpid($pid, WNOHANG) and last;
[download]

and modify it to read

    do {
        $r = waitpid($pid, WNOHANG);
    } while $r<0 and ($! == Errno::EINTR or $! == Errno::ERESTART);
    last if $r;
[download]

This should take care of this particular waitpid call which produced the message in the debug log.  There are more, though, which would likely need a similar treatment, so it's probably best to get in touch with the module's author... (he frequents this place regularly, so he'll probably see the thread sooner or later, anyway).

___

¹ System calls may be interrupted for a variety of reasons. The more loaded a system, the more often it happens.  Most systems these days automatically resume them, so code isn't always written to handle the rare case where you have to do it manually...

The return value of waitpid is positive so the value of $! is useless. The EINTR probably cames from the previous select call on the loop that is interrupted by the SIGCHLD arriving.

IMO, the way to solve this problem involves strace or some similar utility.

Thanks for both replies. I will try tracing this with strace as suggested when I have some time. Unfortunately, I'm doing this at work so the time I can dedicate to it is limited!