-
Notifications
You must be signed in to change notification settings - Fork 582
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to start icinga2 with kernel-3.10.0-514.21.2 RHEL7 #5367
Comments
Hi there, got the same problem. This happend after upgrading to the newest RHEL kernel / glibc. The following (quick and dirty) fix did at least let me start Icinga again. Change in /usr/sbin/icinga2 the last line to look like this:
|
When running strace, two systems with different patchlevel behave differently: System with 3.10.0-514.21.1.el7.x86_64: setrlimit(RLIMIT_NOFILE, {rlim_cur=16*1024, rlim_max=16*1024}) = 0 setrlimit(RLIMIT_NPROC, {rlim_cur=16*1024, rlim_max=16*1024}) = 0 getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM64_INFINITY}) = 0 setrlimit(RLIMIT_STACK, {rlim_cur=256*1024, rlim_max=RLIM64_INFINITY}) = 0 execve("/usr/lib64/icinga2/sbin/icinga2", ["/usr/lib64/icinga2/sbin/icinga2", "--no-stack-rlimit"], [/* 25 vars */]) = 0 brk(0) = 0x243b000` System with 3.10.0-514.21.2.el7.x86_64: setrlimit(RLIMIT_NOFILE, {rlim_cur=16*1024, rlim_max=16*1024}) = 0 setrlimit(RLIMIT_NPROC, {rlim_cur=16*1024, rlim_max=16*1024}) = 0 getrlimit(RLIMIT_STACK, {rlim_cur=RLIM64_INFINITY, rlim_max=RLIM64_INFINITY}) = 0 setrlimit(RLIMIT_STACK, {rlim_cur=256*1024, rlim_max=RLIM64_INFINITY}) = 0 execve("/usr/lib64/icinga2/sbin/icinga2", ["/usr/lib64/icinga2/sbin/icinga2", "--no-stack-rlimit"], [/* 21 vars */]) = -1 E2BIG (Argument list too long) There seems to be some major change in the behavior of the kernels. Any idea how to change that? |
I suppose this is related to https://rhn.redhat.com/errata/RHSA-2017-1484.html. Is this something that must be fixed within Icinga? |
Looks like their security fix inadvertently breaks legitimate uses of |
Thanks for the report, we'll look into that and are therefore postponing today's v2.7 release. |
CVE-2017-1000364 seems fixed/applied in Debian too. https://security-tracker.debian.org/tracker/CVE-2017-1000364 |
@dnsmichi I applied the patches this morning to our Debian 8 'jessie' system and Icinga 2 is still starting after a reboot.
Is there anything else I can send you to help with this problem? |
@mcktr thanks a lot, it's good to know that Debian does not seem to be affected. We're currently investigating on the RHEL kernel update, diff'ing -1 and -2 source rpms. |
Setting 4.5 MB stack size works, 4 MB does not. |
We're lowering the stack size not to reserve too much memory for spawned threads. An older version just attempted to set Options:
|
|
Alright, for now you can use @pefmeister workaround, we'll have a blogpost detailing the issues out in the coming days and 2.7 will come with a longterm solution. |
We reported a bug to RedHat mentioning the problem: The bug is currently private (I guess default for kernel) You can reproduce the problem in a more simple way:
|
RHEL 6 seems to be fine:
|
The workaround for systemd also requires the
|
CentOS 7 is currently rolling the kernel update onto the mirrors. The main mirror has it available.
|
Looks like there are related problems with the Kernel Update, but also on Debian jessie here: |
Reported CentOS bug: https://bugs.centos.org/view.php?id=13453 |
We received a test-build from RedHat that works fine in my test environment. |
…mitProcesses and RLimitStack refs #5367
Make rlimits configurable by adding three variables: RLimitFiles, RLimitProcesses and RLimitStack refs #5367
Our advisory is updated with everything that happened. https://www.icinga.com/2017/06/20/advisory-for-latest-security-updates-on-rhel-7/ Please ensure to open a support case at RedHat to ask for an accelerated fix, or a test RPM. This raises awareness that they'll release it soon enough. The configuration options have been added for v2.7. I would leave this issue open until RedHat/CentOS released a new Kernel update. |
New kernel from RH is available. No issues so far. |
I can confirm this, too. Seems to be working with the new kernel. Let's go 2.7! |
Thanks for your tests. We'll wait until everything is publicly resolved. https://bugzilla.redhat.com/show_bug.cgi?id=1463241 is not clear about its state, CentOS still has the old Kernel version. It is also highly likely that Debian was affected as they recently changed their patch set. There might be more patches or regressions coming in, see e.g. torvalds/linux@98da7d0 Let's wait and see when the Kernel problems will calm down, then we'll may start a release cycle for 2.7 again. |
A knowledge base entry has been published, saying solution is in progress |
Also related: https://access.redhat.com/solutions/3098341 |
Hi, CentOS has released new kernel update 3.10.0-514.26.1 and i could confirm that icinga2 process starts well. |
Catching up after vacation - the CentOS bug tracker item (https://bugs.centos.org/view.php?id=13453) is resolved and RedHat has published multiple Kernel versions too. Tested that inside the Vagrant box, works fine.
We'll discuss the 2.7 release once everyone involved returned from holidays, probably next week or so. Closing here, thanks to everyone involved 👍 |
…mitProcesses and RLimitStack refs #5367
General Notes
This seems to be an upstream Kernel regression in RHEL 7 only.
Please read the published advisory and our twitter channel where we keep posting updates on the matter.
https://www.icinga.com/2017/06/20/advisory-for-latest-security-updates-on-rhel-7/
Original Description
Hello,
I've applied the latest kernel update on my Icinga2 box. After booting the new kernel icinga2 is no longer able to start.
Running the previous kernel version is my current workaround.
Log:
Jun 20 08:15:05 icinga.example.com prepare-dirs[2629]: execvp: Argument list too long
Jun 20 08:15:05 icinga.example.com prepare-dirs[2629]: Could not fetch RunAsUser variable. Error ''. Exiting.
Jun 20 08:15:05 icinga.example.com systemd[1]: icinga2.service: control process exited, code=exited status=6
Jun 20 08:15:05 icinga.example.com systemd[1]: Failed to start Icinga host/service/network monitoring system.
Jun 20 08:15:05 icinga.example.com systemd[1]: Unit icinga2.service entered failed state.
Jun 20 08:15:05 icinga.example.com systemd[1]: icinga2.service failed.
Icinga2 version is 2.6.3
RHEL7.3 with all updates
kernel-3.10.0-514.21.2.el7.x86_64
The text was updated successfully, but these errors were encountered: