• 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!
  • 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.

Large log files view by plesk-panel log_viewer

unlo

New Pleskian
Hello!

Some clients take a looks at large files by the plesk log_file_viewer.php and after it, process of lighttpd (sw-cp-server) are growing for that size.

Now i can solving the problem only by restarting of lighttpd, then proccess grows for more than 100Mb:
ps aux |grep sw-cp-server |grep 1001 |awk '{if($5>100000) system("/etc/init.d/sw-cp-server restart")}'

Seems to be lighttpd dont have some parameter to limit body_size.

PHP parameters are not usefull for this problem (memory_limit is lower, and i dont want to chane of max_execution_time
for some other reasons).

To parallels: Maybe its possible to set some filesize limit in log_viewer for exclude memory leaks of sw-cp-serverd?
 
unlo,

As I know such behaviour is caused by the sw-cp-server architecture. Reading and writing work as intependend "threads" there (is uses poll-based multiplexing so they are not real, but are still undependent). If browser initiate the requests and do not actually read data, waiting for user to answer the "what to do with this file" dialog (IE does so, and Firefox _sometimes_ do not, that is, it begins reading data before user decides).
This problem under developers investigation now and I hope it will be solved in the one of the nearest Plesk updates.
 
sw-cp-serverd is eating all free memory

sw-cp-serverd is eating all free memory while I downloading backup file.
And after downloading, sw-cp-serverd is still huge in size.
Do you know why?
 
sw-cp-serverd is eating all free memory while I downloading backup file.
And after downloading, sw-cp-serverd is still huge in size.
Do you know why?

There is the same reason that I have described above.
 
Back
Top