I am currently utilizing SSH for a few jobs in order to send a Unix command to an AIX server and return the output. Recently I switched these from the "Send Text" to "Send Command" option in the SSH task, and am now encountering sporadic orphaned processes on the AIX server. The output returned from "Send Command" is easier to work with for my needs, but I am wondering why it does not appear to be disconnecting after sending the command.

For a simple example, I monitor specific files for the last few lines of text so I will send a simple command via SSH such as:


I will then take the output returned in order to send an email if necessary. Previously this was not problematic, but with "send command" I am seeing quite a few orphaned processes that appear to stem from the change.

Edit to add: This is on version 8.2.0

Update: Perhaps this is just a case of not throwing a second command - 'exit'.

Please let us know if you can reproduce this in the latest version 8.2.3 and even better, the beta 8.2.4. It helps us a lot.

---

Just upgraded to 8.2.3 today and cleared orphaned processes. Will report back as to whether this resolves the issue. As a side note - this continued even after sending an exit command.

Update - this issue persists, but appears to stem from SSH tasks that encounter a connection timeout (for reasons unknown). I traced one orphaned process to a task that encountered an error 10060 when trying to run the 'tail' command on an AIX server. The task re-ran on the error, but the first connection attempt left a zombie process on the server.

Thanks for the information - please test this build: http://www.visualcron.co....aspx?g=posts&t=7049 

---