• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • 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.

Forwarded to devs Out of memory php error on Let's Encrypt keep-secured.php crontab job

Bitpalast

Plesk addicted!
Plesk Guru
TITLE:
Out of memory php error on Let's Encrypt keep-secured.php crontab job
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
CentOS 7.6
Plesk Onyx 17.8, latest MUs
PROBLEM DESCRIPTION:
/usr/local/psa/admin/bin/php -dauto_prepend_file=sdk.php '/usr/local/psa/admin/plib/modules/letsencrypt/scripts/keep-secured.php'

not running because of "out of memory" php error on a machine with only 800 domains.​
STEPS TO REPRODUCE:
Nothing special, simply run
/usr/local/psa/admin/bin/php -dauto_prepend_file=sdk.php '/usr/local/psa/admin/plib/modules/letsencrypt/scripts/keep-secured.php'
either manually or from cronjobs.

However, not reproducible on other machines with practically identical setup. Some of our systems service more domains, e.g. 1000. Until now, the issue does not occur on them.​
ACTUAL RESULT:
Out of memory​
EXPECTED RESULT:
Running script​
ANY ADDITIONAL INFORMATION:
Can be solved by changing the default /usr/local/psa/admin/conf/php.ini RAM value to a higher value. We also realized that the script runtime on the machine in question was 960 seconds after the problem was fixed. With the default value of max script execution time of only 600 seconds in the same php.ini this would not have been possible to successfully execute either.

My suggestion is to consider higher default RAM and max execution time entries in the panel .php ini file to avoid issues with the keep-secured.php script.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
Peter, we know this issue: EXTLETSENC-644. Now it is under developer's investigation.

So far, you really need to increase memory and runtime limits.
 
Back
Top