A pod’s desired state is to get to a running state with a Ready of 1/1. If you see a Ready
Status of 0/1 or see several Restarts for the pod, then you may need to investigate further.
The kubectl log command can be used to get more information on what the container/pod
is doing. Pod onedb-sever-0 hasn’t moved into a running state yet and we want to dig deeper into
what is going on with this specific pod.
kubectl logs onedb-server-0
20:59:00 Peer node onedb1 has version 131077
20:59:00 RSS Server onedb1 - state is now connected
20:59:00 setting version information for onedb1 131077
2022-01-08 20:59:03 LICENSING: <Information> Reacquire licenses: current allocation != expected count
2022-01-08 20:59:03 LICENSING: <Information> Processing current Capability
2022-01-08 20:59:13 LICENSING: <Information> Reacquire licenses: current allocation != expected count
2022-01-08 20:59:13 LICENSING: <Information> Processing current Capability
20:59:13 HDR TIMEOUT - log buffers being sent to onedb1
20:59:13 Error receiving a buffer from RSS onedb1 - shutting down
20:59:14 RSS Server onedb1 - state is now disconnected
20:59:14 RSS onedb1 deleted
2022-01-08 20:59:23 LICENSING: <Information> Reacquire licenses: current allocation != expected count
2022-01-08 20:59:23 LICENSING: <Information> Processing current Capability
