Last week, I ran into a _really_ weird problem with my KnoppMyth box. First of all, when I went into View Recordings, nothing showed up. If I tried to go to mythweb from my other machines, my browser would just tell me that there's a problem with the webserver. A bunch of other stuff stopped working correctly, too.

It turned out that my / partition filled up. /var/log/mysql/mysql.log had ballooned to over a gig. So any time a process tried to write to /tmp or /var/log or anything on the / partition, it failed, and apparently myth and apache don't handle this in the most graceful manner.

Solution: clear out the log file and now everything works.

For the record, I'm currently using R5B7, but I upgraded from R5A30.1, which was upgraded from R5A16.

I Had the same problem, I can't remember exactly what the cause was, but I had to amend the logrotate scripts to get them to run correctly, so that the mysql.log file would rollover each night.

This just happened to me, too. I found that logrotate is supposed to run daily (from cron.daily) to keep this, and other log files, from getting too big.

However, when I ran /etc/cron.daily/logrotate manually, I got the error "error: hibernate-script:1 duplicate log entry for /var/log/hibernate.log". Looking in /etc/logrotate.d, I saw two files dealing with hibermate, "hibernate" and "hibernate-script". These both have the exact same contents, so I deleted "hibernate-script" and /etc/cron.daily/logrotate seems to run fine now.

Hopefully, this will keep mysql.log from growing too big.