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

Listener Process does not startup on some servers #68

Open
bakshigit opened this issue Apr 25, 2022 · 1 comment
Open

Listener Process does not startup on some servers #68

bakshigit opened this issue Apr 25, 2022 · 1 comment

Comments

@bakshigit
Copy link

On some Linux servers we are not able to see the message "Listening for webex teams events..." and the only message we get is below :
LoggerProxy->error#NO LOGGER DEFINED

Because of this missing listener process the bot never responds to any of the requests generated from any webex space .

Can you suggest how to troubleshoot this issue further ?? How can more logging be enabled ??

Our startup command is

docker run
-e PORT=8000
-e https_proxy=http://.......
-e http_proxy=http://.......
-e JENKINS_URL=http://.....
-e WEBEX_TOKEN=.....
-e PASS_USER_TO_JENKINS=true
--rm --name nonprod-bot
docker.artifactory.us......

Jenkins URL is accessible from all environments.

Please help

@jpjpjp
Copy link
Collaborator

jpjpjp commented Apr 25, 2022

Hi @bakshigit, you might get more immediate help by posting a message in the "Webex Node Bot Framework" space on Webex.

Its not clear to me from your docker command how you are configuring the framework. Are you setting a webhookUrl in the framework's config object? If so are you able to send a curl request to your websocket address from a machine outside your network?

If you aren't setting webhookUrl in the framework's config object, then the SDK is attempting to negotiate a websocket connection with your server. There may be firewall configurations that prevent this. I can see that you have some proxy servers so you also may need to set httpsProxy in the framework's config object as well.

Hope this helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants