1. Identify which container went for restart using the oc describe pod command.
  2. Issue the corresponding command: kubectl logs <pod name> -p -c <container name>-- timestamps


Example:
 
[jdoe@cli-blr-2 ~]$ kubectl logs sbc-sandbox-rcoocp1-cs-c998469cd-pctg9 -p -c oamproxy-container --timestamps
2024-02-20T11:27:28.763088284Z eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450
2024-02-20T11:27:28.763088284Z inet 10.234.56.789 netmask 255.255.254.0 broadcast 10.234.56.255
2024-02-20T11:27:28.763088284Z inet6 fe80::b0c3:1fff:feff:e0d0 prefixlen 64 scopeid 0x20<link>
2024-02-20T11:27:28.763088284Z ether 0a:58:0a:e7:31:b6 txqueuelen 0 (Ethernet)
2024-02-20T11:27:28.763088284Z RX packets 7 bytes 726 (726.0 B)
2024-02-20T11:27:28.763088284Z RX errors 0 dropped 0 overruns 0 frame 0
2024-02-20T11:27:28.763088284Z TX packets 6 bytes 516 (516.0 B)
2024-02-20T11:27:28.763088284Z TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
2024-02-20T11:27:28.763088284Z
2024-02-20T11:27:28.779666369Z 2024-02-20 11:27:28,779364713 UTC startOamProxy.sh eth0 interface present
2024-02-20T11:27:31.210882085Z 2024-02-20 11:27:31,210594405 UTC startOamProxy.sh setting POD_IP to 10.234.56.789
2024-02-20T11:27:31.312027804Z no crontab for root
2024-02-20T11:27:31.319364244Z Starting periodic command scheduler: cron.
2024-02-20T11:28:27.209719954Z 2024-02-20 11:28:27,209336474 UTC startOamProxy exiting..
[jdoe@cli-blr-2 ~]$


  • No labels