Jump to content

Recommended Posts

Hi,

 

Server is Windows 2003

php 5.0.5

OpenSSL 0.9.8d

mod_SSL 2.0.59

Apache 2.0.59 (win32)

MySQL 5.0.41

 

 

I am currently trying to build a new site which is going well, however on a frequent basis I am getting an error msg of "DIE!!!!" in my web browser, I have tried IE7 and FF3 but both will give me the same msg, then it will work with explination or change of URL.

 

I have also tested on the dev box and it will display the page at the same time as the other browsers giving me the die msg.

 

I have set all logging on as this is the dev box and set Debug or On (in php.ini), and there is nothing in any of the log file for either PHP or for Apache, and I have checked the event viewer with no PHP or Apache errors showing in there.

 

I can not understand why this si giving me this error, is this a browsers based issue or is it a config issue.

 

Let me know what info to post to see if you can help.

 

Thanks for reading

 

B

Thanks for the reply, I have checked all of the config files, and have switched on every piece of error msg that I can and set mysql DB to log all transactions to see if I can catch it there, but so far no joy.

 

I just do not understand why it will work directly on the server but not on my machine? lost all I can think of is comms between 32 bit machines and 64 bit.

 

Pass may be it is just time for a new dev machine.....

 

Thanks for the thoughts....

Hi Corbin,

 

The page is index.php, on seeing your question I have put an index.html page on the server to see if that worked with out issues unfortunatley the same responce was given fine on servers own browser but not when called from a client.

 

I have kept searching and I am wondering if it is the DNS, my little set up is driven by my prod server as the main DNS server so when called it goes there and is then redirected to the test server. I got a friend to check if they could see the dev server and the index page and they could not, this could be my isssue, although I would have expected to see a time out on the browser rather than die.

 

What are your thoughts on the index.php page?

 

Again thanks for the help.

I did an ipconfig first and the name resolved to the correct ip addy, however I had not tried nslookup / to be honest I never heard of it, it did give the correct IP address and shows the bounce from the the other machine which is the primary DNS server e.g.

 

Name: host.com

Addresses: ***.***.***.2, ***.***.***.3

Aliases: new.host.com

 

I therefore assume that it is working correctly?

Yeah that means it's resolving correctly.  OK, now to test if it's client or server side.

 

Go into CMD (or shell if you're on Linux/Mac), and type the following:

 

telnet <host ip> 80
GET /index.php HTTP/1.1
Host: host.com
Connection: close

 

With two lines after the Connection line.  See if it says the DIE thing or not.

Hi Corbin, I am not sure what you are asking me to do here, however I did try what you sent across, the sciprt you gave did not see to accepted so I keep trying and in the end telnet ip port did get a responce from the server once I had broker the call it did give teh source of page index.php I hope this is what you expected me to see?

 

Cheers

Hi Corbin,

 

Ok I just tried this when the browers cam back with DIE!!!!, telnet * thing again and this came back with the page source.

 

I am hoping that we are getting closer?

 

BTW I only have one dns server set up on the client, and then set the seocnd up to see if that would help and no same error?

 

 

Hum I have no idea.....

So if you use telnet, you get the content you would expect, but if you use a browser, you get the die message?  That must mean either it's client side where the error is, or your server isn't mixing well with a certain browser.  I would guess the first option.  I'm thinking at this point that it's a DNS error.  Try going to your site by the IP address in the browser. and see if it works.

Ok Corbin,

 

I know understand why you are listed as a guru...

 

Calling the site via the domain name is failing and giving the die!!! error, however calling it by the ip addy is getting a result, I this would indicat the DNS on the server is failing somewhere?

 

I ait for you adive in the mean time I am off to check the servers DNS.

 

Cheers

Yes, it would seem that the DNS thing is the problem.

 

 

 

Hrmmm, just to clarify, since I'm kind of confused, and rereading the thread isn't helping, what exactly is the setup?

 

You have a DNS server and a web server?  So if you ping the domain name, the IP is correct?

 

 

Like if you do 'ping host.com' does it say the right IP address?

Hi,

 

Server 1 is a windows box and is the production (so to speak) enviroment, which has a web server (apache) and a mail server, it is also listed as the primary DNS server and holds all of my domain DNS on it.

 

The second box is the dev enviroment, again with a web server and mail server on it, I need the mail server just to make life easy when testing send mail from php.

 

The prod server is working fine and picks up all DNS and completes all call e.g. to the listed domains for either web or email. It is using vhosts to complete multiple domains. However as there are x domains on the server it has a DNS record for each domain and does come with a syslog warning to say that no primary domain has been found??? although it does over ride this error, I assume because all of the domain act as primary it can not distiguish the true primary.

 

With in on of the domains there is a second A (host) record that points to the dev box's ip address and then 2 alias reocreds to point to a secure connection and non secure connection on the dev box. (I use the secure connection where any client details are added to mailing lists or loging in to make their own changes. The exact set set up for this is also on the prod box.

 

So, I can call the domain (prod box) (also being used for test) from a client to web the site and get emails from the prod box so I bielive that this is set up correctly.

 

If I call the dev box from a client (http://new.host.com) it will intermitantly give me the development site, and then also intermiterantly give me the "DIE!!!" message, however if I now call the dev box on the local netwrok using the network IP address it will display the home page without errors and seems to be stable e.g. I do not get the message.

 

However if I leave the dev box on try to call the server from the WAN (so out side of the LAN) it will not display, so this why I think it could be DNS aswell. The final parts of the set up, the dev box is not listed as a dns server on the router and in the past when I have done this it has stopped the prod box from showing the domain (I have no idea as to why as the Primary DNS server should be called).

 

All of the tests LAN side will resovle and give me the dev details, but I have the DIE error on client browers (intermiterantly) and it can not be called externally.

 

I hope that summarises the issue?

 

Cheers 

Hi Corbin,

 

I think that you are right, and I am not sure that I have the knowledge base to make the changes, your suggestion just to call the IP address is working, and is allowing me to see the dev servers page which is all I need so I think we can kind of call this a fix.

 

Cheers for your patience and help on this one.

 

Gingerboy101

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.