>_ IzzyLab

Topic breakdown

Only one process can listen on a port — if it's taken by another, the new app fails when it tries to bind. Diagnosis: tools like ss or lsof show which process, with which PID, holds the port, and the full command line helps confirm you're killing the squatter and not something you need. Having freed the port with a signal (a soft one, escalating to a hard one if it's stubborn), start the real app so it survives your session: the background process must be detached from the TTY with its I/O redirected, otherwise it's cut off along with the command.

What's checked

  1. Port 5000 serves the real app

What it looks like