Tagged: x
-
AuthorPosts
-
July 13, 2016 at 3:10 pm #1085519
andisitesParticipantHi!
When we attempt to upload an image to the media library we were getting HTTP error and Service Unavailable on site. We contacted our host for support and I am posting their reply here:
http://109.199.101.20/~ophdev/
WP 4.5.3
Cornerstone Version 1.3.0
X 4.3.4Thank you!
From our host support:
The issue seem to be caused by the theme of your site. When I have tried to upload the image with your original theme, I have noticed that the server load have increased to more than 100. Please note that such server load will affect all other sites on the server.
Of course, I have created a backup prior changing the theme and after I have finished my work, I have restored the database from that backup. During my investigation, I have traced the process started by your application when the images is uploaded through its original theme. In the output, I have noticed lots of entries like the ones below:
Code:
clone(child_stack=0x61e4f210, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x61e4f9d0, tls=0x61e4f940, child_tidptr=0x61e4f9d0) = 46624 <0.000032>
mmap(NULL, 16781312, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS|MAP_32BIT, -1, 0) = 0x61e50000 <0.000011>
mprotect(0x61e50000, 4096, PROT_NONE) = 0 <0.000017>
clone(child_stack=0x62e50210, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x62e509d0, tls=0x62e50940, child_tidptr=0x62e509d0) = 46625 <0.000019>
mmap(NULL, 16781312, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS|MAP_32BIT, -1, 0) = 0x62e51000 <0.000010>
mprotect(0x62e51000, 4096, PROT_NONE) = 0 <0.000017>
clone(child_stack=0x63e51210, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x63e519d0, tls=0x63e51940, child_tidptr=0x63e519d0) = 46626 <0.000017>
mmap(NULL, 16781312, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS|MAP_32BIT, -1, 0) = 0x63e52000 <0.000010>
mprotect(0x63e52000, 4096, PROT_NONE) = 0 <0.000017>
clone(child_stack=0x64e52210, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x64e529d0, tls=0x64e52940, child_tidptr=0x64e529d0) = 46627 <0.000018>
mmap(NULL, 16781312, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS|MAP_32BIT, -1, 0) = 0x64e53000 <0.000010>
mprotect(0x64e53000, 4096, PROT_NONE) = 0 <0.000017>
clone(child_stack=0x65e53210, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x65e539d0, tls=0x65e53940, child_tidptr=0x65e539d0) = 46628 <0.000018>
mmap(NULL, 16781312, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS|MAP_32BIT, -1, 0) = 0x65e54000 <0.000010>
mprotect(0x65e54000, 4096, PROT_NONE) = 0 <0.000017>
clone(child_stack=0x66e54210, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x66e549d0, tls=0x66e54940, child_tidptr=0x66e549d0) = 46629 <0.000021>
mmap(NULL, 16781312, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS|MAP_32BIT, -1, 0) = 0x66e55000 <0.000011>
mprotect(0x66e55000, 4096, PROT_NONE) = 0 <0.000021>
clone(child_stack=0x67e55210, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x67e559d0, tls=0x67e55940, child_tidptr=0x67e559d0) = 46630 <0.000022>
mmap(NULL, 16781312, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS|MAP_32BIT, -1, 0) = 0x67e56000 <0.000011>
mprotect(0x67e56000, 4096, PROT_NONE) = 0 <0.000019>
clone(child_stack=0x68e56210, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x68e569d0, tls=0x68e56940, child_tidptr=0x68e569d0) = 46631 <0.000023>
mmap(NULL, 16781312, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS|MAP_32BIT, -1, 0) = 0x68e57000 <0.000011>
mprotect(0x68e57000, 4096, PROT_NONE) = 0 <0.000019>
clone(child_stack=0x69e57210, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x69e579d0, tls=0x69e57940, child_tidptr=0x69e579d0) = 46632 <0.000020>
mmap(NULL, 16781312, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS|MAP_32BIT, -1, 0) = 0x69e58000 <0.000010>
mprotect(0x69e58000, 4096, PROT_NONE) = 0 <0.000019>it seems that for some reason, your theme is spawning quite a lot of child processes, which are overloading the entire server and ultimately, the upload process is being killed:
Code:
+++ killed by SIGKILL +++In order to resolve the issue, you should consider contacting the developers of the theme and ask for their assistance on the matter as they are more familiar with the functionality of their scripts than us. The full results from the system call trace are located in:
/home/ophdev/public_html/wp-admin/strace_new.txt
in case they need to check them.
July 13, 2016 at 11:42 pm #1086203
Rue NelModeratorHello There,
Thanks for writing in! X 4.6 is now available in automatic updates! This release contains fixes for several issues so be sure to check out the changelog. Please do update to the latest version. After doing the updates, always remember to clear all caches when updating so that the code from the latest release is always in use. This will help you to avoid any potential errors.
Please let us know how it goes.
July 14, 2016 at 6:06 am #1086608
jstherapiesParticipantI’m having a similar issue, can’t upload even small images. Everything is up to date and I’ve cleared the cache.
July 14, 2016 at 8:14 am #1086757
Paul RModeratorHi,
Would you mind providing us with login credentials so we can take a closer look? To do this, you can make a post with the following info:
– Link to your site
– WordPress Admin username / password
– FTP credentialsDon’t forget to select Set as private reply. This ensures your information is only visible to our staff.
July 14, 2016 at 11:45 am #1087068
andisitesParticipantThis reply has been marked as private.July 14, 2016 at 3:31 pm #1087415
ncuervo001ParticipantThis reply has been marked as private.July 14, 2016 at 8:34 pm #1087790
Rue NelModeratorHello Guys,
Thanks for updating this thread!
@andisites:
I did some further investigation. I noticed that you are using PHP version 5.3.29 and WordPress 4.5 requires at least 5.6 (https://wordpress.org/about/requirements/). This could possibly be the cause of the issue. In most cases you cannot update your PHP version yourself and need to contact your host about this. The upgrade process is an easy process and should be something your host can do for you without affecting your website or charging you for it. Here’s a letter you can send to your hosting company:Dear host, I\'m interested in running the open-source WordPress <https://wordpress.org/> web software and I was wondering if my account supported the following: - PHP 5.6 or greater - MySQL 5.6 or greater - The mod_rewrite Apache module Looking forward to your reply.Hope this helps. Kindly let us know.
@ncuervo001:
Please do check your PHP version because you are using an older version too! You are using 5.4.45.For more troubleshooting with this issue, please check out this article:
13 Ways to Fix the HTTP Error When Uploading Images to WordPress
July 15, 2016 at 7:01 am #1088376
andisitesParticipantThank you so much!! I will pass this along to our host and request they update.
Hope you have a great weekend and thank you again!
July 15, 2016 at 5:38 pm #1089134
FriechModeratorLet us know how it goes, have a wonderful weekend too.
Thanks.
-
AuthorPosts
- <script> jQuery(function($){ $("#no-reply-1085519 .bbp-template-notice, .bbp-no-topic .bbp-template-notice").removeClass('bbp-template-notice'); }); </script>
