Jump to content
The TIBCO Platform is a real-time, composable data platform that will bring together an evolving set of your TIBCO solutions - and it's available now! See more information here ×

Tibco BWCE_Mon container not able to start - timeout with mysql connection


dijesh tanna

Recommended Posts

Hello All,

We are trying to run Tibco BWCEMon container in Docker (Linux). Although the mysql server is up & running , we are getting below error while starting the BWCEMon Container (refer attachment).

docker run -p 8080:8080 -e PERSISTENCE_TYPE="mysql" -e DB_URL="mysql://username:password@local ip of the machine:3306/bwcemonitoring" --name bwce-monitoring bwce/monitoring:latest

I'm trying to start the bwce monitoring container on my local machie on DockerForWindows (Linux containers)

INFO : Initializing mysql DB.... [2019-04-30T06:33:28.504Z] => ERROR : {"message":"connect ETIMEDOUT","stack":"Error: connect ETIMEDOUTn at Connection._handleConnectTimeout (/usr/src/app/node_modules/mysql/lib/Connection.js:419:13)n at Socket.g (events.js:291:16)n at emitNone (events.js:86:13)n at Socket.emit (events.js:185:7)n at Socket._onTimeout (net.js:339:8)n at ontimeout (timers.js:365:14)n at tryOnTimeout (timers.js:237:5)n at Timer.listOnTimeout (timers.js:207:5)n --------------------n at Protocol._enqueue (/usr/src/app/node_modules/mysql/lib/protocol/Protocol.js:141:48)n at Protocol.handshake (/usr/src/app/node_modules/mysql/lib/protocol/Protocol.js:52:41)n at Connection.connect (/usr/src/app/node_modules/mysql/lib/Connection.js:130:18)n at /usr/src/app/node_modules/knex/lib/dialects/mysql/index.js:106:18n at Promise._execute (/usr/src/app/node_modules/bluebird/js/release/debuggability.js:303:9)n at Promise._resolveFromExecutor (/usr/src/app/node_modules/bluebird/js/release/promise.js:483:18)n at new Promise (/usr/src/app/node_modules/bluebird/js/release/promise.js:79:10)n at Client_MySQL.acquireRawConnection (/usr/src/app/node_modules/knex/lib/dialects/mysql/index.js:104:12)n at Object.create (/usr/src/app/node_modules/knex/lib/client.js:239:16)n at Pool._createResource (/usr/src/app/node_modules/generic-pool/lib/generic-pool.js:354:17)n at Pool._ensureMinimum (/usr/src/app/node_modules/generic-pool/lib/generic-pool.js:408:12)n at new Pool (/usr/src/app/node_modules/generic-pool/lib/generic-pool.js:157:8)n at Client_MySQL.initializePool (/usr/src/app/node_modules/knex/lib/client.js:269:17)n at Client_MySQL.Client (/usr/src/app/node_modules/knex/lib/client.js:116:12)n at new Client_MySQL (/usr/src/app/node_modules/knex/lib/dialects/mysql/index.js:62:20)n at Knex (/usr/src/app/node_modules/knex/lib/index.js:60:34)","errorno":"ETIMEDOUT","code":"ETIMEDOUT","syscall":"connect","fatal":true} [2019-04-30T06:33:28.504Z] => INFO : DB Retry Count :1

Thanks & Regards.

Dijesh Tanna

Link to comment
Share on other sites

  • 2 weeks later...

Issue got resolved by using the mysql 5.7 version instead of latest version.

Latest version of the mysql provides different kind of authentication which is not working with current Tibco BWCE Mon.

 

While pulling the image for mysql please use the tag 5.7.

 

docker run -p 3306:3306 --name mysql -e MYSQL_ROOT_PASSWORD=root -e -d mysql:5.7

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...