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

Error "Unable to connect MessageBus" occurs sometimes when deploying backward compose file with mqtt bus #4141

Open
cherrycl opened this issue Sep 1, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@cherrycl
Copy link
Contributor

cherrycl commented Sep 1, 2022

🐞 Bug Report

Affected Services [REQUIRED]

The issue is located in: Data

Is this a regression?

No

Description and Minimal Reproduction [REQUIRED]

Run scenarios for backward compatibility test on Jenkins. See scenarios on edgex-taf-pipeline #108
Can't reproduce on my local machine so far.

This issue does not happen every time.
Attached backward compose files and logs.
backward-compose.zip
mqtt-bus-core-data.log
mqtt-broker.log

🔥 Exception or Error




Unable to connect MessageBus: %!w(mqtt.OperationErr={Connect network Error : dial tcp 172.20.0.5:1883: connect: connection refused})"

🌍 Your Environment

Deployment Environment:

EdgeX Version [REQUIRED]:

Anything else relevant?

@cherrycl cherrycl added the bug Something isn't working label Sep 1, 2022
@lenny-goodell
Copy link
Member

lenny-goodell commented Sep 1, 2022

Can you try setting EDGEX_STARTUP_DURATION: "120" on core data to extend bootstrapping duration? Default is 60s.

@cherrycl
Copy link
Contributor Author

cherrycl commented Sep 2, 2022

Added the EDGEX_STARTUP_DURATION: "120" on all core-services and support-services. Still got the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants