Control Web Panel
WebPanel => CentOS 7 Problems => Topic started by: gailclark80 on February 05, 2021, 06:38:28 AM
-
my WordPress running on CWP7, PHP 7.027
Today, my wordpress can’t upload images suddenly, the error is as follows:
“Post-processing of the image failed likely because the server is busy or does not have enough resources. Uploading a smaller image may help. Suggested maximum size is 2500 pixels.”
I open the apache error_log, the following error is prompted
AH00052: child pid 4822 exit signal Segmentation fault (11)
I have searched many methods and tried all of them, but none of them can solve the problem. I tried the following methods
1. Change these data in php.ini
post_max_size = 128M
upload_max_filesize = 128M
max_execution_time = 360
memory_limit = 1024M
2. Add this to functions.php of my theme
add_filter(‘wp_image_editors’, function() {return array(‘WP_Image_Editor_GD’ );} );
3. Add this to wp-includes/functions.php
function use_gd_editor($array) {
return array(‘WP_Image_Editor_GD’, );
}
add_filter(‘wp_image_editors’,’use_gd_editor’ );
4. install imagick module for PHP
How to solve this problem?
The strange thing is that in addition to this wordpress, I can't upload pictures on another wordpress on another VPS, and the same error occurs. This VPS is also running on CWP7
Thank you very much!
-
remove mod security and reinstall it again and test.
-
Yesterday we went through this problem with many servers that use CWP. The solution was to do apache rebuild and use version 2.4.46
-
similar problem here.
I can upload images, but I can't save changes in the wordpress pages...
It started from one day to another, two or three days ago.
I have another wordpress installations in another servers and are working ok.
I pay for a one time solution, because the problem is very weird... Nitin is helping me.
-
Yesterday we went through this problem with many servers that use CWP. The solution was to do apache rebuild and use version 2.4.46
Hello! I have the same problem.
Does this solution of recompiling Apache to 2.4.46 work?
-
Yesterday we went through this problem with many servers that use CWP. The solution was to do apache rebuild and use version 2.4.46
Hello! I have the same problem.
Does this solution of recompiling Apache to 2.4.46 work?
Hello,
it sure did for me. There are already more than 8 servers with similar problems and that was the solution for everyone.
-
WOWWWWWW
THANK YOU SO MUCH!! Just for curiosity... vocę é Br? Obrigado mesmo!!
My problem was a bit different but moving to apache 2.4.46 resolve my problem.
-
Thanks man!
I haven't slept for two days !
Thanks a lot.
-
Thanks man!
I haven't slept for two days !
Thanks a lot.
you are not alone Jonatan... you are not alone... I believe that a lot people do not sleep in the last days with this problem.
-
WOWWWWWW
THANK YOU SO MUCH!! Just for curiosity... vocę é Br? Obrigado mesmo!!
My problem was a bit different but moving to apache 2.4.46 resolve my problem.
Sou BR sim.. ;)
Que bom que deu certo.
Thanks man!
I haven't slept for two days !
Thanks a lot.
Glad I was able to collaborate so that we can sleep in peace all weekend.
-
Thank you so much. Updated to Apache version worked like a charm. God bless you.
-
Updating Apache didn't work for me... :(
any other solution?
-
Update or rebuild the apache will resolve this issue.