New answers tagged process
So disabling UsePrivilegeSeparation in sshd_config seems to do the trick. Not really a huge fan of doing that, but it works ..
If the process is in [defunct] state possible reason could be that it waits one of his child processes to complete. If this is handwrited script try to observe what child processes he calls and check if there are some hanging.
If a process is not terminated after a kill -9 the reason is that it is stuck in an uninterruptible sleep in kernel code. This is mostly related to I/O problems. Either the sleep ends (I/O ends or fails or times out, etc.) and then the process will be cleaned up, or you'll have to reboot the machine.
Ubuntu Upstart Cookbook has an answer for this: If a job specifies respawn, but you want to delay the respawn for some reason, simply use a post-stop stanza: respawn exec mydaemon post-stop exec sleep 10 Now, every time mydaemon exits with a non-zero return code, the job will sleep for 10 seconds before Upstart restarts it. For a real ...
If you send signal number 9 (sigKILL) to right PID and process will not end, there is only one possible solution. Restart machine. Common mistake is sending sigKILL to wrong proces number PID, so check it twicely before hit enter.
What port is your application listening on? sudo netstat -plnt | grep ':PORT' Or alternatively you can try to detect it with the ps command: ps aux | grep -i APPLICATION_NAME
Top 50 recent answers are included