There is a discussion about how to get systems configured for Outbound Connection to reconnect when in a disconnected state. It is mentioned that the agents should try to connect by themselves unless they are stopped. One user had more success restarting just the monitor service. Another user mentions a new version (9.0.0.1680) that should fix outbound communication issues, with a link provided for the download.
Read the entire ‘How to Reconnect Systems Configured for Outbound Connection on ControlUp?’ thread below:
How do I get my systems that are configured for Outbound connection to reconnect when they are in a disconnected state?
I assume they are attempting but are running into one of the issues described here.
Check one of the disconnected machines. I suspect you’ll see they are trying to reconnect.
But unless the agent is stopped. They should try to connect by themselves. See here.
I had restarted the monitor servers this morning hoping that would resolve things, but it didn’t. I saw something about restarting agents, and that didn’t fix anything. Out of desperation, I restarted just the monitor service on the broken site and now many more have connected.
I thought they all were connected for a moment because it says none listed as disconnected. My number of connected agents is dropping again…
That’s probably it Dennis. Going to take a bit to get things upgraded…sigh. Wish I had remembered seeing that post before upgrading.
Hi @member
We have a released a new version (9.0.0.1680) that should fix all major outbound communication issues. You can find the version here
https://controlup.sharefile.com/share/view/s6c9357d36a3a4dd58d842d8f52355166
Would be great to get some feedback on this
Continue reading and comment on the thread ‘How to Reconnect Systems Configured for Outbound Connection on ControlUp?’. Not a member? Join Here!
Categories: All Archives, ControlUp for VDI