I am setting up an environment, where I have 2 VAs in a cluster which are both in connected state. Also, they have performed an upgrade after they reach connnection.
But when performing the AD connector test connection, I receive an error that says Timeout waiting for response to message 1 from client, alterning # between 0 and 1.
On AD, there is only one ip set up. On VA, NC command shows that connection to port 389 is opened. No IQS configured yet.
Can it be that VA does not reach Tenant message queue, or that VA does not respond? Thanks.
These are really difficult to troubleshoot. There are so many systems involved. Test connection call gets triggered from identitynow cloud → goes to VA → then AD and response comes back in same path.
Instead of troubleshooting, just increase timeout and see if that works.
Sorry I am a little lost, these attributes can be updated in source via API? I tried to add the healthCheckTimeout attribute, updates sucessfull but is not reflected on json response.
This is common mistake because postman collection does no have that header pre-checked.
Regarding timing out before 180 seconds, there is limit on that value and if you set beyond that limit it would not be considered. Check with support on that threshold value if you want.
Regarding actual problem, it is time to check network latency instead of increasing timeout considering you tried that option. Start from ccg trace logs for AD connector.
Hi Chirag, finally get it worked. I think it was a problem with client VA (azure image). We realized that although VA connection test passed, ccg service was with some failure, as ccg version was not being displayed on VA details.
Trying-error, we deleted ccg directory and restarted VA. After that, ccg was recreated and all begin to work. As I do not know the reason, I should not recommedn to do it, as Sailpoint encourage to not alter VA.
