Re: Upgrade from 7.0.2 to 8.0_BETA: some trouble with sockets (I think)

[BERTRAND Joël <joel.bertrand%systella.fr@localhost>]

Le 02.07.2017 14:49, Manuel Bouyer a écrit :
> On Sun, Jul 02, 2017 at 02:20:54PM +0200, BERTRAND Joël wrote:
> > [...]
> > I have tried with or without NPF with the same result. With tcpdump, I 
> > can
> > see for example on mysql client :
> > root@hilbert:~# tcpdump port 3306
> > tcpdump: verbose output suppressed, use -v or -vv for full protocol 
> > decode
> > listening on enp3s0, link-type EN10MB (Ethernet), capture size 262144 
> > bytes
> > 14:14:51.734354 IP 192.168.10.103.59516 > 192.168.10.128.mysql: Flags 
> > [S],
> > seq 3338130626, win 29200, options [mss 1460,sackOK,TS val 25821788 
> > ecr
> > 0,nop,wscale 7], length 0
> > 14:14:51.734458 IP 192.168.10.128.mysql > 192.168.10.103.59516: Flags 
> > [S.],
> > seq 3511699100, ack 3338130627, win 32768, options [mss 
> > 1460,nop,wscale
> > 3,sackOK,TS val 1 ecr 25821788], length 0
> > 14:14:51.734490 IP 192.168.10.103.59516 > 192.168.10.128.mysql: Flags 
> > [.],
> > ack 1, win 229, options [nop,nop,TS val 25821788 ecr 1], length 0
> > 14:14:51.734581 IP 192.168.10.128.mysql > 192.168.10.103.59516: Flags 
> > [R],
> > seq 3511699101, win 0, length 0
>
> Can you ktrace the mysql daemon while doint this ?
> Eventually match the tcpdump timestamps with the kdump one, to see 
> exaclty
> what cause the socket to be closed, and what is happening before.

I have ktrace'd mysqld process before posting here (only when I try to 
open a new connection from client). I paste an extraction of this file :

 14288     13 mysqld   RET   __gettimeofday50 0
 14288     13 mysqld   CALL  
___lwp_park60(0,1,0x79f65fdffed0,0,0x79f663df2198,0x79f663df2198)
 14288     14 mysqld   RET   ___lwp_park60 -1 errno 60 Connection timed 
out
 14288     14 mysqld   CALL  __gettimeofday50(0x79f65f9feef0,0)
 14288     14 mysqld   RET   __gettimeofday50 0
 14288     14 mysqld   CALL  __gettimeofday50(0x79f65f9fee20,0)
 14288     14 mysqld   RET   __gettimeofday50 0
 14288     14 mysqld   CALL  
___lwp_park60(0,1,0x79f65f9fee90,0,0x79f688d17b98,0x79f688d17b98)
 14288     16 mysqld   RET   __select50 0
 14288     16 mysqld   CALL  __gettimeofday50(0x79f65f1fcf70,0)
 14288     16 mysqld   RET   __gettimeofday50 0
 14288     16 mysqld   CALL  __gettimeofday50(0x79f65f1fcf70,0)
 14288     16 mysqld   RET   __gettimeofday50 0
 14288     16 mysqld   CALL  __gettimeofday50(0x79f65f1fcf60,0)
 14288     16 mysqld   RET   __gettimeofday50 0
 14288     16 mysqld   CALL  __select50(0,0,0,0,0x79f65f1fcf70)
 14288     18 mysqld   RET   __select50 0
 14288     18 mysqld   CALL  __gettimeofday50(0x79f6607f5f10,0)
 14288     18 mysqld   RET   __gettimeofday50 0
 14288     18 mysqld   CALL  __gettimeofday50(0x79f6607f5f10,0)
 14288     18 mysqld   RET   __gettimeofday50 0
 14288     18 mysqld   CALL  __select50(0,0,0,0,0x79f6607f5f10)
 14288     13 mysqld   RET   ___lwp_park60 -1 errno 60 Connection timed 
out
 14288     13 mysqld   CALL  __gettimeofday50(0x79f65fdffe60,0)
 14288     13 mysqld   RET   __gettimeofday50 0
 14288     13 mysqld   CALL  
___lwp_park60(0,1,0x79f65fdffed0,0,0x79f663df2198,0x79f663df2198)
 14288     14 mysqld   RET   ___lwp_park60 -1 errno 60 Connection timed 
out
 14288     14 mysqld   CALL  __gettimeofday50(0x79f65f9feef0,0)
 14288     14 mysqld   RET   __gettimeofday50 0
 14288     14 mysqld   CALL  __gettimeofday50(0x79f65f9fee20,0)
 14288     14 mysqld   RET   __gettimeofday50 0
 14288     14 mysqld   CALL  
___lwp_park60(0,1,0x79f65f9fee90,0,0x79f688d17b98,0x79f688d17b98)

I haven't seen strange syscalls nor error in kdump.

> I guess you don't have error messages in mysql logs ?

No error in log, of course.

Best regards,

JKB