You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 23, 2024. It is now read-only.
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:
[ 138.321970] init: mesos-slave main process (2811) killed by ABRT signal
[ 138.321977] init: mesos-slave main process ended, respawning
[ 138.341067] init: mesos-slave main process (2835) killed by ABRT signal
[ 138.341075] init: mesos-slave main process ended, respawning
[ 138.359238] init: mesos-slave main process (2851) killed by ABRT signal
[ 138.359254] init: mesos-slave main process ended, respawning
[ 138.377498] init: mesos-slave main process (2867) killed by ABRT signal
[ 138.377507] init: mesos-slave main process ended, respawning
[ 138.395897] init: mesos-slave main process (2883) killed by ABRT signal
[ 138.395906] init: mesos-slave main process ended, respawning
[ 138.414475] init: mesos-slave main process (2899) killed by ABRT signal
[ 138.414483] init: mesos-slave main process ended, respawning
[ 138.432855] init: mesos-slave main process (2915) killed by ABRT signal
[ 138.432863] init: mesos-slave main process ended, respawning
[ 138.451119] init: mesos-slave main process (2932) killed by ABRT signal
[ 138.451127] init: mesos-slave main process ended, respawning
[ 138.469644] init: mesos-slave main process (2948) killed by ABRT signal
[ 138.469652] init: mesos-slave main process ended, respawning
[ 138.488002] init: mesos-slave main process (2964) killed by ABRT signal
[ 138.488010] init: mesos-slave main process ended, respawning
[ 138.506841] init: mesos-slave main process (2980) killed by ABRT signal
[ 138.506849] init: mesos-slave respawning too fast, stopped
All of slaves which faces this issue printed out below syslog.
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 script
regards
The text was updated successfully, but these errors were encountered: