question

VivekBezavada-3666 avatar image
0 Votes"
VivekBezavada-3666 asked karishmatiwari-msft edited

I am getting Timeout error while connecting to Cyclecloud

It seems that nodes are unable to communicate back to the CycleCloud application server. I am seeing this timeout error "Timeout awaiting system boot-up"

[Note: As we migrate from MSDN, this question has been posted by an Azure Cloud Engineer as a frequently asked question]

azure-cyclecloud
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

karishmatiwari-msft avatar image
0 Votes"
karishmatiwari-msft answered

If the CycleCloud server and the cluster is in the same VNET, check the network security groups for the subnets in the VNET. Cluster nodes need to be able to reach the CycleCloud server at TCP 9443 and 5672. In the other direction, Azure CycleCloud needs to be able to reach ganglia (TCP 8652) and SSH (TCP 22) ports of the cluster for system and job monitoring.

You may need to add a public IP address.

If the error message indicates a return proxy, check the return proxy settings.

After updating network or proxy settings, you can test connectivity by SSHing into the node as the cyclecloud user and using curl -k {https://error-message-url}.

After validating that network connectivity is fixed, you will need to terminate and restart the node.

Source: Azure Documentation


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.