-
Notifications
You must be signed in to change notification settings - Fork 16
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
Error - False port in use #1
Comments
I have quite the same issue... Following the instructions here, running
The only thing changed is the remove of the engines section in Seems that 2 processes are trying to start. Digging. |
@jichu4n FYI |
OK just to confirm following that:
and my output:
My config
the
|
Testing with the HTTP server start commented... Why the adapater is starting a second HTTP server ? |
OK disabling the existing HTTP server is not a good idea. But here is a commit to re-use the existing HTTP server built-in and just listen a particular url via Can I push the 2 commits as a PR ? If you want to test my fork this just edit your
Then run |
@a4sh3u Can you try setting EXPRESS_PORT and PORT environment variables explicitly as shown in https://developers.google.com/hangouts/chat/how-tos/integrate-hubot#deploy_in_appengine As @bobman38 mentioned, there are two express servers being initialized today - an express server that comes built-in with Hubot and one that is spinned up by this adapter. If the EXPRESS_PORT and PORT environment variables are not explicitly set, both try to listen to the same port 8080 and hence clash. This is not ideal. We will look into fixing this. |
@bobman38 Let me make sure using the hubot built-in express server is OK and get back to you on the PR. |
@kumarse thanks. that works |
To disable the default HTTP daemon, just pass The developer doc has been updated: |
Hi,
I'm trying to run this app in docker and get the port in use error with any port I use. Please help
Here is my Dockerfile:
And here is the error I get while trying to the run the image created from above:
The text was updated successfully, but these errors were encountered: