Thanks Angfe for your tips..
1. Logs say nothing: After trying activation (in Gws):
[root@P03TULIPAN ~]# impctl show log | grep ERROR[root@P03TULIPAN ~]# impctl show log | grep "Data Sync"[root@P03TULIPAN ~]#
Running first command with option
-i, I see some errors, but they are old. I think it was while I was restarting GWs services.
root@P03TULIPAN ~]# impctl show log | grep -i error...
root@P03TULIPAN ~]# impctl show log | grep -i errorimpctl_legacy --no-trace gateway start --from-watchdog WARNING gateway_state: no reply from "http_get_trust --gw --timeout=10 /isalive". Error message: "04/09/2022 22:53:18.092322 [log_warning] /mnt/workspace/ci-dam_v14.7_P31-pipeline-dam/Gateway/src/argus/network/TcpConnection.cpp:424 Failed to connect to 10.3.3.99:443 error_num : 111 poll err :1impctl_legacy --no-trace gateway start --from-watchdog WARNING 04/09/2022 22:53:18.092437 [log_error] /mnt/workspace/ci-dam_v14.7_P31-pipeline-dam/Gateway/src/argus/network/SslConnection.cpp:986 Cannot connect. Error is 5impctl_legacy --no-trace gateway start --from-watchdog WARNING 04/09/2022 22:53:18.092464 [log_error] /mnt/workspace/ci-dam_v14.7_P31-pipeline-dam/Gateway/src/argus/baseutil/HttpFileClient.cpp:360 Cannot send/receive request/response. Error number is:1 Retried 1 times Max retries is 1impctl_legacy --no-trace gateway start --from-watchdog WARNING 04/09/2022 22:53:18.092495 [log_error] /mnt/workspace/ci-dam_v14.7_P31-pipeline-dam/Gateway/src/argus/gwlib/TrustUtils.cpp:1220 platformGetAction - failed to perform Http Get action to the Gateway on URL- /isalive.".""2.About automation of GW registration, I'm sorry, but I don't see what the benefit should be (automating it)
Do you think running those commands manually, would be a good idea ?
Finally, I could downgrade to v14.5, however the appliances are in a collocation, and we need to get authorized for access.
This would be the third time asking for access to downgrade. My only concern is that nothing guarantees tthat it will work.
I initially installed v14.8 recommended by support. Then updated to v14.9, It didn't worked. After that, downgrade to v14.7 (current version). Same error.
Now, another downgrade to 14.5..
Best regards
------------------------------
Elfego
------------------------------
Original Message:
Sent: 09-07-2022 07:29
From: Angfe Landagan
Subject: Cluster activation problem
Hello,
From the documentation, i would highly recommend to have the version to 14.5 after checking all the needed licenses (MX and GW).
Couple of logs to look for at least, depending on your preference;
1.) From the cli;
impctl show log | grep ERROR
impctl show log | grep "Data Sync"
2. Or automate the gateway registration;
Automating Cluster Creation
In order to automatically set up a Gateway and register it to a Cluster, add following lines to the automatic FTL script, after the FTL line:
impctl stop --teardown --transient
impctl gateway unregister
impctl gateway cluster config --cluster-port=<port> --cluster-interface=eth0
impctl platform config --staging-asset-tag=<Gateway model from auto-ftl>
impctl sniffing config --delete-blocking-interface
impctl gateway sniffing config --delete-blocking-interface
impctl gateway register
impctl service start --prepare --transient gateway
Thanks,
A