Open ryoichitaniguchi opened 8 years ago
For the below error, I internally uploaded 18934f5e4f4d07137f7aeaa1f137e22985b1350c, to delay launching mesos-* service on startup, hope someone kindly review it
Apr 4 01:26:15 jptolx10221 mesos-slave[2989]: F0404 01:26:15.667261 2989 process.cpp:889] Failed to initialize: Failed to bind on 10.XX.XX.XX:5051: Cannot assign requested address: Cannot assign requested address [99]
Hi experts,
Currently I run 10 mesos-slaves on ubuntu-trusty using latest deb package(version 0.28.0-2.0.16)
I installed and configured "mesos" package by using ansible role (https://github.com/AnsibleShipyard/ansible-mesos) But it uses default configuration (of this, mesosphere/mesos-deb-packaging)
I noticed that after my scheduled OS reboot, sometimes a few of them (2-3 of 10 total) fail launch mesos-slave with below error.
dmesg:
All of slaves which faces this issue printed out below syslog.
corresponding code: https://github.com/apache/mesos/blob/845fa6abdc163676cde225e2dc72cee9e3e964f5/3rdparty/libprocess/src/process.cpp#L889
I bet, it likely EADDRNOTAVAIL (errno=99) occured on bind() ? (-> interface is not ready to be used for bind??) :
syslog:
Actually this can be recovered with
service mesos-slave start
but could I avoid that ? appreciate someone fix upstart scriptregards