MDCB installation issue

Hello, i’m trying to helm upgrade with licence of MDCB but got issue connection reset by peers in logs

helm show values tyk-helm/tyk-pro > values.yaml

After got licence edit values.yaml mdcb.enable: true and mdcb.license: “valueOfLicence”

helm upgrade -f values.yaml tyk-pro tyk-helm/tyk-pro -n tyk-dev

version helm: tyk-pro-0.9.3
Redis (redis_version:5.0.5) and Mongodb is using Apsara RDS by Alicloud

Here’s the logs:

kac logs pod/mdcb-tyk-pro-6556496958-tszqp -n tyk-dev
time="2021-09-14T12:00:50Z" level=info msg="Starting Tyk DC Bridge v1.8.0"
time="2021-09-14T12:00:50Z" level=info msg="Connecting Store"
time="2021-09-14T12:00:50Z" level=info msg="--> [REDIS] Creating single-node client"
time="2021-09-14T12:00:50Z" level=info msg="Connecting Session Store"
time="2021-09-14T12:00:50Z" level=info msg="Setting up dispatcher"
time="2021-09-14T12:00:50Z" level=info msg="Connecting to Mongo"
time="2021-09-14T12:00:50Z" level=info msg="Connecting to MongoDB: [dds-aliyuncs.com:3717]"
time="2021-09-14T12:00:50Z" level=info msg="MongoDB connection established"
time="2021-09-14T12:00:50Z" level=info msg="Starting pub/sub signal handler"
time="2021-09-14T12:00:50Z" level=info msg="Starting Keyspace watcher"
time="2021-09-14T12:00:50Z" level=info msg="Starting RPC server"
time="2021-09-14T12:00:50Z" level=info msg="Keyspace listener starting..."
time="2021-09-14T12:00:50Z" level=info msg="--> Starting pub/sub"
time="2021-09-14T12:00:50Z" level=info msg="Subscription started: tyk.cluster.keyspace.ops"
time="2021-09-14T12:00:50Z" level=info msg="Subscription started: tyk.cluster.notifications"
2021/09/14 12:00:57 gorpc.Server: []->[:9090]. OnConnect error: [read tcp 172.31.128.86:9090->172.31.128.65:20857: read: connection reset by peer]
2021/09/14 12:00:57 gorpc.Server: []->[:9090]. OnConnect error: [read tcp 172.31.128.86:9090->10.2.28.193:23700: read: connection reset by peer]
2021/09/14 12:00:57 gorpc.Server: []->[:9090]. OnConnect error: [read tcp 172.31.128.86:9090->10.2.28.193:12233: read: connection reset by peer]
2021/09/14 12:00:57 gorpc.Server: []->[:9090]. OnConnect error: [read tcp 172.31.128.86:9090->172.31.128.65:44591: read: connection reset by peer]
2021/09/14 12:00:59 gorpc.Server: []->[:9090]. OnConnect error: [read tcp 172.31.128.86:9090->172.31.128.65:30931: read: connection reset by peer]

In values.yaml in mdcb part

    image:
        # Requires credential
        repository: tykio/tyk-mdcb-docker

Is this still relevant, credentials for docker images?

Is my setup correct? Any help appreciated, thank you

Hi, welcome to the Community Forums!

The fact you have the docker image up and running and logs demonstrates you don’t have to worry about docker credentials anymore. We’ll get the comments updated to reflect that.

I assume the target IP addresses listed in the logs correspond to the mongodb and/or redis stores that the mdcb requires to operate. If they are not, can you check the connection details specified in the mdcb deployment, I assume you filled them in when completing the yaml file where you enabled the mdcb.

If these are all correct, are your dashboard and gateway(s) from your existing installation still functioning okay? They aren’t having connection problems to these services?

Best Regards,
Chris

Dashboard and gateway can connect well to mongodb and redis store. Just MDCB issue.

Here’s dashboard logs:

time="Sep 14 04:39:32" level=info msg="Tyk Analytics Dashboard v3.2.0"
time="Sep 14 04:39:32" level=info msg="Copyright Tyk Technologies Ltd 2020"
time="Sep 14 04:39:32" level=info msg="https://www.tyk.io"
time="Sep 14 04:39:32" level=info msg="Using /etc/tyk-dashboard/tyk_analytics.conf for configuration"
time="Sep 14 04:39:32" level=info msg="Listening on port: 3000"
time="Sep 14 04:39:32" level=info msg="Connecting to MongoDB: [dds-aliyuncs.com:3717]"
time="Sep 14 04:39:32" level=info msg="Mongo connection established"
time="Sep 14 04:39:32" level=info msg="Creating new Redis connection pool"
time="Sep 14 04:39:32" level=info msg="--> [REDIS] Creating single-node client"
time="Sep 14 04:39:32" level=info msg="Creating new Redis connection pool"
time="Sep 14 04:39:32" level=info msg="--> [REDIS] Creating single-node client"
time="Sep 14 04:39:32" level=info msg="Licensing: Setting new license"
time="Sep 14 04:39:32" level=info msg="Licensing: Registering nodes..."
time="Sep 14 04:39:32" level=info msg="Adding available nodes..."
time="Sep 14 04:39:32" level=info msg="Licensing: Checking capabilities"
time="Sep 14 04:39:32" level=info msg="Audit log is disabled in config"
time="Sep 14 04:39:32" level=info msg="Creating new Redis connection pool"
time="Sep 14 04:39:32" level=info msg="--> [REDIS] Creating single-node client"
time="Sep 14 04:39:32" level=info msg="--> Standard listener (http) for dashboard and API"
time="Sep 14 04:39:32" level=info msg="Starting zeroconf heartbeat"
time="Sep 14 04:39:32" level=info msg="Starting notification handler for gateway cluster"
time="Sep 14 04:39:32" level=info msg="Loading routes..."

Here gateway logs:

time="Sep 15 02:49:49" level=info msg="Tyk API Gateway v3.1.2" prefix=main
time="Sep 15 02:49:49" level=warning msg="Insecure configuration allowed" config.allow_insecure_configs=true prefix=checkup
time="Sep 15 02:49:49" level=warning msg="AnalyticsConfig.PoolSize unset. Defaulting to number of available CPUs" prefix=checkup runtime.NumCPU=4
time="Sep 15 02:49:49" level=warning msg="AnalyticsConfig.RecordsBufferSize < minimum - Overriding" minRecordsBufferSize=1000 prefix=checkup
time="Sep 15 02:49:49" level=info msg="Starting Poller" prefix=host-check-mgr
time="Sep 15 02:49:49" level=info msg="PIDFile location set to: /mnt/tyk-gateway/tyk.pid" prefix=main
time="Sep 15 02:49:49" level=warning msg="The control_api_port should be changed for production" prefix=main
time="Sep 15 02:49:49" level=info msg="Initialising Tyk REST API Endpoints" prefix=main
time="Sep 15 02:49:49" level=info msg="--> [REDIS] Creating single-node client"
time="Sep 15 02:49:49" level=info msg="--> Standard listener (http)" port=":8080" prefix=main
time="Sep 15 02:49:49" level=warning msg="Starting HTTP server on:[::]:8080" prefix=main
time="Sep 15 02:49:49" level=info msg="Registering gateway node with Dashboard" prefix=dashboard
time="Sep 15 02:49:49" level=info msg="--> [REDIS] Creating single-node client"
time="Sep 15 02:49:49" level=info msg="Node Registered" id=62c277a3-1fc1-4587-76c0-575cd0b0e77d prefix=dashboard
time="Sep 15 02:49:49" level=info msg="Initialising distributed rate limiter" prefix=main
time="Sep 15 02:49:49" level=info msg="Tyk Gateway started (v3.1.2)" prefix=main
time="Sep 15 02:49:49" level=info msg="--> Listening on address: (open interface)" prefix=main
time="Sep 15 02:49:49" level=info msg="--> Listening on port: 8080" prefix=main
time="Sep 15 02:49:49" level=info msg="--> PID: 1" prefix=main
time="Sep 15 02:49:49" level=info msg="Loading policies" prefix=main
time="Sep 15 02:49:49" level=info msg="Using Policies from Dashboard Service" prefix=main
time="Sep 15 02:49:49" level=info msg="Mutex lock acquired... calling" prefix=policy
time="Sep 15 02:49:49" level=info msg="Calling dashboard service for policy list" prefix=policy
time="Sep 15 02:49:49" level=info msg="Starting gateway rate limiter notifications..."
time="Sep 15 02:49:49" level=info msg="Processing policy list" prefix=policy
time="Sep 15 02:49:49" level=info msg="Policies found (0 total):" prefix=main
time="Sep 15 02:49:49" level=info msg="Detected 10 APIs" prefix=main

Hi,

Thanks for sharing the logs, and confirming your gateway and dashboard are operational. I believe one of our Customer Success Engineers has or will soon be in contact to help you through the setup and configuration of your MDCB. If this is not the case, please reach out via [email protected] and we’ll ensure this is taken care of for you!

Best Regards,
Chris