Troubleshooting
Lemur Daemon wont start
Started by Mugison on .
Sign in or create an account to join the conversation.
When trying to run Lemur Deamon I get this :
ERROR
"Couldn´t bind to port 8001. Please check if port is used by another applicaton or service"
dose anyone know what to do?
thanks
ERROR
"Couldn´t bind to port 8001. Please check if port is used by another applicaton or service"
dose anyone know what to do?
thanks
see if there are any other tools or applications that may be using port 8001. If there is none, I would try to reinstall.
hi Phil999
how do I do that?
how do I do that?
Are you using any other apps that are using OSC?
Max, Osculator ? Or similar?
Have you tried after a restart ?
MM
Max, Osculator ? Or similar?
Have you tried after a restart ?
MM
having the same problem.
i cant figure out where/how to find out what other process might be using port 8001.
i've been looking for a while and cant find an answer on this. found the question in a couple other forums and one dude said that his problem went away after a day or two, then came back.
this topic in this forum has the most recent activity so here goes again.
bump.
osx 10.7.5 - ipad 2 ios5 - Lemur-Installer-3.2.3
i cant figure out where/how to find out what other process might be using port 8001.
i've been looking for a while and cant find an answer on this. found the question in a couple other forums and one dude said that his problem went away after a day or two, then came back.
this topic in this forum has the most recent activity so here goes again.
bump.
osx 10.7.5 - ipad 2 ios5 - Lemur-Installer-3.2.3
I had the same problem. I couldn't see anything using the port 8000 or 8001 using "lsof -i" or "netstat -an" in terminal.
It turns out I had a network midi session running in the Audio Midi Setup in Utilities.
I don't know why i didn't see this in the terminal, but anyway changing that port solved this problem for me.
It turns out I had a network midi session running in the Audio Midi Setup in Utilities.
I don't know why i didn't see this in the terminal, but anyway changing that port solved this problem for me.