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.

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

rocket::ignite does not fail if its desired port is in use #260

Closed
ndarilek opened this issue Apr 15, 2017 · 1 comment
Closed

rocket::ignite does not fail if its desired port is in use #260

ndarilek opened this issue Apr 15, 2017 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@ndarilek
Copy link

Rocket/codegen version: 0.2.4
Rust: rustc 1.18.0-nightly (bbdaad0dc 2017-04-14)

If you have one Rocket server running on port 8000, then launch another, the second claims to work even though it can't possibly since port 8000 is already in use.

I just hit this running one Rocket example in one terminal then forgetting about it. I then launched the Hello World example, which claimed to be running, and couldn't figure out why it kept 404ing on me. It wasn't until I found and killed the other server that I realized what was up.

@SergioBenitez SergioBenitez added the duplicate This issue or pull request already exists label Apr 15, 2017
@SergioBenitez
Copy link
Member

This is a duplicate of #209. Please refer to that issue for details on the matter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants