Sehr geehrte Damen und Herren, 

in der Zeit vom 12.09.2016 bis einschließlich 23.09.2016 befinde ich mich  
nicht im Büro. 

Beachten Sie bitte, dass Ihre EMail nicht automatisch weitergeleitet wird. 
In dringenden Fällen wenden Sie sich bitte an unsere Hotline, 0203-378530, oder 
an Herrn Hesselmann (hesselm...@opm-computer.de).



Mit freundlichen Grüßen 

Ronny Bär
OPM IT Service GmbH 


Send icinga-users mailing list submissions to
        icinga-users@lists.icinga.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.icinga.org/mailman/listinfo/icinga-users
or, via email, send a message with subject or body 'help' to
        icinga-users-requ...@lists.icinga.org

You can reach the person managing the list at
        icinga-users-ow...@lists.icinga.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of icinga-users digest..."


Today's Topics:

   1. Checks stop checking after reboot (Jeff Reese)
   2. Re: Checks stop checking after reboot (Antony Stone)


----------------------------------------------------------------------

Message: 1
Date: Sun, 11 Sep 2016 12:18:52 -0700
From: Jeff Reese <jeffrey.re...@gmail.com>
To: icinga-users@lists.icinga.org
Subject: [icinga-users] Checks stop checking after reboot
Message-ID:
        <CAG-etOO+9JNUKsemat9izf_bj0c0eV3ZH3=vmq-a0fnto50...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi All,

I have found that restarting the machine on which my Icinga2 master
instance is installed causes checks to stop until I manually stop the
icinga2 service, delete the /var/lib/icinga2/icinga2.state file, and start
the icinga2 service.

I have a fresh install of r2.5.4-1 on Ubuntu Server 16.04.1 via
ppa:formorer/icinga.  Other installations on same server are icingaweb2,
graphite-api, and grafana.  No satellites, hosts, services, etc. have been
added.  I only have default, out of the box monitoring of localhost.  Setup
was exhaustively documented if that helps.

If I restart the machine, the "Last check" value in icingaweb2 stops
changing and "Next check" will be a negative value that continues to grow.
Performance data stops flowing to graphite.  Deleting icinga2.state returns
everything to normal until the next time the machine is restarted.

I'm not seeing an errors in icinga2.err and the only reference to
icinga2.state in icinga2.log is "Dumping program state to file
'/var/lib/icinga2/icinga2.state'".

There are some previous mailing list messages and bug reports about parsing
errors related to the state file but I'm not seeing any such parsing errors
in the log.  It might be that I just don't have the appropriate logging
enabled.  I'm relatively new to Icinga2.

Any suggestions on where to look next would be greatly appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.icinga.org/pipermail/icinga-users/attachments/20160911/9e0fa24b/attachment-0001.html>

------------------------------

Message: 2
Date: Sun, 11 Sep 2016 20:49:04 +0100
From: Antony Stone <antony.st...@icinga.open.source.it>
To: "Icinga User's Corner" <icinga-users@lists.icinga.org>
Subject: Re: [icinga-users] Checks stop checking after reboot
Message-ID: <201609112049.04334.antony.st...@icinga.open.source.it>
Content-Type: Text/Plain;  charset="iso-8859-6"

On Sunday 11 Sep 2016 at 20:18, Jeff Reese wrote:

> Hi All,
> 
> I have found that restarting the machine on which my Icinga2 master
> instance is installed causes checks to stop until I manually stop the
> icinga2 service, delete the /var/lib/icinga2/icinga2.state file, and start
> the icinga2 service.

> If I restart the machine, the "Last check" value in icingaweb2 stops
> changing and "Next check" will be a negative value that continues to grow.
> Performance data stops flowing to graphite.  Deleting icinga2.state returns
> everything to normal until the next time the machine is restarted.

> Any suggestions on where to look next would be greatly appreciated.

Maybe a shot in the dark, but are your clock and timezone correct?

Are you running NTP to get a good time source for the machine, and is the 
clock correct when it boots up?

I'm just thinking about those negative values for "next check" - does the 
machine somehow think it's in the future on bootup, and only corrects this by 
the time you restart icinga2?

A check of your /var/log/syslog and/or /var/log/messages should show what 
date/time the machine thinks it is during various parts of startup.

-- 
Is it venison for dinner again?  Oh deer.

                                                   Please reply to the list;
                                                         please *don't* CC me.


------------------------------

Subject: Digest Footer

_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users


------------------------------

End of icinga-users Digest, Vol 33, Issue 8
*******************************************


_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users

Reply via email to