so we upgraded to 3.23.32 last night, but i'm still seeing a ton of:
010126 11:15:24 Aborted connection 30757 to db: 'XXX' user: 'YYY'
host: `ZZZ' (Got an error reading communication packets)
type errors in the error log.
i'm seeing these errors from both php connections and from perl dbi
connections. the versions involved are:
mysql-3.23.32
php-4.0.4pl1
DBI-1.14
Msql-Mysql-modules-1.2215
oh and perl is v5.6.0.
which i believe are the latest stable releases of each.
anything else i should be looking for?
-tcl.
On Tue, 23 Jan 2001, tc lewis wrote:
>
> thanks for the reply. i found a followup on this problem from sasha
> ("Follow up on aborted connections bug in 3.23.31"), but wading through
> the archive searching for the original thread hasn't ended up being
> successful yet. anyone know offhand in which thread this was originally
> discussed?
>
> not all of these errors are coming from php connections. does php have
> some related issue with this also?
>
> -tcl.
>
> ps- i like these informative changelog entries:
>
> . "Fixed security bug in something (please upgrade if you are using a earlier MySQL
>3.23 version)."
> . "Fixed buffer overflow bug when writing a certain error message."
>
>
> On Tue, 23 Jan 2001, Maciek Uhlig wrote:
>
> > Read the archives. The detailed story can be found there. Use newest MySQL
> > and newest PHP CVS. These errors will go away.
> >
> > Maciek
> >
> > > -----Original Message-----
> > > From: tc lewis [mailto:[EMAIL PROTECTED]]
> > > Sent: Tuesday, January 23, 2001 3:56 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: aborted connections?
> > >
> > >
> > >
> > > we're seeing a lot of errors like these in our error log files from mysql:
> > >
> > > 010122 17:38:52 Aborted connection 177373 to db: 'XXX' user: 'YYY'
> > > host: `ZZZ' (Got an error reading communication packets)
> > >
> > > i haven't investigated too too much about this yet, but i was wondering
> > > what common problems this error might be associated with. i'll keep
> > > looking through the manual, but suggestions would of course be wonderful.
> > >
> > > the connections are over ethernet/tcp, and the eth interfaces on the mysql
> > > server are showing 0 errors after months of uptime, so i'm guessing it's
> > > not a tcp/ip issue, as the wording of that error might suggest.
> > >
> > > -tcl.
> > >
> > >
> > > ---------------------------------------------------------------------
> > > Before posting, please check:
> > > http://www.mysql.com/manual.php (the manual)
> > > http://lists.mysql.com/ (the list archive)
> > >
> > > To request this thread, e-mail <[EMAIL PROTECTED]>
> > > To unsubscribe, e-mail
> > > <[EMAIL PROTECTED]>
> > > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > Before posting, please check:
> > http://www.mysql.com/manual.php (the manual)
> > http://lists.mysql.com/ (the list archive)
> >
> > To request this thread, e-mail <[EMAIL PROTECTED]>
> > To unsubscribe, e-mail <[EMAIL PROTECTED]>
> > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
> >
> >
>
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
