I changed a custom OID a while back and updated my data template to reflect the new OID. I had existing graphs using the old one, but rebuilding the poller cache never changed anything. By going into the database I was able to update the arg1 entries in cacti.poller_item, but any time the poller cache is rebuilt they pick up the old ones.
Where is it getting the old OIDs from and how can I change those?
Poller cache rebuild changes data source OIDs to old ones
Moderators: Developers, Moderators
I figured this out, though I still don't understand the cause
I did a mysqldump of the database and searched for the offending OID. I found it in the 'value' column of the 'data_input_data' table. Updating rows with the bad OID to the new OID, then rebuilding the poller cache resulted in the OIDs staying put to the new, correct OIDs.
What's the purpose of the data_input_data table, and how should its contents have been correctly set for an OID change on a data template for existing graphs?
I did a mysqldump of the database and searched for the offending OID. I found it in the 'value' column of the 'data_input_data' table. Updating rows with the bad OID to the new OID, then rebuilding the poller cache resulted in the OIDs staying put to the new, correct OIDs.
What's the purpose of the data_input_data table, and how should its contents have been correctly set for an OID change on a data template for existing graphs?
Who is online
Users browsing this forum: No registered users and 13 guests