-
Notifications
You must be signed in to change notification settings - Fork 268
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
Windows Service fails due to timeout issue. #1467
Comments
I'm still seeing this fail on v1.21.3-rc1+rke2r2, but it's no longer a timeout. Details below: Windows Version:
Cluster Info: Windows Node Steps:
Results from Above:
Also noted there were no rke2 Event Logs. So ran:
Now the Event Logs appears to show the correct information, but then stop after running containerd.
Removed some of the logs for brevity, but that last line is the last event log for rke2. It tries to restart itself and always just ends up with the same result in the logs. |
I see this working following the steps in the docs exactly. The problem I was having was that my PATH in my environment was not set:
The docs are correct and this is working using v1.21.3-rc4+rke2r2. |
Environmental Info:
RKE2 Version:
rke2.exe version v1.21.3+rke2r1 (2ed0b0d)
go version go1.16.6b7
Node(s) CPU architecture, OS, and Version:
Cluster Configuration:
1 server
1 windows node
Describe the bug:
Running the agent as a windows service errors with a timeout issue, why executing the agent not as a service works.
Steps To Reproduce:
Install RKE2 for Windows and try to run the agent as a windows service.
Expected behavior:
rke2 starts up as a windows service and joins a cluster.
Actual behavior:
rke2 starts then fails.
Additional context / logs:
The text was updated successfully, but these errors were encountered: