Adding a new Virtual server Problem

Submitted by mike8 on Sat, 03/10/2012 - 00:49

I don't know why I always seem to have problems pop up on the weekend. Anyway. I have 4 Static IP's 202-205. I have Virtualmin log in on IP 202, I also have a web page on that IP. both work fine. I added a 2nd Virtual Server on IP 203. I can FTP to this site, I can install a SSL Certificate on that site, but when I tried to access that site on the web it takes me to the IP 202 site. I checked all the settings, and everything seems to be set right. After messing with it for a while, it started going to the right site on IP 203.

Not sure what I did to fix it, it just started working. So I decided to set up the next web site on IP 204, set everything up as normal ( I've done this many times) and after it was all set up, database restored, and site ftped up to the site. When I try to access it on the web, it again goes to the IP 202 site. I have checked everything, and rechecked it, but I can't figure out what is going on.

Not sure what to do here, but unless someone has a good idea as to what is going on, I may need someone to log in and check it out.

Regards Michael

Status: 
Closed (fixed)

Comments

Submitted by andreychek on Sat, 03/10/2012 - 07:43

Well, are these sites your having problems with sites that were originally on the .202 IP address?

If so, you may just be dealing with a DNS caching issue, which can occur anytime an IP address changes. It just takes a few hours for the DNS cache to clear, and then it works fine.

One way to test that is to try it from a different computer (on a different ISP, so you can be sure the ISP's DNS hasn't cached it).

Or, if you let us know the name of the domain you're having problems with, we can take a look and make sure the IP is correct.

Submitted by mike8 on Sat, 03/10/2012 - 13:51

Thanks for the reply andreychek, I think you hit it right on the head. because after a while that site I was having problems with started working, (almost) I did change the IP from the IP 202 to IP 204 so I think it was the cache. Anyway then I get a error about "fcgi"

[error] [client xx.xx.xxx.204] Premature end of script headers: home.php
[Sat Mar 10 05:50:02 2012] [warn] (104)Connection reset by peer: mod_fcgid: read data from fastcgi server error.

I switched to "cgi in PHP script execution mode Apache mod_php (run as Apache's user)

and also Ruby script execution mode  CGI wrapper (run as virtual server owner)

it then started working. Also while set to fcgi, I could access the admin back end by using "https"

So it looks like my problem may have something to do the the upgrade to PHP 5.2

Any ideas on how to fix this?

Thanks

Regards Michael

Submitted by andreychek on Sat, 03/10/2012 - 14:35

Well, not all scripts will work in every execution mode.

However, one thing you could try doing is editing $HOME/etc/php.ini, and set cgi.fix_pathinfo to 0. That can resolve some CGI/FCGID problems in PHP under PHP 5.3.

Submitted by mike8 on Sat, 03/10/2012 - 15:03

Thanks for the reply, I looked at the "$HOME/etc/php.ini, and set cgi.fix_pathinfo to 0" but that line is not in my php.ini, and I'm running php 5.2, not php 5.3

All these sites were working fine until I had a error with the Virtualmin Updates, and I had conflicts with the i386 files on a 64bit system. I tried to remove them one at a time, and replace them with the x86_64 version. That's were I had the problems, because It made my server unacceptable. I had to format and reinstall. Originally I had CentOS 5.5, after a few auto updates, I was running CentOS 5.8, anyway I downloaded the 5.8 64bit ISO and installed with it. I noticed it took forever to install, also when I tried to install Vertualmin from the script in MY License on your site It also took forever, and had a few errors, but I think it was just the Clamd that produced the errors. So I didn't worry about it. But there may have been other errors that I didn't see.

maybe I should go back to the CentOS 5.5, as everything worked just fine. I remember trying to run CentOS 6.2, and I had a lot of problems with it, so I went back to 5.5 and didn't have any problems setting it all up.

If that makes any sense.

Michael

Submitted by mike8 on Sat, 03/10/2012 - 17:43

Well I added a couple lines to my ".htaccess" and put the fcgi stuff back to normal, and it is now working.

The thing I don't understand it, before if I created a Virtual Server, and FTPed to it, and uploaded my site, I could access it immediately, but now I have to wait at least 1 hr or more before I can access it. So something is not set right. I just created another Virtual Server on its own IP (same IP it has always been on, but I can't access it, I get the same errors

When going to "www.asr-systems.com/index.php" I get "file not found." if I just go to the url with out the "index.php I get the other error. I attached 2 screen shots of the 2 errors so you can see.

Submitted by andreychek on Sat, 03/10/2012 - 17:48

So right now, the domain "asr-systems.com" points to the .205 IP address, and is showing nothing in the public_html folder for that account.

What should the IP address be, and have you uploaded content into the public_html folder for that account?

Submitted by mike8 on Sat, 03/10/2012 - 18:58

Yes 205 is the right IP address, and yes, I have uploaded the whole site to that folder. so it should come up when you go to the site. Last night when I was having the same problem with the other site, it took 2, to 3 hours before it would actually open the site. And like right now I set up another site on a shared IP of 74.87.143.202 called "www.gochenourfamilyhistory.com" But it comes up as the main site of "asrservice.com.

So maybe after a few hours it may start to work too. I just don't understand why it takes so long to access the site? It never did this before.

By the way, after reinstalling Centos, and Virtualmin, I was able to mount the backup drive on the 2nd hard drive, so I was able to mount it by my self, and also get my mail server working right the 1st try. So I'm gaining on the Linux stuff..

Here is the error log entry; [Wed Mar 07 23:21:17 2012] [warn] (103)Software caused connection abort: mod_fcgid: ap_pass_brigade failed in handle_request function

Michael

Submitted by andreychek on Sat, 03/10/2012 - 19:32

What happens if you restart Apache, does that resolve the issue you're seeing? You can do that with this command:

/etc/init.d/httpd restart

And regarding your earlier question -- I don't think this issue is related to using CentOS 5.5 vs 5.8 -- if you're running CentOS 5, we'd always recommend running the most recent version.

Submitted by mike8 on Sat, 03/10/2012 - 19:51

Tried restarting Apache, but it wouldn't start, I had to remove the 2 lines I added to the "httpd.conf" to get the other site to work. Not its down again too. What ever is going on has to do with the way PHP files are handled.

It opens a html page just fine, but not a php site. I am completely lost here, I don't know what else to try. I guess I could disable fcgi, but I don't want to. Is it possible that when I upgraded my php 5.1 to 5.2 that something didn't get installed correctly? I got it from the Bleeding edge shown in one of the other post that you recommended.

Michael

Submitted by andreychek on Sat, 03/10/2012 - 20:28

Moving from PHP 5.1 to 5.2 shouldn't cause any problems, that's a fairly common things folks here do.

I see it's generating a 500 error now, what error is showing up in the logs?

Submitted by mike8 on Sat, 03/10/2012 - 20:48

The same error I showed you in the earlier post.

Here is the error log entry; [Wed Mar 07 23:21:17 2012] [warn] (103)Software caused connection abort: mod_fcgid: ap_pass_brigade failed in handle_request function

This is the same error on all 3 PHP sites.

Submitted by andreychek on Sat, 03/10/2012 - 20:55

Okay. That's unfortunately a generic error, and typically suggests a problem of some sort with the application, or maybe just an incompatibility with that run mode.

What did you say happens if you set it to use CGI? You can do that in Server Configuration -> Website Options -> PHP Execution Mode.

Also, if you go into System Settings -> Re-Check Config, does it notice any problems?

Submitted by mike8 on Sat, 03/10/2012 - 21:29

I have to set it to "PHP script execution mode Apache mod_php (run as Apache's user)" If I set it to anything else the site won't open. By the way all the sites are assessable now. It took about 2 hrs to start working.

When I Re-Check Config. everything shows OK.

Submitted by mike8 on Sun, 03/11/2012 - 00:31

OK I'm going to close this problem out, and Start a new one. All the sites are up and running, so the original problem no long exists. at lease in the original form.

Thanks for the help,

Michael