Hello Members and Guests,
I have been using cacti since verion 1.1.18. Current using cacti-1.2.21 on Oracle Linux virtual machine. This system has been running
fine for weeks.
Every 5 minutes (approx) I get this warning:
POLLER: Poller[SBC Poller] PID[25979] WARNING: Data Template 'Interface - Traffic' is impacted by lack of complete information
2022/08/05 15:58:09 - POLLER: Poller[SBC Poller] PID[25979] WARNING: There are 1 Data Sources not returning all data leaving rows in the poller output table. Details to follow.
I have been using the CPU usage graphs on a few devices - I deleted them all to see if I still get this warning.
Any idea how to debug this one?
thanks,
Eholz1 - I love cacti
[SOLVED]Data source warning - never seen before
Moderators: Developers, Moderators
[SOLVED]Data source warning - never seen before
Last edited by eholz1 on Tue Sep 27, 2022 5:16 pm, edited 1 time in total.
- TheWitness
- Developer
- Posts: 17047
- Joined: Tue May 14, 2002 5:08 pm
- Location: MI, USA
- Contact:
Re: Data source warning - never seen before
Basically only one of the two values, in or out, was returned. Try increasing you snmp timeout.
True understanding begins only when we realize how little we truly understand...
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
- TheWitness
- Developer
- Posts: 17047
- Joined: Tue May 14, 2002 5:08 pm
- Location: MI, USA
- Contact:
Re: Data source warning - never seen before
Update to the 1.2.x branch, or switch to spine. There was a known issue in 1.2.21 that has been fixed.
True understanding begins only when we realize how little we truly understand...
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
SOLVED- Data source warning - never seen before
Hello Witness,
Thanks for the reply. actually increasing the snmp timeout makes sense.
I will also look into the newer version you mention.
I am using spine.
I did fix the issue by deleting all the CPU usage graphs, that is why
I am thinking increasing the snmp timeout might help.
I will do some experimentation.
Thanks for the product, the forum, and the reply to my post.
eholz1
Thanks for the reply. actually increasing the snmp timeout makes sense.
I will also look into the newer version you mention.
I am using spine.
I did fix the issue by deleting all the CPU usage graphs, that is why
I am thinking increasing the snmp timeout might help.
I will do some experimentation.
Thanks for the product, the forum, and the reply to my post.
eholz1
Who is online
Users browsing this forum: No registered users and 1 guest