Avatar of Jim Youmans
Jim Youmans
Flag for United States of America

asked on 

MySQL Error Log

I am looking at the MySQL error log from today (7-11-2020) and can't figure out the timestamp.  The file looks like this..

190126  6:02:12 [Warning] Aborted connection 3523034 to db: 'mydb' user: 'myuser' host: 'localhost' (Got an error reading communication packets)
190126 12:01:17 [Warning] Aborted connection 3798006 to db: 'mydb' user: 'myuser' host: 'localhost' (Got an error reading communication packets)
190126 18:01:13 [Warning] Aborted connection 4247680 to db: 'mydb' user: 'myuser' host: 'localhost' (Got an error reading communication packets)
190127  0:01:17 [Warning] Aborted connection 4632223 to db: 'mydb' user: 'myuser' host: 'localhost' (Got an error reading communication packets)
190127  6:01:18 [Warning] Aborted connection 4752719 to db: 'mydb' user: 'myuser' host: 'localhost' (Got an error reading communication packets)
190127 12:01:14 [Warning] Aborted connection 5022959 to db: 'mydb' user: 'myuser' host: 'localhost' (Got an error reading communication packets)
190127 18:01:21 [Warning] Aborted connection 5528482 to db: 'mydb' user: 'myuser' host: 'localhost' (Got an error reading communication packets)

Open in new window


so the 190127 is what I am assuming is the date but there are different values for that column from 190127 to 190119.  The second column looks like a timestamp but its not in order and jump from 22:00:00 on one colum and then 08:00 on next.  Which does not make sense.

I moved this file to a windows machine from CentOS, could that have messed it up?  I can still read the rest of it just fine.

Thanks

Jim
LinuxMySQL Server

Avatar of undefined
Last Comment
David Favor

8/22/2022 - Mon