On Wed, Mar 19, 2014 at 11:57 AM, Michael Friedrich <
michael.friedr...@gmail.com> wrote:

> On 15.03.2014 02:10, Brian Dockter wrote:
>
>
>> On Thu, Mar 13, 2014 at 2:17 AM, Gunnar Beutner <
>> gunnar.beut...@netways.de <mailto:gunnar.beut...@netways.de>> wrote:
>>
>>     Hi Brian,
>>
>>     > I have a host that I've left powered off since our last power
>>     failure,
>>     > but I've chosen not to remove it from Icinga. With 0.0.7, this host
>>     > was showing up as DOWN. Now, after I've upgraded to
>>     > 0.0.7-snapshot201403071522, it is showing up as UNREACHABLE.
>>     >
>>     > This is the only host that is not UP. There are no nodes between
>>     > Icinga and this server. The server only has one service configured
>>     > (ping4), which is also the check command. I have disabled active
>>     > checks on this host.
>>     >
>>     > Is the host being UNREACHABLE the result of active checks being
>>     disabled?
>>
>>     I've just tried to reproduce this with v0.0.8-10-g76001c7 and the host
>>     correctly shows up as DOWN. Do you have the same problem with the most
>>     recent version?
>>
>>     Gunnar
>>
>>
>>
>> I installed 0.0.8-snapshot201403131643 and still see the same issue. I
>> turned on active checks and let them run for a while, but no change. They
>> still show as UNREACHABLE.
>>
>
> Please provide the according configuration and also debug logs for that
> specific host.
>

Sorry about the delayed response. I was sent off on a business trip (and
wanted to set up a test environment with minimal local changes).

I've done a fresh install of 0.0.9 onto a Debian box (including purging the
config files and dropping the database) and am still reproducing the issue.
I'm also running icinga-web/v1.11.0 for displaying the results.

Here is what I added to the top of localhost.conf. The rest of the config
is stock (straight from the Debian package):

    object Host "mydeadserver" {
      import "linux-server",

      macros.address = "10.192.130.81"
    }

Other hosts in the 10.192.130.0/24 subnet work fine (if they are online and
responding to pings).

Here is a snippet from the debug.log file. Let me know if you need more:

    [2014-04-01 14:04:09 -0700] <Check Scheduler> debug/checker: Executing
service check for 'mydeadserver!ping4'
    [2014-04-01 14:04:09 -0700] <Q #0xb270480c W #0xb27048f4> debug/base:
Running command '/usr/lib/nagios/plugins/check_ping -4 -H 10.192.130.81 -w
100,5% -c 200,15% -p 5 -t 0': PID 16603
    [2014-04-01 14:04:09 -0700] <Q #0xb270480c W #0xb27048f4>
debug/checker: Check finished for service 'mydeadserver!ping4'

    ...

    [2014-04-01 14:04:15 -0700] <Q #0xb7536ca4 W #0xb7536d8c> debug/db_ido:
add log entry history for 'mydeadserver!ping4'
    [2014-04-01 14:04:15 -0700] <Q #0xb7536ca4 W #0xb7536d8c> debug/db_ido:
add log entry history for 'mydeadserver!ping4'
    [2014-04-01 14:04:15 -0700] <Q #0xb7536ca4 W #0xb7536d8c> debug/db_ido:
add service check history for 'mydeadserver!ping4'
    [2014-04-01 14:04:15 -0700] <WQ #5> debug/db_ido_mysql: Query: INSERT
INTO icinga_logentries (entry_time, entry_time_usec, instance_id,
logentry_data, logentry_time, logentry_type, object_id) VALUES (FROM_UNIXTI
ME(1396386255), '603111', 1, 'SERVICE ALERT:
mydeadserver;ping4;CRITICAL;HARD;1;PING CRITICAL - Packet loss = 100%',
FROM_UNIXTIME(1396386255), '65536', 48)
    [2014-04-01 14:04:15 -0700] <Q #0xb7536ca4 W #0xb7536d8c> debug/db_ido:
Endpoint node: 'dhcp-192-168-112-71' status update for 'mydeadserver!ping4'
    [2014-04-01 14:04:15 -0700] <WQ #5> debug/db_ido_mysql: Query: INSERT
INTO icinga_logentries (entry_time, entry_time_usec, instance_id,
logentry_data, logentry_time, logentry_type, object_id) VALUES (FROM_UNIXTI
ME(1396386255), '603111', 1, 'SERVICE ALERT:
mydeadserver;ping4;CRITICAL;HARD;1;PING CRITICAL - Packet loss = 100%',
FROM_UNIXTIME(1396386255), '65536', 47)
    [2014-04-01 14:04:15 -0700] <Q #0xb7536ca4 W #0xb7536d8c> debug/db_ido:
Endpoint node: 'dhcp-192-168-112-71' status update for 'mydeadserver'
    [2014-04-01 14:04:15 -0700] <Q #0xb7536ca4 W #0xb7536d8c> debug/db_ido:
add state change history for 'mydeadserver!ping4'
    [2014-04-01 14:04:15 -0700] <WQ #5> debug/db_ido_mysql: Query: INSERT
INTO icinga_logentries (entry_time, entry_time_usec, instance_id,
logentry_data, logentry_time, logentry_type, object_id) VALUES (FROM_UNIXTI
ME(1396386255), '603205', 1, 'HOST ALERT: mydeadserver;DOWN;HARD;1;PING
CRITICAL - Packet loss = 100%', FROM_UNIXTIME(1396386255), '4096', 48)
    [2014-04-01 14:04:15 -0700] <WQ #5> debug/db_ido_mysql: Query: INSERT
INTO icinga_logentries (entry_time, entry_time_usec, instance_id,
logentry_data, logentry_time, logentry_type, object_id) VALUES (FROM_UNIXTI
ME(1396386255), '603205', 1, 'HOST ALERT: mydeadserver;DOWN;HARD;1;PING
CRITICAL - Packet loss = 100%', FROM_UNIXTIME(1396386255), '4096', 47)

The debug.log looks to me like it is identifying the server as DOWN, but
the web interface displays it as UNREACHABLE.

BTW, I also removed, purged, dropped database and reinstalled icinga-web,
with the same results.
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users

Reply via email to