Yes, according to the manual that number will disable the error. However I
would still run a FLUSH HOSTS after a crash just to be sure that all of
the old IPs are cleared out.
I have seen IIS go down for stranger reasons. I don't know if you have
any performance numbers available to track how many ODBC connections are
open at any one time. Check perfmon to see if any are listed for your
platform and version. I know there are several IIS-related things you
_can_ chart (I remember them from a MSDN KB article describing how to
monitor IIS 4.0 for performance. I have no clue if they have kept it up to
date). These were things like active connections, wait queue, etc. that
basically told about the health of the server and how backed up it was.
Sorry I can't be more specific but it's been several years since I last
set up perfmon to keep tabs on IIS.
I think your bigger problem is figuring out why IIS keeps crashing. Do the
web logs or the error logs provide any clues? Do you know which IIS
process is taking you down? Is it crashed or just hung? all of this is
basically OT but I thought I would ask anyway.... ;-)
Yours,
Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine
"James Frankman" <jfrankman@stripped> wrote on 07/29/2004 01:56:03 PM:
> We have quite a bit of code to go through to find a place where a
> connection isn't closed properly. Are you saying the un-closed
> connections causes IIS to crash? Is there some way to monitor open
> connections?
>
> From the MySQL side of things I am thinking about putting the
> following line in my.ini:
> set-variable = max_connect_errors=999999999
>
> If I understand the documentation correctly this will not solve the
> problem with IIS crashing, but after IIS restarts, I will not have
> to flush hosts. Is this correct?
> -----Original Message-----
> From: SGreen@stripped [mailto:SGreen@stripped]
> Sent: Thursday, July 29, 2004 11:20 AM
> To: James Frankman
> Cc: win32@stripped
> Subject: Re: Host 'xxx.xxx.xxx.xxx' is blocked
>
>
>
>
> I think you should also review your data access code and make sure
> that all of your connections are being closed on every page. Just
> one page with a still open connection can hang you up like this
> depending on how often it is called. Do not rely on the garbage
> collector to close it for you.
>
> Yours,
> Shawn Green
> Database Administrator
> Unimin Corporation - Spruce Pine
>
> "James Frankman" <jfrankman@stripped> wrote on 07/29/2004 01:13:04
PM:
>
> > We have MySQL 4.0 running on our IIS web server. Occasionally, IIS
> > crashes and after restarting the server, we get the error message:
> >
> > '' Microsoft OLE DB Provider for ODBC Drivers [MySQL][ODBC 3.51
> > Driver]Host 'xxx.xxx.xxx.xxx' is blocked because of many connection
> > errors. Unblock with 'mysqladmin fulsh-hosts' "
> >
> > Other connections to MySQL work, only connections from IIS to MySQL
> > fail until the MySQL service is restarted. I have not tried 'flush
> > hosts' since at the time I wasn't familiar with the command, and I
> > was under the gun to get our Intranet back up. Restarting MySQL was
> > my quickest option
> >
> > A couple questions:
> >
> > 1. Is 'mysqladmin flush-hosts' equivelant to the mysql command
> 'flush hosts'?
> > 2. How can I avoid this problem in the future?
> >
> > --
> > MySQL Windows Mailing List
> > For list archives: http://lists.mysql.com/win32
> > To unsubscribe: http://lists.mysql.com/win32?unsub=1
> >
>
>