-
-
Notifications
You must be signed in to change notification settings - Fork 405
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
cmd.php poller not stripping alpha from snmp get values #1501
Comments
So, it's numeric data with a string suffix. Yea, sorry, we have to fix that then. Just confirm that please. |
cmd.php poller not stripping alpha from snmp get values
This issue is resolved. Simply update cmd.php and lib/snmp.php from the develop branch. |
Thanks for the response @cigamit but after updating the 2 files you mention with the development version i get this log message and no graphs:04-04-2018 10:28:18 - RECACHE STATS: Poller: RecacheTime:45.7376 DevicesRecached:12 i copy the 1.1.35 version of the same 2 files (cmd.php and snmp.php) and everything is working smooth again |
I have fixed the remaining issue with the ASSERT. This was caused by using the php-snmp module. I had stopped using it in my test environment as it desperately needs a code change (which is of course no excuse for not testing), and I just don't have the time to invest in fixing that php module. |
Thanks for the support, i will wait the next official release for testing. |
cmd.php poller not stripping alpha from snmp get values (cherry picked from commit 636a277)
cmd.php poller not stripping alpha from snmp get values (cherry picked from commit 636a277)
I think you could be on to something there, though it does make me wonder if there is a placed that has been missed. |
I have some graphs of cisco receiver Temperature that worked just fine until this morning when i update my cacti instalattion, this is the debug log for one of the receivers:
27-03-2018 16:20:59 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[4] Device[19] Device[TNT Series] Thread[1] Graphs[TNT Series - Temperatures, TNT Series - Temperatures] Graphs[TNT Series - Temperatures, TNT Series - Temperatures] Graphs[TNT Series - Temperatures, TNT Series - Temperatures] Graphs[TNT Series - Temperatures, TNT Series - Temperatures] DS[TNT Series - CurrTemp, TNT Series - FPGAT, TNT Series - I1T, TNT Series - I2T]
27-03-2018 16:20:59 - POLLER: Poller[Main Poller] Device[19] Device[TNT Series] Graphs[TNT Series - Traffic - 192.168.169.64 (ETHER0), TNT Series - Traffic - 192.168.169.64 (ETHER0)] DS[TNT Series - Traffic - 192.168.169.64/ETHER0] SNMP: v2: 192.168.169.64, dsname: traffic_out, oid: .1.3.6.1.2.1.2.2.1.16.2, output: 6335189
27-03-2018 16:20:59 - POLLER: Poller[Main Poller] Device[19] Device[TNT Series] Graphs[TNT Series - Traffic - 192.168.169.64 (ETHER0), TNT Series - Traffic - 192.168.169.64 (ETHER0)] DS[TNT Series - Traffic - 192.168.169.64/ETHER0] SNMP: v2: 192.168.169.64, dsname: traffic_in, oid: .1.3.6.1.2.1.2.2.1.10.2, output: 13454229
27-03-2018 16:20:59 - POLLER: Poller[Main Poller] Device[19] Device[TNT Series] Graphs[TNT Series - Temperatures, TNT Series - Temperatures] DS[TNT Series - I2T] SNMP: v2: 192.168.169.64, dsname: PVU_In2Temp, oid: 1.3.6.1.4.1.1429.2.2.5.18.2.1.1.3.5, output: U
27-03-2018 16:20:59 - POLLER: Poller[Main Poller] Device[19] Device[TNT Series] Graphs[TNT Series - Temperatures, TNT Series - Temperatures] DS[TNT Series - I1T] SNMP: v2: 192.168.169.64, dsname: PVU_In1Temp, oid: 1.3.6.1.4.1.1429.2.2.5.18.2.1.1.3.4, output: U
27-03-2018 16:20:59 - POLLER: Poller[Main Poller] Device[19] Device[TNT Series] Graphs[TNT Series - Temperatures, TNT Series - Temperatures] DS[TNT Series - FPGAT] SNMP: v2: 192.168.169.64, dsname: PVU_FPGATemp, oid: 1.3.6.1.4.1.1429.2.2.5.18.2.1.1.3.7, output: U
27-03-2018 16:20:59 - POLLER: Poller[Main Poller] Device[19] Device[TNT Series] Graphs[TNT Series - Temperatures, TNT Series - Temperatures] DS[TNT Series - CurrTemp] SNMP: v2: 192.168.169.64, dsname: PVU_CTemp, oid: 1.3.6.1.4.1.1429.2.2.5.18.2.1.1.3.1, output: U
27-03-2018 16:20:59 - POLLER: Poller[Main Poller] Device[19] Device[TNT Series] Graphs[TNT Series - Signal, TNT Series - Signal] DS[TNT Series - Signal] SNMP: v2: 192.168.169.64, dsname: PVU_Signal, oid: 1.3.6.1.4.1.1429.2.2.5.5.3.1.1.7.1, output: -47
27-03-2018 16:20:59 - POLLER: Poller[Main Poller] Device[19] Device[TNT Series] Graphs[TNT Series - Alerts & Warnings, TNT Series - Alerts & Warnings] DS[TNT Series - Warn] SNMP: v2: 192.168.169.64, dsname: PVU_Warn, oid: 1.3.6.1.4.1.1429.2.2.5.17.1.2.0, output: 1
27-03-2018 16:20:59 - POLLER: Poller[Main Poller] Device[19] Device[TNT Series] Graphs[TNT Series - Alerts & Warnings, TNT Series - Alerts & Warnings] DS[TNT Series - Alert] SNMP: v2: 192.168.169.64, dsname: PVU_Alert, oid: 1.3.6.1.4.1.1429.2.2.5.17.1.1.0, output: 0
27-03-2018 16:20:59 - POLLER: Poller[Main Poller] Device[19] Device[TNT Series] Graphs[TNT Series - Carrier to Noise Margin, TNT Series - Carrier to Noise Margin] DS[TNT Series - CN] SNMP: v2: 192.168.169.64, dsname: PVU_CN, oid: 1.3.6.1.4.1.1429.2.2.5.5.3.1.1.6.1, output: 1.0
27-03-2018 16:20:59 - POLLER: Poller[Main Poller] Device[19] Device[TNT Series] RECACHE DQ[SNMP - Interface Statistics] OID: .1.3.6.1.2.1.1.3.0, output: 36632898
27-03-2018 16:20:59 - POLLER: Poller[Main Poller] Device[19] Device[TNT Series] RECACHE: Processing 1 items in the auto reindex cache for '192.168.169.64'.
27-03-2018 16:20:59 - POLLER: Poller[Main Poller] Device[19] Device[TNT Series] STATUS: Device '192.168.169.64' is UP.
## and this is the snmp check with an external program using the same OIDs:
----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: MONITOR-PC Interface: 192.168.169.9
27/03/2018 04:20:57 p.m. (45 ms) : Device: 192.168.169.64
27/03/2018 04:20:57 p.m. (50 ms) : SNMP V2c
27/03/2018 04:20:57 p.m. (51 ms) : Custom OID 1.3.6.1.4.1.1429.2.2.5.18.2.1.1.3.1
27/03/2018 04:20:57 p.m. (86 ms) : SNMP Datatype: ASN_OCTET_STR
27/03/2018 04:20:57 p.m. (88 ms) : -------
27/03/2018 04:20:57 p.m. (89 ms) : Value: 30.0øC
27/03/2018 04:20:57 p.m. (90 ms) : Done
----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: MONITOR-PC Interface: 192.168.169.9
27/03/2018 04:21:51 p.m. (3 ms) : Device: 192.168.169.64
27/03/2018 04:21:51 p.m. (5 ms) : SNMP V2c
27/03/2018 04:21:51 p.m. (7 ms) : Custom OID 1.3.6.1.4.1.1429.2.2.5.18.2.1.1.3.5
27/03/2018 04:21:51 p.m. (23 ms) : SNMP Datatype: ASN_OCTET_STR
27/03/2018 04:21:51 p.m. (25 ms) : -------
27/03/2018 04:21:51 p.m. (27 ms) : Value: 28.0øC
27/03/2018 04:21:51 p.m. (30 ms) : Done
----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: MONITOR-PC Interface: 192.168.169.9
27/03/2018 04:21:55 p.m. (5 ms) : Device: 192.168.169.64
27/03/2018 04:21:55 p.m. (8 ms) : SNMP V2c
27/03/2018 04:21:55 p.m. (11 ms) : Custom OID 1.3.6.1.4.1.1429.2.2.5.18.2.1.1.3.4
27/03/2018 04:21:55 p.m. (25 ms) : SNMP Datatype: ASN_OCTET_STR
27/03/2018 04:21:55 p.m. (29 ms) : -------
27/03/2018 04:21:55 p.m. (32 ms) : Value: 32.0øC
27/03/2018 04:21:55 p.m. (36 ms) : Done
----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: MONITOR-PC Interface: 192.168.169.9
27/03/2018 04:21:59 p.m. (7 ms) : Device: 192.168.169.64
27/03/2018 04:21:59 p.m. (11 ms) : SNMP V2c
27/03/2018 04:21:59 p.m. (15 ms) : Custom OID 1.3.6.1.4.1.1429.2.2.5.18.2.1.1.3.7
27/03/2018 04:21:59 p.m. (31 ms) : SNMP Datatype: ASN_OCTET_STR
27/03/2018 04:21:59 p.m. (35 ms) : -------
27/03/2018 04:21:59 p.m. (39 ms) : Value: 47.0øC
27/03/2018 04:21:59 p.m. (59 ms) : Done
## I think it could be an octet datatype problem in the new version, thanks in advance.
The text was updated successfully, but these errors were encountered: