After Update to 17.1.7 Gateway Status was Pending on both Cluster Nodes

[RainerR]

Hi.

I've updated both nodes of my HA cluster to from version 17.1.6 to version 17.1.7.

After checking the Dashboard I saw that my Gateway status was unknown on both nodes.
I checked the apinger service and it was down on both nodes and I was unable to start the service.
In the service log there was the messages "apinger: No usable targets found, exiting".

So first I've done a reboot of both nodes but nothing changed.
I was unable to start the apinger service.

At this point I had a weird idea.
I went to System-Gateways-All and select the "edit gateway" action.
I don't changed a setting but I've saved by using the save button.
After applying the setting (strange because I didn't changed anything) the pinger service starts and my Gateway status in the Dashboard changed from unknown to online. :-)

I post this here for people who run into the same issue.

Best regards,
Rainer.

[franco]

Hi Rainer,

Thanks for posting this. It seemed that the newer gateway code is more strict about the gateway monitoring IP, I suspect something changed there while saving the gateway configuration (you can check the config.xml differences from System: Configuration: History)?


Cheers,
Franco