-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] - conda-store-server silently exits when port is already in use #562
Comments
From today's meeting, we should have a helpful error message here. Also, as a sidenote, we should change the default port to something other than 5000 (because 5000 doesn't work on Mac machines). |
For developers, it makes total sense to have two simultaneously running instances of conda-store, for instance to compare behaviors after a modification. Note that in this context, we're talking of two different versions running simultaneously, or twice the same version from two different directories. For the users, I don't see any scenario requiring two instances running simultaneously but I'd rather not limit what users can do. So I think multiple instances running should be supported. Now, two cases :
We'll discuss the prefered behavior during our meeting. |
Status as of 5e4e2e5:
|
Describe the bug
If you start conda-store-server when the configured port is already in use (e.g., because conda-store-server is already running), the process just silently exits.
Expected behavior
It should at least give an error message.
Actually, it should probably do one of the following:
Even if the latter is the case, finding a free port could be useful in case some other application is using port 5000.
How to Reproduce the problem?
Run
conda-store-server
then runconda-store-server
again in a different terminal.Output
This is the only output that appears
However, you can tell what the real problem is if you make the following patch
Then you get the error in the additional printed traceback:
Versions and dependencies used.
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: