Actions
Bug #14088
closedmon: nothing logged when ENOSPC encountered during start up
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Monitor
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
For example, ceph-mon process was dying and reporting only the
following to dmesg, nothing to /var/log/ceph/mon.log
init: ceph-mon (ceph/monhost) main process (16538) terminated with status 28
init: ceph-mon (ceph/monhost) main process ended, respawning
init: ceph-create-keys main process (16227) killed by TERM signal
init: ceph-mon (ceph/monhost) main process (16546) terminated with status 28
init: ceph-mon (ceph/monhost) main process ended, respawning
init: ceph-create-keys main process (16548) killed by TERM signal
init: ceph-mon (ceph/monhost) main process (16556) terminated with status 28
init: ceph-mon (ceph/monhost) main process ended, respawning
init: ceph-create-keys main process (16558) killed by TERM signal
init: ceph-mon (ceph/monhost) main process (16566) terminated with status 28
init: ceph-mon (ceph/monhost) respawning too fast, stopped
init: ceph-create-keys main process (16568) killed by TERM signal
It required looking at the sources to see that status 28 meant
that monhost's disk free space was very low.
From Brad Hubbard...
it may not have been anticipated that init would swallow these types of errors early in the process and just report the return code.
Actions