Getting some broken graph

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

Moderators: Developers, Moderators

Post Reply
shamimbdren
Posts: 12
Joined: Fri Feb 05, 2021 12:55 pm

Getting some broken graph

Post by shamimbdren »

I am newly using cacti. Everything was fine at the beginning but after few days when i started to add more device, I found lots of broken graph (not all graph) as attached image. I deleted that device and add again but the results are same. My rrd tool version is 1.4+ and cacti version is Version 1.2.15. It is running on Centos 7 (core) OS.

Any one can help please?
Attachments
cacti broken graph 2.JPG
cacti broken graph 2.JPG (107.33 KiB) Viewed 3743 times
cacti broken graph 1.JPG
cacti broken graph 1.JPG (128.94 KiB) Viewed 3743 times
cigamit
Developer
Posts: 3367
Joined: Thu Apr 07, 2005 3:29 pm
Location: B/CS Texas
Contact:

Re: Getting some broken graph

Post by cigamit »

Check the log. Post your STATS line.
shamimbdren
Posts: 12
Joined: Fri Feb 05, 2021 12:55 pm

Re: Getting some broken graph

Post by shamimbdren »

RRDtool Command:

/usr/bin/rrdtool graph - \
--imgformat=PNG \
--start='-86400' \
--end='-60' \
--pango-markup \
--title='BUET-EDGE-R1 - Traffic - Gi0/0/0' \
--vertical-label='bits per second' \
--slope-mode \
--base=1000 \
--height=200 \
--width=700 \
--rigid \
--alt-autoscale \
COMMENT:"From 2021-05-23 08\:34\:46 To 2021-05-24 08\:33\:46\c" \
COMMENT:" \n" \
--color BACK#F3F3F3 \
--color CANVAS#FDFDFD \
--color SHADEA#CBCBCB \
--color SHADEB#999999 \
--color FONT#000000 \
--color AXIS#2C4D43 \
--color ARROW#2C4D43 \
--color FRAME#2C4D43 \
--border 1 --font TITLE:11:'Arial' \
--font AXIS:8:'Arial' \
--font LEGEND:8:'Courier' \
--font UNIT:8:'Arial' \
--font WATERMARK:6:'Arial' \
--slope-mode \
--watermark 'Generated by Cacti®BdREN' \
DEF:a='/usr/share/cacti/rra/239/5085.rrd':'traffic_in':AVERAGE \
DEF:b='/usr/share/cacti/rra/239/5085.rrd':'traffic_out':AVERAGE \
CDEF:cdefa='a,8,*' \
CDEF:cdeff='b,8,*' \
AREA:cdefa#00CF007F:'Inbound ' \
GPRINT:cdefa:LAST:'Current\:%8.2lf %s' \
GPRINT:cdefa:AVERAGE:'Average\:%8.2lf %s' \
GPRINT:cdefa:MAX:'Maximum\:%8.2lf %s\n' \
COMMENT:'Total In\: 591.34 GB\n' \
AREA:cdeff#002A977F:'Outbound' \
GPRINT:cdeff:LAST:'Current\:%8.2lf %s' \
GPRINT:cdeff:AVERAGE:'Average\:%8.2lf %s' \
GPRINT:cdeff:MAX:'Maximum\:%8.2lf %s\n' \
COMMENT:'Total Out\: 142.71 GB\n'

RRDtool Command lengths = 1260 charaters.

RRDtool Says:

OK


Cacti log:

2021-05-24 08:36:46 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[13] Device[UGC-CORE-SW2] Thread[1] DS[UGC-CORE-SW2 - Traffic - 10.10.22.3 - Vlan302, UGC-CORE-SW2 - Traffic - 103.28.120.236 - Vlan801, UGC-CORE-SW2 - Traffic - port-channel6, UGC-CORE-SW2 - Traffic - Ethernet5/1, UGC-CORE-SW2 - Traffic - Ethernet5/6, UGC-CORE-SW2 - Traffic - Ethernet5/16, UGC-CORE-SW2 - Traffic - Ethernet5/30, UGC-CORE-SW2 - Traffic - Ethernet6/7, UGC-CORE-SW2 - Traffic - Ethernet6/12, UGC-CORE-SW2 - Traffic - Ethernet6/17, UGC-CORE-SW2 - Traffic - Ethernet6/22, UGC-CORE-SW2 - Traffic - Ethernet6/32, UGC-CORE-SW2 - Traffic - Ethernet6/36] Graphs[UGC-CORE-SW2 - Traffic - Vlan302, UGC-CORE-SW2 - Traffic - Vlan302, UGC-CORE-SW2 - Traffic - Vlan801, UGC-CORE-SW2 - Traffic - *** connected to UGC-SVF-FW2 int TenGig , UGC-CORE-SW2 - Traffic - port-channel6, UGC-CORE-SW2 - Traffic - Ethernet5/1, UGC-CORE-SW2 - Traffic - Ethernet5/6, UGC-CORE-SW2 - Traffic - Ethernet5/16, UGC-CORE-SW2 - Traffic - Ethernet5/30, UGC-CORE-SW2 - Traffic - Ethernet6/7, UGC-CORE-SW2 - Traffic - Ethernet6/12, UGC-CORE-SW2 - Traffic - Ethernet6/17, UGC-CORE-SW2 - Traffic - Ethernet6/22, UGC-CORE-SW2 - Traffic - Ethernet6/32, UGC-CORE-SW2 - Traffic - Ethernet6/36]
2021-05-24 08:36:18 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[2] Device[UGC-CORE-SW1] Thread[1] DS[UGC-CORE-SW1 - Traffic - Ethernet5/26, UGC-CORE-SW1 - Traffic - Ethernet6/36] Graphs[UGC-CORE-SW1 - Traffic - Ethernet5/26, UGC-CORE-SW1 - Traffic - Ethernet6/36]
2021-05-24 08:36:13 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[BRRI-EDGE] Thread[1] DS[BRRI-EDGE - CPU - Idle] Graphs[BRRI-EDGE - CPU Utilization]
2021-05-24 08:36:12 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[BMD-EDGE] Thread[1] DS[BMD-EDGE - CPU - Idle] Graphs[BMD-EDGE - CPU Utilization]
2021-05-24 08:36:12 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[BLRI-EDGE] Thread[1] DS[BLRI-EDGE - CPU - System] Graphs[BLRI-EDGE - CPU Utilization]
2021-05-24 08:36:12 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[BJRI-EDGE] Thread[1] DS[BJRI-EDGE - CPU - User] Graphs[BJRI-EDGE - CPU Utilization]
2021-05-24 08:36:12 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[BARI-EDGE] Thread[1] DS[BARI-EDGE - CPU - Idle] Graphs[BARI-EDGE - CPU Utilization]
2021-05-24 08:36:12 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[BARD-EDGE] Thread[1] DS[BARD-EDGE - CPU - System] Graphs[BARD-EDGE - CPU Utilization]
2021-05-24 08:36:12 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[SSMC-EDGE] Thread[1] DS[SSMC-EDGE - CPU - System] Graphs[SSMC-EDGE - CPU Utilization]
2021-05-24 08:36:12 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[SBMC-EDGE] Thread[1] DS[SBMC-EDGE - CPU - User] Graphs[SBMC-EDGE - CPU Utilization]
2021-05-24 08:36:11 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[MAGOMC-EDGE] Thread[1] DS[MAGOMC-EDGE - CPU - Idle] Graphs[MAGOMC-EDGE - CPU Utilization]
2021-05-24 08:36:11 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[DMC-EDGE] Thread[1] DS[DMC-EDGE - CPU - Idle] Graphs[DMC-EDGE - CPU Utilization]
2021-05-24 08:36:11 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[DDC-EDGE] Thread[1] DS[DDC-EDGE - CPU - User] Graphs[DDC-EDGE - CPU Utilization]
2021-05-24 08:36:10 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[BUP-EDGE] Thread[1] DS[BUP-EDGE - CPU - System] Graphs[BUP-EDGE - CPU Utilization]
2021-05-24 08:36:10 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[BSMMU-EDGE] Thread[1] DS[BSMMU-EDGE - CPU - System] Graphs[BSMMU-EDGE - CPU Utilization]
2021-05-24 08:36:10 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[JNU-EDGE] Thread[1] DS[JNU-EDGE - CPU - User] Graphs[JNU-EDGE - CPU Utilization]
2021-05-24 08:36:10 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[DU-EDGE] Thread[1] DS[DU-EDGE - CPU - User] Graphs[DU-EDGE - CPU Utilization]
2021-05-24 08:36:10 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[NU-EDGE] Thread[1] DS[NU-EDGE - CPU - Idle] Graphs[NU-EDGE - CPU Utilization]
2021-05-24 08:36:09 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[BoU-EDGE] Thread[1] DS[BoU-EDGE - CPU - System] Graphs[BoU-EDGE - CPU Utilization]
2021-05-24 08:36:09 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[IUT-EDGE] Thread[1] DS[IUT-EDGE - CPU - System] Graphs[IUT-EDGE - CPU Utilization]
2021-05-24 08:36:09 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[CVASU-EDGE] Thread[1] DS[CVASU-EDGE - CPU - Idle] Graphs[CVASU-EDGE - CPU Utilization]
2021-05-24 08:36:09 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[CUET-EDGE] Thread[1] DS[CUET-EDGE - CPU - User] Graphs[CUET-EDGE - CPU Utilization]
2021-05-24 08:36:08 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[CoU-EDGE] Thread[1] DS[CoU-EDGE - CPU - Idle] Graphs[CoU-EDGE - CPU Utilization]
2021-05-24 08:36:08 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[SAU-EDGE] Thread[1] DS[SAU-EDGE - CPU - System] Graphs[SAU-EDGE - CPU Utilization]
2021-05-24 08:36:08 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[SUST-EDGE] Thread[1] DS[SUST-EDGE - CPU - System] Graphs[SUST-EDGE - CPU Utilization]
2021-05-24 08:36:08 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[JKKNIU-EDGE] Thread[1] DS[JKKNIU-EDGE - CPU - User] Graphs[JKKNIU-EDGE - CPU Utilization]
2021-05-24 08:36:08 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[KUET-EDGE] Thread[1] DS[KUET-EDGE - CPU - System] Graphs[KUET-EDGE - CPU Utilization]
2021-05-24 08:36:07 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[KU-EDGE] Thread[1] DS[KU-EDGE - CPU - User] Graphs[KU-EDGE - CPU Utilization]
2021-05-24 08:36:07 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[JUST-EDGE] Thread[1] DS[JUST-EDGE - CPU - User] Graphs[JUST-EDGE - CPU Utilization]
2021-05-24 08:36:07 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[PSTU-EDGE] Thread[1] DS[PSTU-EDGE - CPU - Idle] Graphs[PSTU-EDGE - CPU Utilization]
2021-05-24 08:36:06 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[SBAU-EDGE] Thread[1] DS[SBAU-EDGE - CPU - User] Graphs[SBAU-EDGE - CPU Utilization]
2021-05-24 08:36:06 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[HSTU-EDGE] Thread[1] DS[HSTU-EDGE - CPU - Idle] Graphs[HSTU-EDGE - CPU Utilization]
2021-05-24 08:36:06 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[PUST-EDGE] Thread[1] DS[PUST-EDGE - CPU - User] Graphs[PUST-EDGE - CPU Utilization]
2021-05-24 08:36:05 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[RU-EDGE] Thread[1] DS[RU-EDGE - CPU - Idle] Graphs[RU-EDGE - CPU Utilization]
2021-05-24 08:36:04 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[CoU-DIST] Thread[1] DS[CoU-DIST - Traffic - |query_ifName|] Graphs[CoU-DIST - Traffic - TenGigE0/0/0/0]
2021-05-24 08:36:02 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[UGC-CORE-R1] Thread[1] DS[UGC-CORE-R1 - CPU - Idle] Graphs[UGC-CORE-R1 - CPU Utilization]
2021-05-24 08:35:56 - SYSTEM MONITOR STATS: Time:0.0128 Reboots:0 DownDevices:0 Notifications:0 Purges:0
2021-05-24 08:35:56 - MONITOR WARNING: No Global Notification List defined. Please set under Settings -> Thresholds
2021-05-24 08:35:56 - SYSTEM THOLD STATS: Time:0.0407 Tholds:0 TotalDevices:82 DownDevices:0 NewDownDevices:0
2021-05-24 08:35:56 - WEATHERMAP STATS: Weathermap 0.98a run complete - Mon, 24 May 21 08:35:56 +0600: 0 maps were run in 0 seconds with 1 warnings. (Permissions problem prevents any maps running WMPOLL06)
2021-05-24 08:35:56 - WEATHERMAP WARNING: Output directory (/usr/share/cacti/plugins/weathermap/output) isn't writable (tried to create '/usr/share/cacti/plugins/weathermap/output/weathermap.permissions.test'). No maps created. You probably need to make it writable by the poller process (like you did with the RRA directory) [WMPOLL06]
2021-05-24 08:35:56 - CMDPHP PHP ERROR WARNING Backtrace: (/poller.php[771]:api_plugin_hook(), /lib/plugins.php[74]:api_plugin_run_plugin_hook(), /lib/plugins.php[177]:weathermap_poller_bottom(), /plugins/weathermap/setup.php[787]:weathermap_run_maps(), /plugins/weathermap/lib/poller-common.php[112]:fopen(), CactiErrorHandler())
2021-05-24 08:35:56 - ERROR PHP WARNING in Plugin 'weathermap': fopen(/usr/share/cacti/plugins/weathermap/output/weathermap.permissions.test): failed to open stream: Permission denied in file: /usr/share/cacti/plugins/weathermap/lib/poller-common.php on line: 112
2021-05-24 08:35:56 - WEATHERMAP Weathermap 0.98a starting - Normal logging mode. Turn on DEBUG in Cacti for more information
2021-05-24 08:35:54 - SYSTEM STATS: Time:53.4542 Method:cmd.php Processes:1 Threads:0 Hosts:82 HostsPerProcess:82 DataSources:627 RRDsProcessed:0
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DS[BUET-EDGE-R1 - Traffic - 163.47.37.121 - Gi0/3/2] Graphs[BUET-EDGE-R1 - Traffic - Gi0/3/2] SNMP: v2: 103.28.123.141, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.21, output: 1052069866
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DS[BUET-EDGE-R1 - Traffic - 163.47.37.121 - Gi0/3/2] Graphs[BUET-EDGE-R1 - Traffic - Gi0/3/2] SNMP: v2: 103.28.123.141, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.21, output: 52815749
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DS[BUET-EDGE-R1 - Traffic - 163.47.36.153 - Gi0/1/0.21] Graphs[BUET-EDGE-R1 - Traffic - Gi0/1/0.21] SNMP: v2: 103.28.123.141, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.15, output: 2500129026
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DS[BUET-EDGE-R1 - Traffic - 163.47.36.153 - Gi0/1/0.21] Graphs[BUET-EDGE-R1 - Traffic - Gi0/1/0.21] SNMP: v2: 103.28.123.141, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.15, output: 5197470651
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DS[BUET-EDGE-R1 - Traffic - 10.30.248.5 - Gi0/0/1] Graphs[BUET-EDGE-R1 - Traffic - Gi0/0/1] SNMP: v2: 103.28.123.141, dsname: traffic_out, oid: .1.3.6.1.2.1.31.1.1.1.10.2, output: 8013271883
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DS[BUET-EDGE-R1 - Traffic - 10.30.248.5 - Gi0/0/1] Graphs[BUET-EDGE-R1 - Traffic - Gi0/0/1] SNMP: v2: 103.28.123.141, dsname: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.2, output: 9995663521
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.9, (assert:Null0 = output:Null0)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.8, (assert:VoIP-Null0 = output:VoIP-Null0)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.7, (assert:GigabitEthernet0 = output:GigabitEthernet0)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.6, (assert:GigabitEthernet0/1/1 = output:GigabitEthernet0/1/1)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.5, (assert:GigabitEthernet0/1/0 = output:GigabitEthernet0/1/0)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.4, (assert:GigabitEthernet0/0/3 = output:GigabitEthernet0/0/3)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.3, (assert:GigabitEthernet0/0/2 = output:GigabitEthernet0/0/2)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.23, (assert:GigabitEthernet0/3/4 = output:GigabitEthernet0/3/4)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.22, (assert:GigabitEthernet0/3/3 = output:GigabitEthernet0/3/3)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.21, (assert:GigabitEthernet0/3/2 = output:GigabitEthernet0/3/2)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.20, (assert:GigabitEthernet0/3/1 = output:GigabitEthernet0/3/1)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.2, (assert:GigabitEthernet0/0/1 = output:GigabitEthernet0/0/1)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.19, (assert:GigabitEthernet0/3/0 = output:GigabitEthernet0/3/0)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.18, (assert:GigabitEthernet0/1/0.24 = output:GigabitEthernet0/1/0.24)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.17, (assert:GigabitEthernet0/1/0.23 = output:GigabitEthernet0/1/0.23)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.16, (assert:GigabitEthernet0/1/0.22 = output:GigabitEthernet0/1/0.22)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.15, (assert:GigabitEthernet0/1/0.21 = output:GigabitEthernet0/1/0.21)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.14, (assert:GigabitEthernet0/0/2.21 = output:GigabitEthernet0/0/2.21)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.13, (assert:GigabitEthernet0/0/0-mpls layer = output:GigabitEthernet0/0/0-mpls layer)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.12, (assert:Loopback10 = output:Loopback10)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.11, (assert:Loopback1 = output:Loopback1)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.10, (assert:Loopback0 = output:Loopback0)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] DQ[SNMP - Interface Statistics] RECACHE OID: .1.3.6.1.2.1.2.2.1.2.1, (assert:GigabitEthernet0/0/0 = output:GigabitEthernet0/0/0)
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] RECACHE: Processing 23 items in the auto reindex cache for '103.28.123.141'.
2021-05-24 08:35:53 - POLLER: Poller[Main Poller] Device[BUET-EDGE-R1] STATUS: Device '103.28.123.141' is UP.
2021-05-24 08:35:51 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[2] Device[BUET-DIST-R2] Thread[1] DS[BUET-DIST-R2 - Traffic - |query_ifName|, BUET-DIST-R2 - Traffic - dwdm0/1/0/3] Graphs[BUET-DIST-R2 - Traffic - GigabitEthernet0/0/0/8, BUET-DIST-R2 - Traffic - GigabitEthernet0/0/0/12]
cigamit
Developer
Posts: 3367
Joined: Thu Apr 07, 2005 3:29 pm
Location: B/CS Texas
Contact:

Re: Getting some broken graph

Post by cigamit »

Your close to going over your polling interval on that one particular polling, so I imagine you are going over other times.

Goto
Console >> Data Collection >> Data Collectors >> Main Poller and increase the Processes from 1 to the number of CPUs cores in your Cacti system (and you can probably double even that).
shamimbdren
Posts: 12
Joined: Fri Feb 05, 2021 12:55 pm

Re: Getting some broken graph

Post by shamimbdren »

Thank you so much for your reply.
I have 4 cores in my server. So can I increase the main poller process number from 1 to 8 or it will be 4 only ??
cigamit
Developer
Posts: 3367
Joined: Thu Apr 07, 2005 3:29 pm
Location: B/CS Texas
Contact:

Re: Getting some broken graph

Post by cigamit »

I would try 8 first, and if your server gets overloaded, drop it to 4. I think 8 will be fine.
shamimbdren
Posts: 12
Joined: Fri Feb 05, 2021 12:55 pm

Re: Getting some broken graph

Post by shamimbdren »

Thank you soo much for your help.
I already change it to 8 and observing the graph. Till now it looks fine. I will let you know the result after 1 week.
Thanks once again for your help.
shamimbdren
Posts: 12
Joined: Fri Feb 05, 2021 12:55 pm

Re: Getting some broken graph

Post by shamimbdren »

Still I am getting the following error in cacti log.
LOG:

2021-06-01 11:55:33 - AUTOM8 WARNING: Automation Rule[Traffic 64 bit Server] for Device[UGC-CORE-SW2] - DQ[SNMP - Interface Statistics] includes a SQL column ifOperStatus that is not found for the Device. Can not continue.
2021-06-01 11:55:32 - DSTRACE Field Name 'ifIP' found not suitable during Re-Index for Device[UGC-CORE-SW2], DQ[SNMP - Interface Statistics]
2021-06-01 11:55:32 - DSTRACE Field Name 'ifHwAddr' found not suitable. The Sort field does not have sufficient values for Device[UGC-CORE-SW2], DQ[SNMP - Interface Statistics]
2021-06-01 11:55:32 - DSTRACE Field Name 'ifHighSpeed' found not suitable during Re-Index for Device[UGC-CORE-SW2], DQ[SNMP - Interface Statistics]
2021-06-01 11:55:32 - DSTRACE Field Name 'ifSpeed' found not suitable during Re-Index for Device[UGC-CORE-SW2], DQ[SNMP - Interface Statistics]
2021-06-01 11:55:32 - DSTRACE Field Name 'ifType' found not suitable during Re-Index for Device[UGC-CORE-SW2], DQ[SNMP - Interface Statistics]
2021-06-01 11:55:32 - DSTRACE Field Name 'ifAlias' found not suitable during Re-Index for Device[UGC-CORE-SW2], DQ[SNMP - Interface Statistics]
2021-06-01 11:55:32 - DSTRACE Field Name 'ifName' found suitable during Re-Index for Device[UGC-CORE-SW2], DQ[SNMP - Interface Statistics]
2021-06-01 11:55:32 - DSTRACE Field Name 'ifDescr' found suitable during Re-Index for Device[UGC-CORE-SW2], DQ[SNMP - Interface Statistics]
2021-06-01 11:55:32 - DSTRACE Field Name 'ifAdminStatus' found not suitable during Re-Index for Device[UGC-CORE-SW2], DQ[SNMP - Interface Statistics]
2021-06-01 11:55:32 - DSTRACE Field Name 'ifOperStatus' found not suitable during Re-Index for Device[UGC-CORE-SW2], DQ[SNMP - Interface Statistics]
2021-06-01 11:55:32 - DSTRACE Field Name 'ifIndex' is an SNMP index and suitable Re-Index for Device[UGC-CORE-SW2], DQ[SNMP - Interface Statistics]
2021-06-01 11:55:32 - DSTRACE Available Sort Fields for Re-Index for Device[UGC-CORE-SW2], DQ[SNMP - Interface Statistics] are [ifName:ifDescr:ifHwAddr:ifIndex]
2021-06-01 11:55:26 - SYSTEM MONITOR STATS: Time:0.0114 Reboots:0 DownDevices:0 Notifications:0 Purges:0
2021-06-01 11:55:26 - MONITOR WARNING: No Global Notification List defined. Please set under Settings -> Thresholds
2021-06-01 11:55:25 - SYSTEM THOLD STATS: Time:0.0274 Tholds:0 TotalDevices:83 DownDevices:0 NewDownDevices:0
2021-06-01 11:55:25 - WEATHERMAP STATS: Weathermap 0.98a run complete - Tue, 01 Jun 21 11:55:25 +0600: 0 maps were run in 0 seconds with 1 warnings. (Permissions problem prevents any maps running WMPOLL06)
2021-06-01 11:55:25 - WEATHERMAP WARNING: Output directory (/usr/share/cacti/plugins/weathermap/output) isn't writable (tried to create '/usr/share/cacti/plugins/weathermap/output/weathermap.permissions.test'). No maps created. You probably need to make it writable by the poller process (like you did with the RRA directory) [WMPOLL06]
2021-06-01 11:55:25 - CMDPHP PHP ERROR WARNING Backtrace: (/poller.php[771]:api_plugin_hook(), /lib/plugins.php[74]:api_plugin_run_plugin_hook(), /lib/plugins.php[177]:weathermap_poller_bottom(), /plugins/weathermap/setup.php[787]:weathermap_run_maps(), /plugins/weathermap/lib/poller-common.php[112]:fopen(), CactiErrorHandler())
2021-06-01 11:55:25 - ERROR PHP WARNING in Plugin 'weathermap': fopen(/usr/share/cacti/plugins/weathermap/output/weathermap.permissions.test): failed to open stream: Permission denied in file: /usr/share/cacti/plugins/weathermap/lib/poller-common.php on line: 112
2021-06-01 11:55:25 - WEATHERMAP Weathermap 0.98a starting - Normal logging mode. Turn on DEBUG in Cacti for more information
2021-06-01 11:55:24 - DSTRACE Running Re-Index for Device[UGC-CORE-SW2], DQ[SNMP - Interface Statistics]
2021-06-01 11:55:24 - PCOMMAND Device[UGC-CORE-SW2] WARNING: Recache Event Detected for Device
2021-06-01 11:55:24 - SYSTEM STATS: Time:23.1660 Method:cmd.php Processes:8 Threads:0 Hosts:83 HostsPerProcess:11 DataSources:630 RRDsProcessed:0
2021-06-01 11:55:23 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[2] Device[BUET-DIST-R2] Thread[1] DS[BUET-DIST-R2 - Traffic - |query_ifName|, BUET-DIST-R2 - Traffic - dwdm0/1/0/3] Graphs[BUET-DIST-R2 - Traffic - GigabitEthernet0/0/0/8, BUET-DIST-R2 - Traffic - GigabitEthernet0/0/0/12]
2021-06-01 11:55:23 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[8] Device[BUET-CORE-SW] Thread[1] DS[BUET-CORE-SW - Traffic - |query_ifIP| - loopback70, BUET-CORE-SW - Traffic - Ethernet5/3, BUET-CORE-SW - Traffic - Ethernet5/13, BUET-CORE-SW - Traffic - Ethernet5/23, BUET-CORE-SW - Traffic - Ethernet6/4, BUET-CORE-SW - Traffic - Ethernet6/14, BUET-CORE-SW - Traffic - Ethernet6/39, BUET-CORE-SW - Traffic - Ethernet6/44] Graphs[BUET-CORE-SW - Traffic - loopback70, BUET-CORE-SW - Traffic - Ethernet5/3, BUET-CORE-SW - Traffic - Ethernet5/13, BUET-CORE-SW - Traffic - Ethernet5/23, BUET-CORE-SW - Traffic - Ethernet6/4, BUET-CORE-SW - Traffic - Ethernet6/14, BUET-CORE-SW - Traffic - Ethernet6/39, BUET-CORE-SW - Traffic - Ethernet6/44]
2021-06-01 11:55:20 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[5] Device[UGC-CORE-SW1] Thread[1] DS[UGC-CORE-SW1 - Traffic - Ethernet5/4, UGC-CORE-SW1 - Traffic - Ethernet5/9, UGC-CORE-SW1 - Traffic - Ethernet5/14, UGC-CORE-SW1 - Traffic - Ethernet6/14, UGC-CORE-SW1 - Traffic - Ethernet6/40] Graphs[UGC-CORE-SW1 - Traffic - Ethernet5/4, UGC-CORE-SW1 - Traffic - Ethernet5/9, UGC-CORE-SW1 - Traffic - Ethernet5/14, UGC-CORE-SW1 - Traffic - Ethernet6/14, UGC-CORE-SW1 - Traffic - Ethernet6/40]
2021-06-01 11:55:12 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[3] Device[UGC-CORE-SW2] Thread[1] DS[UGC-CORE-SW2 - Traffic - 10.50.64.3 - Vlan131, UGC-CORE-SW2 - Traffic - 10.40.240.3 - Vlan601, UGC-CORE-SW2 - Traffic - Ethernet5/44] Graphs[UGC-CORE-SW2 - Traffic - Vlan131, UGC-CORE-SW2 - Traffic - Vlan131, UGC-CORE-SW2 - Traffic - Vlan601, UGC-CORE-SW2 - Traffic - Vlan601, UGC-CORE-SW2 - Traffic - Ethernet5/44]
2021-06-01 11:55:04 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[CoU-DIST] Thread[1] DS[CoU-DIST - Traffic - |query_ifIP| - |query_ifName|] Graphs[CoU-DIST - Traffic - Connected to CoU-EDGE-R1 Gi0/0/0, CoU-DIST - Traffic - GigabitEthernet0/0/0/2]
2021-06-01 11:55:04 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[KUET-EDGE] Thread[1] DS[KUET-EDGE - CPU - Idle] Graphs[KUET-EDGE - CPU Utilization]
2021-06-01 11:55:04 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[BUP-EDGE] Thread[1] DS[BUP-EDGE - CPU - Idle] Graphs[BUP-EDGE - CPU Utilization]
2021-06-01 11:55:04 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[KU-EDGE] Thread[1] DS[KU-EDGE - CPU - System] Graphs[KU-EDGE - CPU Utilization]
2021-06-01 11:55:04 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[BSMMU-EDGE] Thread[1] DS[BSMMU-EDGE - CPU - Idle] Graphs[BSMMU-EDGE - CPU Utilization]
2021-06-01 11:55:04 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[JNU-EDGE] Thread[1] DS[JNU-EDGE - CPU - System] Graphs[JNU-EDGE - CPU Utilization]
2021-06-01 11:55:04 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[JUST-EDGE] Thread[1] DS[JUST-EDGE - CPU - System] Graphs[JUST-EDGE - CPU Utilization]
2021-06-01 11:55:04 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[1] Device[DU-EDGE] Thread[1] DS[DU-EDGE - CPU - System] Graphs[DU-EDGE - CPU Utilization]
2021-06-01 11:55:04 - POLLER: Poller[Main Poller] Device[UGC-CORE-SW2] DQ[SNMP - Interface Statistics] RECACHE ASSERT FAILED '3218306092<

These device graphs are still broken.
please share a solution.
Thanks in advance.
Attachments
cacti.PNG
cacti.PNG (101.46 KiB) Viewed 3520 times
cigamit
Developer
Posts: 3367
Joined: Thu Apr 07, 2005 3:29 pm
Location: B/CS Texas
Contact:

Re: Getting some broken graph

Post by cigamit »

2021-06-01 11:55:25 - ERROR PHP WARNING in Plugin 'weathermap': fopen(/usr/share/cacti/plugins/weathermap/output/weathermap.permissions.test): failed to open stream: Permission denied in file: /usr/share/cacti/plugins/weathermap/lib/poller-common.php on line: 112
You need to fix the permissions on "/usr/share/cacti/plugins/weathermap/output/" so that your webserver user can write to it.
cigamit
Developer
Posts: 3367
Joined: Thu Apr 07, 2005 3:29 pm
Location: B/CS Texas
Contact:

Re: Getting some broken graph

Post by cigamit »

2021-06-01 11:55:20 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[5] Device[UGC-CORE-SW1] Thread[1] DS[UGC-CORE-SW1 - Traffic - Ethernet5/4, UGC-CORE-SW1 - Traffic - Ethernet5/9, UGC-CORE-SW1 - Traffic - Ethernet5/14, UGC-CORE-SW1 - Traffic - Ethernet6/14, UGC-CORE-SW1 - Traffic - Ethernet6/40] Graphs[UGC-CORE-SW1 - Traffic - Ethernet5/4, UGC-CORE-SW1 - Traffic - Ethernet5/9, UGC-CORE-SW1 - Traffic - Ethernet5/14, UGC-CORE-SW1 - Traffic - Ethernet6/14, UGC-CORE-SW1 - Traffic - Ethernet6/40]
There isn't anything that Cacti can do about these. Your device is returning invalid data, so you might want to manually walk the device to see what data they are returning.
shamimbdren
Posts: 12
Joined: Fri Feb 05, 2021 12:55 pm

Re: Getting some broken graph

Post by shamimbdren »

Since last few days, I am not getting graph in cacti. When I debug, rrd says ok. My main poller is in idle mode. I enabled it several times, but it shows idle mode again.
Please help me to solve this issue.
Attachments
Capture.PNG
Capture.PNG (12.09 KiB) Viewed 3290 times
cigamit
Developer
Posts: 3367
Joined: Thu Apr 07, 2005 3:29 pm
Location: B/CS Texas
Contact:

Re: Getting some broken graph

Post by cigamit »

Its just saying IDLE because its not polling right that moment. Your polling now only takes 1.9 seconds, based upon that screen shot, so for 58 seconds out of the minute, it is actually idle and will say so. So that isn't your issue.
shamimbdren
Posts: 12
Joined: Fri Feb 05, 2021 12:55 pm

Re: Getting some broken graph

Post by shamimbdren »

But why there is no data in my graph??
cigamit
Developer
Posts: 3367
Joined: Thu Apr 07, 2005 3:29 pm
Location: B/CS Texas
Contact:

Re: Getting some broken graph

Post by cigamit »

2021-06-01 11:55:20 - POLLER: Poller[Main Poller] WARNING: Invalid Response(s), Errors[5] Device[UGC-CORE-SW1] Thread[1] DS[UGC-CORE-SW1 - Traffic - Ethernet5/4, UGC-CORE-SW1 - Traffic - Ethernet5/9, UGC-CORE-SW1 - Traffic - Ethernet5/14, UGC-CORE-SW1 - Traffic - Ethernet6/14, UGC-CORE-SW1 - Traffic - Ethernet6/40] Graphs[UGC-CORE-SW1 - Traffic - Ethernet5/4, UGC-CORE-SW1 - Traffic - Ethernet5/9, UGC-CORE-SW1 - Traffic - Ethernet5/14, UGC-CORE-SW1 - Traffic - Ethernet6/14, UGC-CORE-SW1 - Traffic - Ethernet6/40]
Your devices are sending back invalid data. You will want to run in medium log mode to try and see what they are sending back if anything. You might try manually walking them also to see what data they are sending back via the command line.
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest