raul_coca

I guess the problem has gone now, I optimized css and the images, I have like 2000+ images, this was the problem I think .

The error is exactly as I posted, nothing else.

The server had 768 MB allocated, I told them to make this value a bit higher and now it’s at 1024 MB.

I have seen that there is an apache update, could this be the problem?
The website is quite complex, I have 17 scripts running, maybe this is what’s causing the ocasional spikes.

I found something. Check out the first paragraph. I can’t find CGI Script on the server.

https://encodable.com/internal_server_error/

Maybe this last version of WP has some issues. Or not…
I have 5 other websites, I have hosting plans from the same company, I never had any troubles with them. This is the most complex website I have, maybe a shared server can’t whithstand this type of website.

Ok, now the error has changed a little.

[Thu Nov 06 22:02:39 2014] [error] [client 79.118.198.65] (12)Cannot allocate memory: couldn’t create child process: /opt/suphp/sbin/suphp for /home/public_html/index.php

Now the old error isn’t showing anymore:

Cannot allocate memory: couldn’t create child process: /opt/suphp/sbin/suphp for /home/public_html/xmlrpc.php

The .htaccess begins on the second line, the first line is blank. Maybe the code should be moved upwards.

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

Yes, the same error.

Same problem once again…after 6 hours though.

The topic can be closed. Thanks.

After I deleted the .htaccess file and recreated it from scratch, the website is running just fine for 4 hours or so without any issues. Thanks guys.

Yes. The problem is that I can’t see the errors right now because the site is working fine, I have seen that error logs shows the errors only when the website is down.

I don’t need the stuff in the old .htaccess, so this means that I can leave it as it is.

Yeah it works, but this is the normal behaviour, it only spikes ocasionally.

I deleted the .htaccess, but when I access an article it says

404 Not Found

The server can not find the requested page:
(port 80)
Please forward this error screen to WebMaster.

So I put the .htaccess file back. It’s really annoying…

My hosting provider has set the Virtual Memory Usage at 768 MB, he moved it up to 1024 MB for now. My website is a news website, I didn’t get that much traffic, only around 400 a day, but the website is complex, although I have bought a responsive and well built theme, which is called Newspaper from themeforest. My website is https://www.ziarulargesenilor.ro in case you missed it.

I deleted .htaccess and the website works again. What would be the problem then? Isn’t the .htaccess a must in order for the website to work? I know it is generated automatically if you delete it, but for now it isn’t showing up on the server.

Cannot allocate memory: couldn’t create child process: /opt/suphp/sbin/suphp for /home/site/public_html/xmlrpc.php

This is the only error that repeats itself on and on.
The only different line is this:

<?xmlversion=”1.0″?><methodCall><methodName>pingback.ping</methodName><params><[Thu Nov 06 11:28:10 2014] [error] [client 80.82.78.166] (12)Cannot allocate memory: couldn’t create child process: /opt/suphp/sbin/suphp for /home/site/public_html/xmlrpc.php

The permissions of files and folders are as it should be, 755 for folders and 644 for files.

You say I should delete the .htaccess from the server? I have a copy anyway. Let’s see what happens.