Greetings.
I am trying to diagnose a problem I have encountered in mysql, and
would sincerely apprecaiate any help. Mysql is running generally fine,
but we have noticed that our log files are enormous in size prior to
compression (most recent is 2.5 gigs) and that these log files seem to
contain a great deal of null (\0) characters in set locations
throughout. We are running Debian stable with a locally compiled and
installed mysql 4.0.16-2. The nulls appear in the following manner in
the logs:
031203 3:41:11 19630 Query UPDATE loginblock SET
createtime=createtime,
updatetime=1070440639, gametime = '1070440605', blocknumber = '0',
numlogins
= '69', logins = '<92>\0F<90>r<D0>4\0\0\0\0\0cPF<80><D2>@<AA><D0>\0 \03<A0><86>
<80>^^ 2@<AE> s<90>I<D0><A3><D0>\Z<80><A6><90>\0\0q<C0>\0\0<B0>< 80>\r^P<CB>`<85>
<90>K<D0>\0\0\0\0\0\0b^P^`\0\0:<90><B1><A0>^T
N<80>\0\0$<90>^U<90>q@<9C>`B`\0\0\
0\0<C4>@<80><E0>s^P<CD><E0>\0\0\0\02^P\0\0\0\0\Z<8 0>k\0\0\0\0\0<AD>^PC@<B9>
<B1>
<E0>3`\Z<80>\0\0\0\0\0\0\0\0^L<D0><92><90>R<90><93 ><90>c\0<A1><C0><8B><C0>p`X
<90>0<E0>T^P\0\0<BD>`\0\0\0\0\0\0\0\0\0\0^U^P<D2>@ y\0t<80><8E><90><A8><80>\0\0UP
\0\0\0\0t@\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0 \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
.... <snipped as it is just \0s for the next thousand lines or so>
Has this ever been observed by anyone else? I have searched high and
low, but not found anything like this as observed by anyone else and
so documented. I will of course gladly provide further information as
requested.
--
- gnostic
