Aborted clients - Got an error reading communication packets

[Database Administrator]

Hello,

I get pages of error logs with this message -
"Got an error reading communication packets". And the aborted clients
are easily in hundreds.

Here is my set of configurations:
I am running Microsoft .Net 2.0 on Windows 2003 Server using IIS 6.0.
I am using Mysql 5.0 with Mysql/.Net Connector 1.0.

Some of the settings on my.ini -
Connection timeout - 180
Wait timeout - 360
Max packet size - 10 M
Max connections - 5000 (pretty high, but set to be on a safer side)

When a perform a netstat -ao - I have lot many sockets open with
TIME_WAIT status. On the MySql Command client - the Aborted clients
average around 100's

The connection string from ,Net application has pooling=false with no
help.

The webserver does not have a heavy load and has less than 5 users at
any point in time.

On the registry settings, I have the max ports > 60000 and the
time_wait setting changed to 30.

My application is opens a connection, performs a query and closes the
connection and this is the fashion followed for all DB operations.

Been hunting around for a solution and it has been driving me crazy.
Any suggestions will be highly appreciated.

Thanks,
Narmatha

[Database Administrator]

== Quote from narmathabala ( narmathabala@gmail.com)'s article
> Hello,
> I get pages of error logs with this message -
> "Got an error reading communication packets". And the aborted clients
> are easily in hundreds.
> Here is my set of configurations:
> I am running Microsoft .Net 2.0 on Windows 2003 Server using IIS 6.0.
> I am using Mysql 5.0 with Mysql/.Net Connector 1.0.
> Some of the settings on my.ini -
> Connection timeout - 180
> Wait timeout - 360
> Max packet size - 10 M
> Max connections - 5000 (pretty high, but set to be on a safer side)
> When a perform a netstat -ao - I have lot many sockets open with
> TIME_WAIT status. On the MySql Command client - the Aborted clients
> average around 100's
> The connection string from ,Net application has pooling=false with no
> help.
> The webserver does not have a heavy load and has less than 5 users at
> any point in time.
> On the registry settings, I have the max ports > 60000 and the
> time_wait setting changed to 30.
> My application is opens a connection, performs a query and closes the
> connection and this is the fashion followed for all DB operations.
> Been hunting around for a solution and it has been driving me crazy.
> Any suggestions will be highly appreciated.
> Thanks,
> Narmatha


increase your packet size
--
POST BY: lark with PHP News Reader

[Database Administrator]

On Jun 26, 12:46 pm, lark wrote:
> == Quote from narmathabala ( narmathab...@gmail.com)'s article
>
>
>
> > Hello,
> > I get pages of error logs with this message -
> > "Got an error reading communication packets". And the aborted clients
> > are easily in hundreds.
> > Here is my set of configurations:
> > I am running Microsoft .Net 2.0 on Windows 2003 Server using IIS 6.0.
> > I am using Mysql 5.0 with Mysql/.Net Connector 1.0.
> > Some of the settings on my.ini -
> > Connection timeout - 180
> > Wait timeout - 360
> > Max packet size - 10 M
> > Max connections - 5000 (pretty high, but set to be on a safer side)
> > When a perform a netstat -ao - I have lot many sockets open with
> > TIME_WAIT status. On the MySql Command client - the Aborted clients
> > average around 100's
> > The connection string from ,Net application has pooling=false with no
> > help.
> > The webserver does not have a heavy load and has less than 5 users at
> > any point in time.
> > On the registry settings, I have the max ports > 60000 and the
> > time_wait setting changed to 30.
> > My application is opens a connection, performs a query and closes the
> > connection and this is the fashion followed for all DB operations.
> > Been hunting around for a solution and it has been driving me crazy.
> > Any suggestions will be highly appreciated.
> > Thanks,
> > Narmatha
>
> increase your packet size
> --
> POST BY: lark with PHP News Reader

Bigger than 10 M?

Thanks,
Narmatha

[Database Administrator]

narmathabala@gmail.com wrote:
> Hello,
>
> I get pages of error logs with this message -
> "Got an error reading communication packets". And the aborted clients
> are easily in hundreds.
>
> Here is my set of configurations:
> I am running Microsoft .Net 2.0 on Windows 2003 Server using IIS 6.0.

Ouch, not sure if even microsoft would run that combination, they seem to like
BSD servers.

> I am using Mysql 5.0 with Mysql/.Net Connector 1.0.

Is the mysql on the same machine as the web server? if not, maybe you have
trouble with firewalls, try to allow unblocked traffic between the machines.




--

//Aho

[Database Administrator]

== Quote from narmathabala ( narmathabala@gmail.com)'s article
> On Jun 26, 12:46 pm, lark wrote:
> > == Quote from narmathabala ( narmathab...@gmail.com)'s article
> >
> >
> >
> > > Hello,
> > > I get pages of error logs with this message -
> > > "Got an error reading communication packets". And the aborted clients
> > > are easily in hundreds.
> > > Here is my set of configurations:
> > > I am running Microsoft .Net 2.0 on Windows 2003 Server using IIS 6.0.
> > > I am using Mysql 5.0 with Mysql/.Net Connector 1.0.
> > > Some of the settings on my.ini -
> > > Connection timeout - 180
> > > Wait timeout - 360
> > > Max packet size - 10 M
> > > Max connections - 5000 (pretty high, but set to be on a safer side)
> > > When a perform a netstat -ao - I have lot many sockets open with
> > > TIME_WAIT status. On the MySql Command client - the Aborted clients
> > > average around 100's
> > > The connection string from ,Net application has pooling=false with no
> > > help.
> > > The webserver does not have a heavy load and has less than 5 users at
> > > any point in time.
> > > On the registry settings, I have the max ports > 60000 and the
> > > time_wait setting changed to 30.
> > > My application is opens a connection, performs a query and closes the
> > > connection and this is the fashion followed for all DB operations.
> > > Been hunting around for a solution and it has been driving me crazy.
> > > Any suggestions will be highly appreciated.
> > > Thanks,
> > > Narmatha
> >
> > increase your packet size
> > --
> > POST BY: lark with PHP News Reader
> Bigger than 10 M?
> Thanks,
> Narmatha


apparently so. also look at the client packet size because that is also
controllable. all of your clients must be configured to use the same packet size
and this packets size has to be less than the packet size allowed by the server.
increase your packet size to 32 or 64 M.
--
POST BY: lark with PHP News Reader

[Database Administrator]

narmathabala@gmail.com wrote:
>
> I get pages of error logs with this message -
> "Got an error reading communication packets". And the aborted clients
> are easily in hundreds.

You get that message in the log every time the server closes a client
connection because it was inactive too long. Too long is "longer than
wait_timeout".

> Some of the settings on my.ini -
> Connection timeout - 180
> Wait timeout - 360

This is 6 minutes. Each client connection that stays idle will be
forcibly closed by the MySQL server after 6 minutes.
What was your reason to decrease wait_timeout from the 8 hour default?

> Max connections - 5000 (pretty high, but set to be on a safer side)

This safety is expensive. You risk running out of memory instead.
On Windoze you may run out of TCP handles even before...

> My application is opens a connection, performs a query and closes the
> connection and this is the fashion followed for all DB operations.

Obviously the connections were *not* closed.


XL
--
Axel Schwenke, Support Engineer, MySQL AB

Online User Manual: http://dev.mysql.com/doc/refman/5.0/en/
MySQL User Forums: http://forums.mysql.com/

[dfriedmann]

Hi,
I've got similar problems.
I'm getting lots of "(Got an error reading communication packets)" errors in mysqld.err and at the same time I can no longer connect to the mysql db from my web app.

I'm running mysql Gentoo Linux mysql-5.0.44-r2 and accessing it with IIS6 myodbc.

Some of the setttings:
wait_timeout 28,800
connect_timeout 10
max allowed packet 134,216,704
max connections 1000

Could this also be a problem of the connections not being properly closed?