• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Apache piped logging doesn't work for errorlogs

mooiesite

Basic Pleskian
PRODUCT, VERSION, MICROUPDATE, OPERATING SYSTEM, ARCHITECTURE
Plesk 11, Centos6, all microupdates, x86_64

PROBLEM DESCRIPTION
When enabling apache pipe logging al accesslogs are piped through /usr/local/psa/admin/sbin/pipelog
But errorlogs are not. This still can give problems with 'too many open files' when having hunderds of vhosts.

STEPS TO REPRODUCE
Enable piped logging:
mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa -e "replace into misc (param,val) values ('apache_pipelog', 'true');"
Rebuild config:
$PRODUCT_ROOT_D/admin/sbin/websrvmng -v -a
Check for open error_log files
lsof | grep error_log

ACTUAL RESULT
httpd 26774 apache 396w REG 202,1 711363 3281418 /var/www/vhosts/..../statistics/logs/error_log
httpd 26774 apache 397w REG 202,1 1702 3279866 /var/www/vhosts/..../statistics/logs/error_log
httpd 26774 apache 398w REG 202,1 0 3279066 /var/www/vhosts/..../statistics/logs/error_log
httpd 26774 apache 399w REG 202,1 23400 3278742 /var/www/vhosts/..../statistics/logs/error_log
httpd 26774 apache 400w REG 202,1 68739 3278396 /var/www/vhosts/..../statistics/logs/error_log
httpd 26774 apache 401w REG 202,1 41217 3277785 /var/www/vhosts/..../statistics/logs/error_log
httpd 26774 apache 402w REG 202,1 0 3277209 /var/www/vhosts/..../statistics/logs/error_log
httpd 26774 apache 403w REG 202,1 309490 3155146 /var/www/vhosts/..../statistics/logs/error_log
httpd 26774 apache 404w REG 202,1 24809 3150687 /var/www/vhosts/..../statistics/logs/error_log
httpd 26774 apache 405w REG 202,1 6031 3149764 /var/www/vhosts/..../statistics/logs/error_log
httpd 26774 apache 406w REG 202,1 1250 3148732 /var/www/vhosts/..../statistics/logs/error_log
httpd 26774 apache 407w REG 202,1 43174 3148317 /var/www/vhosts/..../statistics/logs/error_log
httpd 26774 apache 408w REG 202,1 198514 3147249 /var/www/vhosts/..../statistics/logs/error_log
httpd 26774 apache 409w REG 202,1 9528 3146567 /var/www/vhosts/..../statistics/logs/error_log
httpd 26774 apache 410w REG 202,1 0 3146282 /var/www/vhosts/..../statistics/logs/error_log
httpd 26774 apache 411w REG 202,1 10770 3145962 /var/www/vhosts/..../statistics/logs/error_log
(.....and a lot more)

EXPECTED RESULT
pipelog 20041 root 2w REG 202,1 5571760 810509 /var/www/vhosts/..../statistics/logs/error_log

ANY ADDITIONAL INFORMATION
It should also be possible to pipe the other apache logs like:
/var/log/atmail/access_log
/var/log/httpd/ssl_access_log
 
Last edited:
a simple reply would be nice..

a 'thank you, bug confirmed. We will try to fix this asap'
or 'we don't bother your bugreports...'
 
mooiesite, thank you for your feedback. We comfirmed such problem.
We will add information here when problem will be fixed.
 
Back
Top