Cannot log in to the web client

You get an error when you try to log in to the Cloud Pak for Data web client.

Symptoms

When you try to log in to the web client, you see an error message.

Causes

If the web client displays a 502 Bad Gateway error message, you have too many cookies, your web browser might truncate requests, which causes errors.
If the web client displays a Your request cannot be processed. One or more required services are not running. error message, some required pods are not running.

Resolving the problem

For the 502 Bad Gateway error message, either remove large cookies or sign in to the web client using a private Firefox window or an incognito Chrome window. See Websites don't load - troubleshoot and fix error messages (Mozilla Firefox) or Browse in private (Google Chrome) for details.
For a Your request cannot be processed. One or more required services are not running. error message, the cluster administrator can verify the status of the following pods:
ibm-nginx pods
1. Check the status of the ibm-nginx pods:
```
oc get pods -n ${PROJECT_CPD_INST_OPERANDS} -l component=ibm-nginx
```
2. If a pod is not Running, check the ibm-nginx pod logs:
```
oc logs <nginx-pod-name> -n ${PROJECT_CPD_INST_OPERANDS}
```
  Replace <nginx-pod-name> with the name of the pod.
usermgmt pods
1. Check the status of the pods:
```
oc get pods -n ${PROJECT_CPD_INST_OPERANDS} -l component=usermgmt
```
2. If the pods are not Running, restart the pods:
```
oc delete pod -n ${PROJECT_CPD_INST_OPERANDS} -l component=usermgmt
```
zen-metastore-edb pods
1. Check the status of the cluster:
```
oc get cluster.postgresql.k8s.enterprisedb.io zen-metastore-edb -n ${PROJECT_CPD_INST_OPERANDS}
```
  Verify the status of the cluster, which should say Cluster in healthy state as shown in the following example.
```
NAME               AGE  INSTANCES  READY  STATUS                    PRIMARY
zen-metastore-edb  17h  2          2      Cluster in healthy state  zen-metastore-edb-1
```
2. If the status is not Cluster in healthy state, check the status of the pods.
```
oc get pods -l k8s.enterprisedb.io/cluster=zen-metastore-edb \
-n ${PROJECT_CPD_INST_OPERANDS}
```
  The command returns information with the following format:
```
NAME                 READY  STATUS            RESTARTS  AGE 
zen-metastore-edb-1  0/1    CrashLoopBackOff  0         66s 
zen-metastore-edb-2  1/1    Running           0         7d2h
```
3. If the problem is with one of the replicas, delete the replica and the persistent volume claim associated with the pod.
  Important: Do not delete the primary pod. Deleting the primary pod might result in data loss or make the system unrecoverable.
  For example, if the problem is with the zen-metastore-edb-2 pod, run:
```
oc delete pod/zen-metastore-edb-2 pvc/zen-metastore-edb-2 pod \
-n ${PROJECT_CPD_INST_OPERANDS} 
```
zen-core
1. Check the status of the pods:
```
oc get pods -n ${PROJECT_CPD_INST_OPERANDS} -l component=zen-core
```
2. If the pods are not Running, restart the pods:
```
oc delete pod -n ${PROJECT_CPD_INST_OPERANDS} -l component=zen-core
```
zen-core-api
1. Check the status of the pods:
```
oc get pods -n ${PROJECT_CPD_INST_OPERANDS} -l component=zen-core-api
```
2. If the pods are not Running, restart the pods:
```
oc delete pod -n ${PROJECT_CPD_INST_OPERANDS} -l component=zen-core-api
```