dman
Perch
Hey Stephen,
Thanks for the reply! Sounds like isolation mode is a positive change. The fact though is that one of these sites is live and the other is in development and only accessible via the "Instant access domain alias". When one of these sites is unresponsive, both are unresponsive. If it is an issue with a specific site, maybe a DDOS or some code issue, it should not effect both sites, especially the site using the "Instant access domain alias". One site is plain PHP and the other uses MySQL. This also does not explain why the live site worked without issue until the beginning of September when it started to have these issues.
I just got a reply to my support ticket and they asked that I turn on the error logs, which are already on. There are some file not found errors like the favicon.ico and possible broken links. Other than that there are the following FastCGI errors:
FastCGI: incomplete headers (0 bytes) received from server "/hsphere/shared/php5/bin/php"
Possible Cause: http://www.forum.psoft.net/archive/index.php/t-28571.html
(2)No such file or directory: FastCGI: failed to connect to (dynamic) server "/hsphere/shared/php5/bin/php": something is seriously wrong, any chance the socket/named_pipe directory was removed?, see the FastCgiIpcDir directive
Possible Cause: http://forum.psoft.net/showthread.php?t=30658
(111)Connection refused: FastCGI: failed to connect to server "/hsphere/shared/php5/bin/php": connect() failed, referer: http://instantaccessalias/company/page.php
Any ideas what is causing the above errors? Is this something I need to handle in my CP? There is another post about these issues in the past but there did not appear to be a resolution: http://support.jodohost.com/showthread.php?t=21661#post81628
At this point I'm at a loss for how to fix it. I can try to move these sites to another server but that is not easy and I'm not clear it would fix these issues. If this is a code issue can some one point me in the direction of a fix? I've googled these errors and they all appear to point to HSphere configuration issues.
Thanks for the reply! Sounds like isolation mode is a positive change. The fact though is that one of these sites is live and the other is in development and only accessible via the "Instant access domain alias". When one of these sites is unresponsive, both are unresponsive. If it is an issue with a specific site, maybe a DDOS or some code issue, it should not effect both sites, especially the site using the "Instant access domain alias". One site is plain PHP and the other uses MySQL. This also does not explain why the live site worked without issue until the beginning of September when it started to have these issues.
I just got a reply to my support ticket and they asked that I turn on the error logs, which are already on. There are some file not found errors like the favicon.ico and possible broken links. Other than that there are the following FastCGI errors:
FastCGI: incomplete headers (0 bytes) received from server "/hsphere/shared/php5/bin/php"
Possible Cause: http://www.forum.psoft.net/archive/index.php/t-28571.html
(2)No such file or directory: FastCGI: failed to connect to (dynamic) server "/hsphere/shared/php5/bin/php": something is seriously wrong, any chance the socket/named_pipe directory was removed?, see the FastCgiIpcDir directive
Possible Cause: http://forum.psoft.net/showthread.php?t=30658
(111)Connection refused: FastCGI: failed to connect to server "/hsphere/shared/php5/bin/php": connect() failed, referer: http://instantaccessalias/company/page.php
Any ideas what is causing the above errors? Is this something I need to handle in my CP? There is another post about these issues in the past but there did not appear to be a resolution: http://support.jodohost.com/showthread.php?t=21661#post81628
At this point I'm at a loss for how to fix it. I can try to move these sites to another server but that is not easy and I'm not clear it would fix these issues. If this is a code issue can some one point me in the direction of a fix? I've googled these errors and they all appear to point to HSphere configuration issues.