Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
cml-runner times out when trying to check status of spawned instance
See original GitHub issueHey everyone!
We’ve been using cml for a bout a month now to deploy ec2 runners and run tests on them. We have run into a weird problem today where the deploy runners command times out because it cannot talk to the ec2 instances. I’m attaching the logs below.
As far as I can tell the runners are getting deployed and have public ipv4 addresses assigned to them. However, when I try to connect using EC2 connect i get this error:
Does someone know what could be going on here? Has something been updated on the cml side that we should know about? Any help would be greatly appreciated!
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@thatGreekGuy96 I can confirm that the issue should be now fixed. Could you please confirm it? Thank you for your support 🙏
@thatGreekGuy96 we have identified the potential issue. hopefully it will be fixed within the next hour