Reindex Error at 1.2.2

Post general support questions here that do not specifically fall into the Linux or Windows categories.

Moderators: Moderators, Developers

Author
Message
mpj
Posts: 16
Joined: Wed Jun 01, 2005 10:24 am
Contact:

Reindex Error at 1.2.2

#1 Post by mpj » Wed Mar 06, 2019 1:10 pm

I am running Cacti 1.2.2 on Ubuntu 18.04.2 LTS. I upgraded from 1.2.1 last night, and now I am getting for most of my SNMP_Informant Windows servers the following error message when I try to reindex the CPU's or the entire device:
REINDEX ERROR: Re-Indexing failed due to a NULL sort field for Device[MACHINENAMELINK] and DQ[SNMP_Informant_Standard - CPU Statistics]. Can not continue with Re-Index.
I have never seen this error before and I have been running Cacti since version 0.8.7.

Also, I have had several devices that have caused this error:
POLLER: Poller[Main Poller] WARNING: You have 18 Devices with bad SNMP Indexes. Devices: {LIST OF DEVICES} totalling 428 Data Sources. Please Either Re-Index, Delete or Disable these Data Sources.
Is there an easier way to resolve this rather than delete the device or all graphs and data sources of the device then re-create?

Thank you for all your help.

--MPJ

netniV
Cacti Guru User
Posts: 2978
Joined: Sun Aug 27, 2017 12:05 am

Re: Reindex Error at 1.2.2

#2 Post by netniV » Wed Mar 06, 2019 6:13 pm

Go to your Datasources (Console -> Management -> Datasources), change the status column to Bad Indexes and it should show all those which have an indexed that is invalid. You will then have to manually correct those. It occurred due to a bug in 1.2.0/1.2.1.

mpj
Posts: 16
Joined: Wed Jun 01, 2005 10:24 am
Contact:

Re: Reindex Error at 1.2.2

#3 Post by mpj » Wed Mar 06, 2019 6:41 pm

Awesome! Thank you! That is better than recreating everything for each of those devices.

svenbosmans2
Posts: 3
Joined: Wed Mar 27, 2019 7:30 am

Re: Reindex Error at 1.2.2

#4 Post by svenbosmans2 » Thu Mar 28, 2019 9:44 am

netniV wrote:Go to your Datasources (Console -> Management -> Datasources), change the status column to Bad Indexes and it should show all those which have an indexed that is invalid. You will then have to manually correct those. It occurred due to a bug in 1.2.0/1.2.1.
What do you mean with manually correct those? recreate the graph?

Regards

Sven

netniV
Cacti Guru User
Posts: 2978
Joined: Sun Aug 27, 2017 12:05 am

Re: Reindex Error at 1.2.2

#5 Post by netniV » Thu Mar 28, 2019 2:34 pm

Edit the datasource and set the index value to the correct one. That should then stick.

arek
Posts: 4
Joined: Fri Sep 27, 2019 7:02 am

Re: Reindex Error at 1.2.2

#6 Post by arek » Fri Sep 27, 2019 7:19 am

How to figure out correct valid value? For example I have partition being monitored, Index Type is dskDevice, Index Value is "/dev/mapper/vgstorage-lv_db01" and it shows up in "Bad indexes" list. What value will be correct one for this ?

I'm looking for more information about the problem (like commit which introduced the bug and fixed it, github issue or anything else that will help me figure out what exactly happened and what is needed to fix this).

Maybe it is possible to fix this on sql level (if having older DB backups for example) ?

User avatar
Osiris
Cacti Pro User
Posts: 863
Joined: Mon Jan 05, 2015 10:10 am

Re: Reindex Error at 1.2.2

#7 Post by Osiris » Sat Sep 28, 2019 6:10 am

Get to 1.2.7 as soon as it's released. There were a few speed bumps in the early 1.2.x around reindexing. It's mostly fixed in 1.2.6, but there were a few regressions in 1.2.6. So, according to GitHub, 1.2.7 is scheduled for release this weekend.
Before history, there was a paradise, now dust.


arek
Posts: 4
Joined: Fri Sep 27, 2019 7:02 am

Re: Reindex Error at 1.2.2

#9 Post by arek » Wed Oct 02, 2019 2:59 am

There are still bugs it seems.


Variant of this query is used by cacti to find "Bad indexes" in web interface. Ok, so let see what bad indexes we have in my setup:

Code: Select all

09:45:23 mysql{6}> SELECT dl.id, dl.snmp_index, dl.snmp_query_id, dtd.local_data_id, dtd.name_cache, dtd.active, dtd.rrd_step, dt.name AS data_template_name, dl.host_id, dtd.data_source_profile_id FROM data_local AS dl INNER JOIN data_template_data AS dtd ON dl.id=dtd.local_data_id LEFT JOIN data_template AS dt ON dt.id=dl.data_template_id LEFT JOIN host AS h ON h.id = dl.host_id WHERE  (dl.snmp_index = "" AND dl.snmp_query_id > 0) ORDER BY `name_cache` ASC LIMIT 0,100;
+------+------------+---------------+---------------+----------------------------------------------------------+--------+----------+----------------------------+---------+------------------------+
| id   | snmp_index | snmp_query_id | local_data_id | name_cache                                               | active | rrd_step | data_template_name         | host_id | data_source_profile_id |
+------+------------+---------------+---------------+----------------------------------------------------------+--------+----------+----------------------------+---------+------------------------+
| 2367 |            |             2 |          2367 | firma2.example.com - Partition - /dev/mapper/pve-root       | on     |      300 | ucd/net - Hard Drive Space |      89 |                      2 |
| 2370 |            |             2 |          2370 | firma2.example.com - Partition - /dev/mapper/pve-root       | on     |      300 | ucd/net - Hard Drive Space |      89 |                      2 |
| 2369 |            |             2 |          2369 | firma2.example.com - Partition - /dev/mapper/pve-root       | on     |      300 | ucd/net - Hard Drive Space |      89 |                      2 |
| 2368 |            |             2 |          2368 | firma2.example.com - Partition - /dev/mapper/pve-root       | on     |      300 | ucd/net - Hard Drive Space |      89 |                      2 |
| 1532 |            |            16 |          1532 | mbox1.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |       5 |                      2 |
| 1540 |            |            16 |          1540 | mbox1.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |       5 |                      2 |
| 1536 |            |            16 |          1536 | mbox1.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |       5 |                      2 |
| 1520 |            |            16 |          1520 | mbox2.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      33 |                      2 |
| 1525 |            |            16 |          1525 | mbox2.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      33 |                      2 |
| 1524 |            |            16 |          1524 | mbox2.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      33 |                      2 |
| 1529 |            |            16 |          1529 | mbox2.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      33 |                      2 |
| 1521 |            |            16 |          1521 | mbox2.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      33 |                      2 |
| 1528 |            |            16 |          1528 | mbox2.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      33 |                      2 |
| 1498 |            |            16 |          1498 | mbox4.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      51 |                      2 |
| 1506 |            |            16 |          1506 | mbox4.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      51 |                      2 |
| 1502 |            |            16 |          1502 | mbox4.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      51 |                      2 |
| 1424 |            |            16 |          1424 | mbox5.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      65 |                      2 |
| 1432 |            |            16 |          1432 | mbox5.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      65 |                      2 |
| 1428 |            |            16 |          1428 | mbox5.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      65 |                      2 |
| 2400 |            |             1 |          2400 | poznan.rtr.example.com - Traffic - 1.1.1.1 - eth1.7 | on     |      300 | Interface - Traffic        |      90 |                      2 |
| 1894 |            |             1 |          1894 | vps1.example.com - Traffic - |query_ifName|                 | on     |      300 | Interface - Traffic        |      80 |                      2 |
| 1632 |            |             2 |          1632 | vps2.example.com - Partition - /dev/mapper/pve-root         | on     |      300 | ucd/net - Hard Drive Space |      77 |                      2 |
| 1635 |            |             2 |          1635 | vps2.example.com - Partition - /dev/mapper/pve-root         | on     |      300 | ucd/net - Hard Drive Space |      77 |                      2 |
| 1631 |            |             2 |          1631 | vps2.example.com - Partition - /dev/mapper/pve-root         | on     |      300 | ucd/net - Hard Drive Space |      77 |                      2 |
| 1634 |            |             2 |          1634 | vps2.example.com - Partition - /dev/mapper/pve-root         | on     |      300 | ucd/net - Hard Drive Space |      77 |                      2 |
| 1633 |            |             2 |          1633 | vps2.example.com - Partition - /dev/mapper/pve-root         | on     |      300 | ucd/net - Hard Drive Space |      77 |                      2 |
| 1636 |            |             2 |          1636 | vps2.example.com - Partition - /dev/mapper/pve-root         | on     |      300 | ucd/net - Hard Drive Space |      77 |                      2 |
+------+------------+---------------+---------------+----------------------------------------------------------+--------+----------+----------------------------+---------+------------------------+
27 rows in set (0.00 sec)

So lets try to fix empy snmp_index:

Code: Select all

09:45:35 mysql{7}> UPDATE data_local set snmp_index=1 WHERE id IN (2367,2370,2369,2368,1532,1540,1536,1520,1525,1524,1529,1521,1528,1498,1506,1502,1424,1432,1428,2400,1894,1632,1635,1631,1634,1633,1636);
Query OK, 27 rows affected (0.05 sec)
Rows matched: 27  Changed: 27  Warnings: 0
Are there no bad indexes anymore?

Code: Select all

09:47:27 mysql{8}> SELECT dl.id, dl.snmp_index, dl.snmp_query_id, dtd.local_data_id, dtd.name_cache, dtd.active, dtd.rrd_step, dt.name AS data_template_name, dl.host_id, dtd.data_source_profile_id FROM data_local AS dl INNER JOIN data_template_data AS dtd ON dl.id=dtd.local_data_id LEFT JOIN data_template AS dt ON dt.id=dl.data_template_id LEFT JOIN host AS h ON h.id = dl.host_id WHERE  (dl.snmp_index = "" AND dl.snmp_query_id > 0) ORDER BY `name_cache` ASC LIMIT 0,100;
Empty set (0.00 sec)
So lets try reindexing:

Code: Select all

[[email protected] cli]$ cd /usr/share/cacti/cli; ./poller_reindex_hosts.php --id=All; ./poller_data_sources_reapply_names.php --id=All; ./poller_graphs_reapply_names.php -id=All
WARNING: Do not interrupt this script.  Reindexing can take quite some time
...................................................................................................................................................................................WARNING: Do not interrupt this script.  Interrupting during rename can cause issues
.....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................WARNING: Do not interrupt this script.  Interrupting during rename can cause issues
...................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
[[email protected] cli]$
And recheck if there are bad indexes again:

Code: Select all

09:47:29 mysql{9}> SELECT dl.id, dl.snmp_index, dl.snmp_query_id, dtd.local_data_id, dtd.name_cache, dtd.active, dtd.rrd_step, dt.name AS data_template_name, dl.host_id, dtd.data_source_profile_id FROM data_local AS dl INNER JOIN data_template_data AS dtd ON dl.id=dtd.local_data_id LEFT JOIN data_template AS dt ON dt.id=dl.data_template_id LEFT JOIN host AS h ON h.id = dl.host_id WHERE  (dl.snmp_index = "" AND dl.snmp_query_id > 0) ORDER BY `name_cache` ASC LIMIT 0,100;
+------+------------+---------------+---------------+----------------------------------------------------------+--------+----------+----------------------------+---------+------------------------+
| id   | snmp_index | snmp_query_id | local_data_id | name_cache                                               | active | rrd_step | data_template_name         | host_id | data_source_profile_id |
+------+------------+---------------+---------------+----------------------------------------------------------+--------+----------+----------------------------+---------+------------------------+
| 2367 |            |             2 |          2367 | firma2.example.com - Partition - /dev/mapper/pve-root       | on     |      300 | ucd/net - Hard Drive Space |      89 |                      2 |
| 2370 |            |             2 |          2370 | firma2.example.com - Partition - /dev/mapper/pve-root       | on     |      300 | ucd/net - Hard Drive Space |      89 |                      2 |
| 2369 |            |             2 |          2369 | firma2.example.com - Partition - /dev/mapper/pve-root       | on     |      300 | ucd/net - Hard Drive Space |      89 |                      2 |
| 2368 |            |             2 |          2368 | firma2.example.com - Partition - /dev/mapper/pve-root       | on     |      300 | ucd/net - Hard Drive Space |      89 |                      2 |
| 1532 |            |            16 |          1532 | mbox1.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |       5 |                      2 |
| 1540 |            |            16 |          1540 | mbox1.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |       5 |                      2 |
| 1536 |            |            16 |          1536 | mbox1.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |       5 |                      2 |
| 1520 |            |            16 |          1520 | mbox2.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      33 |                      2 |
| 1525 |            |            16 |          1525 | mbox2.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      33 |                      2 |
| 1524 |            |            16 |          1524 | mbox2.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      33 |                      2 |
| 1529 |            |            16 |          1529 | mbox2.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      33 |                      2 |
| 1521 |            |            16 |          1521 | mbox2.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      33 |                      2 |
| 1528 |            |            16 |          1528 | mbox2.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      33 |                      2 |
| 1498 |            |            16 |          1498 | mbox4.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      51 |                      2 |
| 1506 |            |            16 |          1506 | mbox4.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      51 |                      2 |
| 1502 |            |            16 |          1502 | mbox4.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      51 |                      2 |
| 1424 |            |            16 |          1424 | mbox5.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      65 |                      2 |
| 1432 |            |            16 |          1432 | mbox5.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      65 |                      2 |
| 1428 |            |            16 |          1428 | mbox5.example.com - Device I/O -ram0                        | on     |      300 | ucd/net - Device I/O       |      65 |                      2 |
| 2400 |            |             1 |          2400 | poznan.rtr.example.com - Traffic - 1.1.1.1 - eth1.7 | on     |      300 | Interface - Traffic        |      90 |                      2 |
| 1894 |            |             1 |          1894 | vps1.example.com - Traffic - |query_ifName|                 | on     |      300 | Interface - Traffic        |      80 |                      2 |
+------+------------+---------------+---------------+----------------------------------------------------------+--------+----------+----------------------------+---------+------------------------+
21 rows in set (0.01 sec)

09:52:52 mysql{10}>

And unfortunately reindexing introduced bad indexes again. Why?
Last edited by arek on Thu Oct 03, 2019 3:07 am, edited 1 time in total.

User avatar
TheWitness
Developer
Posts: 14817
Joined: Tue May 14, 2002 5:08 pm
Location: MI, USA
Contact:

Re: Reindex Error at 1.2.2

#10 Post by TheWitness » Wed Oct 02, 2019 5:13 am

Let's just pick the one case:
| 2367 | | 2 | 2367 | firma2.example.com - Partition - /dev/mapper/pve-root | on | 300 | ucd/net - Hard Drive Space | 89 | 2 |
To get more information, on why it's broken:
SELECT * FROM host_snmp_cache WHERE snmp_query_id = 2367 AND host_id = ? AND field_value LIKE '%pve-root';
If it does not come back with anything, that is the reason that it's broken. If the value is gone from the host_snmp_cache, are these values transient in other words, do they come and go? Please advise.
True understanding begins only when we realize how little we truly understand...

Life is an adventure, let yours begin with Cacti!

Author of MacTrack, Boost, CLog, SpikeKill, Platform RTM, DSStats, maintainer of Spine, lot's of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Central Plugin Repository
Central Templates Repository


I'm still out there people. Getting excited for Cacti 1.2. I think it will be a great release.

User avatar
TheWitness
Developer
Posts: 14817
Joined: Tue May 14, 2002 5:08 pm
Location: MI, USA
Contact:

Re: Reindex Error at 1.2.2

#11 Post by TheWitness » Wed Oct 02, 2019 5:17 am

If you are using Cacti 1.2.6 or 1.2.7, and these indexes are indeed transient, or you don't want to see these warning messages, you can set
<index_transient>true</index_transient>
In the Resource XML file for the Data Query, and these messages will disappear after you correct the indexes one more time manually.
True understanding begins only when we realize how little we truly understand...

Life is an adventure, let yours begin with Cacti!

Author of MacTrack, Boost, CLog, SpikeKill, Platform RTM, DSStats, maintainer of Spine, lot's of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Central Plugin Repository
Central Templates Repository


I'm still out there people. Getting excited for Cacti 1.2. I think it will be a great release.

arek
Posts: 4
Joined: Fri Sep 27, 2019 7:02 am

Re: Reindex Error at 1.2.2

#12 Post by arek » Thu Oct 03, 2019 3:04 am

TheWitness wrote:
Wed Oct 02, 2019 5:13 am
SELECT * FROM host_snmp_cache WHERE snmp_query_id = 2367 AND host_id = ? AND field_value LIKE '%pve-root';
If it does not come back with anything, that is the reason that it's broken. If the value is gone from the host_snmp_cache, are these values transient in other words, do they come and go? Please advise.
Hm, why 2367 and not 2 (snmp_query_id is 2 in data_local table) ?

Code: Select all

10:02:32 mysql{13}> SELECT * FROM host_snmp_cache WHERE field_value LIKE '%pve-root';
+---------+---------------+------------+----------------------+------------+---------------------------+---------+---------------------+
| host_id | snmp_query_id | field_name | field_value          | snmp_index | oid                       | present | last_updated        |
+---------+---------------+------------+----------------------+------------+---------------------------+---------+---------------------+
|      77 |             2 | dskDevice  | /dev/mapper/pve-root | 1          | .1.3.6.1.4.1.2021.9.1.3.1 |       1 | 2019-09-29 01:21:04 |
|      77 |             2 | dskDevice  | /dev/mapper/pve-root | 3          | .1.3.6.1.4.1.2021.9.1.3.3 |       1 | 2019-09-29 01:21:04 |
|      89 |             2 | dskDevice  | /dev/mapper/pve-root | 1          | .1.3.6.1.4.1.2021.9.1.3.1 |       1 | 2019-10-02 09:48:39 |
|      89 |             2 | dskDevice  | /dev/mapper/pve-root | 3          | .1.3.6.1.4.1.2021.9.1.3.3 |       1 | 2019-10-02 09:48:39 |
+---------+---------------+------------+----------------------+------------+---------------------------+---------+---------------------+
4 rows in set (0.03 sec)
(firma2.example.com - Partition - /dev/mapper/pve-root - that has host_id=89 in data_local table)

arek
Posts: 4
Joined: Fri Sep 27, 2019 7:02 am

Re: Reindex Error at 1.2.2

#13 Post by arek » Sat Oct 26, 2019 3:31 pm

So any ideas why reindexing behaves like that - braking things?

Chrysalis
Cacti User
Posts: 69
Joined: Fri Sep 19, 2008 10:14 am
Location: UK

Re: Reindex Error at 1.2.2

#14 Post by Chrysalis » Wed Oct 30, 2019 5:42 pm

I got this error popping up today, my cacti has never been on earlier 1.2.x builds.

I was on 0.8.x about 2 days ago and went straight to 1.2.7, and it showed up about 30 mins ago.

The device in question has a interface I monitor that is only present sometimes, as its a ue0 (mobile usb ethernet) network interface that activates when I use the backup 4g connection, I am not going to keep a mobile phone hooked up 24/7/365 for those few times its needed so hence been transient.

0.8.x handled this fine without moaning about it.

My question is are you going to fix this behaviour in a future version? as I dont think its reasonable to expect people to hack xml files and manually fix indexes (especially when you not providing step by step how).

--edit--

Ok I fixed the bad indexes using the guide from netniV.

Basically it was 3 datasources from my ovpnc2 interface with index for some reason as ovpnc1, so i edited the 1 for 2 and it fixed them.

I am pretty sure this is related to my temporary activation of ue0 which is graphed in cacti.

How did 0.8.x deal with this? was it broken in that also (but it just didnt warn), or is this due to new behaviour in 1.x that doesnt support my use case?

--edit-- some more info

Timeline of events.

1 - Originally just an amber warning for missing ue0 interface which I was ignoring knowing its not present.
2 - The pfsense unit went offline as I took down its main connection, it was brought online via 4g (ue0), but snmp wouldnt have been accessible during this time, so cacti still considered it down.
3 - When the main connection was online again with phone still connected, it appeared in the logs with this error. I find odd considering nothing changed in its disk config.

Code: Select all

30/Oct/2019 21:35:09 - REINDEX WARNING: Sort Field has Changed for Device[PfSense] and DQ[ucd/net - Get Monitored Partitions]. Old Sort:dskIndex, New Sort:dskPath. Re-mapping issues may occur!
30/Oct/2019 21:35:08 - REINDEX WARNING: Sort Field has Changed for Device[PfSense] and DQ[SNMP - Interface Statistics]. Old Sort:ifDescr, New Sort:ifName. Re-mapping issues may occur!
30/Oct/2019 21:35:07 - PCOMMAND Device[PfSense] WARNING: Recache Event Detected for Device
4 - From this point onwards until I fixed it manually, this was on every poll.

Code: Select all

30/Oct/2019 21:40:06 - POLLER: Poller[Main Poller] WARNING: You have 1 Devices with bad SNMP Indexes. Devices: Device[PfSense] totalling 3 Data Sources. Please Either Re-Index, Delete or Disable these Data Sources.
Hope this helps.

I set in the mean time for the pfsense device the snmp interface statistics to 'none' for reindexing.

netniV
Cacti Guru User
Posts: 2978
Joined: Sun Aug 27, 2017 12:05 am

Re: Reindex Error at 1.2.2

#15 Post by netniV » Wed Oct 30, 2019 6:55 pm

Yes, I think if you know that your indexes aren't changing, turn off the reindex for now. I'm not sure why it's flitting between ifDescr and ifName, it should only be using ifName with the new templates fo 1.2.x. Thanks for the useful breakdown though, as it does make it an interesting case to review and aide in diagnostics.

Post Reply