[BlueOnyx:04633] Re: Help with recent Installs (/var Full)(Mysql quit

[Jeff Folk]

On May 24, 2010, at 1:49 PM, publictv at cox.net wrote:

> This is what it came up with I noticed that the Mysql log is massive  
> and I am guessing that's not normal so if its not then what could  
> have caused it? and how do I fix this? Also just for reference all  
> that is installed for Blueonyx, and Cantos is the original install  
> plus the updates nothing additional!

Have you looked in it to see what it is logging? My log file is 23K  
since February of 2009...

tail -n 50 /var/log/mysqld.log (That will give you the last 50 lines  
of the log to look at)

Should see something like this:

100319  7:58:53 [Note] /usr/libexec/mysqld: Normal shutdown
100319  7:58:54  InnoDB: Starting shutdown...
100319  7:58:56  InnoDB: Shutdown completed; log sequence number 0  
8000288
100319  7:58:56 [Note] /usr/libexec/mysqld: Shutdown complete
100319 07:58:56  mysqld ended
100319 08:01:30  mysqld started
100319  8:01:30 [Warning] option 'max_join_size': unsigned value  
18446744073709551615 adjusted to 4294967295
100319  8:01:30 [Warning] option 'max_join_size': unsigned value  
18446744073709551615 adjusted to 4294967295
100319  8:01:32  InnoDB: Started; log sequence number 0 8000288
100319  8:01:32 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.77'  socket: '/var/lib/mysql/mysql.sock'  port: 3306   
Source distribution
100518 09:06:47  mysqld started
100518  9:06:47 [Warning] option 'max_join_size': unsigned value  
18446744073709551615 adjusted to 4294967295
100518  9:06:47 [Warning] option 'max_join_size': unsigned value  
18446744073709551615 adjusted to 4294967295
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
100518  9:06:48  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
100518  9:06:48  InnoDB: Started; log sequence number 0 10094681
100518  9:06:48 [Note] /usr/libexec/mysqld: ready for connections.

Did you by chance enable debug level logging by issuing a 'debug'  
command while in mysql? If you (or your software) did, you'll see log  
entries for each and every query... Can make the log big in a hurry.  
Log in to mysql from the command line and issue the 'debug' command  
again to turn it off.

In order to get mysqld to start up, you'll probably have to move (or  
delete) the existing log file, then do a 'mysqladmin flush-logs' after  
starting mysqld again. Then take care of that debug problem (if that's  
what it is).

HTH
Jeff