Can you share the full log while added the host ? -Wei
On Monday, 27 March 2023, Sanjay Kumar <sslinuxp...@gmail.com> wrote: > Hi All, > > We have setup the lab acs 4.18 with Rocky linux 9 and it was running but > after a day we faced the issue. is there any OS dependencies with 4.18? > > > > Could not add host at [http://10.40.40.71] with zone [1], pod [1] and > cluster [1] due to: [ can't setup agent, due to > com.cloud.utils.exception.CloudRuntimeException: Failed to setup keystore > on the KVM host: 10.40.40.71 - Failed to setup keystore on the KVM host: > 10.40.40.71]. > > > 2023-03-27 10:09:11,382 DEBUG [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-3383eeb3) (logid:c03fe0a7) Detected management > node left, id:2, nodeIP:10.40.40.23 > 2023-03-27 10:09:11,382 INFO [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-3383eeb3) (logid:c03fe0a7) Trying to connect to > 10.40.40.23 > 2023-03-27 10:09:11,383 INFO [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-3383eeb3) (logid:c03fe0a7) Management node 2 is > detected inactive by timestamp but is pingable > 2023-03-27 10:09:12,882 DEBUG [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-ee783d0b) (logid:87ac62d2) Detected management > node left, id:2, nodeIP:10.40.40.23 > 2023-03-27 10:09:12,882 INFO [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-ee783d0b) (logid:87ac62d2) Trying to connect to > 10.40.40.23 > 2023-03-27 10:09:12,882 INFO [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-ee783d0b) (logid:87ac62d2) Management node 2 is > detected inactive by timestamp but is pingable > 2023-03-27 10:09:14,382 DEBUG [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-1f50e525) (logid:a4ef06ad) Detected management > node left, id:2, nodeIP:10.40.40.23 > 2023-03-27 10:09:14,383 INFO [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-1f50e525) (logid:a4ef06ad) Trying to connect to > 10.40.40.23 > 2023-03-27 10:09:14,383 INFO [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-1f50e525) (logid:a4ef06ad) Management node 2 is > detected inactive by timestamp but is pingable > 2023-03-27 10:09:15,122 DEBUG [o.a.c.h.HAManagerImpl] > (BackgroundTaskPollManager-6:ctx-b26dd505) (logid:66b6c0db) HA health > check > task is running... > [root@ASCLDACS01 ~]# tail > /var/log/cloudstack/management/management-server.log > 2023-03-27 10:09:14,382 DEBUG [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-1f50e525) (logid:a4ef06ad) Detected management > node left, id:2, nodeIP:10.40.40.23 > 2023-03-27 10:09:14,383 INFO [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-1f50e525) (logid:a4ef06ad) Trying to connect to > 10.40.40.23 > 2023-03-27 10:09:14,383 INFO [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-1f50e525) (logid:a4ef06ad) Management node 2 is > detected inactive by timestamp but is pingable > 2023-03-27 10:09:15,122 DEBUG [o.a.c.h.HAManagerImpl] > (BackgroundTaskPollManager-6:ctx-b26dd505) (logid:66b6c0db) HA health > check > task is running... > 2023-03-27 10:09:15,881 DEBUG [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-b3ca8d68) (logid:50c9cf85) Detected management > node left, id:2, nodeIP:10.40.40.23 > 2023-03-27 10:09:15,881 INFO [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-b3ca8d68) (logid:50c9cf85) Trying to connect to > 10.40.40.23 > 2023-03-27 10:09:15,882 INFO [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-b3ca8d68) (logid:50c9cf85) Management node 2 is > detected inactive by timestamp but is pingable > 2023-03-27 10:09:17,382 DEBUG [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-2dbaab99) (logid:7f3a46b4) Detected management > node left, id:2, nodeIP:10.40.40.23 > 2023-03-27 10:09:17,382 INFO [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-2dbaab99) (logid:7f3a46b4) Trying to connect to > 10.40.40.23 > 2023-03-27 10:09:17,383 INFO [c.c.c.ClusterManagerImpl] > (Cluster-Heartbeat-1:ctx-2dbaab99) (logid:7f3a46b4) Management node 2 is > detected inactive by timestamp but is pingable > > > Any help you can give would be greatly appreciated > > > > With Regards, > > Sanjay >
