Is it possible to use checkmk with thruk in front?

Hello,

Actually we are using nagios 3 with nconf and thruk in front-end + mk_livestatus but we are planning to migrate to high version (nagios 4, nagiosql, thruk). I just discovered that mk_livestatus is now checkmk, so I installed the raw version. Could you tell me if it’s possible to use it with thruk in frontend ? is it compatible with nagiosql ? Please let know with details.
Your help will be appreciated.

Thanks

Maybe this thread is helpful?

Hello,

that checkmk is debian, y os is redhat9, is it compatible ? not sure, so this is not helpfull.

I’m meanwhile trying naemon+ livestatus+thruk but getting below errors:

from Thruk :

livestatus (no lmd): get_hostgroups:
BACKEND01: 500: socket error - reading header from socket failed: Connection reset by peer.
backend error at /usr/share/thruk/lib/Thruk/Backend/Manager.pm line 2167.
Thruk::Backend::Manager::AUTOLOAD(Thruk::Backend::Manager=HASH(0x55f9491b2940), “filter”, ARRAY(0x55f949ad9e28)) called at /usr/share/thruk/lib/Thruk/Controller/status.pm line 733
Thruk::Controller::status::_process_overview_page(Thruk::Context=HASH(0x55f948dba548)) called at /usr/share/thruk/lib/Thruk/Controller/status.pm line 146
Thruk::Controller::status::index(Thruk::Context=HASH(0x55f948dba548), “/thruk/cgi-bin/status.cgi”) called at /usr/share/thruk/lib/Thruk.pm line 332
eval {…} called at /usr/share/thruk/lib/Thruk.pm line 327
Thruk::_dispatcher(HASH(0x55f948d59208)) called at /usr/lib64/thruk/perl5/Plack/Util.pm line 145
eval {…} called at /usr/lib64/thruk/perl5/Plack/Util.pm line 145
Plack::Util::run_app(CODE(0x55f948321d80), HASH(0x55f948d59208)) called at /usr/lib64/thruk/perl5/Plack/Handler/FCGI.pm line 147
Plack::Handler::FCGI::run(Plack::Handler::FCGI=HASH(0x55f946ddf838), CODE(0x55f948321d80)) called at /usr/share/thruk/script/thruk_fastcgi.pl line 28

fom /var/log/messages:

systemd-coredump[3154313]: /etc/systemd/coredump.conf:26: Unknown section ‘Journal’. Ignoring.
systemd[1]: Started Process Core Dump (PID 3154313/UID 0).
systemd-coredump[3154314]: /etc/systemd/coredump.conf:26: Unknown section ‘Journal’. Ignoring.
systemd-coredump[3154314]: Resource limits disable core dumping for process 3154312 (livestatus.so).
systemd-coredump[3154314]: Process 3154312 (livestatus.so) of user 987 dumped core.
systemd[1]: mklivestatus@117-10.118.140.169:6557-10.118.140.169:50366.service: Main process exited, code=dumped, status=11/SEGV
systemd[1]: mklivestatus@117-10.118.140.169:6557-10.118.140.169:50366.service: Failed with result ‘core-dump’.
systemd[1]: systemd-coredump@113-3154313-0.service: Deactivated successfully.
systemd[1]: Started mklivestatus Per-Connection Server (MY_IPADDRESS:50382).
kernel: livestatus.so[3154321]: segfault at 0 ip 00007fe55af7a330 sp 00007ffc95f20bb0 error 4 in livestatus.so[7fe55af77000+43000]
kernel: Code: 25 2d c7 05 00 0f 1f 44 00 00 f3 0f 1e fa f2 ff 25 25 c7 05 00 0f 1f 44 00 00 f3 0f 1e fa f2 ff 25 1d c7 05 00 0f 1f 44 00 00 <4c> 8b 07 4d 85 c0 74 0f 48 8b 77 10 4c 89 c7