Hallo,
Ich bin was mysql betrifft ein voelliger Newbie!
Ich habe ein Problem mit meiner mysql DB unter RedHat 6.2.
Im logfile finde ich ständig folgende Eintraege:
010622 2:25:13 Aborted connection 753312 to db: 'ezmlm' user: 'root' \
host: `localhost' (Got an error reading communication packets)
koennte mir jemand sagen wie diese auftreten, was sie bedeuten,
welche Konsequenzen das hat und was ich dagegen tun koennte?
Vielen Dank!
tom
MySQL: Fehlermeldungen im Logfile
Re: MySQL: Fehlermeldungen im Logfile
Was für Versionen setzt Du denn auf Server und Client ein? Differieren die Versionen vielleicht?
bye.olli
--
"Where's Oswald when we need him.."
--
"Where's Oswald when we need him.."
Re: MySQL: Fehlermeldungen im Logfile
Installiert ist: 3.23.33-1
Client und Server haben die gleiche Versionsnummer
der tom
Client und Server haben die gleiche Versionsnummer
der tom
Re: MySQL: Fehlermeldungen im Logfile
21.4.9 Communication Errors / Aborted Connection
Starting with MySQL 3.23.40 you only get the Aborted connection error of you start mysqld with --warnings.
If you find errors like the following in your error log.
010301 14:38:23 Aborted connection 854 to db: 'users' user: 'josh'
See section 23.1 The Error Log.
This means that something of the following has happened:
The client program did not call mysql_close() before exit.
The client had been sleeping more than wait_timeout or interactive_timeout without doing any requests. See section 7.28.4 SHOW VARIABLES.
The client program ended abruptly in the middle of the transfer.
When the above happens, the server variable Aborted_clients is incremented.
The server variable Aborted_connects is incremented when:
When a connection packet doesn't contain the right information.
When the user didn't have privileges to connect to a database.
When a user uses a wrong password.
When it takes more than connect_timeout seconds to get a connect package.
Note that the above could indicate that someone is trying to break into your database!
See section 7.28.4 SHOW VARIABLES.
Other reasons for problems with Aborted clients / Aborted connections.
Usage of duplex Ethernet protocol, both half and full with Linux. Many Linux Ethernet drivers have this bug. You should test for this bug by transferring a huge file via ftp between these two machines. If a transfer goes in
burst-pause-burst-pause ... mode then you are experiencing a Linux duplex syndrome. The only solution to this problem is switching of both half and full duplexing on hubs and switches.
Some problem with the thread library that causes interrupts on reads.
Badly configured TCP/IP.
Faulty Ethernets or hubs or switches, cables ... This can be diagnosed properly only by replacing hardware.
Starting with MySQL 3.23.40 you only get the Aborted connection error of you start mysqld with --warnings.
If you find errors like the following in your error log.
010301 14:38:23 Aborted connection 854 to db: 'users' user: 'josh'
See section 23.1 The Error Log.
This means that something of the following has happened:
The client program did not call mysql_close() before exit.
The client had been sleeping more than wait_timeout or interactive_timeout without doing any requests. See section 7.28.4 SHOW VARIABLES.
The client program ended abruptly in the middle of the transfer.
When the above happens, the server variable Aborted_clients is incremented.
The server variable Aborted_connects is incremented when:
When a connection packet doesn't contain the right information.
When the user didn't have privileges to connect to a database.
When a user uses a wrong password.
When it takes more than connect_timeout seconds to get a connect package.
Note that the above could indicate that someone is trying to break into your database!
See section 7.28.4 SHOW VARIABLES.
Other reasons for problems with Aborted clients / Aborted connections.
Usage of duplex Ethernet protocol, both half and full with Linux. Many Linux Ethernet drivers have this bug. You should test for this bug by transferring a huge file via ftp between these two machines. If a transfer goes in
burst-pause-burst-pause ... mode then you are experiencing a Linux duplex syndrome. The only solution to this problem is switching of both half and full duplexing on hubs and switches.
Some problem with the thread library that causes interrupts on reads.
Badly configured TCP/IP.
Faulty Ethernets or hubs or switches, cables ... This can be diagnosed properly only by replacing hardware.
bye.olli
--
"Where's Oswald when we need him.."
--
"Where's Oswald when we need him.."