derailed / k9s

🐶 Kubernetes CLI To Manage Your Clusters In Style!
https://k9scli.io
Apache License 2.0
26.42k stars 1.65k forks source link

Log entry is missing #1510

Open varac opened 2 years ago

varac commented 2 years ago




Describe the bug When I look at a pod's log in k9s, I don't see every line. Looking with kubectl shows the missing line.

To Reproduce

Steps to reproduce the behavior:

  1. Show the logs of a failing Nextcloud cron job installed by the NC helm chart (i.e. one where NC is set to use system cron)
  2. Show the same pod's logs with kubectl
  3. Compare the difference, kubectl shows the error while k9s doesn't

Expected behavior Both should show exactly the same lines.

Screenshots

k9s:

image

kubectl:

❯ kc -n stackspin-apps logs nc-nextcloud-cron-27468605-g5flj
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    77  100    77    0     0     15      0  0:00:05  0:00:05 --:--:--    17
{"data":{"message":"Backgroundjobs are using system cron!"},"status":"error"}%     

Versions (please complete the following information):

I tried to find out if this is a duplicate of i.e. #1483 but I was unsure about it, feel free to close it if it is.

varac commented 2 years ago

Btw, this is critical, because if my colleague would not have used kubectl instead of k9s, we would never have noticed ...

kinoute commented 1 year ago

No news about this? We are experiencing the same here.

dod38fr commented 1 year ago

Same problem here. We often have to fallback on kubectl logs command to debug

trexx commented 1 month ago

I've also just experienced this. It seems to be when the log updates too quickly, some updates maybe missed. A guess maybe that a buffer might be too small for the amount of updates that need to be displayed.