-
-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on interpretation of snmpUtime, when to big #4428
Comments
This may be the difference between 32-bit and 64-bit uptime counters. Uptime is recorded in seconds if I remember rightly as I used to have this issue on older 32-bit hardware making Cacti think it had rebooted when it hadn't. What is your OS/Arch for all involved systems? |
My 1.2.18 run on centos 10.0-1160.42.2.el7.x86_64 My 1.2.17 run on centos 10.0-1160.42.2.el7.x86_64 The only point can find is that on has PHP 7.4.2 on the 1.2.17 version, the other one has 7.4.14 where cacti 1.2.18 run. Otherwise, it should be same same! As for the client I'm polling there are both the same device Cisco Switch |
What about the SNMP libraries? Are you using php-snmp or net-snmp? |
php-snmp |
Don't think the problem is on the polling part. Mineur difference. |
I think we need to move that column to a bigint later tonight my time unless @netniV want's to hammer it out. |
Okay, this is resolved for the 1.2.19 release. You can just hand run the two SQL alters at the bottom of the 1_2_19.php file if you want to hack it in. |
Thanks for keeping your eye on the ball. |
Can you reopen it, it dosen't solve the problem. Here is the ouput of my DB, the first 2 record are in SNMP v3 and are show as DOWN, the last one is in SNMP V2, and see as UP. I'm looking on that track to see if it's a SNMP version problem. "3159","1","3","8","core","10.0.2.26",," EZV: En service","SR02129 SR02128 ","telvlsn","3","SNMP_USER","SNMP_KEY","SHA","SNMP_KEY","AES128",,,"161","500","Cisco IOS Software [Fuji], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 16.9.5, RELEASE SOFTWARE (fc1) "3160","1","3","7","vbb","10.1.128.10",,,,"telvlsn","3","SNMP_USER","SNMP_KEY","SHA","SNMP_KEY","AES128",,,"161","500","Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software (cat4500e-UNIVERSALK9-M), Version 03.08.08.E RELEASE SOFTWARE (fc3) "4515","1","3","9","pdp","10.128.1.41",," EZV: En service","SR01288 ","telvlsn","2",,,,,,,,"161","500","Cisco NX-OS(tm) n5000, Software (n5000-uk9), Version 5.1(3)N2(1b), RELEASE SOFTWARE Copyright (c) 2002-2011 by Cisco Systems, Inc. Device Manager Version 5.2(1), Compiled 8/31/2012 17:00:00","iso.3.6.1.4.1.9.12.3.1.3.1084","1643546154","","PDP","LOCATION","4","1","23","400","1","10","-1","1",,,"on",,"0","0","0","1","0","3","0","2021-08-04 18:05:05","2021-08-04 18:19:02","Device did not respond to SNMP, ICMP: Ping timed out","0.00000","55.65691","0.00000","1.20858","0.046","371268","14","99.99620","2021-10-19 08:35:02","SSI154300JT","N5K-C5548UP",,"of","UNAW2m3sFF+9uSzZf","1","off","off","off","PASSWORD","bundle" |
Using spine or cmd.php? Problem could be spine at this point. |
I'm using spine, and I'm looking into it. |
So here is the output of spine: Total[0.7770] Device[3160] DEBUG: Entering ICMP Ping Total[0.7851] Device[3160] HT[1] NOTE: There are '350' Polling Items for this Device |
Open a spine bug would you. Cacti is fixed. |
Let me take that back, spine uses a string. So, it might have something to do with the snmp library. In the mean time. Edit poller.c and make the modification as in the highlighted row below: Then, make spine and run as follows: ./spine -R --mibs --first host_id1 --last host_id2
<snip>
NOTE: The SNMP Uptime was 8536518
NOTE: The SNMP Uptime was 8537397
NOTE: The SNMP Uptime was 8536553
NOTE: The SNMP Uptime was 318654799
NOTE: The SNMP Uptime was 318654799
Time: 2.8684 s, Threads: 4, Devices: 47 Which should show the output above. Let us know if the value is correct there. |
Continuing this discussion on the spine side. |
Okay, made a few more GUI changes so that when you edit the device, you also see the correct uptime. Also addressed cmd.php and reindexing there. |
Just wondering where did you change the GUI |
What do you mean? If you edit the device, it grabs uptime dynamically. |
Ho ok, I where wondering if you add a field. |
This particular check was not caught. Thanks @jdcoats
The wrong OID uptime is inserted into the poller_reindex table.
On a device when uptime is to long (more than 224 days I think) the device is seen as down, if the monitoring is set to snmpUptime and ping.
As an exemple I have this:
Uptime: 4190934469 (485days, 1hours, 29minutes)
and device is down.
ON 1.2.18 I have this:
And on 1.2.17
The text was updated successfully, but these errors were encountered: