Invoke-SSHCommand hangs and does not return control to the script when the command hangs on the remote side

[SeanD-Entara]

I'm pushing out a 'head' command on some remote files via SSH using Invoke-SSHCommand. Once in a while one or two of these files I'm heading will just hang indefinitely on the command. I can actually reproduce that behavior on those particular files manually and that's not the issue. The issue is that even when Invoke-SSHCommand times out, control never returns to my script and everything hangs indefinitely. In fact, I can't even CTRL-C the script and have to close the session entirely.

Error returned:

Exception calling "EndExecute" with "1" argument(s): "Command 'head -n 10 "/path/to/file"' has timed out."
At C:\Program Files\WindowsPowerShell\Modules\Posh-SSH\3.2.4\Posh-SSH.psm1:294 char:25
+                         $Output = $_.cmd.EndExecute($_.Async)
+                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : SshOperationTimeoutException

Wanted to post the issue here before I started trying to muck around in your code in case you have any idea.

Any help is appreciated and also want to add that this is a great module that I get a lot of mileage out of and really appreciate the work.

Thanks!

[SeanD-Entara]

Ugh. okay. this might be a me problem. I was able to prepend the linux "timeout" command and then when i run Invoke-SSHCommand manually it times out now but when I do this via a function it hangs forever. So I don't know what's wrong with my function thats causing this but regardless I guess it's a me problem so i'll close this.

[SeanD-Entara]

Okay. I figured out what was hanging things up. The session itself remains stuck. It won't accept any input. My script was attempting to run Remove-SSHSession on the session after issuing the command and THAT is what is hanging. Not sure how you can reproduce but if you find a command to run that just totally hangs on the server side such that the session is useless you could reproduce. So I have a feature request instead of an issue. I need a -Force switch on Remove-SSHSession and I need it to not F around. Haha. I mean I don't care what condition or state the remote session is in, it must die and no longer show from a Get-SSHSession.