Error in production only

views:

answers:

Error in production only

An error was discovered in our ASP.NET application where a URL on an anchor was incorrect.

The production staff made an emergency fix by rewriting the URL of the page on a BIG-IP F5 hardware load balancer.

We now have to fix the bug but I cannot see it in the code. Everything looks perfect. We cannot reproduce the error, not even in QA. The only way to reproduce it seems to be to revert the F5 configuration which will break a working live system.

What to do?

You could set up a virtual machine (i.e clean) with configuration exactly the same as the live server. Its possible you've got extra configuration on your dev boxes that is fixing or masking the error

David Archer 2009-06-24 09:46:02

The production environment has 47 servers with 20+ unique server roles. Our QA consists of the same servers virtualized. I cannot figure out why it does not happen there. I am starting to doubt what they say the problem is since I cannot verify anything.

Hans Malherbe 2009-06-24 15:45:25

+1 A:

Can you not bypass the F5 for the purposes of debugging? Browse to the IP address of the actual webserver rather than the load balanced IP?

1800 INFORMATION 2009-06-24 09:49:41

This is a good idea. If I can someone to test on the local production LAN we should be able to recreate the error condition.

Hans Malherbe 2009-06-24 15:46:51

ansaurus

tags:

views:

answers:

Error in production only

related questions