Open SriRamya-M opened 6 years ago
Hi
Can you check the cacti.log for your polling stats?
2018/03/16 14:05:03 - SYSTEM STATS: Time:2.3074 Method:spine Processes:1 Threads:1 Hosts:3 HostsPerProcess:3 DataSources:30 RRDsProcessed:21 --
Hi, The below are the stats I have took from cacti.log 2018/03/20 08:55:03 - SYSTEM STATS: Time:2.2974 Method:spine Processes:2 Threads:1 Hosts:13 HostsPerProcess:7 DataSources:628 RRDsProcessed:171 2018/03/20 08:55:03 - SYSTEM THOLD STATS: Time:0.0237 Tholds:1 TotalDevices:13 DownDevices:0 NewDownDevices: 2018/03/20 08:55:04 - SYSTEM MONITOR STATS: Time:0.08 Reboots:0 DownDevices:0 Notifications:0 Purges:0
2018/03/20 09:00:24 - SYSTEM STATS: Time:22.4391 Method:spine Processes:2 Threads:1 Hosts:13 HostsPerProcess:7 DataSources:628 RRDsProcessed:121 2018/03/20 09:00:24 - SYSTEM THOLD STATS: Time:0.0969 Tholds:1 TotalDevices:13 DownDevices:0 NewDownDevices: 2018/03/20 09:00:25 - SYSTEM MONITOR STATS: Time:0.06 Reboots:0 DownDevices:0 Notifications:0 Purges:0
2018/03/20 09:05:19 - SYSTEM STATS: Time:18.3472 Method:spine Processes:2 Threads:1 Hosts:13 HostsPerProcess:7 DataSources:628 RRDsProcessed:137 2018/03/20 09:05:19 - SYSTEM THOLD STATS: Time:0.0288 Tholds:1 TotalDevices:13 DownDevices:2 NewDownDevices: 2018/03/20 09:05:20 - SYSTEM MONITOR STATS: Time:0.06 Reboots:0 DownDevices:2 Notifications:0 Purges:2
Although there are no down devices in first two slots,the no of rrds is inconsistent.
I could also see below errors/warns in addition to stats 2018/03/20 09:05:01 - POLLER: Poller[1] WARNING: Poller Output Table not Empty. Issues: 3, DS[265, 265, 265] 2018-03-20 09:05:02 - SPINE: Poller[1] Device[7] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.2.2.1.14.0), Set MAX_OIDS to 1 for this host to isolate bad OID
We are currently setting up Cacti (Version 1.1.28) with Mirage plugin in our environment. Everything working well except we observed that number of data records collected across the 5 minutes interval is inconsistent. Here are summary of our observations from mirage log:
Few additional details:
Any reason for above observation, Any suggestion how to debug this? Thanks.