Find (AND KILL) port 23515 Mac osx

Question

new here have learned tons over the years and happen to have a pretty puzzling question. I just purchased a product to help edit photos in Adobe Lightroom. Its called a Loupedeck. Comes with software and is a device that controls all the parameters in Lightroom (makes editing way quicker) Once I installed their loupdeck software and opened Lightroom I immediately got this prompt.

"Loupedeck needs access to tcp ports 23515 and 23516. Other process is currently occupying 23515. Loupedeck will not work until that application is closed."

I have been searching for days trying to find what app I have installed thats using or used port 23515. I have tried checking in terminal with the simple netstat command, and found nothing. I've used little snitch to see if any programs are using that port, still nothing. Im a little lost and sadly the company is also lost and has no advice.

Computer - Macbook pro 2011 17" 2.3ghz OSX 10.12.6

Here is the error in Lightroom

h0n3ycl0ud · Answer 1 · 2017-08-18T20:09:50.343

6

From this answer:

lsof -n -i4TCP:23515
lsof -n -i TCP:23515 | grep LISTEN
lsof -n -i:23515 | grep LISTEN

Netstat may also work:

netstat -ap tcp | grep -i "23515"

Any of these commands should give you the name and PID of the process. Once you have the PID, you can kill the process, or if you know the process name is process_name you can use killall -KILL process_name .

Just for the record though, your terminal isn't running an administrative shell by default. In order to execute commands in terminal as an administrator, you have to use the command sudo su and then enter your password. Once you have a prompt with a #, you can try these commands again, just to be sure.

edited Aug 18 '17 at 20:09

answered Aug 18 '17 at 19:14

h0n3ycl0ud

65
4

Hmm, im getting nothing with trying each line you sent, as well as minhtuannguyen's line he posted. – David Iliyn Aug 18 '17 at 19:23
Have you tried `netstat -ap tcp | grep -i "23515"` ? If neither `lsof` nor `netstat` show an open port, then certainly the OS isn't aware of 23515 being occupied and it may be a bug in the software – h0n3ycl0ud Aug 18 '17 at 19:29
OH also: you may have to be an administrator to get all of the information about open ports. Not sure about that but it's possible. – h0n3ycl0ud Aug 18 '17 at 19:31
I also tried netstat -ap tcp | grep -i "23515" and it gave me nothing :-/ I am the admin of the computer, it sounds like it has to be a bug in the software, there have been a few cases with people running into the same thing. – David Iliyn Aug 18 '17 at 19:40
Well unfortunately all we can do is tell you how to do what you're asking x) If it were open source software, it'd be figured out and fixed lickety-split. Since it's not, you could at least contact customer support :) – h0n3ycl0ud Aug 18 '17 at 19:53
I edited my answer to include information about running the commands as an administrator. – h0n3ycl0ud Aug 18 '17 at 20:10
@ac1dh0n3ycl0ud your commands are working. @David lliyn, I would recommend the `lsof` command over `netstat` for this type of job. My experience with `netstat` is that some times it freezes (maybe my computer ;-) – Stephane Paquet Aug 19 '17 at 00:31
Crazy, cant find them! Not sure whats going on. Hopefully the company can figure it out otherwise this unit people are purchases is a big ole paper weight... – David Iliyn Aug 20 '17 at 01:18
Did you try running those commands from a root shell? I can't think of a reason why `netstat` or `lsof` wouldn't find them as a regular user, but that's the only reason I can think of that those ports might be occupied and you can't see them. Obviously you checked both ports (in case it's actually 23516 that's occupied and the error message is wrong...) ? – h0n3ycl0ud Aug 20 '17 at 01:39
ALSO... if you have a firewall, that could be blocking Loupedeck's access to the ports. Check those settings. Specifically, try disabling your firewall then trying to make it work. – h0n3ycl0ud Aug 20 '17 at 01:50

score 3 · Answer 2 · answered Aug 19 '17 at 00:29

In one command find and kill:

kill -9 `lsof -i : 23515 -t` or if the existing process was launched by root or an other user: sudo kill -9 `lsof -i : 23515 -t`

lsof -i : 23515 returns the process id using the port 23515 on your machine.

You may also want to restart your computer, just in case the process using this port went into a "zombie" mode or lock the port and went off without freeing the port.

score 2 · Answer 3 · edited Aug 19 '17 at 00:16

2

You can try to fine the process listening to those ports:

lsof -i :23515 -t

edited Aug 19 '17 at 00:16

Miriam Farber

18,986
14
61
76

answered Aug 18 '17 at 19:11

Minh Tuan Nguyen

1,026
8
13

score 2 · Answer 4 · answered Jan 08 '23 at 11:14

If you want to save time in the long run, you can add this script "kill-process.sh" into your /usr/local/bin

#!/bin/bash
echo Killing process..

usage() { echo "Usage: $0 [-p <port-number>]" 1>&2; exit 1; }

while getopts ":p:" o; do
    case "${o}" in
        p)
            p=${OPTARG}
            ((p > 0 )) || usage
            ;;
        *)
            usage
            ;;
    esac
done

shift $((OPTIND-1))

if [ -z "${p}" ]; then
    usage
fi

PID=$(lsof -ti:$p)
if [ -z "${PID}" ]; then
    echo "No process running on port ${p}"
else 
    kill $PID
    echo "Killed process PID: ${PID}"
fi

Add this line into your .zshrc

alias kill-process="sh /usr/local/bin/kill-process.sh"

Then just run from your terminal

kill-process -p 23515

You will save time in the long run and this is useful if you need to close any process in any port by specifying it as a parameter.

Find (AND KILL) port 23515 Mac osx

4 Answers4