"." was lost

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

Moderators: Developers, Moderators

Post Reply
ogreeeen
Posts: 4
Joined: Tue Feb 05, 2019 5:57 pm

"." was lost

Post by ogreeeen »

he following problems occur in cacti 1.2.1

At irregular timing, "Index Value" changes as below.

[Custom Data] - [Index Value]
Before: vmxnet3 Ethernet Adapter.
After : vmxnet3 Ethernet Adapter ("." was lost)

As a result, it becomes impossible to collect data.
It occured more than once.

Please tell me if somebody know the cause of this event and how to prevent it from happening again.
netniV
Cacti Guru User
Posts: 3441
Joined: Sun Aug 27, 2017 12:05 am

Re: "." was lost

Post by netniV »

When upgrading to 1.2, we corrected a hidden issue that manufactor's were changing the ifDecr field during firmware updates. As such it wasn't static as expected. However, the ifName is so the indexing has been changed to that. Your issue sounds like it is that problem and if so, you'll need to set the index field and value against the data source manually.
Cacti Developer & Release Manager
The Cacti Group

Director
BV IT Solutions Ltd

+--------------------------------------------------------------------------+

Cacti Resources:
Cacti Website (including releases)
Cacti Issues
Cacti Development Releases
Cacti Development Documentation
ogreeeen
Posts: 4
Joined: Tue Feb 05, 2019 5:57 pm

Re: "." was lost

Post by ogreeeen »

Thank you for answering.
I fixed it manually, and the problem was resolved.
However, when the monitored device reboots, the problem recurs.
Is there a way to prevent a recurrence?
Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests