Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pkg/debug: use correct libexecdir #4079

Merged
merged 1 commit into from
Jul 11, 2024

Conversation

christoph-zededa
Copy link
Contributor

this fixes that sshd-session cannot be found and therefore

  1. debug container is not started
  2. ssh server is not started

this fixes that sshd-session cannot be found and therefore
1. debug container is not started
2. ssh server is not started

Signed-off-by: Christoph Ostarek <christoph@zededa.com>
@christoph-zededa christoph-zededa requested a review from rene July 11, 2024 12:49
@github-actions github-actions bot requested a review from eriknordmark July 11, 2024 12:49
@christoph-zededa christoph-zededa added the bug Something isn't working label Jul 11, 2024
@eriknordmark eriknordmark added the stable Should be backported to stable release(s) label Jul 11, 2024
Copy link
Contributor

@rene rene left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@christoph-zededa
Copy link
Contributor Author

@christoph-zededa
Copy link
Contributor Author

Also I see:

 {"status":"Pulling from library/redis","id":"7"}
        {"errorDetail":{"message":"toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit"},"error":"toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit"}

@eriknordmark eriknordmark merged commit 2b8f196 into lf-edge:master Jul 11, 2024
34 of 52 checks passed
@milan-zededa
Copy link
Contributor

milan-zededa commented Jul 11, 2024

collect-info failed: https://github.com/lf-edge/eve/actions/runs/9893585532/job/27329096007?pr=4079#step:3:2497

reason I think is that lf-edge/eden#987 is not merged

still it does not explain why ssh fails: https://github.com/lf-edge/eve/actions/runs/9893585532/job/27329096007?pr=4079#step:3:2308 ...

The problem is not port 7777 collision, we do not have it in these buildjet runners.
Instead, the Linux kernel crashed which brought the qemu down. This happens from time to time so just ignore it:

        rebooted with reason Reboot reason - kernel crash (no kdump) - at 2024-07-11T15:33:19.66283075Z at 2024-07-11 15:33:19.66283075 +0000 UTC/n    testProc.go:84: time: 2024-07-11T15:34:17.937499703Z out: projects.ProcInfoFunc done with return: abnormal reboot: Reboot reason - kernel crash (no kdump) - at 2024-07-11T15:33:19.66283075Z

But we should investigate why smoke tests are failing (preferably before merging going forward..). It could be related to these ssh changes because we expect this to appear in the logs after sshing into EVE: https://github.com/lf-edge/eden/blob/master/tests/lim/testdata/log_test.txt#L6-L8
The test seems to timeout after waiting for the log, but I have not investigated this further...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stable Should be backported to stable release(s)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants