Results

By type
Logs
raw version
          + 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: '0b562186-4e3d-b69a-e088-d6098d01fad6'
         Node name: 'onap-consul-server-0'
        Datacenter: 'dc1' (Segment: '')
            Server: true (Bootstrap: false)
       Client Addr: [0.0.0.0] (HTTP: 8500, HTTPS: -1, DNS: 8600)
      Cluster Addr: 10.233.71.98 (LAN: 8301, WAN: 8302)
           Encrypt: Gossip: false, TLS-Outgoing: false, TLS-Incoming: false

==> Log data will now stream in as it occurs:

    2023/02/04 02:48:27 [INFO] raft: Initial configuration (index=0): []
    2023/02/04 02:48:27 [INFO] raft: Node at 10.233.71.98:8300 [Follower] entering Follower state (Leader: "")
    2023/02/04 02:48:27 [INFO] serf: EventMemberJoin: onap-consul-server-0.dc1 10.233.71.98
    2023/02/04 02:48:27 [INFO] serf: EventMemberJoin: onap-consul-server-0 10.233.71.98
    2023/02/04 02:48:27 [INFO] consul: Adding LAN server onap-consul-server-0 (Addr: tcp/10.233.71.98:8300) (DC: dc1)
    2023/02/04 02:48:27 [INFO] consul: Handled member-join event for server "onap-consul-server-0.dc1" in area "wan"
    2023/02/04 02:48:27 [INFO] agent: Started DNS server 0.0.0.0:8600 (udp)
    2023/02/04 02:48:27 [INFO] agent: Started DNS server 0.0.0.0:8600 (tcp)
    2023/02/04 02:48:27 [INFO] agent: Started HTTP server on [::]:8500 (tcp)
    2023/02/04 02:48:27 [INFO] agent: started state syncer
    2023/02/04 02:48:27 [INFO] agent: Retry join LAN is supported for: aliyun aws azure digitalocean gce os scaleway softlayer
    2023/02/04 02:48:27 [INFO] agent: Joining LAN cluster...
    2023/02/04 02:48:27 [INFO] agent: (LAN) joining: [onap-consul-server-0.consul-server onap-consul-server-1.consul-server onap-consul-server-2.consul-server]
    2023/02/04 02:48:29 [WARN] memberlist: Failed to resolve onap-consul-server-0.consul-server: lookup onap-consul-server-0.consul-server on 169.254.25.10:53: no such host
    2023/02/04 02:48:31 [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
    2023/02/04 02:48:33 [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
    2023/02/04 02:48:33 [INFO] agent: (LAN) joined: 0 Err: 3 error(s) occurred:

* Failed to resolve onap-consul-server-0.consul-server: lookup onap-consul-server-0.consul-server on 169.254.25.10:53: no such host
* 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
* 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
    2023/02/04 02:48:33 [WARN] agent: Join LAN failed: , retrying in 30s
    2023/02/04 02:48:33 [WARN] raft: no known peers, aborting election
    2023/02/04 02:48:34 [ERR] agent: failed to sync remote state: No cluster leader
==> Newer Consul version available: 1.14.4 (currently running: 1.0.6)
    2023/02/04 02:48:58 [INFO] serf: EventMemberJoin: onap-consul-5c69875fbb-kbbsv 10.233.71.27
    2023/02/04 02:49:02 [ERR] agent: Coordinate update error: No cluster leader
    2023/02/04 02:49:03 [INFO] agent: (LAN) joining: [onap-consul-server-0.consul-server onap-consul-server-1.consul-server onap-consul-server-2.consul-server]
    2023/02/04 02:49:03 [ERR] agent: failed to sync remote state: No cluster leader
    2023/02/04 02:49:07 [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
    2023/02/04 02:49:09 [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
    2023/02/04 02:49:09 [INFO] agent: (LAN) joined: 1 Err: 
    2023/02/04 02:49:09 [INFO] agent: Join LAN completed. Synced with 1 initial agents
    2023/02/04 02:49:27 [ERR] agent: failed to sync remote state: No cluster leader
    2023/02/04 02:49:31 [ERR] agent: Coordinate update error: No cluster leader
    2023/02/04 02:49:34 [INFO] serf: EventMemberJoin: onap-consul-server-1 10.233.70.74
    2023/02/04 02:49:34 [INFO] consul: Adding LAN server onap-consul-server-1 (Addr: tcp/10.233.70.74:8300) (DC: dc1)
    2023/02/04 02:49:34 [INFO] serf: EventMemberJoin: onap-consul-server-1.dc1 10.233.70.74
    2023/02/04 02:49:34 [INFO] consul: Handled member-join event for server "onap-consul-server-1.dc1" in area "wan"
    2023/02/04 02:49:51 [INFO] serf: EventMemberJoin: onap-consul-server-2 10.233.66.136
    2023/02/04 02:49:51 [INFO] consul: Adding LAN server onap-consul-server-2 (Addr: tcp/10.233.66.136:8300) (DC: dc1)
    2023/02/04 02:49:51 [INFO] consul: Found expected number of peers, attempting bootstrap: 10.233.71.98:8300,10.233.70.74:8300,10.233.66.136:8300
    2023/02/04 02:49:51 [INFO] serf: EventMemberJoin: onap-consul-server-2.dc1 10.233.66.136
    2023/02/04 02:49:51 [INFO] consul: Handled member-join event for server "onap-consul-server-2.dc1" in area "wan"
    2023/02/04 02:49:56 [ERR] agent: Coordinate update error: No cluster leader
2023/02/04 02:49:59 [DEBUG] raft-net: 10.233.71.98:8300 accepted connection from: 10.233.66.136:55104
2023/02/04 02:49:59 [DEBUG] raft-net: 10.233.71.98:8300 accepted connection from: 10.233.66.136:55102
    2023/02/04 02:49:59 [INFO] consul: New leader elected: onap-consul-server-2
    2023/02/04 02:49:59 [INFO] agent: Synced node info
    2023/02/04 05:49:18 [ERR] consul.rpc: multiplex conn accept failed: read tcp 10.233.71.98:8300->10.233.70.74:49250: read: connection reset by peer from=10.233.70.74:49250
    2023/02/04 06:54:29 [WARN] yamux: failed to send ping reply: session shutdown
    2023/02/04 08:32:31 [WARN] yamux: failed to send ping reply: session shutdown
    2023/02/04 13:58:33 [ERR] yamux: keepalive failed: session shutdown
    2023/02/04 13:58:34 [ERR] memberlist: Failed fallback ping: write tcp 10.233.71.98:36046->10.233.71.27:8301: i/o timeout
    2023/02/04 14:49:34 [ERR] yamux: keepalive failed: session shutdown
    2023/02/04 14:49:34 [WARN] yamux: failed to send ping reply: session shutdown
    2023/02/04 14:49:34 [ERR] yamux: keepalive failed: session shutdown
    2023/02/04 16:42:39 [INFO] consul.fsm: snapshot created in 85.955µs
    2023/02/04 16:42:39 [INFO] raft: Starting snapshot up to 8192
    2023/02/04 16:42:39 [INFO] snapshot: Creating new snapshot at /consul/data/raft/snapshots/2-8192-1675528959582.tmp
    2023/02/04 16:42:39 [INFO] raft: Snapshot to 8192 complete
    2023/02/04 17:13:34 [ERR] memberlist: Failed fallback ping: write tcp 10.233.71.98:38604->10.233.71.27:8301: i/o timeout
    2023/02/04 17:13:34 [INFO] memberlist: Suspect onap-consul-5c69875fbb-kbbsv has failed, no acks received