Ad Widget

Collapse

"Unknown" status in host map

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Aly
    replied
    Well possibly someone needs to know if some triggers are in UNKNOWN state.

    P.S. In 2.0 version, unknown status will be slightly different for triggers, and I think it will not be an issue anymore.
    P.S.S. Those patches are unofficial. I write them in my free time.
    Last edited by Aly; 13-10-2010, 13:01.

    Leave a comment:


  • Zaniwoop
    replied
    Can this rather be an option on Zabbix, rather than patching each version?

    Leave a comment:


  • alfsolli
    replied
    Worked nicely

    Thanks, that worked pretty well. just tested really quick with my biggest map, and all the unknown's disappeared.

    - Alf Solli -

    Leave a comment:


  • Aly
    replied
    And here is patch against 1.8.3 (although not very tested, and unknown triggers will be counted for submaps):
    Attached Files

    Leave a comment:


  • Aly
    replied
    OK, here is the patch for 1.8.4 RC2 (although not very tested):
    Attached Files

    Leave a comment:


  • alfsolli
    replied
    Originally posted by Aly
    I guess you have to wait my return from vocation
    Are you back yet? Are you back yet?

    But seriously, when you are, and I hope you had a nice one, could we have an updated patch for 1.8.3 please?

    Leave a comment:


  • spamkiller
    replied
    Hi Guys,

    Somebody know how to apply this Patch? I don“t no how to do this.

    Best regards.

    Leave a comment:


  • Aly
    replied
    I guess you have to wait my return from vocation

    Leave a comment:


  • gospodin.horoshiy
    replied
    zbx_182_map_unknown.patch doesn't work for 1.8.3 ...
    any thoughts how to fix it? Can't figure it out...

    Leave a comment:


  • craigwelsh
    replied
    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?
    Attached Files
    Last edited by craigwelsh; 15-04-2010, 18:32.

    Leave a comment:


  • radamand
    replied
    Originally posted by 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.
    This patch is bad; the lines of maps.inc.php should read as:

    Code:
    $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.

    Leave a comment:


  • stuart.willoughby
    replied
    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
    Attached Files

    Leave a comment:


  • Murilex
    replied
    Very good! The patch have worked perfectly.

    Leave a comment:


  • gospodin.horoshiy
    replied
    Thnx, Aly!

    Leave a comment:


  • Aly
    replied
    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.
    Attached Files

    Leave a comment:

Working...