Re: Hangup of /dev/log syslogd

kunt wrote:
J.O. Aho wrote:
Did it really hang or was there something else that caused a block and not a hang?

I have no idea of what exactly happened. Symptoms were these: messages in stdout by mysqlimport were not progressing any further, hard disk was still, and CPU was basically idle (0% used by mysqlimport). Unfortunately we could not attach strace on mysqlimport because we did not have another user already logged as root (mysqlimport was executing as root).

With the limited amount of information it's not possible to give a good answer, but I do suggest you look at the logs and see what happen when things got blocked.

The logs in /var/log did not show anything useful. Are there other logs I can look?

You have the mysql logs in /var/log/mysql

Now I don't know how long block you had, in the message log you would be able to see if cron activity has been done while the block was, which would indicate that the syslog wasn't part of the problem.

It could also be good to check the blocks on the hard drive, as it could be possible that the binary log for mysql tried to store data, but the bad block could cause trouble while trying to write to it or read from it.


Did you install an official debian mysql or you installed the precompiled version from mysql.com?
official Debian mysql

Good, one less thing to think about.

--

//Aho
.