topic Re: bind_addr cannot be empty - SAS Viya single machine deployment in Administration and Deployment

bind_addr cannot be empty - SAS Viya single machine deployment

arkam — Tue, 05 Nov 2019 17:30:32 GMT

While doing single machine deployment I am facing the error below

2019-11-05 19:31:03,991 p=22387 u=root | fatal: [deployTarget]: FAILED! => {"changed": true, "cmd": ["bash", "-c", "source /opt/sas/viya/config/consul.conf && /opt/sas/viya/home/bin/sas-bootstrap-config status leader"], "delta": "0:00:00.203617", "end": "2019-11-05 19:31:03.940516", "msg": "non-zero return code", "rc": 1, "start": "2019-11-05 19:31:03.736899", "stderr": "level=error command=\"status leader\" successful=false msg=\"Unable to status leader\" err=\"Get https://localhost:8501/v1/status/leader: dial tcp [::1]:8501: connect: connection refused\"\nERROR: Unable to determine the address of the Raft leader for the data center in which the Consul agent is running.", "stderr_lines": ["level=error command=\"status leader\" successful=false msg=\"Unable to status leader\" err=\"Get https://localhost:8501/v1/status/leader: dial tcp [::1]:8501: connect: connection refused\"", "ERROR: Unable to determine the address of the Raft leader for the data center in which the Consul agent is running."], "stdout": "", "stdout_lines": []}
2019-11-05 19:31:03,994 p=22387 u=root | NO MORE HOSTS LEFT *************************************************************
2019-11-05 19:31:03,996 p=22387 u=root | PLAY RECAP *********************************************************************
2019-11-05 19:31:03,997 p=22387 u=root | deployTarget : ok=237 changed=83 unreachable=0 failed=1
2019-11-05 19:31:03,997 p=22387 u=root | localhost : ok=14 changed=1 unreachable=0 failed=0
2019-11-05 21:15:08,107 passlib.registry registered 'md5_crypt' handler: <class 'passlib.handlers.md5_crypt.md5_crypt'>
2019-11-05 21:15:08,911 p=10886 u=root | deployTarget | SUCCESS | rc=0 >>

In Consul log I can see "==> bind_addr cannot be empty". I confirmed and I have added "consul_bind_adapter = eth0 in inventory.ini file.

Re: bind_addr cannot be empty - SAS Viya single machine deployment

alexal — Tue, 05 Nov 2019 17:36:36 GMT

@arkam ,

I would like to review the output from these two commands:

ifconfig
grep CONSUL_BIND_EXTERNAL /etc/sysconfig/sas/sas-viya-consul-default

Re: bind_addr cannot be empty - SAS Viya single machine deployment

arkam — Tue, 05 Nov 2019 17:43:07 GMT

ifconfig

em1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:23:ae:ec:62:60 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

em2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:23:ae:ec:62:62 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

em3: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:23:ae:ec:62:64 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

em4: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:23:ae:ec:62:66 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 1250 bytes 205180 (200.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1250 bytes 205180 (200.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

p3p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.29.80.56 netmask 255.255.255.0 broadcast 172.29.80.255
inet6 fe80::74d8:c7ea:94eb:4006 prefixlen 64 scopeid 0x20<link>
ether a0:36:9f:12:e0:14 txqueuelen 1000 (Ethernet)
RX packets 37827327 bytes 41471556878 (38.6 GiB)
RX errors 0 dropped 36491 overruns 0 frame 0
TX packets 16835795 bytes 1231821191 (1.1 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

p3p2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether a0:36:9f:12:e0:16 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

grep CONSUL_BIND_EXTERNAL /etc/sysconfig/sas/sas-viya-consul-default

export CONSUL_BIND_EXTERNAL='eth0'

Re: bind_addr cannot be empty - SAS Viya single machine deployment

alexal — Tue, 05 Nov 2019 17:45:10 GMT

@arkam ,

I'm curious why did you specify "eth0" if that network interface isn't configured on your server?

Re: bind_addr cannot be empty - SAS Viya single machine deployment

arkam — Tue, 05 Nov 2019 17:54:28 GMT

Ah apologies. I used another server before and created installation guide based on that and it had eth0.
One question, p3p1 is the only one which is currently up. I can specify that in inventory file and restart the install or I need to clean up and start fresh?

Re: bind_addr cannot be empty - SAS Viya single machine deployment

alexal — Tue, 05 Nov 2019 18:06:07 GMT

@arkam ,

You do not need to redeploy the software. Just update CONSUL_BIND_EXTERNAL in /etc/sysconfig/sas/sas-viya-consul-default file, but also do not forget to update consul_bind_adapter property in the inventory.ini file. If you don't that and run the playbook again, for example, to install fixes, that property will be overwritten.