-
Notifications
You must be signed in to change notification settings - Fork 4
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
Failed to start DRB: port already in use #6
Comments
I'll come back to better handling the failure later. For now, how are you ascertaining that nothing is holding the port? |
If I kill ahn and immediately start it again, it works.. thought it was a Vagrant networking thing while I was developing it, but also seeing it on a live staging server too. |
How do you kill ahn? |
In development, "cd #{@talkbox_path} && bundle exec ahn stop . && bundle exec ahn daemon ." |
|
This implies some other process already has the port open. Is it possible that you have another instance of Adhearsion (perhaps not quite shutdown) still running? Even another Ruby process using DRb on the same port? |
No other ahn running at the time... forgot to |
I've occasionally seen adhearsion-drb fail to initialize, both legitimately (something already had the port), or freakishly randomly. No log at the moment, I'll try to capture one next time I see a random fail...
But, if it does fail, it just logs a one-line error, and the adhearsion up starts up normally. Most applications using adhearsion-drb probably rely on it for core functionallity, so I think adhearsion-drb should either:
Any thoughts about better failure handling?
The text was updated successfully, but these errors were encountered: