• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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