Ad Widget

Collapse

beta5: schema.sql, graph, minor problem input

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • markpr
    Member
    • Sep 2005
    • 31

    #1

    beta5: schema.sql, graph, minor problem input

    Hi,

    I just did a fresh install of beta5 to replace my existing 1.1a10 installation and this release is working very well for me. A big improvement in functionality/usability of alpha 10. I even have templates working...

    I did find a few minor issues (at least one reported so far).

    1) schema.sql

    reports an error loading table "rights". I had to change the following definition in the rights table:
    userid int(4) DEFAULT '0' NOT NULL,

    2) defining graphs (resolved?)

    graphs are created per host. To view a graph you have to select a host and to create a graph you have to remember to select a host first (or all graphs will be listed under "Select host....."

    3) 1 hour graphs: I have a strange problem with one simple graph (1h period) where the graph line is being displayed below the x axis. I don't see the problem with any of my other 50+ graphs on the same screens page. The value spread is 0.0823 to 0.0828. I can email you a graph if it's helpful.

    4) Very Minor: IP address can only be defined once (icmpping and icmppingsec). If (for some strange reason) you want to define two hosts that both have the same IP address (host1 10.10.0.1 and host2 10.10.0.1) values will only be stored against one of the hosts.

    5) Very Minor: Items.php throws IDS rule. I noticed that Items.php is throwing an Intrusion Detection rule error coming out of mod_security (it uses SNORT type rules). The pattern match throwing the rule is "DELETE". I know this is minor and can probably be solved with a rule exception but if others are using similar IDS/IDP protection they may run into problems. DELETE is a keyword that you want to avoid like LS, PS, RMDIR, KILL etc

    Here is the error that I see in the logs:

    [Sat Jan 14 16:34:32 2006] [error] [client **.**.**.**] mod_security: Warning. Pattern match "DELETE " at REQUEST_URI [hostname "www.******.net"] [uri "/items.php?hostid=10011&17230=on&register=Delete+se lected"]

    6) Delete Trigger: SQL error.

    This is a clean install of beta5 into a fresh database. Deleting a trigger from a host seems to work fine but generates the following error: [ERROR:Cannot delete trigger] SQL error: Unknown column 'triggerid' in 'where clause' Query: delete from actions where triggerid=12376 and scope=0

    7) Update Group: Group Already Exists Error. If I go into Configuration | Hosts | Host Groups and select additional hosts to add to a Host Group. The error that I get is [ERROR:_S_CANNOT_UPDATE_GROUP] Group "Servers" already exists. This error is expected with an add group not an update group.

    8) Bulk Load: Duplicate Groups. I bulk loaded a bunch of hosts into an existing group expecting the hosts to be added to the existing group. However a new group was created with the same name but a different ID. I can send you a screenshot or other info if you need it...

    9) Template Update (Trigger Delete) does not propogate to Host Linkages. I have a template used by a host template that has a bunch of triggers defined. This is the template that was used to configure all hosts originally. If I try to delete a trigger from the template it appears to be deleted OK (no longer listed) but the changes do not propogate out to the linked hosts. Note that I do get the same SQL error listed in problem 6) so this may have something to do with it.


    thanks again. I think all of these issues are fairly minor: This is a really good release.....

    Mark
    Last edited by markpr; 17-01-2006, 02:53.
  • Alexei
    Founder, CEO
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Sep 2004
    • 5654

    #2
    Thanks for your post. Very useful indeed!

    Some updates :

    1) Fixed.
    4) Not sure how to fix this as this is how ping works. There is no way to distinguish one host from another if they both have the same IP.
    6) Fixed.
    7) Will be fixed as we are doing quite significant improvements of all forms.
    Alexei Vladishev
    Creator of Zabbix, Product manager
    New York | Tokyo | Riga
    My Twitter

    Comment

    Working...