Hi,
I just purchased Newsmag and right after installing the theme, I get Error 503. I’m able to change themes via FTP and that brings back the site, but otherwise I’m not even able to access the back-end.
Any suggestions as to how I can fix this? Thanks in advance.
Error 503 is server overload, as you likely know.
Check your server error logs to see WHAT is causing it to die.
If it’s the issue with the CPU spikes, then you might have to request the older version of Visual Composer, due to a semi-rare issue with some web servers.
See: https://forum.tagdiv.com/topic/newsmag-1-7-1-killed-our-server-again/
Make sure you disable ALL your other plugins EXCEPT for Visual Composer as starting point!
Chris, thanks for the response.
This is what the hosting company told me about the issue – please bear with me since I’m not very accustomed to such issues.
I have checked the logs of rcdronearena.com and found the following error messages:-
------
[Thu Jun 04 15:39:39 2015] [warn] [client <myIP>] mod_fcgid: can't apply process slot for /usr/local/cpanel/cgi-sys/php-fcgi, referer: http://www.rcdronearena.com/wp-admin/admin.php?page=td_theme_panel
[Thu Jun 04 15:40:01 2015] [warn] [client <myIP>] mod_fcgid: can't apply process slot for /usr/local/cpanel/cgi-sys/php-fcgi, referer: http://www.rcdronearena.com/wp-admin/admin.php?page=td_theme_panel
[Thu Jun 04 15:40:14 2015] [warn] [client <myIP>] mod_fcgid: can't apply process slot for /usr/local/cpanel/cgi-sys/php-fcgi, referer: http://www.rcdronearena.com/wp-admin/themes.php
[Thu Jun 04 15:40:43 2015] [warn] [client <myIP>] mod_fcgid: can't apply process slot for /usr/local/cpanel/cgi-sys/php-fcgi, referer: http://www.rcdronearena.com/wp-admin/admin.php?page=td_theme_panel
[Thu Jun 04 15:41:18 2015] [warn] [client <myIP>] mod_fcgid: can't apply process slot for /usr/local/cpanel/cgi-sys/php-fcgi, referer: http://www.rcdronearena.com/wp-admin/themes.php
------
The issue that you are facing is mainly due to saturation of the number of fcgi processes allocated for your account. We allow 3 child process and for each child process, 256 worker processes. Once that limit is breached, you see that kind of error. However, those errors are auto-fixed once the number of processes reduce.
Killed queries for the database(s):-
----------------------------
<dbName>
Also, the following error message regarding the database(s):-
------
2015-06-02 21:15:16 +0000 [info] killed_thread_id:67165003 user:<user> host:localhost db:<dB> command:Sleep time:23 query:
2015-06-03 20:44:47 +0000 [info] killed_thread_id:68010453 user:<user> host:localhost db:<dB> command:Sleep time:23 query:
------
------
The MySQL queries for the above mentioned databases are getting killed by the server which is causing the intermittent issue with the site loading. You can verify the same from cPanel >> Health checks and Monitoring >> Mysql Killed Queries.
Please note that, the long_query_time set for the MySQL service is 15 seconds.
Since it is a shared server, we can't alter this values for single domain. We have set this limit carefully to avoid any wastage/abuse of server resources and increasing the limit will result in degradation of server's performance.
Do you think I need an older version of Visual Composer?
Thanks once again.
I think so !
Lucian should be back soon for support methinks.
I think you can request the older version from contact@tagdiv.com (unless they changed that).
You could post basic CPU usage — but not really relevant if it’s not your server dedicated to your website, as any CPU usage would be for the “entire” box with all websites, and not just your site — unless you have a VPN which splinters the system into chunks and shows just the CPU usage for your “container.”
But anyway … you likely need to wait for official tagdiv support folk to help any further 🙂
Yes…. I think you will need to do what we did:
a) use older version of Visual Composer — which the main thing is missing is the extra woocommerce modules, I think.
b) possibly use the SHIM plugin; where you would setup your home page with VC then turn VC off leaving the shim plugin active.
In theory, if you go back to a 4.3.5 version of VC the shim may not be needed. It’s really only needed with the 4.4x versions which added a ton of ‘code bloat’ and hence the CPU issues started to crop up. Likely you’re getting a 503 due to how they have your container setup; in our case having dedicated server, it didn’t kill the box entirely but it started to really slow down when CPU usage jumped by 50 times normal load (!) — might be 500 or 5000 times normal load, actually — dropping a zero someplace there.