[MDEV-14662] crash when packets out of order Created: 2017-12-15 Updated: 2020-08-25 Resolved: 2018-02-14 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Server, Storage Engine - Spider |
| Affects Version/s: | 10.3 |
| Fix Version/s: | 10.0.35, 10.1.32, 10.2.14, 10.3.5 |
| Type: | Bug | Priority: | Major |
| Reporter: | Simon Mudd | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Description |
|
I noticed mysqld crash after running for some time. Version running was 10.3 branch commit 159a6c2e608d04732cb6 Logging shows
Reporting in case this is something that's not known. |
| Comments |
| Comment by Simon Mudd [ 2017-12-15 ] | |
|
Note: server on startup reports as 10.3.3-MariaDB-debug-log | |
| Comment by Elena Stepanova [ 2017-12-15 ] | |
|
Since you're already running a debug build, could you please get it produce a coredump (if it doesn't yet) and collect all threads' stack trace from it? | |
| Comment by Daniel Black [ 2018-01-04 ] | |
|
Looks like some authentication protocol error with the mysql client you are using. As a MITM debugging of this something like the following can show the bytes sent/received. UNIX-> TCP options also exist:
| |
| Comment by Simon Mudd [ 2018-01-12 ] | |
|
Provided core dump file to support site with some comments. | |
| Comment by Simon Mudd [ 2018-01-30 ] | |
|
Note sure that using the socat options suggested would be good. The server was doing a "parallel dump" of a 300+GB database into the spider node and the failure took place after about 1 hour. So to me catching adhoc traffic between the server and the client(s) is not going to be useful here. |