-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
data not being pushed to poller_output table despite all values are retrieved properly #5115
Comments
This sounds like a bug we found in 1.2.22 and already fixed @gj00354347. I'm assuming you are using boost? If so, it's |
If your pulling down the latest boost updates on 1.2.22 make sure to also
download rrdcheck.php in the lib folder
…On Thu., Dec. 22, 2022, 5:31 a.m. TheWitness, ***@***.***> wrote:
This sounds like a bug we found in 1.2.22 and already fixed @gj00354347
<https://github.com/gj00354347>. I'm assuming you are using boost? If so,
it's lib/boost.pho and poller_boost.php.
—
Reply to this email directly, view it on GitHub
<#5115 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADGEXTHC4NQTVC2FO7FWIPDWOQUYRANCNFSM6AAAAAATGN37QY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
yes Larry , we are using boost so I did not get this "it's in lib/boost.php and poller_boost.php" . Can you please elaborate this step so that I can apply the fix . |
Hi Sean , Many Thanks , |
@gj00354347, Sean likely has a better recollection, but basically, the RRDupdates were being skipped for a reason. You can look at the history in lib/boost.php and you will see the update. Let me try to get the command changelog entry for your management. |
The issue was #4941 and there were fivecommits. Just check the history here: |
Describe the bug
HI Developers ,
we have come across an issue where the customer has complained of NAN in the graphs , so we began troubleshooting and did snmpwalk and found that values are being retrieved that too very quickly , which rules out the timeout or unreachability issue .
then we enabled the debug for that device and found that the data is being retrieved properly in the logs and then we tried to look for the rrd_name or even local_data_id in poller_output table and much to our surprise i could not find that .
yes one more info , this polling is done on remote poller rmvirtual-machine and then polled data is transferred to poller_output on main poller mainpoller .
for the sake of convenience i am taking example of one data source dsname: asa_act_connections and see the log below of remote poller
2022-12-22 07:06:40 - SPINE: Poller[4] PID[62059] PT[140323862853376] Device[287] HT[1] DS[14772] TT[4.05] SNMP: v2: IP, dsname: asa_act_connections, oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 9
2022-12-22 07:11:41 - SPINE: Poller[4] PID[6674] PT[140002496202496] Device[287] HT[1] DS[14772] TT[3.95] SNMP: v2: IP, dsname: asa_act_connection , oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 5
2022-12-22 07:16:41 - SPINE: Poller[4] PID[16341] PT[140274045789952] Device[287] HT[1] DS[14772] TT[4.64] SNMP: v2: IP, dsname: asa_act_connections, oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 5
2022-12-22 07:21:40 - SPINE: Poller[4] PID[25994] PT[140552729257728] Device[287] HT[1] DS[14772] TT[3.82] SNMP: v2: IP, dsname: asa_act_connections, oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 5
2022-12-22 07:26:40 - SPINE: Poller[4] PID[35647] PT[140019691943680] Device[287] HT[1] DS[14772] TT[5.70] SNMP: v2: IP, dsname: asa_act_connections, oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 5
2022-12-22 07:31:40 - SPINE: Poller[4] PID[45910] PT[139822626748160] Device[287] HT[1] DS[14772] TT[3.94] SNMP: v2: IP, dsname: asa_act_connections, oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 36
2022-12-22 07:36:40 - SPINE: Poller[4] PID[55596] PT[140092530923264] Device[287] HT[1] DS[14772] TT[5.77] SNMP: v2: IP, dsname: asa_act_connections, oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 7
2022-12-22 07:41:40 - SPINE: Poller[4] PID[65208] PT[139916981810944] Device[287] HT[1] DS[14772] TT[4.25] SNMP: v2: IP, dsname: asa_act_connections, oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 6
2022-12-22 07:46:40 - SPINE: Poller[4] PID[9860] PT[139963102385920] Device[287] HT[1] DS[14772] TT[5.79] SNMP: v2: IP, dsname: asa_act_connection , oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 5
2022-12-22 07:51:39 - SPINE: Poller[4] PID[19521] PT[140321725798144] Device[287] HT[1] DS[14772] TT[3.62] SNMP: v2: IP, dsname: asa_act_connections, oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 5
2022-12-22 07:56:40 - SPINE: Poller[4] PID[29177] PT[140697684403968] Device[287] HT[1] DS[14772] TT[13.62] SNMP: v2: IP, dsname: asa_act_connections, oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 5
2022-12-22 08:01:41 - SPINE: Poller[4] PID[40526] PT[140377499621120] Device[287] HT[1] DS[14772] TT[3.64] SNMP: v2: IP, dsname: asa_act_connections, oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 5
2022-12-22 08:06:40 - SPINE: Poller[4] PID[50253] PT[140595402102528] Device[287] HT[1] DS[14772] TT[3.69] SNMP: v2: IP, dsname: asa_act_connections, oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 9
2022-12-22 08:11:41 - SPINE: Poller[4] PID[59907] PT[140205675751168] Device[287] HT[1] DS[14772] TT[5.74] SNMP: v2: IP, dsname: asa_act_connections, oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 7
2022-12-22 08:16:39 - SPINE: Poller[4] PID[4483] PT[140210099435264] Device[287] HT[1] DS[14772] TT[6.97] SNMP: v2: IP, dsname: asa_act_connection , oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 5
2022-12-22 08:21:39 - SPINE: Poller[4] PID[14185] PT[140588951258880] Device[287] HT[1] DS[14772] TT[4.42] SNMP: v2: IP, dsname: asa_act_connections, oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 5
2022-12-22 08:26:39 - SPINE: Poller[4] PID[23842] PT[139780297840384] Device[287] HT[1] DS[14772] TT[3.70] SNMP: v2: IP, dsname: asa_act_connections, oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 5
2022-12-22 08:31:40 - SPINE: Poller[4] PID[33641] PT[139968001332992] Device[287] HT[1] DS[14772] TT[4.29] SNMP: v2: IP, dsname: asa_act_connections, oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 5
2022-12-22 08:36:39 - SPINE: Poller[4] PID[43341] PT[139996799428352] Device[287] HT[1] DS[14772] TT[4.29] SNMP: v2: IP, dsname: asa_act_connections, oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 5
2022-12-22 08:41:38 - SPINE: Poller[4] PID[52969] PT[140097504655104] Device[287] HT[1] DS[14772] TT[9.60] SNMP: v2: IP, dsname: asa_act_connections, oid: 1.3.6.1.4.1.9.9.491.1.1.1.6.0, value: 5
now see the output of sql query on main poller
MariaDB [cacti]> select * from poller_output where rrd_name='Webvpn_session';
Empty set (1.46 sec)
MariaDB [cacti]> select * from poller_output where rrd_name='asa_act_connections';
Empty set (1.41 sec)
MariaDB [cacti]> select count(1) from poller_output where rrd_name='traffic_in'; ---this one just to show that poller_output is not empty .
+----------+
| count(1) |
+----------+
| 165017 |
+----------+
1 row in set (1.44 sec)
now the same query on remote poller
remote poller_output is completely empty as after polling the data is passed to poller_output of main poller .
MariaDB [cacti]> select * from poller_output where rrd_name='asa_act_connections';
Empty set (0.00 sec)
MariaDB [cacti]> select * from poller_output where rrd_name like '%traffic%';
Empty set (0.00 sec)
spine version 1.2.22
cacti - 1.2.18
main poller and remote poller
yes there are many devices for that remote poller and all working fine except 4 devices .
we have done poller reindexing , poller recache and checked the logs , in the logs all ok but somehow the data is not being passed .
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information)
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information)
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: