Bug 1585168

Summary: check-mk-livestatus-1.4.0p31-1.el7.x86_64 causes nagios crash short after start
Product: [Fedora] Fedora EPEL Reporter: Peter Bieringer <pb>
Component: check-mkAssignee: Andrea Veri <andrea.veri>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: epel7CC: andrea.veri, mjtrangoni
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-07-09 02:23:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Peter Bieringer 2018-06-01 12:07:19 UTC
Description of problem:
after updating check-mk from 1.2.8p18-1.el7.x86_64 to 1.4.0p31-1.el7.x86_64 (and fixing the dependency to "boost-system", nagios crashed short after start


Version-Release number of selected component (if applicable):
check-mk-livestatus-1.4.0p31-1.el7.x86_64     Fri 01 Jun 2018 09:01:43 AM UTC
check-mk-1.4.0p31-1.el7.x86_64                Fri 01 Jun 2018 09:01:41 AM UTC
nagios-4.3.4-5.el7.x86_64


How reproducible:
always


Steps to Reproduce:
1. upgrade check-mk
2. restart nagios


Actual results:
Crashing short after start


Expected results:
not crashing

Additional info:

[1527853888] livestatus: TIMEPERIOD TRANSITION: 24X7;-1;1
[1527853888] livestatus: TIMEPERIOD TRANSITION: 24x7;-1;1
[1527853888] livestatus: TIMEPERIOD TRANSITION: none;-1;0
[1527853888] livestatus: starting main thread and 100 client threads
[1527853888] livestatus: default stack size is 10485760
[1527853888] livestatus: setting thread stack size to 1048576
[1527853888] HOST DOWNTIME ALERT: ***
[1527853888] HOST DOWNTIME ALERT: ***
[1527853891] Caught SIGTERM, shutting down...


Found this already on EL6 earlier this year, afair it's an incompatibility of used header files during compilation between nagios and check-mk-livestatus


Workaround: throw away nagios/check-mk combination as looking no longer proper supported and switch to naemon

Comment 1 Andrea Veri 2018-06-01 14:23:51 UTC
Peter, the problem you're having is not related to livestatus being built against the wrong Nagios headers, that was fixed ages ago (on EL6 too since the time Nagios 4 was pushed to the repositories), the problem you're probably facing is related to [1][2]. I'd suggest opening a bug upstream about that [3]. Please have a look at whether you have empty values on host definitions on your check_mk_objects.cfg file.

[1] epoll_wait(3, terminate called after throwing an instance of 'std::logic_error'
    what():  basic_string::_M_construct null not valid
[2] http://lists.mathias-kettner.de/pipermail/checkmk-en/2014-May/012269.html
[3] http://mathias-kettner.com/check_mk_feedback.php?HTML=yes

Comment 2 Mario Trangoni 2018-07-04 10:09:06 UTC
Hi Andrea,

Is there any other BZ Ticket open related to the missing RPM dependency to "boost-system"?

Comment 3 Andrea Veri 2018-07-04 10:10:49 UTC
Mario,

yes, it's https://bugzilla.redhat.com/show_bug.cgi?id=1585166. A fixed package was released already.

Comment 4 Troy Dawson 2024-07-09 02:23:57 UTC
EPEL 7 entered end-of-life (EOL) status on 2024-06-30.\n\nEPEL 7 is no longer maintained, which means that it\nwill not receive any further security or bug fix updates.\n As a result we are closing this bug.