We start mysql with 'service mysql start' (we install from the RPM for
linux).
I've never seen mysql create binlog files under the name root before, and
after reverting to an old version, it doesn't again. It created a big mess
with all the slaves stuck at the end of an older binlog and not advancing to
the next one and complaining about corruption. Unfortunately, I don't have
the contents of the log (I think the size of the file was 79 bytes) since a
script here checks that all the slaves are at a certain point and then
deletes the logs on the master.
Log:
040519 17:53:41 mysqld started
/usr/sbin/mysqld: ready for connections.
Version: '4.0.18-standard-log' socket: '/tmp/mysql.sock' port: 3306
040520 16:58:54 /usr/sbin/mysqld: Normal shutdown
040520 16:58:56 /usr/sbin/mysqld: Shutdown Complete
040520 16:58:56 mysqld ended
040520 16:59:10 mysqld started
040520 16:59:10 Warning: Asked for 196608 thread stack, but got 126976
/usr/sbin/mysqld: ready for connections.
Version: '4.0.20-standard-log' socket: '/tmp/mysql.sock' port: 3306
040520 16:59:14 Failed to open log (file '/binlogs/binlog.032', errno 13)
040520 16:59:34 Aborted connection 134 to db: 'db' user: 'aaa' host:
`something.i' (Got an error writing communication packets)
040520 16:59:36 Aborted connection 544 to db: 'db' user: 'aaa' host:
`something.i' (Got an error writing communication packets)
040520 16:59:36 Aborted connection 541 to db: 'db' user: 'aaa' host:
`something.i' (Got an error writing communication packets)
> Binary logs are created by the mysqld daemon (after mysqld possibly
> changes to uid of 'mysql' if --user=mysql was used). So in any case,
> if mysqld is running as user mysql (no matter if it was 'mysql' which
> started mysqld or if it was 'root' which did 'mysqld --user=mysql'),
> the binary logs are created by 'mysql'.
> If you have some binary logs created by 'root', it means 'mysqld' was
> run as 'root'; this is what you should really check (if you can
> provide us with the way you started mysqld ('service mysql start',
> whatever) and a listing of 'ps -elf | grep mysqld', we may be able to
> check if it is a MySQL bug but this is quite unlikely, from the above
> reasoning).
>
> Thank you!
> --
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Mr. Guilhem Bichot <[EMAIL PROTECTED]>
> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Software Developer
> /_/ /_/\_, /___/\___\_\___/ Bordeaux, France
> <___/ www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
