Bailongma icon indicating copy to clipboard operation
Bailongma copied to clipboard

Bailongma can not connect to taos db cluster in kubernetes

Open kitianFresh opened this issue 3 years ago • 8 comments

Hi, @sangshuduo I deployed an tdengine cluster in k8s followed TDengine-Operator, following is my tdengine pods and service, and it worked. image

then i deployed bailongma image

bailongma can not connect to taos. following is logs image

and i can connect to tdengine by restful api in blm_prometheus container.

image

kitianFresh avatar Jul 21 '21 07:07 kitianFresh

can you try taos shell to connect the taosd server from blm_prometheus container and see what happen?

sangshuduo avatar Jul 21 '21 08:07 sangshuduo

@sangshuduo taos shell can not connect to server image

kitianFresh avatar Jul 22 '21 08:07 kitianFresh

@kitianFresh okay. I guess something wrong regards network communication. please refer to our FAQ to diagnose. https://www.taosdata.com/cn/documentation/faq

sangshuduo avatar Jul 22 '21 10:07 sangshuduo

@sangshuduo I used image provided by taos in the doc to deploy the blm_prometheus.

tdengine/blm_prometheus latest a284a4917664 11 months ago 246MB

kitianFresh avatar Jul 22 '21 14:07 kitianFresh

@kitianFresh  sorry for that. I think the bailongma docker image is out of date. We will update it with the latest version ASAP.

sangshuduo avatar Jul 22 '21 16:07 sangshuduo

@kitianFresh In order to check the network , you can try to execute ping tdengine-0.tdengine.default.svc.cluster.local on the blm_prometheus container

huskar-t avatar Jul 23 '21 02:07 huskar-t

@huskar-t I think the network is ok. You can read above message.

image

kitianFresh avatar Jul 23 '21 07:07 kitianFresh

@kitianFresh Execute show dnodes and observe whether the end_point column matches the k8s domain .then try to execute taos -h tdengine-0.tdengine.default.svc.cluster.local -u root -p on the blm_prometheus container

huskar-t avatar Jul 23 '21 10:07 huskar-t