[Solved] Cron Interval does't update

Post support questions that directly relate to Linux/Unix operating systems.

Moderators: Developers, Moderators

Post Reply
jajao555
Posts: 5
Joined: Mon Dec 07, 2020 4:12 pm

[Solved] Cron Interval does't update

Post by jajao555 »

I've changed cron interval in the GUI to 5mins and I've also changed it in /etc/cron.d/cacti

Code: Select all

*/5 * * * * apache php /var/www/html/cacti/poller.php &>/dev/null
I gave it about a half hour but still see these logs:

Code: Select all

2020-12-07 14:50:01 - POLLER: Poller[Main Poller] NOTE: Cron is configured to run too often! The Poller Interval is '60' seconds, with a minimum Cron period of '60' seconds, but only 0.3 seconds have passed since the poller last ran.
The log will show up on exactly 5 min or 10min intervals. Then we'll also see gaps in our graphs that line up with the log timestamp. I also tried rebooting but still got the log.

Here's the server specs:

Code: Select all

Date	Mon, 07 Dec 2020 16:25:06 -0500
Cacti Version	1.2.15
Cacti OS	unix
NET-SNMP Version	NET-SNMP version: 5.7.2
RRDtool Version Configured	1.4.0+
RRDtool Version Found	1.4.8
Devices	5
Graphs	86
Data Sources	Script/Command: 10
SNMP Query: 82
Total: 92
Interval	60
Type	SPINE 1.2.16 Copyright 2004-2020 by The Cacti Group (Different version of Cacti and Spine!)
Items	Action[0]: 102
Action[1]: 10
Total: 112
Concurrent Processes	2
Max Threads	4
PHP Servers	1
Script Timeout	25
Max OID	10
Last Run Statistics	Time:0.3228 Method:spine Processes:8 Threads:12 Hosts:5 HostsPerProcess:1 DataSources:112 RRDsProcessed:0
MemTotal	7.46 G
MemFree	6.41 G
MemAvailable	6.40 G
Buffers	2.01 M
Cached	206.62 M
Active	593.45 M
Inactive	132.16 M
SwapTotal	7.69 G
SwapFree	7.69 G
PHP Version	5.4.16
PHP Version 5.5.0+ is recommended due to strong password hashing support.
PHP OS	Linux
PHP uname	Linux nmd-tp-cacti1 3.10.0-1160.6.1.el7.x86_64 #1 SMP Tue Nov 17 13:59:11 UTC 2020 x86_64
PHP SNMP	Installed. Note: If you are planning on using SNMPv3, you must remove php-snmp and use the Net-SNMP toolset.
max_execution_time	60
memory_limit	800M
version	5.5.68-MariaDB	>=	5.6	MySQL 5.6+ and MariaDB 10.0+ are great releases, and are very good versions to choose. Make sure you run the very latest release though which fixes a long standing low level networking issue that was causing spine many issues with reliability.
collation_server	utf8mb4_unicode_ci	=	utf8mb4_unicode_ci	When using Cacti with languages other than English, it is important to use the utf8mb4_unicode_ci collation type as some characters take more than a single byte.
character_set_server	utf8mb4	=	utf8mb4	When using Cacti with languages other than English, it is important to use the utf8mb4 character set as some characters take more than a single byte.
character_set_client	utf8mb4	=	utf8mb4	When using Cacti with languages other than English, it is important to use the utf8mb4 character set as some characters take more than a single byte.
max_connections	151	>=	100	Depending on the number of logins and use of spine data collector, MariaDB will need many connections. The calculation for spine is: total_connections = total_processes * (total_threads + script_servers + 1), then you must leave headroom for user connections, which will change depending on the number of concurrent login accounts.
max_allowed_packet	16777216	>=	16777216	With Remote polling capabilities, large amounts of data will be synced from the main server to the remote pollers. Therefore, keep this value at or above 16M.
max_heap_table_size	123 M	>=	122.21 M	If using the Cacti Performance Booster and choosing a memory storage engine, you have to be careful to flush your Performance Booster buffer before the system runs out of memory table space. This is done two ways, first reducing the size of your output column to just the right size. This column is in the tables poller_output, and poller_output_boost. The second thing you can do is allocate more memory to memory tables. We have arbitrarily chosen a recommended value of 10% of system memory, but if you are using SSD disk drives, or have a smaller system, you may ignore this recommendation or choose a different storage engine. You may see the expected consumption of the Performance Booster tables under Console -> System Utilities -> View Boost Status.
tmp_table_size	123 M	>=	122.21 M	When executing subqueries, having a larger temporary table size, keep those temporary tables in memory.
join_buffer_size	245 M	>=	244.41 M	When performing joins, if they are below this size, they will be kept in memory and never written to a temporary file.
innodb_file_per_table	ON	=	ON	When using InnoDB storage it is important to keep your table spaces separate. This makes managing the tables simpler for long time users of MariaDB. If you are running with this currently off, you can migrate to the per file storage by enabling the feature, and then running an alter statement on all InnoDB tables.
innodb_file_format	Barracuda	=	Barracuda	When using innodb_file_per_table, it is important to set the innodb_file_format to Barracuda. This setting will allow longer indexes important for certain Cacti tables.
innodb_large_prefix	ON	=	1	If your tables have very large indexes, you must operate with the Barracuda innodb_file_format and the innodb_large_prefix equal to 1. Failure to do this may result in plugins that can not properly create tables.
innodb_buffer_pool_size	1910 M	>=	1909.49 M	InnoDB will hold as much tables and indexes in system memory as is possible. Therefore, you should make the innodb_buffer_pool large enough to hold as much of the tables and index in memory. Checking the size of the /var/lib/mysql/cacti directory will help in determining this value. We are recommending 25% of your systems total memory, but your requirements will vary depending on your systems size.
innodb_doublewrite	ON	=	ON	This settings should remain ON unless your Cacti instances is running on either ZFS or FusionI/O which both have internal journaling to accomodate abrupt system crashes. However, if you have very good power, and your systems rarely go down and you have backups, turning this setting to OFF can net you almost a 50% increase in database performance.
innodb_lock_wait_timeout	50	>=	50	Rogue queries should not for the database to go offline to others. Kill these queries before they kill your system.
innodb_flush_method		eq	O_DIRECT	Maximum I/O performance happens when you use the O_DIRECT method to flush pages.
innodb_flush_log_at_trx_commit	2	=	2	Setting this value to 2 means that you will flush all transactions every second rather than at commit. This allows MariaDB to perform writing less often.
Last edited by jajao555 on Mon Dec 07, 2020 10:31 pm, edited 1 time in total.
cigamit
Developer
Posts: 3367
Joined: Thu Apr 07, 2005 3:29 pm
Location: B/CS Texas
Contact:

Re: Cron Interval does't update

Post by cigamit »

Seems like you have to 2 crons scheduled.
jajao555
Posts: 5
Joined: Mon Dec 07, 2020 4:12 pm

Re: Cron Interval does't update

Post by jajao555 »

Thanks! I did find another cron in /etc/crontab but I ended up having to use it instead and commented the other one out. Its been stable for about 40mins so far.

Cron that's working:

Code: Select all

[root@nmd-tp-cacti1 ~]# vim /etc/crontab 
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root

# For details see man 4 crontabs

# Example of job definition:
# .---------------- minute (0 - 59)
# |  .------------- hour (0 - 23)
# |  |  .---------- day of month (1 - 31)
# |  |  |  .------- month (1 - 12) OR jan,feb,mar,apr ...
# |  |  |  |  .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat
# |  |  |  |  |
# *  *  *  *  * user-name  command to be executed

*/5 * * * * cactiadmin php /var/www/html/cacti/poller.php > /dev/null 2>&1
Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests