• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Changing php memory limit on additional phps

AWSolutions

New Pleskian
Hello,

We are using plesk 7.0.x onyx. We have a site that is configured to run php 7.0.21 and I have changed through the control panel AND through editing /opt/plesk/php/7.0/etc/php.ini the memory limit to 512M

When I go to mysite.com/phpinfo.php I see the recorded value. However I have a cron that is being exectued via crontab (/etc/crontab):

* * * * * u_user /opt/plesk/php/7.0/bin/php /var/www/vhosts/mysite.com/httpdocs/cron.php

I am constantly getting these errors via email after cron execution:

PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 87 bytes) in /var/www/vhosts/mysite.com/httpdocs/app/code/community/CompanyModule/ModuleName/Helper/Data.php on line 636

It seems the cli for some reason is still sticking with the default 128M for its memory, although CLI is reporting the correct value

[me@myserver ~]$ /opt/plesk/php/7.0/bin/php -i |grep memory
memory_limit => 512M => 512M

Any ideas, I am completely confused by this!
 
Hi AWSolutions,

try to use a scheduled task as for example:

Code:
cd /var/www/vhosts/mydomain.de/httpdocs/ && /opt/plesk/php/7.0/bin/php cron.php
or
Code:
/opt/plesk/php/7.0/bin/php httpdocs/cron.php

... as your domain specific documentroot starts at "/var/www/vhosts/mydomain.de/". ;)


Pls. check your "panel.log" ( or/and the domain specific log - files ) for possible issues/errors/problems, if you still experience the described issues/problems.



Additional informations:


Sometimes, it is as well a good idea to change the log - level ( TEMPORARILY! ), to get more informations in Plesk - log - files:

 
Back
Top