Segmentation fault initializing host

Archive Rancher 1.x
1

Hey guys, i have three centos7 machines, one rancher server and two hosts. Server initializes fine but I’m seeing this in the logs on my hosts. Every once in a while they will show up in the Infrastructure->hosts section but usually they wont.

Any suggestions would be helpful

goroutine 25 [select]:
net.cgoLookupIP(0xcda3a0, 0xc4202ba120, 0xc420231487, 0x15, 0xc420023ee8, 0xc420023e40, 0x2, 0x2, 0x0, 0x0)
    /usr/local/go/src/net/cgo_unix.go:209 +0x2f5
net.lookupIP(0xcda3a0, 0xc4202ba120, 0xc420231487, 0x15, 0xc4201b9980, 0x0, 0x30, 0xc420023ea0, 0x40580d)
    /usr/local/go/src/net/lookup_unix.go:70 +0xf9
net.glob..func11(0xcda3a0, 0xc4202ba120, 0x9181b8, 0xc420231487, 0x15, 0x61c0f5, 0x805220, 0xc4201b9980, 0xc420023ee8, 0x1)
    /usr/local/go/src/net/hook.go:19 +0x52
net.lookupIPContext.func1(0xc420023f88, 0x5d6ed8, 0xc4200d4000, 0xcda360)
    /usr/local/go/src/net/lookup.go:119 +0x5c
internal/singleflight.(*Group).doCall(0xcf0d30, 0xc4201d6fa0, 0xc420231487, 0x15, 0xc420289c80)
    /usr/local/go/src/internal/singleflight/singleflight.go:93 +0x3c
created by internal/singleflight.(*Group).DoChan
    /usr/local/go/src/internal/singleflight/singleflight.go:86 +0x339
INFO: Starting agent for C6224C4CE36EFD0520EC
INFO: Access Key: C6224C4CE36EFD0520EC
INFO: Config URL: http://rancher.therigy.local:8080/v1
INFO: Storage URL: http://rancher.therigy.local:8080/v1
INFO: API URL: http://rancher.therigy.local:8080/v1
INFO: IP: 10.10.10.59
INFO: Port:
INFO: Required Image: rancher/agent:v1.1.2
INFO: Current Image: rancher/agent:v1.1.2
INFO: Using image rancher/agent:v1.1.2
INFO: Downloading agent http://rancher.therigy.local:8080/v1/configcontent/configscripts
INFO: Updating configscripts
INFO: Downloading http://rancher.therigy.local:8080/v1//configcontent//configscripts current=
INFO: Running /var/lib/cattle/download/configscripts/configscripts-1-f0f3fb2e1110b5ada7c441705981f93a480313a324294321cff467f0c3e12319/apply.sh
INFO: Sending configscripts applied 1-f0f3fb2e1110b5ada7c441705981f93a480313a324294321cff467f0c3e12319
INFO: Updating pyagent
INFO: Downloading http://rancher.therigy.local:8080/v1//configcontent//pyagent current=
INFO: Running /var/lib/cattle/download/pyagent/pyagent-1-9e3dcab12585149a65d818082279708965cd826df1937a55b24f48428f8f0c0644fc1033b5be15c88dcf9540b1c04c67/apply.sh
INFO: Updating host-api
INFO: Downloading http://rancher.therigy.local:8080/v1//configcontent//host-api current=1-9608ead804f8cebbfe95b9f114701d8a5ac4244d603d196068043c902b1a0bdf
INFO: Already up to date
INFO: Sending host-api applied 1-9608ead804f8cebbfe95b9f114701d8a5ac4244d603d196068043c902b1a0bdf
INFO: Updating python-agent
INFO: Downloading http://rancher.therigy.local:8080/v1//configcontent//python-agent current=1-fb8355b64dd7128ac38c76bcff29d08f5af80cdff0e094c8c838e2a4e634918b
INFO: Already up to date
INFO: Sending python-agent applied 1-fb8355b64dd7128ac38c76bcff29d08f5af80cdff0e094c8c838e2a4e634918b
INFO: Sending pyagent applied 1-9e3dcab12585149a65d818082279708965cd826df1937a55b24f48428f8f0c0644fc1033b5be15c88dcf9540b1c04c67
INFO: Starting agent /var/lib/cattle/pyagent/apply.sh
INFO: Executing /var/lib/cattle/pyagent/agent
INFO: Updating host-config
INFO: Downloading http://rancher.therigy.local:8080/v1//configcontent//host-config current=host-config-1-8911a06bb4deb93d34d7f44eeee22000f56edde6952d18faeaf0ec72532c4d48
INFO: Already up to date
INFO: Sending host-config applied 1-8911a06bb4deb93d34d7f44eeee22000f56edde6952d18faeaf0ec72532c4d48
time="2016-12-31T18:18:43Z" level=info msg="Launching agent"
time="2016-12-31T18:18:43Z" level=info msg="Listening for events on     http://rancher.therigy.local:8080/v1"
time="2016-12-31T18:18:43Z" level=info msg="launching hostapi"
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x63 pc=0x7fc08654d259]
2

To add to the issue. I added in an Ubutntu 16.04 host and it worked. However several of the default services aren’t starting up.

3

I’m seeing this as well on a ubuntu 15.10 server. Docker version is 1.12.6. Happy to offer any other info that may help.

4

Are you by chance using non-standard domains? Like rancher.local instead of
ip?

5

Yeah. Using .local tld. Just ran across this GitHub issue referencing the .local trigger.

Luckily I’m just spinning this up on a home lab so changing .local to .home(or anything else I guess) was easy. Once that was done, I just had to change the base url in rancher to reflect the domain name change. Recreated the rancher agent and it came up perfectly!