"Unknown" status in host map

[imarinkovic]

In the map section, all hosts appears as "Unknown", but the polling of data is working ok. If a trigger condition is reached, the icon in the map show the problem.

Version 1.8

Any idea?

[brian]

Same problem here:

http://www.zabbix.com/forum/showthread.php?t=15250

[imarinkovic]

[solved]

Ok,

I found the answer.

The "unknown" status appear by triggers that don't have any item associated (ie: disabled items)

Disabling this triggers to, removes "unknown" statuses

Example:

Trigger: Low number of free inodes on maggie volume /usr
--> In my case, this item was disabled, but no the trigger.

best regards

[Zaniwoop]

Almost solved.

I had the same problem and yes, I did have triggers that were "not supported".

I have removed them and in most cases this has solved the problem. However, there are some hosts that still report a number (2 - 18) of unknowns.
All remaining triggers have (latest) data, so they should be happy.

Is there anyway to find out what triggers are still unknown?

Zabbix 1.8.1 on Centos 5.4 (64 bit)

[maxlock]

We're seeing the same problem here, and would love a solution. We've got templated hosts, and when disabling all the triggers that are unknown we still get this problem saying there are a number of unknown triggers. I've checked one in particular and I've got current data for the item it depends on?! this is a real pain.

-Cheers Max.

[gospodin.horoshiy]

Devs, please let *Unknown* feature be optional on maps....

[maxlock]

I've got rid of the issue for now by performing the following sql

update triggers set status=1 where status=0 and value=2;

However I wouldn't recommend this approach.

-Max

[gospodin.horoshiy]

IMHO, frontend hack would be better....

[Murilex]

Devs, please let *Unknown* feature be optional on maps....

I really support this suggestion. It's very annoying see "unknown" triggers stats on maps.

[Aly]

Here is the patch, it should resolve your problem (it's not included in release).
Patch is against pre1.8.2(r10540):

P.S. You may repost it in thread for patches.

[gospodin.horoshiy]

Thnx, Aly!

[Murilex]

Very good! The patch have worked perfectly.

[stuart.willoughby]

Maps issue after 1.6.6 to 1.8.1 upgrade

Hello,

we've completed the upgrade from 1.6.6 to 1.8.1 on Redhat/mysql. Mysql is 5.0.45. PHP 5.2.6

Two problems really, one -all our icons in the upgraded maps are status 'unknown', however when we go into configuration/maps the icon's are not displayed (see attachment) and it's impossible to select the objects to edit or change them. However, you can see the latest data, triggers, etc when you click on an icon.


mysql> show variables like 'char%';
+--------------------------+----------------------------------+
| Variable_name | Value |
+--------------------------+----------------------------------+
| character_set_client | latin1 |
| character_set_connection | latin1 |
| character_set_database | utf8 |
| character_set_filesystem | binary |
| character_set_results | latin1 |
| character_set_server | latin1 |
| character_set_system | utf8 |
| character_sets_dir | /opt/mysql/share/mysql/charsets/ |
+--------------------------+----------------------------------+

mysql> select HEX(image) from images where imageid=7;
| 89504E470D0A1A0A0000000D494

Should I update the variables to utf8, truncate images table and reload from the 1.8.1/create/data/images_mysql.sql file?
INSERT INTO images VALUES (7,1,'Phone',0x89504E470D0A1A0A0000000D494....

They seem the same.

Is this the same as anyone else has seen?

Thanks

Stuart

[radamand]

Here is the patch, it should resolve your problem (it's not included in release).
Patch is against pre1.8.2(r10540):

P.S. You may repost it in thread for patches.

This patch is bad; the lines of maps.inc.php should read as:

$info['triggers'] = array();
    foreach($info['triggers'] as $tnum => $trigger){
        if($trigger['status'] == TRIGGER_STATUS_DISABLED) continue;
        if($trigger['value'] == TRIGGER_VALUE_UNKNOWN) continue;

        if(!isset($info['type'])){
            $info['type'] = $trigger['value'];

Although this still doesn't fix the problem of "UNKNOWN"s showing up when you have a host disabled.

[craigwelsh]

I'm also having this issue with various 1.8.2 servers (see attached). I haven't managed to find the ticket for this issue on the support site, is anyone tracking it and could give the link?

I'll try the patch below on 1.8.2 to see what that does but servers that are Disabled showing unknown triggers is also annoying.

edit: The patch of line 1569 works on triggers for disabled items, is there a requirement to patch the other section (around line 1339) as well?