Just installed a fresh 1.3.8 version of Cacti with spine, All interfaces, queues, are showing 0 items, 0 rows, and does not seem to be pulling any data. I've tried both version1 and version2 snmp. What is wrong?
2018/05/07 21:28:01 - POLLER: Poller[1] NOTE: Poller Int: '60', Cron Int: '60', Time Since Last: '60.26', Max Runtime '58', Poller Runs: '1'
2018/05/07 21:28:00 - SYSTEM STATS: Time:59.3293 Method:spine Processes:5 Threads:1 Hosts:1 HostsPerProcess:1 DataSources:0 RRDsProcessed:0
2018/05/07 21:28:00 - POLLER: Poller[1] Maximum runtime of 58 seconds exceeded. Exiting.
2018/05/07 21:27:01 - POLLER: Poller[1] NOTE: Poller Int: '60', Cron Int: '60', Time Since Last: '60.2', Max Runtime '58', Poller Runs: '1'
2018/05/07 21:27:00 - SYSTEM STATS: Time:59.3301 Method:spine Processes:5 Threads:1 Hosts:1 HostsPerProcess:1 DataSources:0 RRDsProcessed:0
2018/05/07 21:27:00 - POLLER: Poller[1] Maximum runtime of 58 seconds exceeded. Exiting.
2018/05/07 21:26:01 - POLLER: Poller[1] NOTE: Poller Int: '60', Cron Int: '60', Time Since Last: '60.2', Max Runtime '58', Poller Runs: '1'
2018/05/07 21:26:00 - SYSTEM STATS: Time:59.3584 Method:spine Processes:5 Threads:1 Hosts:1 HostsPerProcess:1 DataSources:0 RRDsProcessed:0
2018/05/07 21:26:00 - POLLER: Poller[1] Maximum runtime of 58 seconds exceeded. Exiting.
2018/05/07 21:25:01 - POLLER: Poller[1] NOTE: Poller Int: '60', Cron Int: '60', Time Since Last: '60.11', Max Runtime '58', Poller Runs: '1'
2018/05/07 21:25:00 - SYSTEM STATS: Time:59.2578 Method:spine Processes:5 Threads:1 Hosts:1 HostsPerProcess:1 DataSources:0 RRDsProcessed:0
2018/05/07 21:25:00 - POLLER: Poller[1] Maximum runtime of 58 seconds exceeded. Exiting.
2018/05/07 21:24:01 - POLLER: Poller[1] NOTE: Poller Int: '60', Cron Int: '60', Time Since Last: '60.19', Max Runtime '58', Poller Runs: '1'
2018/05/07 21:24:00 - SYSTEM STATS: Time:59.2702 Method:spine Processes:5 Threads:1 Hosts:1 HostsPerProcess:1 DataSources:0 RRDsProcessed:0
2018/05/07 21:24:00 - POLLER: Poller[1] Maximum runtime of 58 seconds exceeded. Exiting.
2018/05/07 21:23:01 - POLLER: Poller[1] NOTE: Poller Int: '60', Cron Int: '60', Time Since Last: '60.09', Max Runtime '58', Poller Runs: '1'
2018/05/07 21:23:00 - SYSTEM STATS: Time:58.5733 Method:spine Processes:5 Threads:1 Hosts:1 HostsPerProcess:1 DataSources:0 RRDsProcessed:0
2018/05/07 21:23:00 - POLLER: Poller[1] Maximum runtime of 58 seconds exceeded. Exiting.
2018/05/07 21:22:01 - POLLER: Poller[1] NOTE: Poller Int: '60', Cron Int: '60', Time Since Last: '60.67', Max Runtime '58', Poller Runs: '1'
2018/05/07 21:22:00 - SYSTEM STATS: Time:59.2897 Method:spine Processes:5 Threads:1 Hosts:1 HostsPerProcess:1 DataSources:0 RRDsProcessed:0
2018/05/07 21:22:00 - POLLER: Poller[1] Maximum runtime of 58 seconds exceeded. Exiting.
2018/05/07 21:21:01 - POLLER: Poller[1] NOTE: Poller Int: '60', Cron Int: '60', Time Since Last: '60.58', Max Runtime '58', Poller Runs: '1'
2018/05/07 21:21:00 - SYSTEM STATS: Time:59.2804 Method:spine Processes:5 Threads:1 Hosts:1 HostsPerProcess:1 DataSources:0 RRDsProcessed:0
2018/05/07 21:21:00 - POLLER: Poller[1] Maximum runtime of 58 seconds exceeded. Exiting.
2018/05/07 21:20:01 - POLLER: Poller[1] NOTE: Poller Int: '60', Cron Int: '60', Time Since Last: '60.58', Max Runtime '58', Poller Runs: '1'
2018/05/07 21:20:00 - SYSTEM STATS: Time:59.2646 Method:spine Processes:5 Threads:1 Hosts:1 HostsPerProcess:1 DataSources:0 RRDsProcessed:0
2018/05/07 21:20:00 - POLLER: Poller[1] Maximum runtime of 58 seconds exceeded. Exiting.
2018/05/07 21:19:01 - POLLER: Poller[1] NOTE: Poller Int: '60', Cron Int: '60', Time Since Last: '60.61', Max Runtime '58', Poller Runs: '1'
2018/05/07 21:19:00 - SYSTEM STATS: Time:59.2824 Method:spine Processes:5 Threads:1 Hosts:1 HostsPerProcess:1 DataSources:0 RRDsProcessed:0
2018/05/07 21:19:00 - POLLER: Poller[1] Maximum runtime of 58 seconds exceeded. Exiting.
2018/05/07 21:18:01 - POLLER: Poller[1] NOTE: Poller Int: '60', Cron Int: '60', Time Since Last: '60.56', Max Runtime '58', Poller Runs: '1'
2018/05/07 21:18:00 - SYSTEM STATS: Time:59.3118 Method:spine Processes:5 Threads:1 Hosts:1 HostsPerProcess:1 DataSources:0 RRDsProcessed:0
2018/05/07 21:18:00 - POLLER: Poller[1] Maximum runtime of 58 seconds exceeded. Exiting.
2018/05/07 21:17:01 - POLLER: Poller[1] NOTE: Poller Int: '60', Cron Int: '60', Time Since Last: '60.07', Max Runtime '58', Poller Runs: '1'
Cacti Mikrotik Plugin, not pulling data
Moderators: Developers, Moderators
Cacti Mikrotik Plugin, not pulling data
- Attachments
-
- Data Queries
- 2018-05-07 16_30_30-MainWindow.png (17.6 KiB) Viewed 1358 times
- camerabob
- Cacti User
- Posts: 386
- Joined: Fri Feb 10, 2017 2:45 pm
- Location: Long Island, New York, USA
- Contact:
Re: Cacti Mikrotik Plugin, not pulling data
If you make an SNMP walk from the command line, do you see any good data?
Prod: Cacti 1.2.15 @ CentOS Linux release 7.9.2009 (Core) & PHP 5.4.16-48.el7
Maint @ 1.2
Monitor @ 2.3.6
Thold @ 1.2.4
Temp: Cacti 1.2.3 @ CentOS Linux release 7.9.2009 (Core) & PHP 5.4.16-48.el7
Flowview @ 2.1
Mactrack @ 4.2
Maint @ 1.2
Monitor @ 2.3.6
Router Configs @ 1.3.4
Syslog Monitoring @ 2.1
Thold @ 1.2.4
Maint @ 1.2
Monitor @ 2.3.6
Thold @ 1.2.4
Temp: Cacti 1.2.3 @ CentOS Linux release 7.9.2009 (Core) & PHP 5.4.16-48.el7
Flowview @ 2.1
Mactrack @ 4.2
Maint @ 1.2
Monitor @ 2.3.6
Router Configs @ 1.3.4
Syslog Monitoring @ 2.1
Thold @ 1.2.4
Re: Cacti Mikrotik Plugin, not pulling data
Use the selective plugin debug option under settings to get more information about the plugin.
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
The Cacti Group
Director
BV IT Solutions Ltd
+--------------------------------------------------------------------------+
Cacti Resources:
Cacti Website (including releases)
Cacti Issues
Cacti Development Releases
Cacti Development Documentation
Re: Cacti Mikrotik Plugin, not pulling data
Alright, I was able to get the plugin to pull data, but now the RRA's aren't being created, and the device still shows as "unknown" status, when I click on the device it says its SNMP/PING is responding. Yes the poller is running.
Re: Cacti Mikrotik Plugin, not pulling data
What do the poller logs say?
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
The Cacti Group
Director
BV IT Solutions Ltd
+--------------------------------------------------------------------------+
Cacti Resources:
Cacti Website (including releases)
Cacti Issues
Cacti Development Releases
Cacti Development Documentation
Who is online
Users browsing this forum: No registered users and 2 guests