client creates orphan/zombie processes
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
ParaView doesn't clean up processes it spawns when it starts a server for the user via its UI.
On my system it's only an issue if the spawned process doesn't finish. In that case when ParaView exits the process is orphaned. If the spawned process used ssh ports are left open which prevent ParaView from connecting again, if he tries, then a crash soon follows.
This was reported by Sean Ziegeler in the ParaView user's thread: "[Paraview] paraview - client-server"
steps to reproduce:
-
start the client.
-
connect->Add Server
name: rc-orphan type: reverse connection port: 33333 command: ssh -i /home/burlen/.ssh/id_rsa_G50VT localhost /home/burlen/ext/PV3/bin/pvserver --reverse-connection --client-host=localhost --server-port=33333 && sleep 1d
note: use ssh-keygen to generate a public/private key pair, copy the public key into ~/.ssh/authorized_keys
-
connect using the new server. At this point you can use "pstree -p PV_PID" to view the child process and get its pid.
-
disconnect. At this point you can use pstree again to verify that the child process is still there.
-
connect using the new server again. It fails, crash soon to follow.
-
close paraview (if he didn't crash). View the orphaned ssh process (use its pid from step 3), with ps or pstree.