OSX cannot close server ports properly

Asked Jan 01 '18 at 14:14

Active Jan 01 '18 at 14:14

Viewed 39 times

I use local server enviroments on my mac. But every time I close the server by terminal process is still working so when I want to turn it on again I've got error that port I used previously is already occupied. So I need to find and kill that process with

netstat -vanp tcp | grep [PORT]

command which is very annoing and time-wasting. This is not related to any server technology since I've got the same problem using both Node.js and Ruby on Rails. It's something wrong with OSX. How can I fix that issue? I use OSX El Capitain version 10.11.6

asked Jan 01 '18 at 14:14

Jacek717

You could try trace the command used to "close the server" with `dtruss` – Zlemini Jan 02 '18 at 00:40
I simply type CMD + C to stop the server. It works fine on my second mac computer – Jacek717 Jan 03 '18 at 06:24
CMD + C sends a kill signal to the server PID, to debug precede the kill command with dtruss, see: https://stackoverflow.com/questions/31045575/how-to-trace-system-calls-of-a-program-in-mac-os-x – Zlemini Jan 03 '18 at 13:40
CMD+C performs a clipboard-copy on MacOS. Did you mean to type Ctrl+C? – Christopher Schultz Apr 23 '21 at 01:11

OSX cannot close server ports properly

0 Answers0