CentOS 6.2 x86_64 with Oracl as backend.

Marcus,

Could you please describe more details of a problem and attach some screenshots.

Sure.

Image Zabbix 1.9.10 Graph Config.jpg shows graph configuration with limits 0 and 100 for Y MIN and MAX respectively.

Image Zabbix 1.9.10 Graph Show.jpg shows graph with wrong Y MIN and MAX values.

Marcus

Hi,

Do you need some more info ? Is there any way I can help you ?

Marcus

Confirmed in latest trunk r25854.

Thank you for screenshots. It helped to find a problem.

Fixed in version pre-1.9.10, r25857.

Tried new 2.0.0rc2 package but I still can see the problem. It seems that the lower boundary is OK but the upper is not (still ignores what I set).

I didn't recreate the graphs. Should I ?

Marcus

Tried new 2.0.0rc2 package but I still can see the problem. It seems that the lower boundary is OK but the upper is not (still ignores what I set).

Marcus,

I cannot reproduce problem in a new 2.0.0rc2 package. Works as expected. Could you please attach output of these SQL statements:

select graphid, name, yaxismin, yaxismax, ymin_type, ymax_type, ymin_itemid, ymax_itemid from graphs where name like 'Espaco livre no filesystem

');

Thanks.

New Screenshot (Zabbix 2.0.0rc3 Copyright 2001-2011 by Zabbix SIA)

About the SQLs :

1 )

GRAPHID NAME YAXISMIN YAXISMAX YMIN_TYPE YMAX_TYPE YMIN
_ITEMID YMAX_ITEMID
---------- ---------------------------------------- ---------- ---------- ---------- ---------- ----
------- -----------
610 Espaco livre no filesystem

0 100 1 1

612 Espaco livre no filesystem

0 100 1 1

614 Espaco livre no filesystem

0 100 1 1

616 Espaco livre no filesystem

0 100 1 1

618 Espaco livre no filesystem

0 100 1 1

620 Espaco livre no filesystem

0 100 1 1

Marcus

About the other command, it returned a lot of results. I did this SQL :

SQL> select distinct g.yaxismin, g.yaxismax, g.ymin_type, g.ymax_type, g.ymin_itemid, g.ymax_itemid
from zabbix.graphs g, zabbix.graph_discovery gd where g.graphid = gd.graphid and gd.parent_graphid i
n (select graphid from zabbix.graphs where name like 'Espaco livre no filesystem

');

YAXISMIN YAXISMAX YMIN_TYPE YMAX_TYPE YMIN_ITEMID YMAX_ITEMID
---------- ---------- ---------- ---------- ----------- -----------
0 100 0 0
0 100 1 1

SQL>

I think it shows what you want to see.

Marcus

Marcus,

Discovered elements (items, graphs and triggers) are updated by Zabbix server. Not by a frontend.
Therefore discovery rule should be enabled. Please check it.

Thanks.

The Discovery Rules are enabled... they were never disabled.

Thanks.

Marcus

We cannot reproduce the issue, but it can be fixed after implementation of ZBX-5789. There the code of lld graphs was completely rewritten.

I'm closing the issue. Possibly it is fixed under ZBX-5789.

Please reopen the issue if problem still reproducible.