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

Encountering passwordless SSH error and nmmcrcluster error since mid-Nov #18

Open
tommyk-enablement opened this issue Dec 13, 2023 · 1 comment

Comments

@tommyk-enablement
Copy link

This is happening intermittently.
We have two teams using the tile 1.5.0. We are now testing in 1.6.0 to see if it occurs
We have two teams using the file. We have observed the passwordless SSH in existing workspaces (I will use unique cluster prefix to try to reduce the occurrence of the problem.
We observed the nmmcrcluster error on new workspaces.
We started seeing these in mid-Nov in the SYD1 and SYD2 region with the workspace residing in LON.

Let me know if you want access to the workspaces.

Usually we can get around it by destroying the resources and trying against. Sometimes the failures happen for a few hours until it eventually works

Attached the logs from the passwordless latest occurrences and the mmcrcluster error. The file name will indicate the error type.

@tommyk-enablement
Copy link
Author

tommyk-enablement commented Dec 13, 2023

mmcrcluster-error.txt
successful-deploy-did-not-see-passwordless-ssh-error.txt
passwordless-ssh-error.txt

Included 3 log files.
mmccluster-error is showing the error when were tried to create new workspace and encountering the error.
passwordless-ssh-error.txt is from a workspace that has been running for months and started seeing the error intermittently but eventually works again. You can compare it to the file: successful-deploy-did-not-see-passwordless-ssh-error.txt

Note: I removed the passwords from the files.

Screenshots of the workspace can be made available.
Essentially we are using min and max symphony worker of 5 with scale enabled with 3. Size of the nodes don't seem to matter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant