NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

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



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 guess you don't have error messages in mysql logs ?

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--


Home | Main Index | Thread Index | Old Index