Hello, i`m new in cacti forums.
I will try to clarify my problem cuz my english not good!
I have searched about this problem but i only find similar troubles with up to 114MB Traffic but not less 3mb traffic.
Note: This problem only occur with NEW graphs and the old still fine, same config, same settings. I see nothing can occur this problem.
Cacti LOG:
02/01/2011 10:58:02 AM - CMDPHP: Poller[0] Host[14] DS[163] WARNING: Result from SERVER not valid. Partial Result: U
02/01/2011 10:57:03 AM - SYSTEM STATS: Time:1.9943 Method:cmd.php Processes:10 Threads:N/A Hosts:33 HostsPerProcess:4 DataSources:137 RRDsProcessed:87
02/01/2011 10:57:03 AM - CMDPHP: Poller[0] WARNING: SNMP Get Timeout for Host:'xxxxxxxx', and OID:'.1.3.6.1.2.1.25.2.3.1.5.5'
02/01/2011 10:57:02 AM - CMDPHP: Poller[0] Host[43] DS[446] WARNING: Result from SNMP not valid. Partial Result: U
02/01/2011 10:57:02 AM - CMDPHP: Poller[0] WARNING: SNMP Get Timeout for Host:'xxxxxxxxx', and OID:'.1.3.6.1.2.1.2.2.1.16.2'
02/01/2011 10:57:02 AM - CMDPHP: Poller[0] Host[43] DS[446] WARNING: Result from SNMP not valid. Partial Result: U
02/01/2011 10:57:02 AM - CMDPHP: Poller[0] WARNING: SNMP Get Timeout for Host:'xxxxxx', and OID:'.1.3.6.1.2.1.2.2.1.10.2'
02/01/2011 10:56:06 AM - SYSTEM STATS: Time:5.0774 Method:cmd.php Processes:10 Threads:N/A Hosts:33 HostsPerProcess:4 DataSources:135 RRDsProcessed:78
02/01/2011 10:56:06 AM - CMDPHP: Poller[0] Host[41] DS[472] WARNING: Result from SNMP not valid. Partial Result: U
02/01/2011 10:56:06 AM - CMDPHP: Poller[0] WARNING: SNMP Get Timeout for Host:'xxxxxxxxx', and OID:'.1.3.6.1.2.1.2.2.1.16.2'
02/01/2011 10:56:06 AM - CMDPHP: Poller[0] Host[41] DS[472] WARNING: Result from SNMP not valid. Partial Result: U
02/01/2011 10:56:06 AM - CMDPHP: Poller[0] WARNING: SNMP Get Timeout for Host:'xxxxxxx', and OID:'.1.3.6.1.2.1.2.2.1.10.2'
02/01/2011 10:56:05 AM - CMDPHP: Poller[0] WARNING: SNMP Get Timeout for Host:'xxxxx', and OID:'.1.3.6.1.2.1.25.2.3.1.5.3'
02/01/2011 10:56:04 AM - CMDPHP: Poller[0] WARNING: SNMP GetNext Timeout for Host:'xxxxxxxx', and OID:'.1.3'
02/01/2011 10:56:03 AM - CMDPHP: Poller[0] WARNING: SNMP GetNext Timeout for Host:'xxxxxxx', and OID:'.1.3'
02/01/2011 10:56:02 AM - CMDPHP: Poller[0] WARNING: SNMP GetNext Timeout for Host:'xxxxxxx', and OID:'.1.3'
Cacti Cutting new graphs
Moderators: Developers, Moderators
Cacti Cutting new graphs
- Attachments
-
- cacti_cortando.jpg (64.43 KiB) Viewed 1321 times
- gandalf
- Developer
- Posts: 22383
- Joined: Thu Dec 02, 2004 2:46 am
- Location: Muenster, Germany
- Contact:
Re: Cacti Cutting new graphs
Please increase timeout for that host(s). You seem to suffer from lots of snmp timeouts
R.
R.
Re: Cacti Cutting new graphs
I already increased timeout and retry
updated RRDTOOL 1.4x
=(
the older graphs still fine
updated RRDTOOL 1.4x
=(
the older graphs still fine
- gandalf
- Developer
- Posts: 22383
- Joined: Thu Dec 02, 2004 2:46 am
- Location: Muenster, Germany
- Contact:
Re: Cacti Cutting new graphs
is not related to rrdtool but to polling. If increasing timeout does not help, I suggest performing a network trace (e.g. wireshark)02/01/2011 10:56:06 AM - CMDPHP: Poller[0] Host[41] DS[472] WARNING: Result from SNMP not valid. Partial Result: U
R.
Re: Cacti Cutting new graphs
I have an other feeling on this,
the cacti-guys enabled (after years of begging) 64 Bit - Counters in there basic interface templates (interface.xml change since 0.8.7.e nobody tell, update breaks database , big "thanks" to the guy who did that...) but they did not increase "max.value".
Also the basic interface-template has an issue with the ifSpeed. The problem is that ifHighspeed do not give the value in bit per second anymore, instead cisco decided to use Megabit (not Megabit). Also using IfSpeed as Max.Value is in any case a failure because it is the max traffic per second not per 5 minutes.
I would recommend you to set max.values of all 64Bit-counters using graphs to 2^64 -1 (18446744073709551615).
You "can" edit the max.value field directly in database ( do not remember to table right now.) via sql.
the cacti-guys enabled (after years of begging) 64 Bit - Counters in there basic interface templates (interface.xml change since 0.8.7.e nobody tell, update breaks database , big "thanks" to the guy who did that...) but they did not increase "max.value".
Also the basic interface-template has an issue with the ifSpeed. The problem is that ifHighspeed do not give the value in bit per second anymore, instead cisco decided to use Megabit (not Megabit). Also using IfSpeed as Max.Value is in any case a failure because it is the max traffic per second not per 5 minutes.
I would recommend you to set max.values of all 64Bit-counters using graphs to 2^64 -1 (18446744073709551615).
You "can" edit the max.value field directly in database ( do not remember to table right now.) via sql.
- gandalf
- Developer
- Posts: 22383
- Joined: Thu Dec 02, 2004 2:46 am
- Location: Muenster, Germany
- Contact:
Re: Cacti Cutting new graphs
? 64 bit is in since ages. But it's not the "default" (aka first in the list) entry of the graph template list in that data query. And where do you suppose was the change in interface.xml? I'm not aware of this. I hinestly do not remember all those changes by heart; but for helping out it would be better to know the exact issue you're talking aboutDeviloper wrote:the cacti-guys enabled (after years of begging) 64 Bit - Counters in there basic interface templates (interface.xml change since 0.8.7.e nobody tell, update breaks database , big "thanks" to the guy who did that...)
R.
Re: Cacti Cutting new graphs
I try to change 64 bits graphs, but the problems persists.
=(
deleting and create new one.
=(
deleting and create new one.
Who is online
Users browsing this forum: No registered users and 1 guest