We are facing this issue where jobs have a process ID which is non-existent on the actual system.
Eg, the web UI shows something like this:
isengard:4974:6a5e2a59752f-74845020
But there is no process with the process id 4974, and the job gets stuck forever.