Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 222
  • Last Modified:

Website throwing error

We run important website and are in the middle of converting from server 2003 to server 2010 with all the proper steps but until that comes within the next coming month - Were getting an script error that we can not figure out.

Script is an Perl Script that is trying to make an connection to the website and sends an email with any issues.  The issue is ;
"Tue Sep  4 07:48:42 2012
Slow response from http://www.xxxxxxxxxxxx.gov: 89 seconds"

Now we get this email every 10-30 minutes and with different seconds but always the same website.  Now 6 other websites are running fine with no errors being thrown.

Note: Tracert and pings are responded fast and very acceptable.  Event logs show no errors or anything of notice.

Windows 2003 server
ASP 1.1 - Web Extensions ASP2.0 allowed

any ideas ?
  • 3
  • 3
1 Solution
Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
To double check -- "Server 2003 to Server 2010".  My first read through, I assumed you intended Server 2003 to Server 2008 (or Server 2008 R2), assuming you are referring to Windows Server.  Can you confirm, or specify which Server production 2010?

Any chance you can isolate the Perl script which is generating the alert?  If everything looks normal to you, but the Perl script is reporting some sort of slow response, there are just two possibilities I can think of:
  1. The script is looking at something you are not looking at, and it needs to be fixed.
  2. The script is testing for some functionality which has changed to 2008/2010, and the script needs to be fixed.
  In either case, being able to look at the query will be crucial.  

(And if you find the script to post, you might want to include the PERL subtopic (Under Programming Languages, in Programming.   And if you confirm that it's under Windows 2008/2008 R2 II7.x -- it might be helpful to add the "Windows Server 2008" subtopic as well.)
synertiaAuthor Commented:
let me give a little more clarification.  Nothing has changed on the 03 server.  All i was stating before anyone says "upgrade your server" - We are working on the plans to doing that to 08r2.

Just something over the weekend has changed to throw ALOT of errors.
Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
Oh!  I'm sorry, I misunderstood.
You are getting the errors while the website is still pointed at the 2003 server!

The PERL script might still help narrow down what is wrong.

However, given that nothing has changed, and you're just preparing to move off that server -- an unpleasant option/question, 'Have you rebooted the 2003 server since the problem started?'
   I'd look at memory, handles and threads on the 2003 server, and see if any of them are excessively inflated.   A reboot might mitigate the symptoms, and at least buy you enough time to move to the new server.

Another unpleasant question -- "Are the Windows Server patches up to date?"
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

synertiaAuthor Commented:
due to this being an important website - the move will not be done for a couple more months so i can not just hold. but yes the server has been rebooted.  as well, the watchguard firewall was upgraded over the weekend & im pondering if that is the problem with the connection . ? .
synertiaAuthor Commented:
Patches are not up to date with the August patches due to an old problem we are monitoring with Replication
Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
> watchguard firewall was upgraded over the weekend & im pondering if that is the problem with the connection . ? .

Certainly a possibility, and the timing sounds to be perfect.  Is it possible to move the machine that runs the PERL script inside the firewall briefly, or to add an exclusion to the firewall for just the one machine running the PERL script -- for testing purposes only.

If it does turn out to be the upgrade in the firewall, since it's only the one site that throwing the error, it's possible that the solution will still be to fix an aspect of that one website that the firewall is now 'protecting' against.

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now