Reply
New Contributor
Posts: 2
Registered: ‎06-25-2017

Web pod could not connect to db service

Current issue
Cloudera Data Science Workbench Status

Service Status
docker: active
kubelet: active
nfs: active
Checking kernel parameters...

Node Status
NAME STATUS AGE STATEFUL
workbench.cdsw.redact.local Ready 6d true

System Pod status
NAME READY STATUS RESTARTS AGE
dummy-2088944543-x03js 1/1 Running 0 6d
etcd-workbench.redact.local 1/1 Running 0 6d
kube-apiserver-workbench.cdsw.redact.local 1/1 Running 0 6d
kube-controller-manager-workbench.cdsw.redact.local 1/1 Running 0 6d
kube-discovery-1150918428-ojcd4 1/1 Running 0 6d
kube-dns-248550476-oxyql 3/3 Running 0 6d
kube-proxy-o7qty 1/1 Running 0 6d
kube-scheduler-workbench.cdsw.redact.local 1/1 Running 0 6d
node-problem-detector-v0.1-w83kx 1/1 Running 0 6d
weave-net-f3id4 2/2 Running 0 6d

Cloudera Data Science Workbench Pod Status
NAME READY STATUS RESTARTS AGE ROLE
cron-3971587342-wrxhy 1/1 Running 0 6d cron
db-4066525870-ulh4u 1/1 Running 0 6d db
db-migrate-abec968-sb9nn 0/1 Completed 0 6d db-migrate
engine-deps-r2vo5 1/1 Running 0 6d engine-deps
ingress-controller-2976678207-erjp3 1/1 Running 0 6d ingress-controller
livelog-2494298876-rg3y9 1/1 Running 0 6d livelog
reconciler-577027981-rmdn4 1/1 Running 0 6d reconciler
spark-port-forwarder-q4ghi 1/1 Running 0 6d spark-port-forwarder
web-1304125449-n8odb 1/1 Running 0 6d web
web-1304125449-nt697 1/1 Running 0 6d web
web-1304125449-vunkz 1/1 Running 0 6d web

Cloudera Data Science Workbench is ready!
[root@workbench cloudera-scm-agent]# cdsw validate
Checking services...
Checking if docker is active and enabled
Checking if docker is responsive
Checking if kubelet is active and enabled
Check if docker monitor is active
Testing networking setup...
Check if kubelet iptables rules exist
Check that firewalld is disabled
Check configuration file...
Checking master node filesystem configuration...
Checking kubernetes
Checking system pods
Checking application pods exist
Checking application pods are running
Checking web pods have access to the databases
error: error sending request: Post https://10.21.9.158:6443/api/v1/namespaces/default/pods/web-1304125449-n8odb/exec?command=%2Fbin%2Fb...: http: server gave HTTP response to HTTPS client

ERROR:: Web pod web-1304125449-n8odb could not connect to the db service: 1

Cloudera Employee
Posts: 29
Registered: ‎04-28-2017

Re: Web pod could not connect to db service

Can you also show the output of cdsw status to ensure the database is running? 

 

If the database is running and the web pods can still not access the database this is sometimes a sign of existing iptables rules that conflict with the networking setup within CDSW.  Does your system have any custom iptables rules?  For instance, a NOTRACK rule can break virtual ip functionality used by Kubernetes services.

 

Thanks,

Tristan

Highlighted
New Contributor
Posts: 2
Registered: ‎06-25-2017

Re: Web pod could not connect to db service

Hi,

A complete redo resolved it. 

Announcements