Skip to content

Ubuntu/Debian server process hangs and causes new port after workshop update #289

@isimmons

Description

@isimmons

Reported on the Discord by me on Ubuntu and @dawnmist on Debian.

When using the 'u' option to update the server restarts but on a different port because the default port is still in use.

I did some testing and it seems the issue might not actually be the update process.

As you can see below, if I manually stop the server with ctrl+c and then check, there are two processes still using port 5639.

➜  advanced-mcp-features git:(main) sudo sudo lsof -t -i:5639 
[sudo] password for isimmons: 
104962
105243
➜  advanced-mcp-features git:(main) sudo kill -9 $(sudo lsof -t -i:5639)
➜  advanced-mcp-features git:(main) sudo sudo lsof -t -i:5639           
➜  advanced-mcp-features git:(main) npm run start

> start
> npx --prefix ./epicshop epicshop start

🐨 Welcome to the workshop, isimmons!
Supported keys:
  o - open workshop app
  u - update workshop
  r - restart workshop app
  k - Kody kudos 🐨
  q - exit (or Ctrl+C)

🐨  Let's get learning!
Local:            http://localhost:5639
On Your Network:  http://192.168.86.248:5639

➜  advanced-mcp-features git:(main) sudo sudo lsof -t -i:5639
122023
122409
➜  advanced-mcp-features git:(main) 

I also tried killing the processes, restarting the server (uses correct port 5639) and then open a new terminal tab and see two processes are running.

➜  advanced-mcp-features git:(main) sudo sudo lsof -t -i:5639
[sudo] password for isimmons: 
125342
125751
➜  advanced-mcp-features git:(main) 

Tested on both node v 23.11.1 and node v 24.4.1 and got the same results.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions