[Errno 10048] error while attempting to bind

[ryanwesslen]

hi @beperron,

Thanks for your question.

Typically the main reason you're getting this error is because you still have running another instance of Prodigy running but don't realize it (this is why you're getting a port collision).

The easiest way to resolve is to look at what's running on that port and try to shut it down.

Error: address already in use

hi @bulldog903! Thanks for your post and welcome to the Prodigy community I suspect you have an old session still running. After each time you run Prodigy e.g., python -m prodigy ... you need stop it when you're done by pressing CTRL + C. What I think you're doing is trying to run a second process on the same 8080 port (hence "address already in use"). What do you see when you run: sudo lsof -i :8080 If see something running, find the pid and then run: kill -9 <PID> This will k…

Can you try this? I'd start first with the 8080 as my assumption is you may have a Prodigy process still running on that port and may need to kill it. Alternatively, you could restart your computer and try again. I'm a bit more hesitant on 8000 as I'm a bit worried this may be non-Prodigy/Jupyter related.

@beperron

Prodigy does open on the local server but is certainly problematic as it doesn't load in the details of the dataset:

I don't understand what you mean that "it doesn't load in the details of the dataset:". Can you explain more?

@beperron

Was this from opening localhost:8080 or localhost:8000?

Are you getting these same issues if you run Prodigy from a terminal, not a Jupyter notebook?

[Errno 10048] error while attempting to bind on address ('::1', 8081, 0, 0): only one usage of each socket address (protocol/network address/port) is normally permitted

i got the same error as above (also working under windows 10 in jupyterlab). Installing murmurhash does not show any effect. I also changed the port for the prodigy localhost to e.g. 8081. The Main Problem is that once a prodigy session is started i dont seem to be able to terminate it anymore. So it isnt possible to start another prodigy process with e.g. a different dataset unless i terminate the sessions kernel of the jupyterlab session. Starting and Terminating Sessions from the console…

In the past, I know some users have experienced issues that are actually Jupyter related, not Prodigy. While Jupyter may make be easier for some things, we've noticed a lot of users realizing Jupyter introduces a lot of new problems so Prodigy is typically better to use on the CLI, especially if you're having issues like this.

@beperron

I went into the json config file and changed the port from 8080 to 8000 (as shown here), and the problem persists.

Did you try any other port? Not sure if you have some other non-Prodigy/Jupyter related process running on 8000 too.

Fyi, you can normally specify config overrides like PRODIGY_PORT=1234 python -m prodigy ....

Can you try a few other ports to see if it works?

This can be a bit more complex when using Jupyter too:

setting up multiple annotators on Prodigy web

It looks like this might be some weirdness/quirk of Jupyter Notebooks – maybe you need to use their specific syntax instead. See here:

Hope this gives you a few pointers to start with.