viya vault and pgpool service were down in a fresh deployment to GKE

[sandeepgrande]

Hi Team ,

We have built and deployed SAS Viya Full on GKE. when we checked the status , we see vault and pgpool were down and there are no logs for vault under /var/log/sas/viya.
It is the same situation on pgpool pod.

Can you please help.

bash-4.2$ /etc/init.d/sas-viya-all-services status
Getting service info from consul...
Service Status Host Port PID
sas-viya-consul-default up N/A N/A 537
sas-viya-vault-default down N/A N/A N/A
sas-viya-alert-track-default up 10.32.0.35 0 767
sas-viya-ops-agent-default up 10.32.0.35 0 53704
sas-viya-watch-log-default up 10.32.0.35 0 1107
sas-viya-backup-agent-default up 10.32.0.35 35973 1050

Also , there were some extra characters at the file /opt/sas/viya/home/lib/envesntl/sas-init-functions which is causing error while checking the status of serivces.

Please help

[asbisen]

• vault is disabled by default in Viya 3.4 container recipes, so it being down is not anomalous.

• pgpool's status shows as "not ready", but it seems that the service is up and available because I can log in to the database using psql. most probably a cosmetic bug?

kubectl -n sas-viya exec -it sas-viya-pgpoolc-0 -- /etc/init.d/sas-viya-all-services status
Getting service info from consul...
  Service                                            Status     Host               Port     PID
  sas-viya-consul-default                            up         N/A                 N/A     139
  sas-viya-alert-track-default                       up         10.36.3.140           0     541
  sas-viya-ops-agent-default                         up         10.36.3.140           0    4813
  sas-viya-pgpool-default                            not ready  N/A                 N/A     N/A
  sas-viya-watch-log-default                         up         10.36.3.140           0    1980
  sas-viya-backup-agent-default                      up         10.36.3.140       37727     624

• As you have identified there is a typo in /opt/sas/viya/home/lib/envesntl/sas-init-functions @ line 277 in sas-viya-consul-0. Bug for sure, fortunately it does not affect the functionality.

kubectl -n sas-viya exec -it sas-viya-consul-0 -- /etc/init.d/sas-viya-all-services status
Getting service info from consul...
  Service                                            Status     Host               Port     PID
  sas-viya-consul-default                            up         N/A                 N/A     534
/opt/sas/viya/home/lib/envesntl/sas-init-functions: line 277: status: command not found
/opt/sas/viya/home/lib/envesntl/sas-init-functions: line 277: status: command not found
/opt/sas/viya/home/lib/envesntl/sas-init-functions: line 277: status: command not found
  sas-viya-vault-default                             down       N/A                 N/A     N/A
/opt/sas/viya/home/lib/envesntl/sas-init-functions: line 277: status: command not found
  sas-viya-alert-track-default                       up         10.36.4.126           0     762
/opt/sas/viya/home/lib/envesntl/sas-init-functions: line 277: status: command not found
  sas-viya-ops-agent-default                         up         10.36.4.126           0    8853
/opt/sas/viya/home/lib/envesntl/sas-init-functions: line 277: status: command not found
  sas-viya-watch-log-default                         up         10.36.4.126           0    1124
/opt/sas/viya/home/lib/envesntl/sas-init-functions: line 277: status: command not found
  sas-viya-backup-agent-default                      up         10.36.4.126       37179    1064