mirror of
https://github.com/PegaProx/project-pegaprox.git
synced 2026-04-25 18:15:50 +03:00
[GH-ISSUE #29] 🐞 Bug: Random connection problems via SSH #22
Labels
No labels
Approved
Q2-3 2026 Development
bug
documentation
enhancement
help wanted
invalid
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/project-pegaprox-PegaProx#22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @PhiGi87 on GitHub (Feb 1, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/29
Hi,
we currently have 15 hosts in the cluster we're using to test PegaProx. We frequently receive the following message during updates (the SMBIOS Auto-Configurator Node Status has the same problem with a different message):
[11:06:42] ✗ ERROR on xxx09: Update failed: SSH connection failed to root@XX.XX.XX.XX:22 - Check if password authentication is enabled on the node or configure an SSH key / SSH connection failed - Check if password authentication is enabled on the node or configure an SSH key
However, this isn't actually the case, and if I restart, it works. This happens sporadically and completely randomly, sometimes with one, sometimes with two or three hosts. It's usually not the same hosts in succession.
Best regards
@MrMasterbay commented on GitHub (Feb 1, 2026):
Hi @PhiGi87 ,
thank you for the report. We identified the issue here actually already and working on a fix.
Best regards,
Nico
@MrMasterbay commented on GitHub (Feb 1, 2026):
Hi @PhiGi87 ,
please check if its now working with the new update. This should have a better SSH handling.
Best regards,
Nico