Viewing and Gathering Component Logs
If a component does not work properly or cannot start, use the commands in the table to determine the root cause:
Command | Description |
---|---|
kubectl -n NAMESPACE get pods -o wide | Useful for determining correlation between failures and a particular Kubernetes node. |
kubectl -n NAMESPACE describe pod PODNAME | Useful for displaying events. By default, Kubernetes only shows events from the last 30 minutes. |
kubectl -n NAMESPACE get events | Displays all events for all resources in the specified namespace. |
kubectl -n NAMESPACE logs PODNAME CONTAINERNAME | Displays logs for a container inside a Pod. |
kubectl -n NAMESPACE logs PODNAME CONTAINERNAME --previous | Displays logs for the previously exited container. Useful if a Pod's behavior is unstable. |
kubectl -n NAMESPACE logs PODNAME CONTAINERNAME --follow | Streams logs in real time. |
kubectl -n NAMESPACE logs -l stellart=worker --follow | Streams logs for BSS workers. |
kubectl -n NAMESPACE logs --all-containers=true -l app=bss --follow --max-log-requests=50 | Streams logs for all containers of the BSS component. |
helm -n NAMESPACE list | Lists installed charts and shows their versions. |
where:
-
NAMESPACE is the namespace of your CloudBlue Commerce installation.
-
PODNAME is the name of the Pod that you need to check.
-
CONTAINERNAME is the name of the container that you need to check.