[icinga-users] Fwd: Icinga 2 systemd problem after update

Johnny johnny.burak at email.cz
Mon Jul 23 10:34:42 CEST 2018


Hi,

thank you for that information. That's great it is already fixed in 2.9.1.

I thought about SELinux, but didn't look in log because thought that it
would have no consequence and it is related only to systemd :).

I tried to put SELinux to permissive mode on icinga2_t domain as
suggested workaround at github issue.
I can confirm it is working workaround.

Thanks.

Antony Stone:
Sorry not to mention.
I upgraded all packages on the systems (yum update).
In the update was Icinga2 2.9.0 and kernel update.
I tried downgrade icinga2 on one system and it doesn't work for me.
The SELinux workaround is working solution.

Peter Eckel:
Thank you, but my sysconfig file /etc/sysconfig/icinga2 doesn't have
anything inside except the comment out defaults.

Best
Johnny


On 22.7.2018 22:56, Florian Bachmann wrote:
> Hi,
>
> I got hit by that problem today, too. There's an issue on Github
> (#6443 - https://github.com/Icinga/icinga2/issues/6443) for it, but it
> has been closed already. The fix is in for 2.9.1, which will be
> released... sometime, I guess.
>
> The workaround is to just put SELinux into permissive mode for the
> time being (sigh), or manually update SELinux policy.
>
> It kind of makes you wonder how on earth this problem could not have
> been detected in pre-release testing, though.
>
> Kind regards
> Florian
>
> On 21.07.2018 14:10, Johnny wrote:
>> Hi all,
>>
>> I updated two hosts today and systemd service icinga2 has problem to
>> start after that. Icinga2 service will start but systemd doesn't know
>> that. Systemd is waiting for something (maybe return code) and after
>> half an hour (30 minutes) timeout. When systemd timeout on start-up of
>> icinga2 service then it shutdown the service. So icinga2 is running till
>> timeout.
>>
>> I'm runnig on:
>>
>>              Operating System: CentOS Linux 7 (Core)
>>              CPE OS Name: cpe:/o:centos:centos:7
>>              Kernel: Linux 3.10.0-693.11.6.el7.x86_64
>>
>> and
>>
>>              Operating System: Red Hat Enterprise Linux
>>              CPE OS Name: cpe:/o:redhat:enterprise_linux:7.5:GA:server
>>              Kernel: Linux 3.10.0-862.6.3.el7.x86_64
>>
>> Start icinga2 using:
>>
>> systemctl start icinga2
>>
>> The command doesn't complete.
>>
>> If I run status in different terminal the service is running:
>>
>> # systemctl status icinga2
>>
>> ● icinga2.service - Icinga host/service/network monitoring system
>>     Loaded: loaded (/usr/lib/systemd/system/icinga2.service; enabled;
>> vendor preset: disabled)
>>     Active: activating (start) since So 2018-07-21 13:00:13 CEST;
>> 13min ago
>>    Process: 6046 ExecStartPre=/usr/lib/icinga2/prepare-dirs
>> /etc/sysconfig/icinga2 (code=exited, status=0/SUCCESS)
>>   Main PID: 6054 (icinga2)
>>     CGroup: /system.slice/icinga2.service
>>             ├─6054 /usr/lib64/icinga2/sbin/icinga2 --no-stack-rlimit
>> daemon -e
>>             └─6088 /usr/lib64/icinga2/sbin/icinga2 --no-stack-rlimit
>> daemon -e
>>
>> The PID file is created.
>> Th process are running.
>> The application is logging.
>> And the agent is communicating with master.
>>
>> After half an hour (30 mins) the start command complete and status is:
>>
>> # systemctl status icinga2
>>
>> ● icinga2.service - Icinga host/service/network monitoring system
>>     Loaded: loaded (/usr/lib/systemd/system/icinga2.service; enabled;
>> vendor preset: disabled)
>>     Active: failed (Result: timeout) since So 2018-07-21 13:30:13
>> CEST; 29min ago
>>    Process: 6054 ExecStart=/usr/sbin/icinga2 daemon -e
>> ${ICINGA2_ERROR_LOG} (code=exited, status=0/SUCCESS)
>>    Process: 6046 ExecStartPre=/usr/lib/icinga2/prepare-dirs
>> /etc/sysconfig/icinga2 (code=exited, status=0/SUCCESS)
>>   Main PID: 6054 (code=exited, status=0/SUCCESS)
>>
>> čec 21 13:30:13 host.example.com icinga2[6054]: [2018-07-21 13:30:08
>> +0200] information/...);
>> čec 21 13:30:13 host.example.com icinga2[6054]: [2018-07-21 13:30:13
>> +0200] information/...n.
>> čec 21 13:30:13 host.example.com icinga2[6054]: [2018-07-21 13:30:13
>> +0200] information/.....
>> čec 21 13:30:13 host.example.com icinga2[6054]: [2018-07-21 13:30:13
>> +0200] information/...d.
>> čec 21 13:30:13 host.example.com icinga2[6054]: [2018-07-21 13:30:13
>> +0200] information/...d.
>> čec 21 13:30:13 host.example.com icinga2[6054]: [2018-07-21 13:30:13
>> +0200] information/...e'
>> čec 21 13:30:13 host.example.com icinga2[6054]: [2018-07-21 13:30:13
>> +0200] information/...n.
>> čec 21 13:30:13 host.example.com systemd[1]: Failed to start Icinga
>> host/service/network...m.
>> čec 21 13:30:13 host.example.com systemd[1]: Unit icinga2.service
>> entered failed state.
>> čec 21 13:30:13 host.example.com systemd[1]: icinga2.service failed.
>>
>>
>> So Icinga2 master still sending emails that
>>
>> load on host.example.com is UNKNOWN!
>> Info:    Remote Icinga instance 'host.example.com' is not connected
>> to 'icinga.example.com'
>>
>> I need to keep agents running.
>>
>> Anybody has a solution how to tell systemd that icinga2 is running?
>> Or at least some workaround that it will not shutdown service at
>> timeout?
>>
>> Thanks in advance for any tips.
>>
>> Best
>> Johnny
>>
>> _______________________________________________
>> icinga-users mailing list
>> icinga-users at lists.icinga.org
>> https://lists.icinga.org/mailman/listinfo/icinga-users
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.icinga.org/pipermail/icinga-users/attachments/20180723/04fc90ee/attachment-0001.html>


More information about the icinga-users mailing list