Reply
New Contributor
Posts: 5
Registered: ‎04-04-2018

CDWS web ui is not up

 

Here is the log of cdsw status command

 

OK: Sysctl params check
Failed to run CDSW Nodes Check.
Failed to run CDSW system pods check.
Failed to run CDSW application pods check.
Failed to run CDSW services check.
Failed to run CDSW config maps check.
Failed to run CDSW secrets check.
Failed to run CDSW persistent volumes check.
Failed to run CDSW persistent volumes claims check.
Failed to run CDSW Ingresses check.
Checking web at url: http://cdswonprem.rush.edu
Web is not yet up.
Cloudera Data Science Workbench is not ready yet

 

 

Log of cdsw logs

 

/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 40: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 40: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 40: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 40: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 40: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 40: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 40: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 58: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 62: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 80: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 85: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 85: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 85: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 85: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 85: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 85: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 85: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 85: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 85: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 106: kubectl: command not found
Exporting user ids...
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-logs.sh: line 223: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-logs.sh: line 224: kubectl: command not found
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-logs.sh: line 225: kubectl: command not found
Checking system logs...
Collecting health logs...
Exporting metrics...
/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-dump-metrics.sh: line 22: kubectl: command not found

ERROR:: Unable to get service account credentials. Provide SERVICE_ACCOUNT_SECRET or run on master node.: 2

 

 

 

Note : In worker node, cdsw <status> works fine, wheareas in master, i need to navigate the parcels directory and provide the following command ./cdsw status.

 

If I type only cdsw status in master node, then it will through error message "cdsw command not found"

 

Could someone help to resolve the issue to webui make is up?

 

 

 

 

 

Highlighted
Posts: 47
Topics: 0
Kudos: 6
Solutions: 5
Registered: ‎05-15-2018

Re: CDWS web ui is not up

Hello @dpugazhe

 

Thanks for posting your query.

 

From the message

 

"/opt/cloudera/parcels/CDSW-1.2.2.p1.216803/scripts/cdsw-pod-logs.sh: line 40: kubectl: command not found"

 

It seems your installation is missing the necessary kubernetes package. Could you please check if there was any installation errors on the node which you specified ?

 

 

Thanks,
Satz
Announcements