Nope. Many of the start times for the mysqld processes go back to June 22, when the server was last rebooted.
The backup script that runs every evening at 11:30pm does do a mysqlhotcopy, and resets the master and slave replica servers. This is reflected in the creation time of the log files with data in them. Judging from the timestamp of the zero length files, however, something else seems to be happening between 4 and 4:30 am which creates a zero length copy of every _bin and _index file in the log area, including the previously created zero length copies (hence the logarithmic growth in numbers of files - 1,3,7,15,31, etc.). Neither 'root' or the mysql user have any crons running at that time. Apparently SOMEONE (or something) does, however... Knowing what would cause the file duplication will hopefully help me track it down. - A -----Original Message----- From: Victor Pendleton [mailto:[EMAIL PROTECTED] Sent: Monday, August 09, 2004 12:17 PM To: Ciarochi, Anthony; '[EMAIL PROTECTED] ' Subject: RE: what is causing these XX.1.1.1.1 logs? Are you in the process of stopping and restarting the MySQL Database server? -----Original Message----- From: Ciarochi, Anthony To: [EMAIL PROTECTED] Sent: 8/9/04 2:13 PM Subject: what is causing these XX.1.1.1.1 logs? For some reason, I am getting hundreds of zero-length binary log remnants in my log area. Any idea what could be causing this? Is there any danger in deleting the logs that don't show up in 'show master logs'? show master logs output: mysqld_bin.058 mysqld_bin.059 bash-2.05b# ls -altr | grep 059 -rw-rw---- 1 psccats mysql 916402 Aug 9 11:43 mysqld_bin.059 bash-2.05b# ls -altr | grep 058 -rw-rw---- 1 psccats mysql 2248499 Aug 8 23:30 mysqld_bin.058.1 -rw-rw---- 1 psccats mysql 0 Aug 9 04:20 mysqld_bin.058 bash-2.05b# ls -altr | grep .057 -rw-rw---- 1 psccats mysql 4275592 Aug 7 23:30 mysqld_bin.057.1.1 -rw-rw---- 1 psccats mysql 0 Aug 9 04:20 mysqld_bin.057.1 bash-2.05b# ls -altr | grep .056 -rw-rw---- 1 psccats mysql 11127356 Aug 5 23:30 mysqld_bin.056.1.1.1 -rw-rw---- 1 psccats mysql 0 Aug 7 04:19 mysqld_bin.056.1 -rw-rw---- 1 psccats mysql 0 Aug 9 04:20 mysqld_bin.056.1.1 bash-2.05b# ls -altr | grep .055 -rw-rw---- 1 psccats mysql 17898151 Aug 3 23:30 mysqld_bin.055.1.1.1.1 -rw-rw---- 1 psccats mysql 0 Aug 5 04:16 mysqld_bin.055.1 -rw-rw---- 1 psccats mysql 0 Aug 7 04:19 mysqld_bin.055.1.1 -rw-rw---- 1 psccats mysql 0 Aug 9 04:20 mysqld_bin.055.1.1.1 bash-2.05b# ls -altr | grep .054 -rw-rw---- 1 psccats mysql 63008 Aug 1 23:30 mysqld_bin.054.1.1.1.1 -rw-rw---- 1 psccats mysql 0 Aug 4 04:05 mysqld_bin.054.1 -rw-rw---- 1 psccats mysql 0 Aug 6 04:28 mysqld_bin.054.1.1 -rw-rw---- 1 psccats mysql 0 Aug 8 04:33 mysqld_bin.054.1.1.1 The pattern (in case it's not obvious): The logs are rotated every day or two, possibly by the backup script Every couple of days, each old log is renamed to mysqld.bin.0XX.1[.1...], and the old name appears as a zero-length file After several days, I have dozens and dozens of these zero length files in my log dir (the number grows exponentially). I am also getting dozens of zero-length mysql_bin_ind.index.1[.1...] files, all with the same time stamp (~4:00-4:30, today's date). Any idea what's up with that? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
