Skip to content
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.

Sign up for GitHub

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

Jump to bottom

"Can't create listen socket: Address already in use" does not say which port is in use #485

Open
preaction opened this issue Apr 2, 2016 · 1 comment
Open

"Can't create listen socket: Address already in use" does not say which port is in use #485

preaction opened this issue Apr 2, 2016 · 1 comment
Labels
bug

Comments

@preaction
Copy link
Owner

When port 3000 is already in use, we get an error: Can't create listen socket: Address already in use. But we don't get told which port is already in use, so we don't know how to proceed. Add an error message that explains how to fix this.
@preaction preaction added the bug label Apr 2, 2016
jluis added a commit to jluis/Statocles that referenced this issue Apr 7, 2016
@jluis
Rewrite Error message Address in use preaction#485
a520cbd 
"Can't create listen socket: Address already in use" is rewriten as
"Can't create listen socket on port $port: Address already in use"

Signed-off-by: Jose Luis Perez Diez <[email protected]>
@jluis
Copy link

jluis commented Apr 7, 2016

Hi
I've created CPR pull request #487 that adrreses this isue loking for the next one

jluis added a commit to jluis/Statocles that referenced this issue Apr 8, 2016
@jluis
Rewrite Error message Address in use preaction#485
335a5a0 
"Can't create listen socket: Address already in use" is rewriten as
"Can't create listen socket for (http://*:3000): Address already in use"
it changes all "Can't create listen socket:" messages to
"Can't create listen socket for ($listen_URL):"


Signed-off-by: Jose Luis Perez Diez <[email protected]>
jluis added a commit to jluis/Statocles that referenced this issue Apr 11, 2016
@jluis
Rewrite Error message Address in use preaction#485
075185e 
"Can't create listen socket: Address already in use" is rewriten as
"Can't create listen socket for (http://*:3000): Address already in use"
it changes all "Can't create listen socket:" messages to
"Can't create listen socket for ($listen_URL):"

It has a test in t/command/daemon.t that test the new messge when no port
is specified


Signed-off-by: Jose Luis Perez Diez <[email protected]>
jluis added a commit to jluis/Statocles that referenced this issue Apr 11, 2016
@jluis
Rewrite Error message Address in use preaction#485
372257e 
"Can't create listen socket: Address already in use" is rewriten as
"Can't create listen socket for (http://*:3000): Address already in use"
it changes all "Can't create listen socket:" messages to
"Can't create listen socket for ($listen_URL):"

It has a test in t/command/daemon.t that test the new messge when no port
is specified


Signed-off-by: Jose Luis Perez Diez <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@preaction @jluis