+ CONSUL_BIND= + [ -n ] + CONSUL_CLIENT= + [ -n ] + CONSUL_DATA_DIR=/consul/data + CONSUL_CONFIG_DIR=/consul/config + [ -n ] + [ a = - ] + [ agent = agent ] + shift + set -- consul agent -data-dir=/consul/data -config-dir=/consul/config -bootstrap-expect=3 -enable-script-checks -retry-join=onap-consul-server-0.consul-server -retry-join=onap-consul-server-1.consul-server -retry-join=onap-consul-server-2.consul-server -client=0.0.0.0 -server -ui + [ consul = consul ] + stat -c %u /consul/data + id -u consul + [ 100 != 100 ] + stat -c %u /consul/config + id -u consul + [ 100 != 100 ] + [ ! -z ] + exec consul agent -data-dir=/consul/data -config-dir=/consul/config -bootstrap-expect=3 -enable-script-checks -retry-join=onap-consul-server-0.consul-server -retry-join=onap-consul-server-1.consul-server -retry-join=onap-consul-server-2.consul-server -client=0.0.0.0 -server -ui bootstrap_expect > 0: expecting 3 servers ==> Starting Consul agent... ==> Consul agent running! Version: 'v1.0.6' Node ID: '558a2720-cbad-3eb5-36f0-d28d9ab773ec' Node name: 'onap-consul-server-1' Datacenter: 'dc1' (Segment: '') Server: true (Bootstrap: false) Client Addr: [0.0.0.0] (HTTP: 8500, HTTPS: -1, DNS: 8600) Cluster Addr: 10.233.75.121 (LAN: 8301, WAN: 8302) Encrypt: Gossip: false, TLS-Outgoing: false, TLS-Incoming: false ==> Log data will now stream in as it occurs: 2022/03/05 00:55:53 [INFO] raft: Initial configuration (index=0): [] 2022/03/05 00:55:53 [INFO] raft: Node at 10.233.75.121:8300 [Follower] entering Follower state (Leader: "") 2022/03/05 00:55:53 [INFO] serf: EventMemberJoin: onap-consul-server-1.dc1 10.233.75.121 2022/03/05 00:55:53 [INFO] serf: EventMemberJoin: onap-consul-server-1 10.233.75.121 2022/03/05 00:55:53 [INFO] agent: Started DNS server 0.0.0.0:8600 (udp) 2022/03/05 00:55:53 [INFO] consul: Handled member-join event for server "onap-consul-server-1.dc1" in area "wan" 2022/03/05 00:55:53 [INFO] agent: Started DNS server 0.0.0.0:8600 (tcp) 2022/03/05 00:55:53 [INFO] agent: Started HTTP server on [::]:8500 (tcp) 2022/03/05 00:55:53 [INFO] agent: started state syncer 2022/03/05 00:55:53 [INFO] consul: Adding LAN server onap-consul-server-1 (Addr: tcp/10.233.75.121:8300) (DC: dc1) 2022/03/05 00:55:53 [INFO] agent: Retry join LAN is supported for: aliyun aws azure digitalocean gce os scaleway softlayer 2022/03/05 00:55:53 [INFO] agent: Joining LAN cluster... 2022/03/05 00:55:53 [INFO] agent: (LAN) joining: [onap-consul-server-0.consul-server onap-consul-server-1.consul-server onap-consul-server-2.consul-server] 2022/03/05 00:55:55 [INFO] serf: EventMemberJoin: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 00:55:55 [INFO] serf: EventMemberJoin: onap-consul-server-0 10.233.70.53 2022/03/05 00:55:55 [INFO] consul: Adding LAN server onap-consul-server-0 (Addr: tcp/10.233.70.53:8300) (DC: dc1) 2022/03/05 00:55:56 [INFO] serf: EventMemberJoin: onap-consul-server-0.dc1 10.233.70.53 2022/03/05 00:55:56 [INFO] consul: Handled member-join event for server "onap-consul-server-0.dc1" in area "wan" ==> Newer Consul version available: 1.11.4 (currently running: 1.0.6) 2022/03/05 00:55:57 [WARN] memberlist: Failed to resolve onap-consul-server-1.consul-server: lookup onap-consul-server-1.consul-server on 169.254.25.10:53: no such host 2022/03/05 00:55:59 [WARN] memberlist: Failed to resolve onap-consul-server-2.consul-server: lookup onap-consul-server-2.consul-server on 169.254.25.10:53: no such host 2022/03/05 00:55:59 [INFO] agent: (LAN) joined: 1 Err: 2022/03/05 00:55:59 [INFO] agent: Join LAN completed. Synced with 1 initial agents 2022/03/05 00:56:00 [ERR] agent: failed to sync remote state: No cluster leader 2022/03/05 00:56:02 [WARN] raft: no known peers, aborting election 2022/03/05 00:56:24 [ERR] agent: Coordinate update error: No cluster leader 2022/03/05 00:56:31 [ERR] agent: failed to sync remote state: No cluster leader 2022/03/05 00:56:43 [INFO] serf: EventMemberJoin: onap-consul-server-2 10.233.72.246 2022/03/05 00:56:43 [INFO] consul: Adding LAN server onap-consul-server-2 (Addr: tcp/10.233.72.246:8300) (DC: dc1) 2022/03/05 00:56:44 [INFO] consul: Existing Raft peers reported by onap-consul-server-2, disabling bootstrap mode 2022/03/05 00:56:44 [INFO] serf: EventMemberJoin: onap-consul-server-2.dc1 10.233.72.246 2022/03/05 00:56:44 [INFO] consul: Handled member-join event for server "onap-consul-server-2.dc1" in area "wan" 2022/03/05 00:56:48 [ERR] agent: Coordinate update error: No cluster leader 2022/03/05 00:56:50 [DEBUG] raft-net: 10.233.75.121:8300 accepted connection from: 10.233.72.246:54234 2022/03/05 00:56:50 [DEBUG] raft-net: 10.233.75.121:8300 accepted connection from: 10.233.72.246:54238 2022/03/05 00:56:51 [INFO] consul: New leader elected: onap-consul-server-2 2022/03/05 00:56:51 [WARN] raft: Failed to get previous log: 1 log not found (last: 0) 2022/03/05 00:56:54 [INFO] agent: Synced node info 2022/03/05 02:36:11 [ERR] memberlist: Failed fallback ping: read tcp 10.233.75.121:48986->10.233.77.119:8301: i/o timeout 2022/03/05 02:36:11 [INFO] memberlist: Suspect onap-consul-667578469f-fwd5j has failed, no acks received 2022/03/05 02:36:11 [INFO] memberlist: Marking onap-consul-667578469f-fwd5j as failed, suspect timeout reached (2 peer confirmations) 2022/03/05 02:36:11 [INFO] serf: EventMemberFailed: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 02:36:19 [INFO] serf: EventMemberJoin: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 02:36:23 [WARN] memberlist: Refuting a suspect message (from: onap-consul-667578469f-fwd5j) 2022/03/05 02:36:57 [ERR] memberlist: Failed fallback ping: read tcp 10.233.75.121:49602->10.233.77.119:8301: i/o timeout 2022/03/05 02:36:57 [INFO] memberlist: Suspect onap-consul-667578469f-fwd5j has failed, no acks received 2022/03/05 02:37:00 [ERR] memberlist: Failed fallback ping: read tcp 10.233.75.121:49632->10.233.77.119:8301: i/o timeout 2022/03/05 02:37:00 [INFO] memberlist: Suspect onap-consul-667578469f-fwd5j has failed, no acks received 2022/03/05 02:37:00 [INFO] serf: EventMemberFailed: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 02:37:07 [ERR] yamux: keepalive failed: i/o deadline reached 2022/03/05 02:37:07 [ERR] consul.rpc: multiplex conn accept failed: keepalive timeout from=10.233.77.119:49180 2022/03/05 02:37:10 [INFO] serf: EventMemberJoin: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 02:37:14 [ERR] memberlist: Failed fallback ping: read tcp 10.233.75.121:49854->10.233.77.119:8301: i/o timeout 2022/03/05 02:37:14 [INFO] memberlist: Suspect onap-consul-667578469f-fwd5j has failed, no acks received 2022/03/05 02:37:17 [ERR] memberlist: Failed fallback ping: read tcp 10.233.75.121:49904->10.233.77.119:8301: i/o timeout 2022/03/05 02:37:17 [INFO] memberlist: Suspect onap-consul-667578469f-fwd5j has failed, no acks received 2022/03/05 02:37:17 [INFO] memberlist: Marking onap-consul-667578469f-fwd5j as failed, suspect timeout reached (2 peer confirmations) 2022/03/05 02:37:17 [INFO] serf: EventMemberFailed: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 02:37:31 [INFO] serf: EventMemberJoin: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 02:37:42 [INFO] memberlist: Suspect onap-consul-667578469f-fwd5j has failed, no acks received 2022/03/05 02:37:46 [INFO] memberlist: Marking onap-consul-667578469f-fwd5j as failed, suspect timeout reached (2 peer confirmations) 2022/03/05 02:37:46 [INFO] serf: EventMemberFailed: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 02:37:48 [INFO] serf: EventMemberJoin: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 02:37:48 [ERR] memberlist: Failed fallback ping: write tcp 10.233.75.121:50316->10.233.77.119:8301: i/o timeout 2022/03/05 02:37:48 [INFO] memberlist: Suspect onap-consul-667578469f-fwd5j has failed, no acks received 2022/03/05 02:38:10 [ERR] memberlist: Failed fallback ping: read tcp 10.233.75.121:50796->10.233.77.119:8301: i/o timeout 2022/03/05 02:38:10 [INFO] memberlist: Suspect onap-consul-667578469f-fwd5j has failed, no acks received 2022/03/05 02:38:13 [ERR] memberlist: Failed fallback ping: read tcp 10.233.75.121:50844->10.233.77.119:8301: i/o timeout 2022/03/05 02:38:13 [INFO] memberlist: Suspect onap-consul-667578469f-fwd5j has failed, no acks received 2022/03/05 02:38:14 [INFO] memberlist: Marking onap-consul-667578469f-fwd5j as failed, suspect timeout reached (2 peer confirmations) 2022/03/05 02:38:14 [INFO] serf: EventMemberFailed: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 02:38:23 [INFO] serf: attempting reconnect to onap-consul-667578469f-fwd5j 10.233.77.119:8301 2022/03/05 02:39:03 [INFO] serf: attempting reconnect to onap-consul-667578469f-fwd5j 10.233.77.119:8301 2022/03/05 02:41:13 [INFO] serf: attempting reconnect to onap-consul-667578469f-fwd5j 10.233.77.119:8301 2022/03/05 02:42:23 [INFO] serf: attempting reconnect to onap-consul-667578469f-fwd5j 10.233.77.119:8301 2022/03/05 02:45:33 [INFO] serf: attempting reconnect to onap-consul-667578469f-fwd5j 10.233.77.119:8301 2022/03/05 02:47:43 [INFO] serf: attempting reconnect to onap-consul-667578469f-fwd5j 10.233.77.119:8301 2022/03/05 02:48:45 [INFO] serf: EventMemberJoin: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 03:32:48 [ERR] memberlist: Failed fallback ping: read tcp 10.233.75.121:60264->10.233.77.119:8301: i/o timeout 2022/03/05 03:32:48 [INFO] memberlist: Suspect onap-consul-667578469f-fwd5j has failed, no acks received 2022/03/05 03:32:51 [ERR] memberlist: Failed fallback ping: read tcp 10.233.75.121:60386->10.233.77.119:8301: i/o timeout 2022/03/05 03:32:51 [INFO] memberlist: Suspect onap-consul-667578469f-fwd5j has failed, no acks received 2022/03/05 03:32:51 [INFO] serf: EventMemberFailed: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 03:33:06 [ERR] yamux: keepalive failed: i/o deadline reached 2022/03/05 03:33:06 [ERR] consul.rpc: multiplex conn accept failed: keepalive timeout from=10.233.77.119:44198 2022/03/05 03:33:29 [ERR] memberlist: Failed fallback ping: write tcp 10.233.75.121:49222->10.233.72.246:8301: i/o timeout 2022/03/05 03:33:29 [INFO] memberlist: Suspect onap-consul-server-2 has failed, no acks received 2022/03/05 03:33:56 [INFO] serf: EventMemberJoin: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 03:35:57 [ERR] memberlist: Failed fallback ping: read tcp 10.233.75.121:38802->10.233.77.119:8301: i/o timeout 2022/03/05 03:35:57 [INFO] memberlist: Suspect onap-consul-667578469f-fwd5j has failed, no acks received 2022/03/05 03:36:00 [INFO] serf: EventMemberFailed: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 03:36:00 [ERR] memberlist: Failed fallback ping: read tcp 10.233.75.121:38900->10.233.77.119:8301: i/o timeout 2022/03/05 03:36:00 [INFO] memberlist: Suspect onap-consul-667578469f-fwd5j has failed, no acks received 2022/03/05 03:36:29 [ERR] yamux: keepalive failed: i/o deadline reached 2022/03/05 03:36:29 [ERR] consul.rpc: multiplex conn accept failed: keepalive timeout from=10.233.77.119:54304 2022/03/05 03:36:53 [INFO] serf: EventMemberJoin: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 03:36:53 [WARN] memberlist: Refuting a suspect message (from: onap-consul-667578469f-fwd5j) 2022/03/05 03:37:18 [ERR] memberlist: Failed fallback ping: read tcp 10.233.75.121:41816->10.233.77.119:8301: i/o timeout 2022/03/05 03:37:18 [INFO] memberlist: Suspect onap-consul-667578469f-fwd5j has failed, no acks received 2022/03/05 03:37:19 [INFO] memberlist: Marking onap-consul-667578469f-fwd5j as failed, suspect timeout reached (2 peer confirmations) 2022/03/05 03:37:19 [INFO] serf: EventMemberFailed: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 03:38:06 [INFO] serf: EventMemberJoin: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 03:40:34 [ERR] memberlist: Failed fallback ping: read tcp 10.233.75.121:49032->10.233.77.119:8301: i/o timeout 2022/03/05 03:40:34 [INFO] memberlist: Suspect onap-consul-667578469f-fwd5j has failed, no acks received 2022/03/05 03:40:38 [ERR] memberlist: Failed fallback ping: read tcp 10.233.75.121:49176->10.233.77.119:8301: i/o timeout 2022/03/05 03:40:38 [INFO] memberlist: Suspect onap-consul-667578469f-fwd5j has failed, no acks received 2022/03/05 03:40:38 [INFO] memberlist: Marking onap-consul-667578469f-fwd5j as failed, suspect timeout reached (2 peer confirmations) 2022/03/05 03:40:38 [INFO] serf: EventMemberFailed: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 03:41:24 [INFO] serf: attempting reconnect to onap-consul-667578469f-fwd5j 10.233.77.119:8301 2022/03/05 03:41:43 [ERR] yamux: keepalive failed: i/o deadline reached 2022/03/05 03:41:43 [ERR] consul.rpc: multiplex conn accept failed: keepalive timeout from=10.233.77.119:32920 2022/03/05 03:42:15 [INFO] serf: EventMemberJoin: onap-consul-667578469f-fwd5j 10.233.77.119 2022/03/05 04:17:05 [ERR] memberlist: Failed fallback ping: write tcp 10.233.75.121:51466->10.233.72.246:8301: i/o timeout 2022/03/05 04:17:05 [INFO] memberlist: Suspect onap-consul-server-2 has failed, no acks received 2022/03/05 04:17:14 [ERR] memberlist: Failed fallback ping: write tcp 10.233.75.121:34426->10.233.70.53:8301: i/o timeout 2022/03/05 04:17:14 [INFO] memberlist: Suspect onap-consul-server-0 has failed, no acks received 2022/03/05 04:17:17 [ERR] memberlist: Failed fallback ping: read tcp 10.233.75.121:51742->10.233.72.246:8301: i/o timeout 2022/03/05 04:17:17 [INFO] memberlist: Suspect onap-consul-server-2 has failed, no acks received 2022/03/05 04:18:32 [ERR] yamux: keepalive failed: i/o deadline reached 2022/03/05 04:18:32 [ERR] agent: failed to sync remote state: rpc error making call: EOF 2022/03/05 04:18:32 [ERR] http: Request GET /v1/catalog/service/config_binding_service, error: rpc error making call: EOF from=10.233.74.254:49944 2022/03/05 04:18:32 [ERR] yamux: keepalive failed: i/o deadline reached 2022/03/05 04:18:32 [ERR] consul.rpc: multiplex conn accept failed: keepalive timeout from=10.233.72.246:54184 2022/03/05 04:18:32 [INFO] memberlist: Marking onap-consul-server-0 as failed, suspect timeout reached (0 peer confirmations) 2022/03/05 04:18:32 [INFO] serf: EventMemberFailed: onap-consul-server-0 10.233.70.53 2022/03/05 04:18:32 [INFO] consul: Removing LAN server onap-consul-server-0 (Addr: tcp/10.233.70.53:8300) (DC: dc1) 2022/03/05 04:18:32 [INFO] memberlist: Marking onap-consul-server-2 as failed, suspect timeout reached (0 peer confirmations) 2022/03/05 04:18:32 [INFO] serf: EventMemberFailed: onap-consul-server-2 10.233.72.246 2022/03/05 04:18:32 [INFO] consul: Removing LAN server onap-consul-server-2 (Addr: tcp/10.233.72.246:8300) (DC: dc1) 2022/03/05 04:18:34 [ERR] memberlist: Failed fallback ping: write tcp 10.233.75.121:34604->10.233.72.246:8302: i/o timeout 2022/03/05 04:18:34 [INFO] memberlist: Suspect onap-consul-server-2.dc1 has failed, no acks received 2022/03/05 04:18:34 [INFO] serf: EventMemberJoin: onap-consul-server-2 10.233.72.246 2022/03/05 04:18:34 [DEBUG] raft-net: 10.233.75.121:8300 accepted connection from: 10.233.72.246:34408 2022/03/05 04:18:34 [WARN] memberlist: Refuting a suspect message (from: onap-consul-667578469f-fwd5j) 2022/03/05 04:18:34 [INFO] consul: Adding LAN server onap-consul-server-2 (Addr: tcp/10.233.72.246:8300) (DC: dc1) 2022/03/05 04:18:35 [DEBUG] raft-net: 10.233.75.121:8300 accepted connection from: 10.233.72.246:34758 2022/03/05 04:18:44 [INFO] memberlist: Suspect onap-consul-server-0 has failed, no acks received 2022/03/05 04:18:44 [DEBUG] raft-net: 10.233.75.121:8300 accepted connection from: 10.233.72.246:34892 2022/03/05 04:18:45 [ERR] memberlist: Failed fallback ping: write tcp 10.233.75.121:48204->10.233.70.53:8302: i/o timeout 2022/03/05 04:18:45 [INFO] memberlist: Suspect onap-consul-server-0.dc1 has failed, no acks received 2022/03/05 04:18:46 [ERR] raft-net: Failed to flush response: write tcp 10.233.75.121:8300->10.233.72.246:54238: write: broken pipe 2022/03/05 04:18:46 [INFO] serf: EventMemberJoin: onap-consul-server-0 10.233.70.53 2022/03/05 04:18:46 [INFO] consul: Adding LAN server onap-consul-server-0 (Addr: tcp/10.233.70.53:8300) (DC: dc1) 2022/03/05 04:18:55 [WARN] memberlist: Refuting a suspect message (from: onap-consul-667578469f-fwd5j)