• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Question What is the task schedule of daily statistics jobs?

raytracy

Basic Pleskian
(CentOS 7.5 + Ontx 17.5)

I have found that my system has two Plesk maintenance process ran daily:

/usr/local/psa/admin/bin/statistics_collector
/usr/local/psa/admin/sbin/statistics_log_processor


Unfortunately, these two process ran at 7:00~10:00AM, which come across the busy time of my web server, and interference the critical web service.

I don't know who spawn these process and wish to know how to shift the job schedule to early hour.
Where can I investigate this incident?
 
In Centos 6 you can go to /etc/anacron and change the value

START_HOURS_RANGE=5-14

In my case start at 5 am (GMT +2, i am in GMT -7) so the are executed al midnight
 
This is my /etc/anacrontab:


# /etc/anacrontab: configuration file for anacron
# See anacron(8) and anacrontab(5) for details.

SHELL=/bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
# the maximal random delay added to the base delay of the jobs
RANDOM_DELAY=45
# the jobs will be started during the following hours only
START_HOURS_RANGE=1-5

#period in days delay in minutes job-identifier command
1 5 cron.daily nice run-parts /etc/cron.daily
7 25 cron.weekly nice run-parts /etc/cron.weekly
@monthly 45 cron.monthly nice run-parts /etc/cron.monthly


Does that possible the maintenance job running over several hours?

By the way, may I specify the START_HOURS_RANGE=22-3 to designate from 22:00 to next day 3:00am?
 
START_HOURS_RANGE is the range this task could be started, i guess tasks execution are not limited to this hours, now i have a problem with a process running for many hours so process are not kill at the end of this range.

START_HOURS_RANGE=22-3 i am not pretty sure if it works but may yes.
 
Back
Top