asked on

HTTP 1/1: 500 Internal Server Error on Web Farm

Windows 2012 R2 Web Farm 2 Nodes
Windows 2012 R2 NLB 2 Nodes.
VMware 6.5
Kemp Load Balancer.

I have the 4 Nodes running as VM's in my VMware environment.

I use the Kemp to load Balance the external web traffic.

I use the NLB Nodes to balance to internal web traffic.

I also use Nagios to monitor the above. And after a long time with out running I started it back up and good thing I did

My internal computers can not access the web sites

HTTP 1/1: 500 Internal Server Error

I get the same error using the DNS or IP address to the site

This started after power outage and one of the NLB servers was down and one of the Web Servers was down.

All web sites work from outside my network computers
They go thru the Kemp Load Balancer

On the NLB I checked all looks ok

On the Web Farm servers all look good.

Any ideas on where to start?

Paul MacDonald

If the web sites work publicly, but not privately, the issue is likely with the component unique to the internal connection: NLB.

If you Stop one server at a time in NLB, you may find the problem server.

Member_2_6492660_1

ASKER

I stopped both hosts using NLB Manager one at a time no change still 500 error.

Then went to IIS and stopped each one at a time still no change 500 error

Thoughts?

Paul MacDonald

You're certain your internal DNS points to the exact same IPs as your external DNS?

Member_2_6492660_1

ASKER

Paul
Good morning,

I will double check today.

Nothing changed in that area that I am aware of this all happened after the power outage to the best of my knowledge.

I will post later with results.

Member_2_6492660_1

ASKER

Paul,

Yes I do have a different IP address for external and internal.

The External user go thru my Kemp for load balancing.

The internal user go thru my NLB Server

I have three sites on the web farm.

Site A works internal and external no problem.

Site b works external but not internal this is the one I posted.

Site c is internal only and works also.

Thoughts?

Member_2_6492660_1

ASKER

Still not working anyone with any ideas?

Member_2_6492660_1

ASKER

I ran IISRESET on all servers NLB and web farms

Still having same issue

any ideas

Paul MacDonald

Okay, understanding that it's only 1 of 3 sites that's having the problem changes things. Does the site come up if you're on one of the servers hosting it? By URL? By IP address? Does the site have an exotic port number (something other than 80 or 443?)

Member_2_6492660_1

ASKER

Paul,

By url same error. By ip address it takes to my default web site all using port 80

Paul MacDonald

"By ip address it takes to my default web site all using port 80"
...and it looks as if that's correct, yes?

So there seems to be a problem with using the host name. That comes down to two things, I believe: DNS and host headers. If you're on and internal machine and ping the site, do you get a response? How about if you're on one of the web servers? Do you use host headers, and are yours configured correctly?

Member_2_6492660_1

ASKER

Paul,

Yes I get a response of the NLB ip address

C:\WINDOWS\system32>ping www.tomsmp3.com

Pinging www.tomsmp3.com [10.2.8.171] with 32 bytes of data:
Reply from 10.2.8.171: bytes=32 time=1ms TTL=128
Reply from 10.2.8.171: bytes=32 time<1ms TTL=128
Reply from 10.2.8.171: bytes=32 time<1ms TTL=128
Reply from 10.2.8.171: bytes=32 time<1ms TTL=128

Ping statistics for 10.2.8.171:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\WINDOWS\system32>ping 10.2.8.123

Pinging 10.2.8.123 with 32 bytes of data:
Reply from 10.2.8.123: bytes=32 time=1ms TTL=128
Reply from 10.2.8.123: bytes=32 time<1ms TTL=128
Reply from 10.2.8.123: bytes=32 time<1ms TTL=128
Reply from 10.2.8.123: bytes=32 time<1ms TTL=128

Ping statistics for 10.2.8.123:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\WINDOWS\system32>ping tomsmp3.com

Pinging tomsmp3.com [10.2.8.171] with 32 bytes of data:
Reply from 10.2.8.171: bytes=32 time<1ms TTL=128
Reply from 10.2.8.171: bytes=32 time<1ms TTL=128
Reply from 10.2.8.171: bytes=32 time<1ms TTL=128
Reply from 10.2.8.171: bytes=32 time<1ms TTL=128

Ping statistics for 10.2.8.171:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\WINDOWS\system32>

In my previous post it shows my host headers they were working fine.

Member_2_6492660_1

ASKER

paul

My DNS record for this

That is the ip address of the NLB setup.

ASKER CERTIFIED SOLUTION

Paul MacDonald

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Member_2_6492660_1

ASKER

Paul,

Just as a test I put the ip address of the web farm server in my local hosts file
to eliminate DNS

Same issue

Has to be a settings somewhere still looking

Thanks Tom

Member_2_6492660_1

ASKER

Paul,

update I just discovered that the site does not work externally also.

Now that makes me happier because this may lead to the problem.

Still struggling to get this up and running again.

www.tomsmp3.com is the site

Let me know if you can get to it

Member_2_6492660_1

ASKER

Paul,

I figured this out late last night.

On my Web Farm I went to the IIS Logs folder and reviewed the logs and I found the issue. the account that I use to connect to the SQL server password had expired. I went to the SQL server and reset the password and like magic the site started working again.

Thanks you all your help

Tom

Paul MacDonald

Hey, that's great!

Knowing the site wasn't available from outside would have changed things for sure. Glad you were able to resolve it.