DailyMaintainance script not printing debug information

[Thomas Gross]

Hi Guys,

My server is running Cloudlinux 6.x and Plesk 11.5.30 (latest MU's installed), the daily maintenance script gets stuck at some stage and not completing at all so no statistics etc.

I tried getting the debug output via this kb article: http://kb.parallels.com/en/114065, however, I do not see any debug information, like below:

+ export PLESK_DEBUG_LEVEL=4
+ PLESK_DEBUG_LEVEL=4
+ /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php

This is all it prints, nothing else...

Is there any (other) way we can force the script to print the steps it does?

Cheers,
Tom

 

[IgorG]

JFYI, some of maintenance processes may take a lot of time.

 

[Thomas Gross]

JFYI, some of maintenance processes may take a lot of time.

I agree, however, the process(es) have been running for several days...

This is what it looks like this morning:

root 672381 0.0 0.0 19492 920 ? Ss 03:01 0:00 /usr/sbin/anacron -s
root 677454 0.0 0.0 106064 1404 ? SN 03:27 0:00 \_ /bin/bash /usr/bin/run-parts /etc/cron.daily
root 677582 0.0 0.0 106064 1272 ? SN 03:28 0:00 \_ /bin/sh /etc/cron.daily/50plesk-daily
root 677584 0.0 0.5 343644 32804 ? SN 03:28 0:00 | \_ /usr/bin/sw-engine -c /usr/local/psa/admin/conf/php.ini /usr/local/psa/admin/plib/DailyMaintainance/script.php
root 677956 0.0 0.4 339800 29588 ? SN 03:28 0:02 | \_ /usr/bin/sw-engine -c /usr/local/psa/admin/conf/php.ini /usr/local/psa/admin/plib/DailyMaintainance/task-script.php ExecuteStatistics --period=daily
root 677960 0.0 0.5 340332 29984 ? SN 03:28 0:02 | \_ /usr/bin/sw-engine -c /usr/local/psa/admin/conf/php.ini /usr/local/psa/admin/sbin/statistics --no-webstat
root 677965 0.0 0.8 365860 51152 ? SN 03:28 0:01 | \_ /usr/bin/sw-engine -c /usr/local/psa/admin/conf/php.ini /usr/local/psa/admin/sbin/statistics --calculate-list --domain-ids 1,2,3,15,99,17,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,49,51,52,53,55,56,57,58,59,60,61,62,63,64,67,89,69,70,187,71,75,76,77,78,126,135,139,142,79,80,81,577,590,594,598,618,91,92,93,94,95,96,97,82,160,98,100,101,102,109,154,172,111,112,123,158,198,431,113,114,115,116,117,118,119,120,121,122,124,128,129,130,131,132,133,134,136,137,141,143,144,145,146,147,148,149,150,151,152,153,156,159,161,163,228,164,165,166,167,168,169,170,173,174,175,180,176,178,179,181,182,183,185,186,188,189,190,191,192,193,196,194,195,197,199,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,217,218,219,220,221,222,223,224,226,227,230,231,232,233,234,236,237,238,239,240,241,242,244,245,246,517 no-webstat
root 690133 0.0 0.0 155724 3144 ? SN 03:34 0:00 | \_ /usr/local/psa/admin/bin/web_statistic_executor
root 677583 0.0 0.0 105948 920 ? SN 03:28 0:00 \_ awk -v progname=/etc/cron.daily/50plesk-daily progname {????? print progname ":\n"????? progname="";???? }???? { print; }


and it will stay like this for several days.

Also, running an strace on those processes shows no activity as well. Igor, could you please find out if there is a way to get the maintenance script to print out debug information ? As I said, the kb article doesn't work for me... but your devs might have an idea as to why.

Thanks,
Tom

 

[IgorG]

Try to add following in file /etc/sw-engine/pool.d/plesk.conf

env[PLESK_DEBUG] = 1

and restart psa service.

 

[IgorG]

Add additionally:

[log]
priority=7

into /usr/local/psa/admin/conf/panel.ini and restart psa service.

 

[Thomas Gross]

Hi Igor,

This has helped, however, only printed until here:

2014-04-08T03:40:56+12:00 INFO (6) [panel]: == End Mail boxes usage
2014-04-08T03:40:56+12:00 INFO (6) [panel]: == Task finish Mail boxes usage
2014-04-08T03:40:56+12:00 INFO (6) [panel]: == Task run Execute statistics backend: /usr/local/psa/bin/sw-engine-pleskrun "/usr/local/psa/admin/plib/DailyMaintainance/task-script.php" ExecuteStatistics '--period=daily'
2014-04-08T03:40:56+12:00 INFO (6) [panel]: == Begin Execute statistics backend

Processes are stuck again, any possibility to get more detail?

 

[IgorG]

Try to run statistics calculation separately with

# /usr/local/psa/admin/bin/statistics --calculate-all

and check output. Maybe it will help to find domain with damaged statistics or something else.

 

[Thomas Gross]

Try to run statistics calculation separately with

# /usr/local/psa/admin/bin/statistics --calculate-all

and check output. Maybe it will help to find domain with damaged statistics or something else.

Unfortunately this didn't print anything else... I've run out of ideas, stracing the processes will eventually bail out as it detects a debugger. Is there a chance to set it more verbose?

 

[Thomas Gross]

If anyone comes across that - it seems like the control panel doesn't like Cloudlinux in all aspects, here is a kb that fixes the issue:

http://kb.parallels.com/121460