Thomas Haberland wrote:
> 
> Hi,
> 
> > Lu:
> > But no matter what I entered, I always end up getting these in the error
> > log.
> >
> > This is from /var/log/mysqld.log
> >
> > 010316 13:24:04  Aborted connection 535 to db: 'vpopmail' user: 'vpopmail'
> > host: `localhost' (Got an error reading communication packets)
> > 010316 13:24:08  Aborted connection 536 to db: 'vpopmail' user: 'vpopmail'
> > host: `localhost' (Got an error reading communication packets)
> > 010316 13:24:16  Aborted connection 537 to db: 'vpopmail' user: 'vpopmail'
> > host: `localhost' (Got an error reading communication packets)
> > 010316 13:24:20  Aborted connection 538 to db: 'vpopmail' user: 'vpopmail'
> > host: `localhost' (Got an error reading communication packets)
> > 010316 13:24:24  Aborted connection 539 to db: 'vpopmail' user: 'vpopmail'
> > host: `localhost' (Got an error reading communication packets)
> 
> unfortunately I can't find a real answer to this problem on several resources
> into the internet. Guess it has less or nothing to do with vpopmail and is
> more a MySQL and machine depended problem, but maybe someone on this list has
> an answer?
> 
> Since past week one of my Internet servers produces the same error messages,
> too. The server was running about 1 year WITHOUT any error.
> 
> Since I installed an complete server update (Linux Mandrake 7.1 -> Mandrake
> 7.2, and MySQL 3.23.36 ), the mysql error log contains the above mentioned
> error messages.
> 
> I also updated to the latest stable vpopmail release, but no changings.
> 
> The server seems to run fine, neither my customers nor myself can find any
> error when using the running services. But why this error message and why
> didn't it happen before the update?
> I'm really very interested to get a solution for this. ;)

Aborted connection means that vpopmail did not call the 
mysql_close() function, and instead just exited and let
the operating system close all of it's file descriptors/sockets.
This isn't a big problem, since any decent server, mysql included,
should be able to clean up when sockets/descriptors close.

I will have to audit the qmailadmin code to add in vclose()
calls before any exits. That will remove the errors from
your mysql log.

ken Jones

Reply via email to