Waiting for IP addresses to resolve upon node restart

[alphaDev23]

While the cluster is initialized without issue, I'm receiving the following on swarm upon a container restart or a new node instance being created after the cluster is initialized.. The node command is: 'node tasks.seed,tasks.node'

...------======------... MariaDB Galera Start Script ...------======------..., t NODE_ADDRESS=10.0.5.19, Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Waiting for at least 2 IP addresses to resolve..., Reducing GCOMM_MINIMUM to 1, Starting node, connecting to gcomm://, Tailing /tmp/mysql-console/fifo..., ===|mysqld.sh|===: uuid is known but seqno is not..., ===|mysqld.sh|===: --------------------------------------------------, ===|mysqld.sh|===: Attempting to recover GTID positon..., 2019-07-22 4:00:32 0 [Note] WSREP: Recovered position: 4634c8a8-ac33-11e9-a7e1-cf5b8e73b43a:0, ===|mysqld.sh|===: --------------------------------------------------, ===|mysqld.sh|===: Found view from gvwstate.dat with (5) members: 3 184788e2-ac34-11e9-9732-eaa27a635ca7 6, ===|mysqld.sh|===: Collecting grastate.dat and gvwstate.dat info from other nodes..., 2019/07/22 04:00:34 socat[658] E getaddrinfo("--console", "NULL", {1,0,1,6}, {}): No address associated with hostname, 2019/07/22 04:00:34 socat[659] E getaddrinfo("--console", "NULL", {1,0,1,6}, {}): No address associated with hostname, 2019/07/22 04:00:34 socat[660] E TCP: wrong number of parameters (3 instead of 2), 2019/07/22 04:00:34 socat[661] E TCP: wrong number of parameters (3 instead of 2), 2019/07/22 04:00:34 socat[662] E getaddrinfo("--wsrep-on=ON", "NULL", {1,0,1,6}, {}): No address associated with hostname, 2019/07/22 04:00:34 socat[663] E getaddrinfo("--wsrep-on=ON", "NULL", {1,0,1,6}, {}): No address associated with hostname, 2019/07/22 04:00:34 socat[664] E getaddrinfo("--wsrep-sst-method=mariabackup", "NULL", {1,0,1,6}, {}): No address associated with hostname, 2019/07/22 04:00:35 socat[665] E getaddrinfo("--wsrep-sst-method=mariabackup", "NULL", {1,0,1,6}, {}): No address associated with hostname, 2019/07/22 04:00:35 socat[666] E getaddrinfo("--wsrep_cluster_name=cluster", "NULL", {1,0,1,6}, {}): No address associated with hostname, 2019/07/22 04:00:35 socat[667] E getaddrinfo("--wsrep_cluster_name=cluster", "NULL", {1,0,1,6}, {}): No address associated with hostname, 2019/07/22 04:00:35 socat[668] E TCP: wrong number of parameters (3 instead of 2), 2019/07/22 04:00:35 socat[669] E TCP: wrong number of parameters (3 instead of 2), 2019/07/22 04:00:35 socat[670] E TCP: wrong number of parameters (3 instead of 2), 2019/07/22 04:00:35 socat[671] E TCP: wrong number of parameters (3 instead of 2), 2019/07/22 04:00:35 socat[672] E TCP: wrong number of parameters (3 instead of 2), 2019/07/22 04:00:35 socat[673] E TCP: wrong number of parameters (3 instead of 2), /usr/local/bin/start.sh: line 418: run-upgrades.sh: command not found, 2019/07/22 04:00:40 socat[682] E getaddrinfo("--console", "NULL", {1,0,1,6}, {}): No address associated with hostname, 2019/07/22 04:00:40 socat[683] E getaddrinfo("--console", "NULL", {1,0,1,6}, {}): No address associated with hostname, 2019/07/22 04:00:40 socat[684] E TCP: wrong number of parameters (3 instead of 2), 2019/07/22 04:00:40 socat[685] E TCP: wrong number of parameters (3 instead of 2), 2019/07/22 04:00:40 socat[686] E getaddrinfo("--wsrep-on=ON", "NULL", {1,0,1,6}, {}): No address associated with hostname, 2019/07/22 04:00:40 socat[687] E getaddrinfo("--wsrep-on=ON", "NULL", {1,0,1,6}, {}): No address associated with hostname, 2019/07/22 04:00:40 socat[688] E getaddrinfo("--wsrep-sst-method=mariabackup", "NULL", {1,0,1,6}, {}): No address associated with hostname, 2019/07/22 04:00:40 socat[689] E getaddrinfo("--wsrep-sst-method=mariabackup", "NULL", {1,0,1,6}, {}): No address associated with hostname, 2019/07/22 04:00:40 socat[690] E getaddrinfo("--wsrep_cluster_name=cluster", "NULL", {1,0,1,6}, {}): No address associated with hostname, 2019/07/22 04:00:40 socat[691] E getaddrinfo("--wsrep_cluster_name=cluster", "NULL", {1,0,1,6}, {}): No address associated with hostname, 2019/07/22 04:00:40 socat[692] E TCP: wrong number of parameters (3 instead of 2), 2019/07/22 04:00:40 socat[693] E TCP: wrong number of parameters (3 instead of 2), 2019/07/22 04:00:40 socat[694] E TCP: wrong number of parameters (3 instead of 2), 2019/07/22 04:00:40 socat[695] E TCP: wrong number of parameters (3 instead of 2), 2019/07/22 04:00:40 socat[696] E TCP: wrong number of parameters (3 instead of 2), 2019/07/22 04:00:40 socat[697] E TCP: wrong number of parameters (3 instead of 2),

[alphaDev23]

This is not an issue and was merely a typo in the compose file.