>_ IzzyLab

Topic breakdown

"The process is alive but not responding" isn't a crash but a hang: a deadlock or an infinite wait inside, during which the socket keeps listening on the port but requests aren't processed. That's why pgrep/ps will show the process as perfectly healthy — you need to diagnose not "is it alive" but "is it stuck": the request hangs and times out (rather than failing with connection refused, as it would if nobody were listening on the port at all), and the process state in ps differs from the normal S/R. ss -tlnp helps find who's holding the port. An important nuance: a process stuck on a lock may not handle a gentle SIGTERM, so be ready to escalate to a forced kill, and bring up the new instance detached from the current session.

What's checked

  1. The service responds again

What it looks like