Applicable to:
- Plesk for Linux
Symptoms
- The following error can be found in
/var/www/vhosts/example.com/logs/error_logfile:
CONFIG_TEXT: [proxy_fcgi:error] [pid 350:tid 139649016084224] (104)Connection reset by peer: [client 203.0.113.2:58642] AH01075: Error dispatching request to :, referer: http://example.com/wordpress/wp-admin/upload.php
- Errors in
/var/log/audit/audit.log:
CONFIG_TEXT: type=ANOM_ABEND msg=audit(1484625171.339:4365269): auid=4294967295 uid=10006 gid=1003 ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0 pid=22074 comm="php-fpm" reason="memory violation" sig=11
- PHP FPM handler errors in
/var/log/messages:
CONFIG_TEXT: server kernel: php-fpm[22064]: segfault at a636 ip 000000000000a636 sp 00007ffcc57f8948 error 14 in php-fpm[400000+3a8000]
`dmesg`command output:
CONFIG_TEXT: [4289853.349667] php-cgi[49427]: segfault at 30 ip 00007fc662113088 sp 00007fc62f2d0d10 error 4
[4289853.349670] php-cgi[49424]: segfault at 30 ip 00007fc662113088 sp 00007fc630ad3d10 error 4
[4289853.349672] in libMagickCore.so.5.0.0[7fc661f8e000+237000]
[4289853.349674] in libMagickCore.so.5.0.0[7fc661f8e000+237000]
[4289853.349680] in libMagickCore.so.5.0.0[7fc661f8e000+237000]
Cause
ImageMagick library bug.
Resolution
As a workaround, disable imagick PHP module for PHP handler that is enabled for the website:
- Log into Plesk
- Browse to Tools & Settings > PHP Settings
- Click on the PHP handler that is set for the domain, e.g. PHP 5.6:
- Uncheck imagick checkbox to disable the extension
Make sure that no sites are using this module.
Note: These settings are common to the following PHP handlers: 5.6.36 CGI application, 5.6.36 FastCGI application. The settings apply to all websites that use these handlers.
Comments
10 comments
Hi, have this problem. Some sites doesnt work fine, there are some problem due to this shit. Its not possible to remove it, missing dependecies. What to do ?
@Petr Vonka,
Hi! Did you try just disabling the module in Tools & Settings > PHP Settings?
Alternatively, you may remove the module without dependencies:
# rpm -e --nodeps --justdb ImageMagick
Manually updating OS packages not working properly. Also FTP link is broken.
Better solution:
add_filter( 'wp_image_editors', 'filter_wp_image_editors', 10, 1 );
function filter_wp_image_editors($array)
{
return ['WP_Image_Editor_GD'];
}
in wp-config.php. You disable Imagick in your WP by doing this.
Is there another solution planned to fix this permanently?
There are no other solutions planned from Plesk side as the issue is related to ImageMagick, it is not related to Plesk.
Are there deb packages for ImageMagick? Is this issue in Ubuntu 16.04 fixed? We have the same error message on a wordpress website on an Ubuntu 16.04 Plesk Installation.
Hi @Roger!
I was not able to find any .deb packages for that, so ImageMagick 6.8.9-9 seemed to be the newest possible on Ubuntu 16 (not talking about a manual compilation of course, for example like here).
However, on Ubuntu 18.04 this PHP extension is updated to 6.9.7-4 for both system PHP and PHP shipped with Plesk:
# for i in `ls /opt/plesk/php/`; do /opt/plesk/php/$i/bin/php -r 'print_r(Imagick::getVersion());'; done
Array
(
[versionNumber] => 1687
[versionString] => ImageMagick 6.9.7-4 Q16 x86_64 20170114 http://www.imagemagick.org
)
Array
(
[versionNumber] => 1687
[versionString] => ImageMagick 6.9.7-4 Q16 x86_64 20170114 http://www.imagemagick.org
)
Array
(
[versionNumber] => 1687
[versionString] => ImageMagick 6.9.7-4 Q16 x86_64 20170114 http://www.imagemagick.org
)
So I suggest considering a migration to Ubuntu 18.04 in order to sort this out.
Im in ubuntu 18.04 and Plesk onyx, but it seems the Error ist Not resolved.
So is there any solution?
Hello @Jens,
The issue should be investigated on ImageMagick side as such behavior is caused by bug in their product.
I would like to suggest opening an issue on the GitHub repository of ImageMagick or at their forum.
Hello in ubuntu 16.04 and Plesk Obsidian 18.0.21 this error is not resolved and it persists only with domains with wordpress sites.
Hi Federica Della Monica: The issue should be investigated on ImageMagick side as such behavior is caused by bug in their product.
I would like to suggest opening an issue on the GitHub repository of ImageMagick or at their forum.
Please sign in to leave a comment.