• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Issue Error Message - Non-zero exit status returned by script

Heavnerboy

New Pleskian
Server operating system version
Windows 10 - Version 22H2 (Build 19045.2486)
Plesk version and microupdate number
18.0.50
Hi guys,
for some time now I have been getting the following error message under the Applications tab on my Plesk interface:

"
Warnung: Die App wurde nicht konfiguriert: Non-zero exit status returned by script. Output stream: 'PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/vhosts/juwelier-carlthomass.de/httpdocs/wp-includes/pomo/mo.php on line 328 PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/vhosts/juwelier-carlthomass.de/httpdocs/wp-includes/class-wp-fatal-error-handler.php on line 74 PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 221184 bytes) in Unknown on line 0 '. Error stream: 'PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/vhosts/juwelier-carlthomass.de/httpdocs/wp-includes/pomo/mo.php on line 328 PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/vhosts/juwelier-carlthomass.de/httpdocs/wp-includes/class-wp-fatal-error-handler.php on line 74 PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 221184 bytes) in Unknown on line 0 '. Non-zero exit status returned by script. Output stream: 'PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 655360 bytes) in /var/www/vhosts/juwelier-carlthomass.de/httpdocs/wp-includes/pomo/translations.php on line 166 '. Error stream: 'PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 655360 bytes) in /var/www/vhosts/juwelier-carlthomass.de/httpdocs/wp-includes/pomo/translations.php on line 166 '. Non-zero exit status returned by script. Output stream: 'PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 655360 bytes) in /var/www/vhosts/juwelier-carlthomass.de/httpdocs/wp-includes/pomo/translations.php on line 166 '. Error stream: 'PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 655360 bytes) in /var/www/vhosts/juwelier-carlthomass.de/httpdocs/wp-includes/pomo/translations.php on line 166 '. Non-zero exit status returned by script. Output stream: 'PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 655360 bytes) in /var/www/vhosts/juwelier-carlthomass.de/httpdocs/wp-includes/pomo/translations.php on line 166 '. Error stream: 'PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 655360 bytes) in /var/www/vhosts/juwelier-carlthomass.de/httpdocs/wp-includes/pomo/translations.php on line 166 '. Non-zero exit status returned by script. Output stream: 'PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 655360 bytes) in /var/www/vhosts/juwelier-carlthomass.de/httpdocs/wp-includes/pomo/translations.php on line 166 '. Error stream: 'PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 655360 bytes) in /var/www/vhosts/juwelier-carlthomass.de/httpdocs/wp-includes/pomo/translations.php on line 166 '."

At first I thought that I can solve the problem by increasing the "memory_limit". I did that and raised it from 128M to 512M. Unfortunately I still get this error message.

Can anyone tell me how to fix this error message?
Greetings

Heavnerboy
 
Ngl that's not a plesk issue but your PHP scripting issue. Probably a memory link. Your script is basically telling it to use all the memory and then some. Since this is wordpress and it's pointing to wp-includes/pomo/translations.php tells me that there might be a plugin that's trying to utilize that API and it's cuasing the issue. I would suggest disabling all plugins and start turning them on one at a time until you get the error to find your broken plugin, assuming you didn't do anything custom yourself.
 
Back
Top