RE: SLAVE aware of binary log file switch?
" Waiting for master to send event" -- just means that nothing is being replicated at the moment. The Yes+Yes says that things are running. Seconds_behind_master = 0 says that the Slave is essentially caught up. NULL means something is broken. >0 _may_ indicate a problem, or it may indicate a brief delay. > -Original Message- > From: Mihamina Rakotomandimby [mailto:miham...@rktmb.org] > Sent: Monday, June 17, 2013 5:35 AM > To: mysql@lists.mysql.com > Subject: Re: SLAVE aware of binary log file switch? > > On 2013-06-17 14:43, Denis Jedig wrote: > >> Say the binary log file (on the master) has reached its maximum size, > >> so that it has to switch to a "+1" binary log file: does he inform > >> the SLAVE of that switch so that the SLAVE updates its information > >> about the MASTER status? > > The master does not "inform" the slave via an immediate communication > > channel, but the slave knows how to keep up because the end of the > > binary log file contains continuation information - i.e. the name of > > the next log file to fetch. > > OK. > > I'm sorry I was mislead by the output of: > [mihamina@prod-ebidual ~]$ echo "SHOW SLAVE STATUS \G;" | mysql -uroot - > px | grep 'Slave_' > Slave_IO_State: Waiting for master to send event <-- > this > Slave_IO_Running: Yes > Slave_SQL_Running: Yes > > -- > RMA.
Re: SLAVE aware of binary log file switch?
On 2013-06-17 14:43, Denis Jedig wrote: Say the binary log file (on the master) has reached its maximum size, so that it has to switch to a "+1" binary log file: does he inform the SLAVE of that switch so that the SLAVE updates its information about the MASTER status? The master does not "inform" the slave via an immediate communication channel, but the slave knows how to keep up because the end of the binary log file contains continuation information - i.e. the name of the next log file to fetch. OK. I'm sorry I was mislead by the output of: [mihamina@prod-ebidual ~]$ echo "SHOW SLAVE STATUS \G;" | mysql -uroot -px | grep 'Slave_' Slave_IO_State: Waiting for master to send event <-- this Slave_IO_Running: Yes Slave_SQL_Running: Yes -- RMA.
SLAVE aware of binary log file switch?
Hi all, Given a MASTER and a SLAVE. When launching the SLAVE, it knows about the binary log file used by the MASTER and the position in that log file. Say the binary log file (on the master) has reached its maximum size, so that it has to switch to a "+1" binary log file: does he inform the SLAVE of that switch so that the SLAVE updates its information about the MASTER status? I'm readind the documentation http://dev.mysql.com/doc/refman/5.1/en/binary-log.html and dont see what is happening while slaving. Thank you. -- RMA.
Re: SLAVE aware of binary log file switch?
Am 17.06.2013 13:11, schrieb Mihamina Rakotomandimby: Say the binary log file (on the master) has reached its maximum size, so that it has to switch to a "+1" binary log file: does he inform the SLAVE of that switch so that the SLAVE updates its information about the MASTER status? The master does not "inform" the slave via an immediate communication channel, but the slave knows how to keep up because the end of the binary log file contains continuation information - i.e. the name of the next log file to fetch. Denis -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: logrotate script doesn't create a new log file
On 02/22/2012 07:58 PM, Johan De Meersman wrote: Having this line commented, we have to rely on logrotate.conf to have something similar defined and we see an error when using mysql-rotate Then something else is wrong. Does your MySQL daemon happen to run as a user who can normally not create files in the directory where the log files are? This seems to be the reason. MySQL is run under mysql user and the log file is located under /var/log in Fedora, so the daemon doesn't have enough privileges. It's clear now, we'd need to un-comment the line in such configuration. Thanks for the tip. Honza -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: logrotate script doesn't create a new log file
- Original Message - > From: "Honza Horak" > > particular reason why the line is not used by default? Can't be bothered to go look at the script, but it should be doing a "flush logs" somewhere. The line is commented by default because MySQL will recreate it's logfiles automatically, and you should only uncomment it if you really feel the need to pre-create the files with other than default permissions or owners. > Having this line commented, we have to rely on logrotate.conf to have > something similar defined and we see an error when using mysql-rotate Then something else is wrong. Does your MySQL daemon happen to run as a user who can normally not create files in the directory where the log files are? > I think the line shouldn't be commented by default. It should - a well-configured system doesn't need it. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
logrotate script doesn't create a new log file
Hi all, I'm thinking of logrotate script, that is shipped in mysql tar ball (e.g. mysql-5.5.20/support-files/mysql-log-rotate.sh). There is a commented line "# create 600 mysql mysql", that should originally ensure logrotate utility creates a new log file after rotating. Is there any particular reason why the line is not used by default? Having this line commented, we have to rely on logrotate.conf to have something similar defined and we see an error when using mysql-rotate script alone, such as: > logrotate -f /etc/logrotate.d/mysqld I think the line shouldn't be commented by default. Any thoughts appreciated. Thanks. Honza -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: PID and LOG file
mysqld_safe might not know where your config file is located. You can specify it's location at the command line with --defaults-file=file_name alternatively, you could specify the location of your log file thus: --log-error=file_name other options found at http://dev.mysql.com/doc/refman/5.1/en/mysqld-safe.html - michael dykman On Tue, Nov 15, 2011 at 7:31 AM, javad bakhshi wrote: > Hi, > > I am trying to install Mysql on linux which I don't have a root access. I > have done the folowing : > > 1. Download source files from http://dev.mysql.com/downloads/mysql/ and > un-tar thwm > 2. configure the instalation using ./configure as: > CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions > -fno-rtti" ; \ > ./configure --prefix=/bubo/home/h10/javad/scratch/mysql \ > --enable-assembler \ > --with-mysqld-ldflags=-all-static \ > --with-client-ldflags=-all-static \ > --with-mysqld-user=javad \ > > --with-unix-socket-path=/bubo/home/h10/javad/scratch/mysql/tmp/mysql.sock \ > --localstatedir=/bubo/home/h10/javad/scratch/mysql/share \ > --datadir=/bubo/home/h10/javad/scratch/mysql/data\ > --enable-thread-safe-client > > 3. execute ./bin/mysql_install_db > 4. execute bin/mysqld_safe & to run mysql. but at this point I get the > folowing error: > Starting mysqld daemon with databases from > /bubo/home/h10/javad/scratch/mysql/data > ./bin/mysqld_safe: line 394: /var/log/mysqld.log: Permission denied > ./bin/mysqld_safe: line 402: /var/log/mysqld.log: Permission denied > STOPPING server from pid file > /bubo/home/h10/javad/scratch/mysql/data/the.pid > tee: /var/log/mysqld.log: Permission denied > 15 13:14:18 mysqld ended > tee: /var/log/mysqld.log: Permission denied > > I don't know why I get this error since I have changed the my.cnf to > err-log=/bubo/home/h10/javad/scratch/mysql/data/the.log > pid-file=/bubo/home/h10/javad/scratch/mysql/data/the.pid > > > > > > Best regards, > Javad Bakhshi, > -- - michael dykman - mdyk...@gmail.com May the Source be with you. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
PID and LOG file
Hi, I am trying to install Mysql on linux which I don't have a root access. I have done the folowing : 1. Download source files from http://dev.mysql.com/downloads/mysql/ and un-tar thwm 2. configure the instalation using ./configure as: CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions -fno-rtti" ; \ ./configure --prefix=/bubo/home/h10/javad/scratch/mysql \ --enable-assembler \ --with-mysqld-ldflags=-all-static \ --with-client-ldflags=-all-static \ --with-mysqld-user=javad \ --with-unix-socket-path=/bubo/home/h10/javad/scratch/mysql/tmp/mysql.sock \ --localstatedir=/bubo/home/h10/javad/scratch/mysql/share \ --datadir=/bubo/home/h10/javad/scratch/mysql/data\ --enable-thread-safe-client 3. execute ./bin/mysql_install_db 4. execute bin/mysqld_safe & to run mysql. but at this point I get the folowing error: Starting mysqld daemon with databases from /bubo/home/h10/javad/scratch/mysql/data ./bin/mysqld_safe: line 394: /var/log/mysqld.log: Permission denied ./bin/mysqld_safe: line 402: /var/log/mysqld.log: Permission denied STOPPING server from pid file /bubo/home/h10/javad/scratch/mysql/data/the.pid tee: /var/log/mysqld.log: Permission denied 15 13:14:18 mysqld ended tee: /var/log/mysqld.log: Permission denied I don't know why I get this error since I have changed the my.cnf to err-log=/bubo/home/h10/javad/scratch/mysql/data/the.log pid-file=/bubo/home/h10/javad/scratch/mysql/data/the.pid Best regards, Javad Bakhshi,
Re: mysql-bin log file
On Mon, Apr 19, 2010 at 12:16 PM, Rob Wultsch wrote: > One way or another this > should be a conscious decision, not a copy and paste from a mailing > list. > As is the case with most settings :-) -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
Re: mysql-bin log file
On Mon, Apr 19, 2010 at 1:07 AM, Johan De Meersman wrote: > On Mon, Apr 19, 2010 at 6:48 AM, Rob Wultsch wrote: >> >> And if your slave's IO lags badly enough this will hose you. Further > > True, but if you remove logs that haven't been transferred, yet, you lose > your slave. > > Transfer of logs shouldn't be lagging that much, really, unless you're > replicating over some POTS line. Don't forget that log transfer doesn't have > to wait for processing on the slave. > > -- Agreed. 7 days is an absurd length of time for the io thread to lag. However, if someone has setup replication but not monitoring it, 7 days isn't that long. The behavior of mysql after a crash (that is, breaking the io thread) makes me weary of suggesting to a inexperienced user that they should turn on this features. In an ideal world the user should determined how many days of backups they need and further how much pitr. It might be very sane to say 30 days of daily backups with 7 days of pitr. One way or another this should be a conscious decision, not a copy and paste from a mailing list. -- Rob Wultsch wult...@gmail.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql-bin log file
On Mon, Apr 19, 2010 at 6:48 AM, Rob Wultsch wrote: > > And if your slave's IO lags badly enough this will hose you. Further > True, but if you remove logs that haven't been transferred, yet, you lose your slave. Transfer of logs shouldn't be lagging that much, really, unless you're replicating over some POTS line. Don't forget that log transfer doesn't have to wait for processing on the slave. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
Re: mysql-bin log file
On Sun, Apr 18, 2010 at 9:40 PM, Prabhat Kumar wrote: > You can add a expire_logs_days Variable in my.cnf during the configuration > of replication server. > > # expire_logs_days = 7 > > It will purged binary logs older than 7 days.The old logs will be purged > during the next bin-log swittch. > And if your slave's IO lags badly enough this will hose you. Further it might well come in handy to an arbitrary number of bin logs for pirt purposes. -- Rob Wultsch wult...@gmail.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql-bin log file
You can add a *expire_logs_days* Variable in my.cnf during the configuration of replication server. #* expire_logs_days = 7* It will purged binary logs older than 7 days.The old logs will be purged during the next bin-log switch. Or, You can also delete bin-log manually using command : PURGE BINARY LOGS TO 'mysql-bin.010'; PURGE BINARY LOGS BEFORE '2008-04-02 22:46:26'; but before you purge please make sure that slave is on sync with master or confirm the current status from slaves. Thanks, On Mon, Apr 19, 2010 at 9:47 AM, Rob Wultsch wrote: > On Sun, Apr 18, 2010 at 8:58 PM, Angelina Paul > wrote: > > How can I remove old mysql-bin log file in log directory? A mysql full > > backup will clear the old mysql bin log file or not? > > > > Thanks, > > Arshu Paul > > > You probably want > http://mysql2.mirrors-r-us.net/doc/refman/5.1/en/purge-master-logs.html > > > -- > Rob Wultsch > wult...@gmail.com > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/mysql?unsub=aim.prab...@gmail.com > > -- Best Regards, Prabhat Kumar MySQL DBA Datavail-India Mumbai Mobile : 91-9987681929 www.datavail.com My Blog: http://adminlinux.blogspot.com My LinkedIn: http://www.linkedin.com/in/profileprabhat
Re: mysql-bin log file
On Sun, Apr 18, 2010 at 8:58 PM, Angelina Paul wrote: > How can I remove old mysql-bin log file in log directory? A mysql full > backup will clear the old mysql bin log file or not? > > Thanks, > Arshu Paul > You probably want http://mysql2.mirrors-r-us.net/doc/refman/5.1/en/purge-master-logs.html -- Rob Wultsch wult...@gmail.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
mysql-bin log file
How can I remove old mysql-bin log file in log directory? A mysql full backup will clear the old mysql bin log file or not? Thanks, Arshu Paul
Re: Install problem: log file issue
On Feb 12, 2009, at 6:28 PM, csego...@gmail.com wrote: Andy, Michael, and Walter - thank you! Adding a [mysqld_safe] group to my.cnf gets me further but the start still fails. The good thing is that the failure is no longer due to the inability to write the log file. The [mysqld_safe] section of my.cnf reads: [mysqld_safe] port= 3306 socket = /tmp/mysql.sock skip-locking key_buffer = 16M max_allowed_packet = 1M table_cache = 64 sort_buffer_size = 512K net_buffer_length = 8K read_buffer_size = 256K read_rnd_buffer_size = 512K myisam_sort_buffer_size = 8M datadir = /app/mysql/data #data_file_path = /app/mysql/data #log = /app/mysql/log/mysqld.log log-bin = /app/mysql/log/mysql-bin.log log-output = FILE general_log = 1 general_log_file = /app/mysql/log/msyql_general.log socket = /app/mysql/var/mysql.sock log-error = /app/mysql/log/error.log Luckily, I now have an error log which reads: 090212 18:24:04 mysqld_safe Starting mysqld daemon with databases from /app/mysql/data InnoDB: Log scan progressed past the checkpoint lsn 0 39548 090212 18:24:04 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... InnoDB: Doing recovery: scanned up to log sequence number 0 46409 090212 18:24:04 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 090212 18:24:04 InnoDB: Started; log sequence number 0 46409 090212 18:24:04 [ERROR] /app/mysql/libexec/mysqld: Can't create/ write to file '/var/run/mysqld/mysqld.pid' (Errcode: 2) 090212 18:24:04 [ERROR] Can't start server: can't create PID file: No such file or directory 090212 18:24:04 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended Now I need to figure out how to point PID file creation the appropriate directory. Sounds like you want: pid-file = /app/mysql/log/mysql.pid http://dev.mysql.com/doc/refman/5.1/en/server-options.html#option_mysqld_pid-file -- Paul DuBois Sun Microsystems / MySQL Documentation Team Madison, Wisconsin, USA www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Install problem: log file issue
Andy, Michael, and Walter - thank you! Adding a [mysqld_safe] group to my.cnf gets me further but the start still fails. The good thing is that the failure is no longer due to the inability to write the log file. The [mysqld_safe] section of my.cnf reads: [mysqld_safe] port= 3306 socket = /tmp/mysql.sock skip-locking key_buffer = 16M max_allowed_packet = 1M table_cache = 64 sort_buffer_size = 512K net_buffer_length = 8K read_buffer_size = 256K read_rnd_buffer_size = 512K myisam_sort_buffer_size = 8M datadir = /app/mysql/data #data_file_path = /app/mysql/data #log = /app/mysql/log/mysqld.log log-bin = /app/mysql/log/mysql-bin.log log-output = FILE general_log = 1 general_log_file = /app/mysql/log/msyql_general.log socket = /app/mysql/var/mysql.sock log-error = /app/mysql/log/error.log Luckily, I now have an error log which reads: 090212 18:24:04 mysqld_safe Starting mysqld daemon with databases from /app/mysql/data InnoDB: Log scan progressed past the checkpoint lsn 0 39548 090212 18:24:04 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... InnoDB: Doing recovery: scanned up to log sequence number 0 46409 090212 18:24:04 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 090212 18:24:04 InnoDB: Started; log sequence number 0 46409 090212 18:24:04 [ERROR] /app/mysql/libexec/mysqld: Can't create/write to file '/var/run/mysqld/mysqld.pid' (Errcode: 2) 090212 18:24:04 [ERROR] Can't start server: can't create PID file: No such file or directory 090212 18:24:04 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended Now I need to figure out how to point PID file creation the appropriate directory. C Walter Heck wrote: > I haven't looked into it in detail an don't have time right nw, but it > is also hardcoded in mysqld_safe. I have seen a case where it had to > be changed there to make it work. try that and please report back :) > > Walter > > OlinData: Professional services for MySQL > Support * Consulting * Administration > http://www.olindata.com > > > > On Thu, Feb 12, 2009 at 6:39 PM, csego...@gmail.com > wrote: > >> Andy, >> >> Thanks for the suggestion. my_print_defaults mysqld indicates that it >> is reading my my.cnf. Furthermore, I have tried both the log and >> log-output variables in my.cnf with no success. Any other ideas? >> >> Thanks! >> C >> >> >> >> >> Andy Smith wrote: >> >>> It could be that your my.cnf isn't being read (permissions or in the >>> wrong directory), or that you have multiple my.cnf files. >>> >>> Quoting "csego...@gmail.com" : >>> >>> >>>> That is intentional. I want to write the log to a non-standard >>>> location. >>>> >>>> >>> >>> This message was sent using IMP, the Internet Messaging Program. >>> >>> >> -- >> MySQL General Mailing List >> For list archives: http://lists.mysql.com/mysql >> To unsubscribe:http://lists.mysql.com/mysql?unsub=li...@olindata.com >> >> >> -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Install problem: log file issue
I haven't looked into it in detail an don't have time right nw, but it is also hardcoded in mysqld_safe. I have seen a case where it had to be changed there to make it work. try that and please report back :) Walter OlinData: Professional services for MySQL Support * Consulting * Administration http://www.olindata.com On Thu, Feb 12, 2009 at 6:39 PM, csego...@gmail.com wrote: > Andy, > > Thanks for the suggestion. my_print_defaults mysqld indicates that it > is reading my my.cnf. Furthermore, I have tried both the log and > log-output variables in my.cnf with no success. Any other ideas? > > Thanks! > C > > > > > Andy Smith wrote: >> It could be that your my.cnf isn't being read (permissions or in the >> wrong directory), or that you have multiple my.cnf files. >> >> Quoting "csego...@gmail.com" : >> >>> That is intentional. I want to write the log to a non-standard >>> location. >>> >> >> >> This message was sent using IMP, the Internet Messaging Program. >> > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe:http://lists.mysql.com/mysql?unsub=li...@olindata.com > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Install problem: log file issue
Andy, Thanks for the suggestion. my_print_defaults mysqld indicates that it is reading my my.cnf. Furthermore, I have tried both the log and log-output variables in my.cnf with no success. Any other ideas? Thanks! C Andy Smith wrote: > It could be that your my.cnf isn't being read (permissions or in the > wrong directory), or that you have multiple my.cnf files. > > Quoting "csego...@gmail.com" : > >> That is intentional. I want to write the log to a non-standard >> location. >> > > > This message was sent using IMP, the Internet Messaging Program. > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Install problem: log file issue
It could be that your my.cnf isn't being read (permissions or in the wrong directory), or that you have multiple my.cnf files. Quoting "csego...@gmail.com" : That is intentional. I want to write the log to a non-standard location. This message was sent using IMP, the Internet Messaging Program. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Install problem: log file issue
That is intentional. I want to write the log to a non-standard location. Thanks! C fire9 wrote: > Colin, > hi, so I think your mysql account doesn't have access /var/log/ > directory Permission. > > > Yours, > fire9 > ÔÚ 2009-2-13£¬ÉÏÎç1:02£¬ csego...@gmail.com > <mailto:csego...@gmail.com> дµÀ£º > >> In the process of installing MySQL 5.1.31, I receive the following error >> when I attempt to start mysqld_safe: >> >> 090212 10:57:40 mysqld_safe Logging to '/var/log/mysqld.log'. >> 090212 10:57:40 mysqld_safe Starting mysqld daemon with databases from >> /app/mysql/data >> /app/mysql/bin/mysqld_safe: line 96: /var/log/mysqld.log: Permission >> denied >> /app/mysql/bin/mysqld_safe: line 133: /var/log/mysqld.log: Permission >> denied >> 090212 10:57:40 mysqld_safe mysqld from pid file >> /var/run/mysqld/mysqld.pid ended >> /app/mysql/bin/mysqld_safe: line 96: /var/log/mysqld.log: Permission >> denied >> >> >> My my.cnf file reads: >> >> # The MySQL server >> [mysqld] >> port= 3306 >> socket = /tmp/mysql.sock >> skip-locking >> key_buffer = 16M >> max_allowed_packet = 1M >> table_cache = 64 >> sort_buffer_size = 512K >> net_buffer_length = 8K >> read_buffer_size = 256K >> read_rnd_buffer_size = 512K >> myisam_sort_buffer_size = 8M >> datadir = /app/mysql/data >> #data_file_path = /app/mysql/data >> general_log = 1 >> general_log_file = /app/mysql/log/ >> socket = /app/mysql/var/mysql.sock >> log-error = /app/mysql/log/error.log >> >> I thought the general_log_file variable would define the location of the >> log file, yet mysqld is trying to write the log file to a different >> directory. Does anyone have any suggestions on how to fix this? >> >> Thanks! >> Colin >> >> -- >> MySQL General Mailing List >> For list archives: http://lists.mysql.com/mysql >> To unsubscribe: >>http://lists.mysql.com/mysql?unsub=fire9di...@gmail.com >> > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Install problem: log file issue
Colin, hi, so I think your mysql account doesn't have access /var/log/ directory Permission. Yours, fire9 在 2009-2-13，上午1:02， csego...@gmail.com 写道： In the process of installing MySQL 5.1.31, I receive the following error when I attempt to start mysqld_safe: 090212 10:57:40 mysqld_safe Logging to '/var/log/mysqld.log'. 090212 10:57:40 mysqld_safe Starting mysqld daemon with databases from /app/mysql/data /app/mysql/bin/mysqld_safe: line 96: /var/log/mysqld.log: Permission denied /app/mysql/bin/mysqld_safe: line 133: /var/log/mysqld.log: Permission denied 090212 10:57:40 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended /app/mysql/bin/mysqld_safe: line 96: /var/log/mysqld.log: Permission denied My my.cnf file reads: # The MySQL server [mysqld] port= 3306 socket = /tmp/mysql.sock skip-locking key_buffer = 16M max_allowed_packet = 1M table_cache = 64 sort_buffer_size = 512K net_buffer_length = 8K read_buffer_size = 256K read_rnd_buffer_size = 512K myisam_sort_buffer_size = 8M datadir = /app/mysql/data #data_file_path = /app/mysql/data general_log = 1 general_log_file = /app/mysql/log/ socket = /app/mysql/var/mysql.sock log-error = /app/mysql/log/error.log I thought the general_log_file variable would define the location of the log file, yet mysqld is trying to write the log file to a different directory. Does anyone have any suggestions on how to fix this? Thanks! Colin -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=fire9di...@gmail.com
Install problem: log file issue
In the process of installing MySQL 5.1.31, I receive the following error when I attempt to start mysqld_safe: 090212 10:57:40 mysqld_safe Logging to '/var/log/mysqld.log'. 090212 10:57:40 mysqld_safe Starting mysqld daemon with databases from /app/mysql/data /app/mysql/bin/mysqld_safe: line 96: /var/log/mysqld.log: Permission denied /app/mysql/bin/mysqld_safe: line 133: /var/log/mysqld.log: Permission denied 090212 10:57:40 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended /app/mysql/bin/mysqld_safe: line 96: /var/log/mysqld.log: Permission denied My my.cnf file reads: # The MySQL server [mysqld] port= 3306 socket = /tmp/mysql.sock skip-locking key_buffer = 16M max_allowed_packet = 1M table_cache = 64 sort_buffer_size = 512K net_buffer_length = 8K read_buffer_size = 256K read_rnd_buffer_size = 512K myisam_sort_buffer_size = 8M datadir = /app/mysql/data #data_file_path = /app/mysql/data general_log = 1 general_log_file = /app/mysql/log/ socket = /app/mysql/var/mysql.sock log-error = /app/mysql/log/error.log I thought the general_log_file variable would define the location of the log file, yet mysqld is trying to write the log file to a different directory. Does anyone have any suggestions on how to fix this? Thanks! Colin -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Rotate regular log file only
You're wrong.The new log file will be generated when you flush logs manually. On Fri, Oct 24, 2008 at 2:23 AM, Olaf Stein < [EMAIL PROTECTED]> wrote: > And I assume you backup script also archives or removes the old log file, > because flush-logs does not start a new log file if there is still one > present > > > On 10/23/08 2:20 PM, "Andy Shellam" <[EMAIL PROTECTED]> wrote: > > > Hi Olaf, > > > > We use our mysqldump script to rotate the binlogs; it's much safer as it > > allows MySQL to do the log rotate natively (if you use logrotate, MySQL > > will complain that either the log doesn't exist when it expects it to, > > or your slaves will bail out because they didn't know the log was > > changed. It happened to us recently when we moved the log directory and > > didn't update the log index.) > > > > At 2am our backup system runs the mysqldump script with the extra > > parameter --flush-logs. This causes MySQL to rotate the log it's using, > > and as you found out, all slaves respond to the change without an issue. > > > > Andy > > > > Olaf Stein wrote: > >> Thanks all... > >> Rotating actually does not affect the slaves, they adjust to the new > binlog > >> just fine, I guess I should have tried that first. > >> > >> I will nevertheless take a closer look at logrotate... > >> > >> Olaf > >> > >> > >> On 10/23/08 12:13 PM, "Uwe Kiewel" <[EMAIL PROTECTED]> wrote: > >> > >> > >>> -BEGIN PGP SIGNED MESSAGE- > >>> Hash: SHA1 > >>> > >>> Olaf Stein schrieb: > >>> > >>>> Hi all > >>>> > >>>> Is it possible to rotate just the regular (--log) log file? > >>>> > >>> I am not sure if it will be safe, but maybe with logrotate and for > >>> /var/log/mysqld.log the "copytruncate" option for logrotate. > >>> > >>> > >>>> If I do flush-logs I have to tell my slaves that (at least I have done > so > >>>> in > >>>> the past, maybe I don't and the slves realizes by itself?) > >>>> > >>> I think so, b/c I've never told my slaves... > >>> > >>> HTH, > >>> Uwe > >>> -BEGIN PGP SIGNATURE- > >>> Version: GnuPG v1.4.9 (MingW32) > >>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > >>> > >>> iQIcBAEBAgAGBQJJAKK3AAoJEEJXG7BUuynntkkP/R5IiZWpafUfQqR+hVUax9at > >>> NV8YKfUIz8J1QLrT7cWOEqpuliABP0P6AOS06Tmm4t2ve15BJ1fwxRqHiHEem9BE > >>> 7nb1AuQDlGW+qTOVpzJqj2H8b5SARdLoKswTisT0Yz++NDj3WQxVM/UIKotwRnLH > >>> edDHSrfjPl+38TmlmGP7/3ZYA2gEAKosgYGrax6bHtSnrw2pfDq6BaXvEwXABAHc > >>> aCE6P3DKGr4Ycs2Xlc49IkPHgE6/+SNM9MqVAs83OgxNZK5+c474YdJl7i5hfth1 > >>> 8RKMPweQgBtYRT3vfrvJdfzg2Wg75pJv1RwkKiGofaAjBmO9y93iNkE57pNXq3sd > >>> eWFZR5YcPA+3+GCnAvOMcjzytISlpxNNic235qaYSuoNDMV1rukxSYNpH62kzQPH > >>> V3gTKuZcjWYWasa0Y6ylSBWywSOnfc49n0mVdXeoHb7CpIQn3jwCtRG2+UCZUM1W > >>> O4U5+bKgXERqqwjNS5sk9SNmq5gQAKYU4IsDZwZcyFY7t/XEHwB3+bCVnm1y4V/s > >>> Fzin0FoAIbqm9VzALzTs5YUkWzoSzniGepIBrZR0PO98sDxOlDFUESpYnFj8oNap > >>> wjM/5P0tgbw99lIsLAMy7+FdPIlSssWxq+LFC4dR6o+pzVrYjFjoRg3MdYn9ein8 > >>> svOEP/N79cK5pPZJpDyY > >>> =cN1H > >>> -END PGP SIGNATURE- > >>> > >> > >> - Confidentiality Notice: > >> The following mail message, including any attachments, is for the > >> sole use of the intended recipient(s) and may contain confidential > >> and privileged information. The recipient is responsible to > >> maintain the confidentiality of this information and to use the > >> information only for authorized purposes. If you are not the > >> intended recipient (or authorized to receive information for the > >> intended recipient), you are hereby notified that any review, use, > >> disclosure, distribution, copying, printing, or action taken in > >> reliance on the contents of this e-mail is strictly prohibited. If > >> you have received this communication in error, please notify us > >> immediately by reply e-mail and destroy all copies of the original > >> message. Thank you. > >> > >> > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > -- I'm a MySQL DBA in china. More about me just visit here: http://yueliangdao0608.cublog.cn
Re: Rotate regular log file only
Nope, we use the expire_logs_days parameter in MySQL's my.cnf (set to
expire_logs_days=7 - removes log files that are 7 days old.)
mysqldump's flush-logs does indeed begin a new log - that's the idea of it:
# ls -l /srv/mysql
rw-rw 1 mysql localservice 213 2008-10-16 00:56 sql-m2-bin.17
-rw-rw 1 mysql localservice 213 2008-10-17 00:56 sql-m2-bin.18
-rw-rw 1 mysql localservice 213 2008-10-18 00:56 sql-m2-bin.19
-rw-rw 1 mysql localservice 213 2008-10-19 00:56 sql-m2-bin.20
-rw-rw 1 mysql localservice 213 2008-10-20 00:56 sql-m2-bin.21
-rw-rw 1 mysql localservice 213 2008-10-21 00:56 sql-m2-bin.22
-rw-rw 1 mysql localservice 213 2008-10-22 00:56 sql-m2-bin.23
-rw-rw 1 mysql localservice 213 2008-10-23 00:56 sql-m2-bin.24
-rw-rw 1 mysql localservice 98 2008-10-23 00:56 sql-m2-bin.25
# /usr/local/mysql/bin/mysqldump --single-transaction --flush-logs
--master-data=2 --all-databases --user=xxx --password=xxx >
/tmp/backup_2008-10-23.sql
# ls -l /srv/mysql
-rw-rw 1 mysql localservice 213 2008-10-17 00:56 sql-m2-bin.18
-rw-rw 1 mysql localservice 213 2008-10-18 00:56 sql-m2-bin.19
-rw-rw 1 mysql localservice 213 2008-10-19 00:56 sql-m2-bin.20
-rw-rw 1 mysql localservice 213 2008-10-20 00:56 sql-m2-bin.21
-rw-rw 1 mysql localservice 213 2008-10-21 00:56 sql-m2-bin.22
-rw-rw 1 mysql localservice 213 2008-10-22 00:56 sql-m2-bin.23
-rw-rw 1 mysql localservice 213 2008-10-23 00:56 sql-m2-bin.24
-rw-rw 1 mysql localservice 213 2008-10-23 19:37 sql-m2-bin.25
-rw-rw 1 mysql localservice 98 2008-10-23 19:37 sql-m2-bin.26
Notice the last write time of sql-m2-bin.25 and the new file
sql-m2-bin.26. Note this was on my slave server which was why the
logs never get written to past 00:56 each morning! Also my backup
script substitutes the date as appropriate into the dump file.
Regards,
Andy
Olaf Stein wrote:
And I assume you backup script also archives or removes the old log file,
because flush-logs does not start a new log file if there is still one
present
On 10/23/08 2:20 PM, "Andy Shellam" <[EMAIL PROTECTED]> wrote:
Hi Olaf,
We use our mysqldump script to rotate the binlogs; it's much safer as it
allows MySQL to do the log rotate natively (if you use logrotate, MySQL
will complain that either the log doesn't exist when it expects it to,
or your slaves will bail out because they didn't know the log was
changed. It happened to us recently when we moved the log directory and
didn't update the log index.)
At 2am our backup system runs the mysqldump script with the extra
parameter --flush-logs. This causes MySQL to rotate the log it's using,
and as you found out, all slaves respond to the change without an issue.
Andy
Olaf Stein wrote:
Thanks all...
Rotating actually does not affect the slaves, they adjust to the new binlog
just fine, I guess I should have tried that first.
I will nevertheless take a closer look at logrotate...
Olaf
On 10/23/08 12:13 PM, "Uwe Kiewel" <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Olaf Stein schrieb:
Hi all
Is it possible to rotate just the regular (--log) log file?
I am not sure if it will be safe, but maybe with logrotate and for
/var/log/mysqld.log the "copytruncate" option for logrotate.
If I do flush-logs I have to tell my slaves that (at least I have done so
in
the past, maybe I don't and the slves realizes by itself?)
I think so, b/c I've never told my slaves...
HTH,
Uwe
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIcBAEBAgAGBQJJAKK3AAoJEEJXG7BUuynntkkP/R5IiZWpafUfQqR+hVUax9at
NV8YKfUIz8J1QLrT7cWOEqpuliABP0P6AOS06Tmm4t2ve15BJ1fwxRqHiHEem9BE
7nb1AuQDlGW+qTOVpzJqj2H8b5SARdLoKswTisT0Yz++NDj3WQxVM/UIKotwRnLH
edDHSrfjPl+38TmlmGP7/3ZYA2gEAKosgYGrax6bHtSnrw2pfDq6BaXvEwXABAHc
aCE6P3DKGr4Ycs2Xlc49IkPHgE6/+SNM9MqVAs83OgxNZK5+c474YdJl7i5hfth1
8RKMPweQgBtYRT3vfrvJdfzg2Wg75pJv1RwkKiGofaAjBmO9y93iNkE57pNXq3sd
eWFZR5YcPA+3+GCnAvOMcjzytISlpxNNic235qaYSuoNDMV1rukxSYNpH62kzQPH
V3gTKuZcjWYWasa0Y6ylSBWywSOnfc49n0mVdXeoHb7CpIQn3jwCtRG2+UCZUM1W
O4U5+bKgXERqqwjNS5sk9SNmq5gQAKYU4IsDZwZcyFY7t/XEHwB3+bCVnm1y4V/s
Fzin0FoAIbqm9VzALzTs5YUkWzoSzniGepIBrZR0PO98sDxOlDFUESpYnFj8oNap
wjM/5P0tgbw99lIsLAMy7+FdPIlSssWxq+LFC4dR6o+pzVrYjFjoRg3MdYn9ein8
svOEP/N79cK5pPZJpDyY
=cN1H
-END PGP SIGNATURE-
- Confidentiality Notice:
The following mail message, including any attachments, is for the
sole use of the intended recipient(s) and may contain confidential
and privileged information. The recipien
Re: Rotate regular log file only
And I assume you backup script also archives or removes the old log file, because flush-logs does not start a new log file if there is still one present On 10/23/08 2:20 PM, "Andy Shellam" <[EMAIL PROTECTED]> wrote: > Hi Olaf, > > We use our mysqldump script to rotate the binlogs; it's much safer as it > allows MySQL to do the log rotate natively (if you use logrotate, MySQL > will complain that either the log doesn't exist when it expects it to, > or your slaves will bail out because they didn't know the log was > changed. It happened to us recently when we moved the log directory and > didn't update the log index.) > > At 2am our backup system runs the mysqldump script with the extra > parameter --flush-logs. This causes MySQL to rotate the log it's using, > and as you found out, all slaves respond to the change without an issue. > > Andy > > Olaf Stein wrote: >> Thanks all... >> Rotating actually does not affect the slaves, they adjust to the new binlog >> just fine, I guess I should have tried that first. >> >> I will nevertheless take a closer look at logrotate... >> >> Olaf >> >> >> On 10/23/08 12:13 PM, "Uwe Kiewel" <[EMAIL PROTECTED]> wrote: >> >> >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> Olaf Stein schrieb: >>> >>>> Hi all >>>> >>>> Is it possible to rotate just the regular (--log) log file? >>>> >>> I am not sure if it will be safe, but maybe with logrotate and for >>> /var/log/mysqld.log the "copytruncate" option for logrotate. >>> >>> >>>> If I do flush-logs I have to tell my slaves that (at least I have done so >>>> in >>>> the past, maybe I don't and the slves realizes by itself?) >>>> >>> I think so, b/c I've never told my slaves... >>> >>> HTH, >>> Uwe >>> -BEGIN PGP SIGNATURE- >>> Version: GnuPG v1.4.9 (MingW32) >>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org >>> >>> iQIcBAEBAgAGBQJJAKK3AAoJEEJXG7BUuynntkkP/R5IiZWpafUfQqR+hVUax9at >>> NV8YKfUIz8J1QLrT7cWOEqpuliABP0P6AOS06Tmm4t2ve15BJ1fwxRqHiHEem9BE >>> 7nb1AuQDlGW+qTOVpzJqj2H8b5SARdLoKswTisT0Yz++NDj3WQxVM/UIKotwRnLH >>> edDHSrfjPl+38TmlmGP7/3ZYA2gEAKosgYGrax6bHtSnrw2pfDq6BaXvEwXABAHc >>> aCE6P3DKGr4Ycs2Xlc49IkPHgE6/+SNM9MqVAs83OgxNZK5+c474YdJl7i5hfth1 >>> 8RKMPweQgBtYRT3vfrvJdfzg2Wg75pJv1RwkKiGofaAjBmO9y93iNkE57pNXq3sd >>> eWFZR5YcPA+3+GCnAvOMcjzytISlpxNNic235qaYSuoNDMV1rukxSYNpH62kzQPH >>> V3gTKuZcjWYWasa0Y6ylSBWywSOnfc49n0mVdXeoHb7CpIQn3jwCtRG2+UCZUM1W >>> O4U5+bKgXERqqwjNS5sk9SNmq5gQAKYU4IsDZwZcyFY7t/XEHwB3+bCVnm1y4V/s >>> Fzin0FoAIbqm9VzALzTs5YUkWzoSzniGepIBrZR0PO98sDxOlDFUESpYnFj8oNap >>> wjM/5P0tgbw99lIsLAMy7+FdPIlSssWxq+LFC4dR6o+pzVrYjFjoRg3MdYn9ein8 >>> svOEP/N79cK5pPZJpDyY >>> =cN1H >>> -END PGP SIGNATURE- >>> >> >> - Confidentiality Notice: >> The following mail message, including any attachments, is for the >> sole use of the intended recipient(s) and may contain confidential >> and privileged information. The recipient is responsible to >> maintain the confidentiality of this information and to use the >> information only for authorized purposes. If you are not the >> intended recipient (or authorized to receive information for the >> intended recipient), you are hereby notified that any review, use, >> disclosure, distribution, copying, printing, or action taken in >> reliance on the contents of this e-mail is strictly prohibited. If >> you have received this communication in error, please notify us >> immediately by reply e-mail and destroy all copies of the original >> message. Thank you. >> >> -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Rotate regular log file only
Hi Olaf, We use our mysqldump script to rotate the binlogs; it's much safer as it allows MySQL to do the log rotate natively (if you use logrotate, MySQL will complain that either the log doesn't exist when it expects it to, or your slaves will bail out because they didn't know the log was changed. It happened to us recently when we moved the log directory and didn't update the log index.) At 2am our backup system runs the mysqldump script with the extra parameter --flush-logs. This causes MySQL to rotate the log it's using, and as you found out, all slaves respond to the change without an issue. Andy Olaf Stein wrote: Thanks all... Rotating actually does not affect the slaves, they adjust to the new binlog just fine, I guess I should have tried that first. I will nevertheless take a closer look at logrotate... Olaf On 10/23/08 12:13 PM, "Uwe Kiewel" <[EMAIL PROTECTED]> wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Olaf Stein schrieb: Hi all Is it possible to rotate just the regular (--log) log file? I am not sure if it will be safe, but maybe with logrotate and for /var/log/mysqld.log the "copytruncate" option for logrotate. If I do flush-logs I have to tell my slaves that (at least I have done so in the past, maybe I don't and the slves realizes by itself?) I think so, b/c I've never told my slaves... HTH, Uwe -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJJAKK3AAoJEEJXG7BUuynntkkP/R5IiZWpafUfQqR+hVUax9at NV8YKfUIz8J1QLrT7cWOEqpuliABP0P6AOS06Tmm4t2ve15BJ1fwxRqHiHEem9BE 7nb1AuQDlGW+qTOVpzJqj2H8b5SARdLoKswTisT0Yz++NDj3WQxVM/UIKotwRnLH edDHSrfjPl+38TmlmGP7/3ZYA2gEAKosgYGrax6bHtSnrw2pfDq6BaXvEwXABAHc aCE6P3DKGr4Ycs2Xlc49IkPHgE6/+SNM9MqVAs83OgxNZK5+c474YdJl7i5hfth1 8RKMPweQgBtYRT3vfrvJdfzg2Wg75pJv1RwkKiGofaAjBmO9y93iNkE57pNXq3sd eWFZR5YcPA+3+GCnAvOMcjzytISlpxNNic235qaYSuoNDMV1rukxSYNpH62kzQPH V3gTKuZcjWYWasa0Y6ylSBWywSOnfc49n0mVdXeoHb7CpIQn3jwCtRG2+UCZUM1W O4U5+bKgXERqqwjNS5sk9SNmq5gQAKYU4IsDZwZcyFY7t/XEHwB3+bCVnm1y4V/s Fzin0FoAIbqm9VzALzTs5YUkWzoSzniGepIBrZR0PO98sDxOlDFUESpYnFj8oNap wjM/5P0tgbw99lIsLAMy7+FdPIlSssWxq+LFC4dR6o+pzVrYjFjoRg3MdYn9ein8 svOEP/N79cK5pPZJpDyY =cN1H -END PGP SIGNATURE- - Confidentiality Notice: The following mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. The recipient is responsible to maintain the confidentiality of this information and to use the information only for authorized purposes. If you are not the intended recipient (or authorized to receive information for the intended recipient), you are hereby notified that any review, use, disclosure, distribution, copying, printing, or action taken in reliance on the contents of this e-mail is strictly prohibited. If you have received this communication in error, please notify us immediately by reply e-mail and destroy all copies of the original message. Thank you. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Rotate regular log file only
Thanks all... Rotating actually does not affect the slaves, they adjust to the new binlog just fine, I guess I should have tried that first. I will nevertheless take a closer look at logrotate... Olaf On 10/23/08 12:13 PM, "Uwe Kiewel" <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Olaf Stein schrieb: >> Hi all >> >> Is it possible to rotate just the regular (--log) log file? > > I am not sure if it will be safe, but maybe with logrotate and for > /var/log/mysqld.log the "copytruncate" option for logrotate. > >> If I do flush-logs I have to tell my slaves that (at least I have done so in >> the past, maybe I don't and the slves realizes by itself?) > > I think so, b/c I've never told my slaves... > > HTH, > Uwe > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iQIcBAEBAgAGBQJJAKK3AAoJEEJXG7BUuynntkkP/R5IiZWpafUfQqR+hVUax9at > NV8YKfUIz8J1QLrT7cWOEqpuliABP0P6AOS06Tmm4t2ve15BJ1fwxRqHiHEem9BE > 7nb1AuQDlGW+qTOVpzJqj2H8b5SARdLoKswTisT0Yz++NDj3WQxVM/UIKotwRnLH > edDHSrfjPl+38TmlmGP7/3ZYA2gEAKosgYGrax6bHtSnrw2pfDq6BaXvEwXABAHc > aCE6P3DKGr4Ycs2Xlc49IkPHgE6/+SNM9MqVAs83OgxNZK5+c474YdJl7i5hfth1 > 8RKMPweQgBtYRT3vfrvJdfzg2Wg75pJv1RwkKiGofaAjBmO9y93iNkE57pNXq3sd > eWFZR5YcPA+3+GCnAvOMcjzytISlpxNNic235qaYSuoNDMV1rukxSYNpH62kzQPH > V3gTKuZcjWYWasa0Y6ylSBWywSOnfc49n0mVdXeoHb7CpIQn3jwCtRG2+UCZUM1W > O4U5+bKgXERqqwjNS5sk9SNmq5gQAKYU4IsDZwZcyFY7t/XEHwB3+bCVnm1y4V/s > Fzin0FoAIbqm9VzALzTs5YUkWzoSzniGepIBrZR0PO98sDxOlDFUESpYnFj8oNap > wjM/5P0tgbw99lIsLAMy7+FdPIlSssWxq+LFC4dR6o+pzVrYjFjoRg3MdYn9ein8 > svOEP/N79cK5pPZJpDyY > =cN1H > -END PGP SIGNATURE- - Confidentiality Notice: The following mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. The recipient is responsible to maintain the confidentiality of this information and to use the information only for authorized purposes. If you are not the intended recipient (or authorized to receive information for the intended recipient), you are hereby notified that any review, use, disclosure, distribution, copying, printing, or action taken in reliance on the contents of this e-mail is strictly prohibited. If you have received this communication in error, please notify us immediately by reply e-mail and destroy all copies of the original message. Thank you. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Rotate regular log file only
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Olaf Stein schrieb: > Hi all > > Is it possible to rotate just the regular (--log) log file? I am not sure if it will be safe, but maybe with logrotate and for /var/log/mysqld.log the "copytruncate" option for logrotate. > If I do flush-logs I have to tell my slaves that (at least I have done so in > the past, maybe I don't and the slves realizes by itself?) I think so, b/c I've never told my slaves... HTH, Uwe -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJJAKK3AAoJEEJXG7BUuynntkkP/R5IiZWpafUfQqR+hVUax9at NV8YKfUIz8J1QLrT7cWOEqpuliABP0P6AOS06Tmm4t2ve15BJ1fwxRqHiHEem9BE 7nb1AuQDlGW+qTOVpzJqj2H8b5SARdLoKswTisT0Yz++NDj3WQxVM/UIKotwRnLH edDHSrfjPl+38TmlmGP7/3ZYA2gEAKosgYGrax6bHtSnrw2pfDq6BaXvEwXABAHc aCE6P3DKGr4Ycs2Xlc49IkPHgE6/+SNM9MqVAs83OgxNZK5+c474YdJl7i5hfth1 8RKMPweQgBtYRT3vfrvJdfzg2Wg75pJv1RwkKiGofaAjBmO9y93iNkE57pNXq3sd eWFZR5YcPA+3+GCnAvOMcjzytISlpxNNic235qaYSuoNDMV1rukxSYNpH62kzQPH V3gTKuZcjWYWasa0Y6ylSBWywSOnfc49n0mVdXeoHb7CpIQn3jwCtRG2+UCZUM1W O4U5+bKgXERqqwjNS5sk9SNmq5gQAKYU4IsDZwZcyFY7t/XEHwB3+bCVnm1y4V/s Fzin0FoAIbqm9VzALzTs5YUkWzoSzniGepIBrZR0PO98sDxOlDFUESpYnFj8oNap wjM/5P0tgbw99lIsLAMy7+FdPIlSssWxq+LFC4dR6o+pzVrYjFjoRg3MdYn9ein8 svOEP/N79cK5pPZJpDyY =cN1H -END PGP SIGNATURE- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Rotate regular log file only
Hi all Is it possible to rotate just the regular (--log) log file? If I do flush-logs I have to tell my slaves that (at least I have done so in the past, maybe I don't and the slves realizes by itself?) Thanks Olaf - Confidentiality Notice: The following mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. The recipient is responsible to maintain the confidentiality of this information and to use the information only for authorized purposes. If you are not the intended recipient (or authorized to receive information for the intended recipient), you are hereby notified that any review, use, disclosure, distribution, copying, printing, or action taken in reliance on the contents of this e-mail is strictly prohibited. If you have received this communication in error, please notify us immediately by reply e-mail and destroy all copies of the original message. Thank you. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
error log file permissions
Background: Solaris 10, MySQL 5.0.45. I have changed something recently that is causing the error log file to be created with mode 660. I would like for it it be mode 664. I admit that I recently changed the my.cnf file and added a log-error line which did not have the fully qualified path and cause mysqld to write the file in the install directory rather than in the data directory, but have since restarted the server without that line. show variables says the file is in './mysql.server.name.edu.err' . I've been looking at the docs, but can't find any reference to how to set the permissions on that file. I use logadm to rotate the error log file and restart the server. The problem is my monitor software wants to read that file and can't. There's no problem with it being world readable since the server is dedicated to MySQL and no one can log in there. Thanks for any pointers. Steve
Why can't output to error log file when INNODB happened ERROR1205?
Why can't output to error log file when INNODB happened ERROR1205? All server error message is output to error log file, isn't it? -- create table test (id int ,name text)engine=innodb; insert into test values ( 1, 'test'); -- Pattern 1 -- CLIENT A: begin; select * from test lock in share mode; -- CLIENT B: begin; update test set name='bbb' where id=1; After 50sec,The following messages are output to the client. ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction -- MYSQL didn't add error message to error.log. -- Pattern 2 -- CLIENT A: begin; update test set name='' where id=1; -- CLIENT B: select * from test order by id, name for update; After 50sec,The following messages are output to the client. ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction -- MYSQL did add error message to error.log. 060808 15:46:09 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Lock wait timeout exceeded; try restarting transaction 060808 15:46:09 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Sort aborted -- <[EMAIL PROTECTED]> -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Why can't output to error log file when INNODB happened ERROR1205?
Why can't output to error log file when INNODB happened ERROR1205? All server error message is output to error log file, isn't it? -- create table test (id int ,name text)engine=innodb; insert into test values ( 1, 'test'); -- Pattern 1 -- CLIENT A: begin; select * from test lock in share mode; -- CLIENT B: begin; update test set name='bbb' where id=1; After 50sec,The following messages are output to the client. ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction -- MYSQL didn't add error message to error.log. -- Pattern 2 -- CLIENT A: begin; update test set name='' where id=1; -- CLIENT B: select * from test order by id, name for update; After 50sec,The following messages are output to the client. ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction -- MYSQL did add error message to error.log. 060808 15:46:09 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Lock wait timeout exceeded; try restarting transaction 060808 15:46:09 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Sort aborted -- <[EMAIL PROTECTED]> -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: about log file
The short answer is "in the config file." The long answer is to read: http://dev.mysql.com/doc/refman/4.1/en/log-files.html Or whatever manual version is appropriate to your MySQL version. -Sheeri On 5/17/06, Peng Yi-fan <[EMAIL PROTECTED]> wrote: Hi everyone, How to change the log file path of a database. I am using Window XP OS. Thanks. Peng -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
about log file
Hi everyone, How to change the log file path of a database. I am using Window XP OS. Thanks. Peng
Replication: slaves don't change to new log file properly
Our mysql master machine crashed (hardware problem) and rebooted. When it came back up, it started a new master log file. The slaves, however, were all stuck on the last log file. They still showed both replication threads running, no errors, but they just did not advance. I had to manually run STOP SLAVE; CHANGE MASTER TO ...; START SLAVE on all of them and then they picked up properly. Why didn't the slaves figure out there was a new log file? -jsd- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: a question about "innodb log file"
Hello. Some information you can find here: http://dev.mysql.com/doc/refman/5.0/en/innodb-parameters.html http://dev.mysql.com/doc/refman/5.0/en/innodb-checkpoints.html Have a look to innobase/log/log0log.c file in MySQL source distribution. wangxu wrote: > There are many information about different logs in manual but innodb log file. > > Please tell me where can i find it? > > What's innodb log file different to binlog? > > Where can i find data about redo and undo? > > thanks -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
a question about "innodb log file"
There are many information about different logs in manual but innodb log file. Please tell me where can i find it? What's innodb log file different to binlog? Where can i find data about redo and undo? thanks
Re: Log file full of Got an error reading communication packets
Hi, I too have a server whose log file is full of these errors. This server is also running MySQL 4.0.20. It is on Red Hat Enterprise Linux AS release 3 (Taroon). The errors are: (many thousands of them)... 051004 15:39:34 Aborted connection 349 to db: 'sqllive' user: 'sqllive' host: `localhost' (Got an error reading communication packets) 051004 15:39:56 Aborted connection 134 to db: 'sqllive' user: 'sqllive' host: `localhost' (Got an error reading communication packets) 051004 16:09:25 Aborted connection 351 to db: 'sqllive' user: 'sqllive' host: `localhost' (Got an error reading communication packets) 051004 16:18:19 Aborted connection 339 to db: 'sqllive' user: 'sqllive' host: `localhost' (Got an error reading communication packets) 051004 16:18:20 Aborted connection 325 to db: 'sqllive' user: 'sqllive' host: `localhost' (Got an error reading communication packets) 051004 17:32:06 Aborted connection 367 to db: 'sqllive' user: 'sqllive' host: `localhost' (Got an error reading communication packets) 051004 18:05:41 Aborted connection 662 to db: 'sqllive' user: 'sqllive' host: `localhost' (Got an error reading communication packets) 051004 19:20:55 Aborted connection 61 to db: 'sqllive' user: 'sqllive' host: `localhost' (Got an error reading communication packets) 051004 21:59:03 Aborted connection 246 to db: 'sqllive' user: 'sqllive' host: `localhost' (Got an error reading communication packets) 051004 22:08:19 Aborted connection 317 to db: 'sqllive' user: 'sqllive' host: `localhost' (Got an error reading communication packets) 051004 22:08:34 Aborted connection 314 to db: 'sqllive' user: 'sqllive' host: `localhost' (Got an error reading communication packets) My /etc/my.cnf is: cat /etc/my.cnf [client] port=3306 socket=/tmp/mysql.sock [mysqld] port=3306 socket=/tmp/mysql.sock set-variable = key_buffer_size=16M set-variable = max_allowed_packet=5M datadir=/usr/local/mysql/data [mysqldump] quick Regards, Ian Collins. Randy Paries wrote: Thanks for the reply and the kindly reprimand Info: DB Server Mysql 4.0.20 Mandrakelinux release 10.1 (Official) for i586 - 2.6.8.1-12mdksmp Application Servers Red Hat Linux release 9 Tomcat 5.0.24 These application servers connect to the DB via Tomcat or by perl scripts In my data directory I have a file called millhouse.unitnet.com.err My main db is unitnet It appears this is a good link that I received from GLEB http://dev.mysql.com/doc/mysql/en/communication-errors.html I am going down that path right now Thanks Randy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 21, 2005 8:19 AM To: Randy Paries Cc: mysql@lists.mysql.com Subject: Re: Log file full of Got an error reading communication packets "Randy Paries" <[EMAIL PROTECTED]> wrote on 09/21/2005 08:56:13 AM: Hello, My log file is getting filled with these. Can someone tell me what these mean? Thanks Randy //-snip-// 050122 20:28:00 Aborted connection 53561 to db: 'unitnet' user: 'paries' host: `local.flanders' (Got an error reading communication packets) 050122 20:28:49 Aborted connection 53612 to db: 'unitnet' user: 'paries' host: `local.krusty' (Got an error reading communication packets) 050122 20:29:20 Aborted connection 53671 to db: 'unitnet' user: 'paries' host: `local.flanders' (Got an error reading communication packets) 050122 20:32:14 Aborted connection 53910 to db: 'unitnet' user: 'paries' host: `local.flanders' (Got an error reading communication packets) 050122 20:34:47 Aborted connection 54111 to db: 'unitnet' user: 'paries' host: `local.flanders' (Got an error reading communication packets) 050122 20:34:48 Aborted connection 54116 to db: 'unitnet' user: 'paries' host: `local.flanders' (Got an error reading communication packets) 050122 20:35:11 Aborted connection 54142 to db: 'unitnet' user: 'paries' host: `local.krusty' (Got an error reading communication packets) 050122 20:38:45 Aborted connection 54468 to db: 'unitnet' user: 'paries' host: `local.flanders' (Got an error reading communication packets) 050122 20:39:46 Aborted connection 54572 to db: 'unitnet' user: 'paries' host: `local.krusty' (Got an error reading communication packets) 050122 20:40:54 Aborted connection 54584 to db: 'unitnet' user: 'paries' host: `local.flanders' (Got an error reading communication packets) 050122 20:42:09 Aborted
RE: Log file full of Got an error reading communication packets
Thanks for the reply and the kindly reprimand Info: DB Server Mysql 4.0.20 Mandrakelinux release 10.1 (Official) for i586 - 2.6.8.1-12mdksmp Application Servers Red Hat Linux release 9 Tomcat 5.0.24 These application servers connect to the DB via Tomcat or by perl scripts In my data directory I have a file called millhouse.unitnet.com.err My main db is unitnet It appears this is a good link that I received from GLEB http://dev.mysql.com/doc/mysql/en/communication-errors.html I am going down that path right now Thanks Randy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 21, 2005 8:19 AM To: Randy Paries Cc: mysql@lists.mysql.com Subject: Re: Log file full of Got an error reading communication packets "Randy Paries" <[EMAIL PROTECTED]> wrote on 09/21/2005 08:56:13 AM: > Hello, > My log file is getting filled with these. > Can someone tell me what these mean? > > Thanks > Randy > //-snip-// > 050122 20:28:00 Aborted connection 53561 to db: 'unitnet' user: 'paries' > host: `local.flanders' (Got an error reading communication packets) > 050122 20:28:49 Aborted connection 53612 to db: 'unitnet' user: 'paries' > host: `local.krusty' (Got an error reading communication packets) > 050122 20:29:20 Aborted connection 53671 to db: 'unitnet' user: 'paries' > host: `local.flanders' (Got an error reading communication packets) > 050122 20:32:14 Aborted connection 53910 to db: 'unitnet' user: 'paries' > host: `local.flanders' (Got an error reading communication packets) > 050122 20:34:47 Aborted connection 54111 to db: 'unitnet' user: 'paries' > host: `local.flanders' (Got an error reading communication packets) > 050122 20:34:48 Aborted connection 54116 to db: 'unitnet' user: 'paries' > host: `local.flanders' (Got an error reading communication packets) > 050122 20:35:11 Aborted connection 54142 to db: 'unitnet' user: 'paries' > host: `local.krusty' (Got an error reading communication packets) > 050122 20:38:45 Aborted connection 54468 to db: 'unitnet' user: 'paries' > host: `local.flanders' (Got an error reading communication packets) > 050122 20:39:46 Aborted connection 54572 to db: 'unitnet' user: 'paries' > host: `local.krusty' (Got an error reading communication packets) > 050122 20:40:54 Aborted connection 54584 to db: 'unitnet' user: 'paries' > host: `local.flanders' (Got an error reading communication packets) > 050122 20:42:09 Aborted connection 54794 to db: 'unitnet' user: 'paries' > host: `local.krusty' (Got an error reading communication packets) > 050122 20:43:33 Aborted connection 54936 to db: 'unitnet' user: 'paries' > host: `local.krusty' (Got an error reading communication packets) > 050122 20:44:40 Aborted connection 55004 to db: 'unitnet' user: 'paries' > host: `local.krusty' (Got an error reading communication packets) > > Not unless you can tell us which application is making those log entries and which log file you just quoted. What you just did is a lot like playing a sound over the telphone and asking a painter what's wrong with your plumbing. This may not even be a MySQL problem. Unless we know where those entries are (which log) and where they come from(which app is making them), we can have no clue what they mean. Next time, please provide us with more context to your question, OK? We need to know what OS you are using, what version of MySQL you are using, and many details about what exactly you were doing that created the problem you are trying to get us to help you with. If you can describe the problem even more, please do. Shawn Green Database Administrator Unimin Corporation - Spruce Pine -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Log file full of Got an error reading communication packets
"Randy Paries" <[EMAIL PROTECTED]> wrote on 09/21/2005 08:56:13 AM: > Hello, > My log file is getting filled with these. > Can someone tell me what these mean? > > Thanks > Randy > //-snip-// > 050122 20:28:00 Aborted connection 53561 to db: 'unitnet' user: 'paries' > host: `local.flanders' (Got an error reading communication packets) > 050122 20:28:49 Aborted connection 53612 to db: 'unitnet' user: 'paries' > host: `local.krusty' (Got an error reading communication packets) > 050122 20:29:20 Aborted connection 53671 to db: 'unitnet' user: 'paries' > host: `local.flanders' (Got an error reading communication packets) > 050122 20:32:14 Aborted connection 53910 to db: 'unitnet' user: 'paries' > host: `local.flanders' (Got an error reading communication packets) > 050122 20:34:47 Aborted connection 54111 to db: 'unitnet' user: 'paries' > host: `local.flanders' (Got an error reading communication packets) > 050122 20:34:48 Aborted connection 54116 to db: 'unitnet' user: 'paries' > host: `local.flanders' (Got an error reading communication packets) > 050122 20:35:11 Aborted connection 54142 to db: 'unitnet' user: 'paries' > host: `local.krusty' (Got an error reading communication packets) > 050122 20:38:45 Aborted connection 54468 to db: 'unitnet' user: 'paries' > host: `local.flanders' (Got an error reading communication packets) > 050122 20:39:46 Aborted connection 54572 to db: 'unitnet' user: 'paries' > host: `local.krusty' (Got an error reading communication packets) > 050122 20:40:54 Aborted connection 54584 to db: 'unitnet' user: 'paries' > host: `local.flanders' (Got an error reading communication packets) > 050122 20:42:09 Aborted connection 54794 to db: 'unitnet' user: 'paries' > host: `local.krusty' (Got an error reading communication packets) > 050122 20:43:33 Aborted connection 54936 to db: 'unitnet' user: 'paries' > host: `local.krusty' (Got an error reading communication packets) > 050122 20:44:40 Aborted connection 55004 to db: 'unitnet' user: 'paries' > host: `local.krusty' (Got an error reading communication packets) > > Not unless you can tell us which application is making those log entries and which log file you just quoted. What you just did is a lot like playing a sound over the telphone and asking a painter what's wrong with your plumbing. This may not even be a MySQL problem. Unless we know where those entries are (which log) and where they come from(which app is making them), we can have no clue what they mean. Next time, please provide us with more context to your question, OK? We need to know what OS you are using, what version of MySQL you are using, and many details about what exactly you were doing that created the problem you are trying to get us to help you with. If you can describe the problem even more, please do. Shawn Green Database Administrator Unimin Corporation - Spruce Pine
Log file full of Got an error reading communication packets
Hello, My log file is getting filled with these. Can someone tell me what these mean? Thanks Randy //-snip-// 050122 20:28:00 Aborted connection 53561 to db: 'unitnet' user: 'paries' host: `local.flanders' (Got an error reading communication packets) 050122 20:28:49 Aborted connection 53612 to db: 'unitnet' user: 'paries' host: `local.krusty' (Got an error reading communication packets) 050122 20:29:20 Aborted connection 53671 to db: 'unitnet' user: 'paries' host: `local.flanders' (Got an error reading communication packets) 050122 20:32:14 Aborted connection 53910 to db: 'unitnet' user: 'paries' host: `local.flanders' (Got an error reading communication packets) 050122 20:34:47 Aborted connection 54111 to db: 'unitnet' user: 'paries' host: `local.flanders' (Got an error reading communication packets) 050122 20:34:48 Aborted connection 54116 to db: 'unitnet' user: 'paries' host: `local.flanders' (Got an error reading communication packets) 050122 20:35:11 Aborted connection 54142 to db: 'unitnet' user: 'paries' host: `local.krusty' (Got an error reading communication packets) 050122 20:38:45 Aborted connection 54468 to db: 'unitnet' user: 'paries' host: `local.flanders' (Got an error reading communication packets) 050122 20:39:46 Aborted connection 54572 to db: 'unitnet' user: 'paries' host: `local.krusty' (Got an error reading communication packets) 050122 20:40:54 Aborted connection 54584 to db: 'unitnet' user: 'paries' host: `local.flanders' (Got an error reading communication packets) 050122 20:42:09 Aborted connection 54794 to db: 'unitnet' user: 'paries' host: `local.krusty' (Got an error reading communication packets) 050122 20:43:33 Aborted connection 54936 to db: 'unitnet' user: 'paries' host: `local.krusty' (Got an error reading communication packets) 050122 20:44:40 Aborted connection 55004 to db: 'unitnet' user: 'paries' host: `local.krusty' (Got an error reading communication packets) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: log file
enable the bin log in mysql. It doesn't log "transactions" i.e. what it was, what it became, but the update will be logged prathima rao wrote: hi, how to create a log file of the updates done on the data in visual basic or in mysql for a particular record for example i have a purchase order record in which my junior changes say rate without my knowledge how will i know what has been changed p rao -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
log file
hi, how to create a log file of the updates done on the data in visual basic or in mysql for a particular record for example i have a purchase order record in which my junior changes say rate without my knowledge how will i know what has been changed p rao -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB lchange log file size
Hello. See: http://dev.mysql.com/doc/mysql/en/adding-and-removing.html >Hi, > > our logfile size is not set like: > > >Set the log file size to about 25% of the buffer pool size > > Could we remove the actual log file and set the new or is this > important? > > Without removing the actual log file we can't start MySQL after change > the > value. Rafal Kedziorski <[EMAIL PROTECTED]> wrote: -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
InnoDB lchange log file size
Hi, our logfile size is not set like: Set the log file size to about 25% of the buffer pool size Could we remove the actual log file and set the new or is this important? Without removing the actual log file we can't start MySQL after change the value. Regards, Rafal
creating mysqldump log file
Hi, Is there any way to create a log file for mysqldump just like oracle export log file i.e what tables exported no of rows exported like that Thanks in advance Anil -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Increasing the InnoDB log file size
if mysql shutdowns cleanly. then there is no chance of loosing data. for safe side take compleate database backup. -Original Message- From: Ronan Lucio [mailto:[EMAIL PROTECTED] Sent: Friday, December 10, 2004 11:39 PM To: Anil Doppalapudi; [EMAIL PROTECTED] Subject: Re: Increasing the InnoDB log file size Anil, > First shutdown the mysql cleanly. > > #mysqladmin shutdown > > then drop log files in data directory. > > restart mysql. it will create new log files. Do you know if is there a risk of loosing any data? Thanks, Ronan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Increasing the InnoDB log file size
Anil and Oropeza, > if mysql shutdowns cleanly. then there is no chance of loosing data. for > safe side take compleate database backup. Ok, thank you very much for your help. Ronan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Increasing the InnoDB log file size
Hello, I had the same issue myself, i read the manual and there says that you have to stop mysql, then change the parameter in my.cnf, then i moved to another directory the log file just to be cautious, and then restarted mysql. Everything went right. Best regards Alejandro -Mensaje original- De: Ronan Lucio [mailto:[EMAIL PROTECTED] Enviado el: Viernes, 10 de Diciembre de 2004 11:38 a.m. Para: [EMAIL PROTECTED] Asunto: Increasing the InnoDB log file size Hi, I need to increase the innodeb_log_file_size parameter, but when I set it higher, mysql don´t starts and give the follow erro: 041210 13:27:40 mysqld started InnoDB: Error: log file ./ib_logfile0 is of different size 0 100663296 bytes InnoDB: than specified in the .cnf file 0 134217728 bytes! 041210 13:27:40 [ERROR] Can't init databases 041210 13:27:40 [ERROR] Aborting 041210 13:27:40 [Note] /usr/local/libexec/mysqld: Shutdown complete 041210 13:27:40 mysqld ended Does anybody knows how can I do it? Thanks, Ronan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Increasing the InnoDB log file size
Anil, > First shutdown the mysql cleanly. > > #mysqladmin shutdown > > then drop log files in data directory. > > restart mysql. it will create new log files. Do you know if is there a risk of loosing any data? Thanks, Ronan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Increasing the InnoDB log file size
Hi, First shutdown the mysql cleanly. #mysqladmin shutdown then drop log files in data directory. restart mysql. it will create new log files. Thanks Anil NOC -Original Message- From: Ronan Lucio [mailto:[EMAIL PROTECTED] Sent: Friday, December 10, 2004 11:08 PM To: [EMAIL PROTECTED] Subject: Increasing the InnoDB log file size Hi, I need to increase the innodeb_log_file_size parameter, but when I set it higher, mysql don´t starts and give the follow erro: 041210 13:27:40 mysqld started InnoDB: Error: log file ./ib_logfile0 is of different size 0 100663296 bytes InnoDB: than specified in the .cnf file 0 134217728 bytes! 041210 13:27:40 [ERROR] Can't init databases 041210 13:27:40 [ERROR] Aborting 041210 13:27:40 [Note] /usr/local/libexec/mysqld: Shutdown complete 041210 13:27:40 mysqld ended Does anybody knows how can I do it? Thanks, Ronan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Increasing the InnoDB log file size
Hi, I need to increase the innodeb_log_file_size parameter, but when I set it higher, mysql don´t starts and give the follow erro: 041210 13:27:40 mysqld started InnoDB: Error: log file ./ib_logfile0 is of different size 0 100663296 bytes InnoDB: than specified in the .cnf file 0 134217728 bytes! 041210 13:27:40 [ERROR] Can't init databases 041210 13:27:40 [ERROR] Aborting 041210 13:27:40 [Note] /usr/local/libexec/mysqld: Shutdown complete 041210 13:27:40 mysqld ended Does anybody knows how can I do it? Thanks, Ronan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: relay log file maintenance problem
Bill Thomason wrote: I have a replication server that is running out of disk space because of old relay binary log files. Both it and the master server are version 4.0.20. I have a cron script that maintains a 3 day history of binary log files on the master server. Has someone figured out a way to manage the number relay log files so that someone doesn't have to check a replication server to see if the filesystem for the MySQL data directory hasn't been filled by old relay log files that haven't been accessed for some specified time? Bill: Doublecheck to make sure your SQL thread is running ( SHOW SLAVE STATUS). Relay logs should get deleted as soon as they are processed by the SQL thread. Another potential problem - if you do not change the default config, and leave less than 1 GB for the relay log partition you will have a problem. Either put them on a bigger partition, or set max-relay-log-size to a lower value. -- Sasha Pachev Create online surveys at http://www.surveyz.com/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
relay log file maintenance problem
I have a replication server that is running out of disk space because of old relay binary log files. Both it and the master server are version 4.0.20. I have a cron script that maintains a 3 day history of binary log files on the master server. Has someone figured out a way to manage the number relay log files so that someone doesn't have to check a replication server to see if the filesystem for the MySQL data directory hasn't been filled by old relay log files that haven't been accessed for some specified time? Thanks in advance, -bill -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RV: Innodb log file
Hi, How can i increase the size of the log file and log buffer size? i tried to change it on my.cnf file but it return this error message: InnoDB: Error: log file ./ib_logfile0 is of different size 0 5242880 bytes InnoDB: than specified in the .cnf file 0 67108864 bytes! 041028 0:10:49 Can't init databases 041028 0:10:49 Aborting thanks in advance Alejandro
Re: Innodb log file
Check out this section in the manual on innodb log files. http://dev.mysql.com/doc/mysql/en/Adding_and_removing.html -Eric On Thu, 28 Oct 2004 15:47:27 -0500, Oropeza Querejeta, Alejandro <[EMAIL PROTECTED]> wrote: > Hi, > > How can i increase the size of the log file and log buffer size? > > i tried to change it on my.cnf file but it return this error message: > > InnoDB: Error: log file ./ib_logfile0 is of different size 0 5242880 > bytes > InnoDB: than specified in the .cnf file 0 67108864 bytes! > 041028 0:10:49 Can't init databases > 041028 0:10:49 Aborting > > thanks in advance > > Alejandro > > -- Eric Bergen [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Innodb log file
Hi, How can i increase the size of the log file and log buffer size? i tried to change it on my.cnf file but it return this error message: InnoDB: Error: log file ./ib_logfile0 is of different size 0 5242880 bytes InnoDB: than specified in the .cnf file 0 67108864 bytes! 041028 0:10:49 Can't init databases 041028 0:10:49 Aborting thanks in advance Alejandro
Re: General log file in v3.23.52
Don Dachner <[EMAIL PROTECTED]> wrote: > How do I turn on the General log file in version 3.23.52? Can I put an entry in the > my.cnf file and reboot? Yes, put the "log" entry in my.cnf and restart MySQL. If you are running Red Hat Linux, restart MySQL by running service mysql restart In other case, run mysqladmin -uroot shutdown Then as root: mysqld_safe & -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
General log file in v3.23.52
How do I turn on the General log file in version 3.23.52? Can I put an entry in the my.cnf file and reboot? Thanks, Don
Re: Out-of-control log file
Seriously, can anyone help me out here? I've searched the list and I've searched around the Internet. I've found other people reporting a similar entry into their log files, but no one answered them either. I've read up on a few things, and I have a feeling that this error is related to some threading bug/error, but I'm not quite sure. Another thing to note, is it seems that the slave server is getting simultaneously issued a 'flush tables' for each entry shown below. Here is a part of a status command: Uptime: 1 day 21 hours 36 min 51 sec Threads: 1 Questions: 2739695 Slow queries: 0 Opens: 1 Flush tables: 1358804 Open tables: 1 Queries per second avg: 16.684 Additionally, I've set up one of my other servers as a slave, and I do not have the same problems as this slav. Same version of mysql (untared from the same file even), so I'm sure that the problem is not starting from the master. The only difference between the two slave servers is the OS. The slave that is 'broken' is on Mac OS X 10.3 Server and the one that works is Mac OS X 10.1 Server. On Dec 01, 2003, at 03:42, Chris Waskowich wrote: One of my server is a slave to another. The slave server's host.err file is getting filled with blocks like this: Status information: Current dir: /usr/local/mysql/var/ Running threads: 0 Stack size: 65536 Current locks: lock: 82268c: key_cache status: blocks used:15 not flushed: 0 w_requests: 0 writes: 0 r_requests: 0 reads: 0 handler status: read_key:0 read_next: 0 read_rnd 0 read_first: 0 write: 0 delete 0 update: 0 Table status: Opened tables: 0 Open tables:0 Open files: 4 Open streams: 0 Alarm status: Active alarms: 1 Max used alarms: 1 Next alarm time: 3600 Does anyone know what this stuff is and how I would stop it from being written? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Out-of-control log file
One of my server is a slave to another. The slave server's host.err file is getting filled with blocks like this: Status information: Current dir: /usr/local/mysql/var/ Running threads: 0 Stack size: 65536 Current locks: lock: 82268c: key_cache status: blocks used:15 not flushed: 0 w_requests: 0 writes: 0 r_requests: 0 reads: 0 handler status: read_key:0 read_next: 0 read_rnd 0 read_first: 0 write: 0 delete 0 update: 0 Table status: Opened tables: 0 Open tables:0 Open files: 4 Open streams: 0 Alarm status: Active alarms: 1 Max used alarms: 1 Next alarm time: 3600 Does anyone know what this stuff is and how I would stop it from being written? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Log file format?
Egor Egorov wrote: It's a process id. You can see it in the output of SHOW PROCESSLIST. So, each Id represents a thread, and each thread represents a connection? So an entry like this in the query log: 031029 9:56:43 6 Quit :: would represent a connection returned to the pool through an explicit close or timeout? (in this case "pool" being a DataSource managed by Tomcat) -- Hassan Schroeder - [EMAIL PROTECTED] Webtuitive Design === (+1) 408-938-0567 === http://webtuitive.com dream. code. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Log file format?
Hassan Schroeder <[EMAIL PROTECTED]> wrote: > If this is documented anywhere, I sure can't find it, so -- > > The query log fields are headed: Time, Id, Command, Argument. > > What is 'Id'? It's a process id. You can see it in the output of SHOW PROCESSLIST. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Log file format?
If this is documented anywhere, I sure can't find it, so -- The query log fields are headed: Time, Id, Command, Argument. What is 'Id'? TIA! -- Hassan Schroeder - [EMAIL PROTECTED] Webtuitive Design === (+1) 408-938-0567 === http://webtuitive.com dream. code. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
script archiving log file
To Walt, > > I came across the articles on archiving log file which posted on Wed, >07 Aug 2002. > can i have a copy of the shell script regarding on automatically > archive log file in MySql. I m currently writing a perl script on >archiving log file generated by Snort Sensor? This script is run >back-end automatically. > > Thanx :-) evon > > the following is the article: > Message-ID: <[EMAIL PROTECTED]> > > Date: Wed, 07 Aug 2002 10:06:04 -0400 > > From: walt <[EMAIL PROTECTED]> > > Reply-To: [EMAIL PROTECTED] > > MIME-Version: 1.0 > > To: "Rochester, Dean" <[EMAIL PROTECTED]> > > CC: "MySQL (E-mail) (E-mail)" <[EMAIL PROTECTED]> > > Subject: Re: Archive files in MySql > > Content-Type: text/plain; charset=us-ascii > > Content-Transfer-Encoding: 7bit > > "Rochester, Dean" wrote: > > > Does MySql have archive files of transactions like Oracle does? So >if my > > > database gets hosed between backups I can roll forward the >transaction > > > archives or logs so the database is back to where it was before it >got > > > hosed. > > > > > > Thanks in advance > > > Dean-O > > > > > > >- > > > Before posting, please check: > > > http://www.mysql.com/manual.php (the manual) > > > http://lists.mysql.com/ (the list archive) > > > > > > To request this thread, e-mail <[EMAIL PROTECTED]> > > > To unsubscribe, e-mail [EMAIL PROTECTED]> > > > Trouble unsubscribing? Try: >http://lists.mysql.com/php/unsubscribe.php > > yes and no > > you can set mysql to use logs (see mysql manual for bin-logs), but >there is no > > way to automatically archive them. What we've done is write a shell >script which > > checks the log size every 5 min and if >= 5mb runs "flush logs" which >starts a > > new log file. It then sleeps for 5 seconds and copies the log file >that is >= 5mb > > to 2 different locations so we have redundancy in the logs, then >deletes the old > > log file from the mysql dir. One other note, if your using replication >and your > > slave server is across a WAN, you'll need to check the status of the >replication > > server before you delete the old log file. In other words, make sure >the slave > > server has caught up with the master after switching logs. I can send >you a copy > > of the scripts if you'd like. > > walt > >
Re: Re-establishing nuked log file
On Tue, Sep 02, 2003 at 07:59:07AM -0700, Bruce Ferrell wrote: > flush logs from the mysql command line works And so it does. Thank you. I misunderstood what the Manual said about this command, though I should have tried it first anyway. Jesse Sheidlower -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Re-establishing nuked log file
flush logs from the mysql command line works Jesse Sheidlower wrote: I recently restarted my MySQL server (4.0.10 in this case) with the general query log enabled, to help out with some debugging and optimization issues. After looking at a batch of these, I then deleted the log file directly, with "rm foo.log", assuming that it would be re-generated as soon as the next query came in. It was not. Is there any way to get logging restarted without stopping and restarting the server itself, which is live and which I'd prefer not to interrupt? Thanks. Jesse Sheidlower -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Re-establishing nuked log file
I don't know the answer to your question, but as a side note, I've always found cat'ing /dev/null into a file to be safer if the file may be in use cat /dev/null > foo.log > -Original Message- > From: Jesse Sheidlower [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 02, 2003 10:27 AM > To: [EMAIL PROTECTED] > Subject: Re-establishing nuked log file > > > > I recently restarted my MySQL server (4.0.10 in this case) with > the general query log enabled, to help out with some debugging and > optimization issues. After looking at a batch of these, I then > deleted the log file directly, with "rm foo.log", assuming that it > would be re-generated as soon as the next query came in. It was > not. > > Is there any way to get logging restarted without stopping and > restarting the server itself, which is live and which I'd prefer > not to interrupt? > > Thanks. > > Jesse Sheidlower > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re-establishing nuked log file
I recently restarted my MySQL server (4.0.10 in this case) with the general query log enabled, to help out with some debugging and optimization issues. After looking at a batch of these, I then deleted the log file directly, with "rm foo.log", assuming that it would be re-generated as soon as the next query came in. It was not. Is there any way to get logging restarted without stopping and restarting the server itself, which is live and which I'd prefer not to interrupt? Thanks. Jesse Sheidlower -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
recovery from log file
Hi group, I have two mysql-Innodb server(4.0.13) with replication enabled in that. server A > Server B I have the database dump of server B. In server B, I have enabled the log- bin, log-slave-update in server B. In case of database crash, How can I restore the data from log file. I know that I can restore the major portion from the database dump, but I am asking about the data update after the dump. How can I restore that from log files. thanks -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: where do I find the error log file?
Pushpinder Singh Garcha <[EMAIL PROTECTED]> wrote: > I need to find out why the mysqld is not starting up ? Can someone > please throw some light to the location of this file on a Mac? By default in the MySQL data dir. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
where do I find the error log file?
I need to find out why the mysqld is not starting up ? Can someone please throw some light to the location of this file on a Mac? Thanks in adavnce. --Pushpinder -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
log file question
Hello Mysql Fans ;-); 030613 16:05:54 3 Connect [EMAIL PROTECTED] on 3 Query SHOW VARIABLES 3 Query SET autocommit=1 3 Query SET autocommit=1 030613 16:05:55 3 Query USE `sam_group_by_db` 3 Prepare select '2003-06-13 16:05:54' as PollTime, count(*) as RowCount, count(*) - count(*) as RowCountChange from members I just had a look through our log files and I am not sure what the Prepare request ?? actually states (2nd last line). What is this prepare reuest ? actually doing - f.e as in the above sample ? Any help much appreciated. -- --- Valentin Nils Internet Technology E-Mail: [EMAIL PROTECTED] URL: http://www.knowd.co.jp Personal URL: http://www.knowd.co.jp/staff/nils -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: resize InnoDB's log file
Ha-nyung, - Original Message - From: ""Chung Ha-nyung"" <[EMAIL PROTECTED]> Newsgroups: mailing.database.mysql Sent: Wednesday, January 22, 2003 6:48 AM Subject: resize InnoDB's log file > > Currently I have three InnoDB log files, whose size is 256MB and main > memory is 2GB. > Since I use 1GB of InnoDB buffer pool, I think log files'd better get > bigger to some extent; > possibly 1GB. > You know, only changing the value in my.cnf cause mysqld not to start > due to error. > I'm wondering if deleting log files after mysqld is stopped and > starting mysqld is safe. yes. You can read the procedure from the manual from http://www.innodb.com/ibman.html#Adding_and_removing: " If you want to change the number or the size of your InnoDB log files, you have to shut down MySQL and make sure that it shuts down without errors. Then copy the old log files into a safe place just in case something went wrong in the shutdown and you will need them to recover the database. Delete then the old log files from the log file directory, edit my.cnf, and start MySQL again. InnoDB will tell you at the startup that it is creating new log files. " Note the following IMPORTANT bug fix: http://www.innodb.com/ibman.html#InnoDB_history: " MySQL/InnoDB-3.23.55, January xx, 2003 ... Fixed a bug: if the combined size of InnoDB log files was >= 2 GB in a 32-bit computer, InnoDB would write log in a wrong position. That could make crash recovery and InnoDB Hot Backup to fail in log scan. " This fix is already in 4.0.9. Also note that the recommendation is that the combined log file size should be 50 % of the buffer pool size and always < 4 GB. 3 GB is too much.for a buffer pool of 1 GB. > I tried this and got some look-so-serious error(or warning?) messages > like following: > > 030121 10:18:49 mysqld ended > > 030121 10:27:07 mysqld started > 030121 10:27:11 InnoDB: Log file ./ib_logfile0 did not exist: new to > be created > InnoDB: Setting log file ./ib_logfile0 size to 1024 MB > InnoDB: Database physically writes the file full: wait... > 030121 10:28:05 InnoDB: Log file ./ib_logfile1 did not exist: new to > be created > InnoDB: Setting log file ./ib_logfile1 size to 1024 MB > InnoDB: Database physically writes the file full: wait... > 030121 10:29:02 InnoDB: Log file ./ib_logfile2 did not exist: new to > be created > InnoDB: Setting log file ./ib_logfile2 size to 1024 MB > InnoDB: Database physically writes the file full: wait... > 030121 10:29:58 InnoDB: Database was not shut down normally. > InnoDB: Starting recovery from log files... > InnoDB: Starting log scan based on checkpoint at > InnoDB: log sequence number 0 3205932556 > InnoDB: Doing recovery: scanned up to log sequence number 0 3205932556 > InnoDB: Last MySQL binlog file position 0 13846, file name ./lacrimosa- > bin.003 > 030121 10:29:58 InnoDB: Flushing modified pages from the buffer pool... > 030121 10:29:59 InnoDB: Started > /austin/local/mysql/bin/mysqld: ready for connections These are the normal messages when you resize the log files. InnoDB always does a 'crash recovery' at a startup. In a regular startup these messages are suppresses and you do not see them. > query. sql > > -- > Chung Ha-nyung > Sayclub <http://www.sayclub.com> > NeoWiz <http://www.neowiz.com> Best regards, Heikki Tuuri Innobase Oy --- Order technical MySQL/InnoDB support at https://order.mysql.com/ See http://www.innodb.com for the online manual and latest news on InnoDB - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
resize InnoDB's log file
Currently I have three InnoDB log files, whose size is 256MB and main memory is 2GB. Since I use 1GB of InnoDB buffer pool, I think log files'd better get bigger to some extent; possibly 1GB. You know, only changing the value in my.cnf cause mysqld not to start due to error. I'm wondering if deleting log files after mysqld is stopped and starting mysqld is safe. I tried this and got some look-so-serious error(or warning?) messages like following: 030121 10:18:49 mysqld ended 030121 10:27:07 mysqld started 030121 10:27:11 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 1024 MB InnoDB: Database physically writes the file full: wait... 030121 10:28:05 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 1024 MB InnoDB: Database physically writes the file full: wait... 030121 10:29:02 InnoDB: Log file ./ib_logfile2 did not exist: new to be created InnoDB: Setting log file ./ib_logfile2 size to 1024 MB InnoDB: Database physically writes the file full: wait... 030121 10:29:58 InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 3205932556 InnoDB: Doing recovery: scanned up to log sequence number 0 3205932556 InnoDB: Last MySQL binlog file position 0 13846, file name ./lacrimosa- bin.003 030121 10:29:58 InnoDB: Flushing modified pages from the buffer pool... 030121 10:29:59 InnoDB: Started /austin/local/mysql/bin/mysqld: ready for connections query. sql -- Chung Ha-nyung Sayclub <http://www.sayclub.com> NeoWiz <http://www.neowiz.com> - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Replication Binary Log File Size
In 3.23.x versions of MySQL the actual binary log file sizes stayed fairly consistent. An 'empty' log file for instance on 3.23.53a is 73 bytes. I have a situation where I'm doing a roll-your-own replication from many sites to one central server where the remote sites are on everything from dialup to dedicated T-1's. I can't easily use the 'real' replication and have written some PERL scripts to check every few minutes to see if there is data in a binary replication log file and 'mysqlbinlog' dump out that data, send it up to the web server, and flush that log file. Very consistent and reliable on 3.23.x but I've started using 4.0.4 at a few places and the binary log file sizes aren't consistent. I'm wondering if that is incidental to something or intentional or something I'll never again be able to count on or what? Example: -rw-rw1 mysqlmysql 46 Nov 27 06:00 srv-bin.036 -rw-rw1 mysqlmysql 46 Nov 27 06:30 srv-bin.037 -rw-rw1 mysqlmysql 46 Nov 27 07:00 srv-bin.038 -rw-rw1 mysqlmysql 46 Nov 27 07:30 srv-bin.039 -rw-rw1 mysqlmysql 46 Nov 27 08:00 srv-bin.040 -rw-rw1 mysqlmysql6233 Nov 27 08:30 srv-bin.041 -rw-rw1 mysqlmysql 46 Nov 27 09:00 srv-bin.042 -rw-rw1 mysqlmysql9502 Nov 27 09:30 srv-bin.043 -rw-rw1 mysqlmysql4939 Nov 27 09:35 srv-bin.044 -rw-rw1 mysqlmysql1426 Nov 27 09:30 srv-bin.index The srv-bin.index file contains a list of all the binary log files in sequence. I just 'tail' off the bottom line which points to srv-bin.044 which I then check the file size of. If in this case it's 46 bytes I'll assume it's empty and contains no new inserts, updates or deletes. On a different server this size though is 45 and after doing a "flush master" the file is 79 bytes and at other times it appears to be 4 bytes. Instead of checking file size, is there some other easy mechanism of checking a server to see if there is anything currently logged in the binary log waiting to be replicated? Thanks! - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
re: log file...
antispam, Monday, September 16, 2002, 11:25:31 PM, you wrote: aafdn> my log file (hostname.log) was soo large and i just deleted it(back up) and created a new file called hostname.log but mysql does not stores anything in the log file.. (i did mysqladmin aafdn> log-flush and server stop and start ) does not work.. it is not storing the log.. Start mysqld with --log option: http://www.mysql.com/doc/en/Query_log.html -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Re: InnoDB: Looong pause when log file is full?
Hi Heikki, Thank you for responding. > > > (http://www.innodb.com/ibman.html#InnoDB_tuning), but am getting bit > > > when the log files are full and the buffer pool is checkpointed. > > InnoDB does 'fuzzy checkpoints'. That means modified database pages in the > buffer pool are flushed to disk in small batches. The time when a physical > log file becomes full does not affect this continuous background > checkpointing activity, since InnoDB sees all the log files as one catenated > log file. That's good to know---so that isn't it. > The pauses you experience are probably caused by high load in general, > probably too much disk i/o. You should study your queries, use the InnoDB > Monitor, watch 'top', adjust buffer pool size, spread disk i/o. Respectfully, I don't think that's it. Both times I've seen the database do this it's been in periods of relatively low traffic. Until we switched to InnoDB tables, the only times the database was frozen up like this was when someone did an ill-advised select that took forever and gummed everything up. That's the main reason we switched to InnoDB tables---so a long select wouldn't hold up the db (by an update blocking, which would block subsequent selects). In this case, when the (inno-)db was 'pausing', all of the queries in the (growing) queue looked normal. And there was a lot of free ram. I didn't see anything useful in the InnoDB monitor, but then I'm new to reading it. Then all of a sudden all queries finished and there were no more in the queue and the problem didn't recur for five days. I thought it must be related to the log files, because when I looked at them it looked like one was just finished being written to. (Because its modification time was the previous minute, while the next (zeroth) log file was now the active one.) I know without a repeatable test case, there's not much you can do. If I get more information I'll let you know. It helps to hear that this behavior isn't normal, though. --Pete sql - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: InnoDB: Looong pause when log file is full?
Pete, - Original Message - From: "Jeremy Zawodny" <[EMAIL PROTECTED]> Newsgroups: mailing.database.mysql Sent: Friday, August 02, 2002 2:40 AM Subject: Re: InnoDB: Looong pause when log file is full? > On Thu, Aug 01, 2002 at 04:37:05PM -0500, Pete Harlan wrote: > > Hi, > > > > I've read the performance tuning tips for InnoDB > > (http://www.innodb.com/ibman.html#InnoDB_tuning), but am getting bit > > when the log files are full and the buffer pool is checkpointed. InnoDB does 'fuzzy checkpoints'. That means modified database pages in the buffer pool are flushed to disk in small batches. The time when a physical log file becomes full does not affect this continuous background checkpointing activity, since InnoDB sees all the log files as one catenated log file. The pauses you experience are probably caused by high load in general, probably too much disk i/o. You should study your queries, use the InnoDB Monitor, watch 'top', adjust buffer pool size, spread disk i/o. If the load is CPU-bound and you have many queries running simultaneously, you may experience 'thread thrashing'. Then you can try to set innodb_thread_concurrency lower than the default 8, even to 1. > > By 'geting bit', I mean for several minutes the db server basically > > stops, and our website stops serving pages. Does anyone have advice > > about what we can do to alleviate this? Instead of having three 150mb > > log files, would we be better off with 30 15mb log files? > > It shouldn't matter how many files you have. InnoDB sees them as one > striped file anyway. > > > Our log files are on the same raid array as the data, but would it > > really make that much difference to move them to a separate disk? > > It can if things are I/O bound, and they likely are. > > > Alternately, is there a way to trigger this action at night, so we can > > avoid it happening during the day? It shut us down for about five > > minutes today. > > You could increase the size of your logs. That'll increase recovery > time if there's ever a crash, but it should give InnoDB more breathing > room. > > Jeremy > -- > Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! > <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ > > MySQL 3.23.51: up 63 days, processed 1,335,360,828 queries (241/sec. avg) Best regards, Heikki Tuuri Innobase Oy --- Order technical MySQL/InnoDB support at https://order.mysql.com/ See http://www.innodb.com for the online manual and latest news on InnoDB - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Re: InnoDB: Looong pause when log file is full?
Thanks for your feedback (and your general untiring devotion to the cause...) On Thu, Aug 01, 2002 at 04:30:10PM -0700, Jeremy Zawodny wrote: > > about what we can do to alleviate this? Instead of having three 150mb > > log files, would we be better off with 30 15mb log files? > > It shouldn't matter how many files you have. InnoDB sees them as one > striped file anyway. That's good to know. > You could increase the size of your logs. That'll increase recovery > time if there's ever a crash, but it should give InnoDB more breathing > room. Won't that only make for fewer long pauses, rather than schedule or shorten them? It won't fly with the powers that be if our system shuts down in the middle of the day and my response is "Oh yeah, our server does that every three weeks and there's nothing we can do about it." Someone else suggested setting innodb_flush_log_at_trx_commit to 1, which should make for many frequent flushes rather than one monster occasional flush. Would that not take care of it? (I set it to 0 because the manual suggested that as a big performance improvement at the expense of a small measure of recoverability in the unlikely event of a crash.) [Is there a way to set that variable with 3.23.51 without shutting down the server? I couldn't find a way.] Thanks, --Pete sql,query - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: InnoDB: Looong pause when log file is full?
On Thu, Aug 01, 2002 at 04:37:05PM -0500, Pete Harlan wrote: > Hi, > > I've read the performance tuning tips for InnoDB > (http://www.innodb.com/ibman.html#InnoDB_tuning), but am getting bit > when the log files are full and the buffer pool is checkpointed. > > By 'geting bit', I mean for several minutes the db server basically > stops, and our website stops serving pages. Does anyone have advice > about what we can do to alleviate this? Instead of having three 150mb > log files, would we be better off with 30 15mb log files? It shouldn't matter how many files you have. InnoDB sees them as one striped file anyway. > Our log files are on the same raid array as the data, but would it > really make that much difference to move them to a separate disk? It can if things are I/O bound, and they likely are. > Alternately, is there a way to trigger this action at night, so we can > avoid it happening during the day? It shut us down for about five > minutes today. You could increase the size of your logs. That'll increase recovery time if there's ever a crash, but it should give InnoDB more breathing room. Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ MySQL 3.23.51: up 63 days, processed 1,335,360,828 queries (241/sec. avg) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
InnoDB: Looong pause when log file is full?
Hi, I've read the performance tuning tips for InnoDB (http://www.innodb.com/ibman.html#InnoDB_tuning), but am getting bit when the log files are full and the buffer pool is checkpointed. By 'geting bit', I mean for several minutes the db server basically stops, and our website stops serving pages. Does anyone have advice about what we can do to alleviate this? Instead of having three 150mb log files, would we be better off with 30 15mb log files? Our log files are on the same raid array as the data, but would it really make that much difference to move them to a separate disk? Alternately, is there a way to trigger this action at night, so we can avoid it happening during the day? It shut us down for about five minutes today. Details follow. Many thanks, --Pete Harlan [EMAIL PROTECTED] Possibly relevant details: 1. Binary mysql-max-3.23.51-pc-linux-gnu-i686.tar.gz. 2. Linux 2.4.19-rc3, though has happened with other kernels. Debian woody. 3. Dual Intel 933mhz, 2gb ram, 15krpm scsi raid. Here's the /etc/my.cnf file we use. Except for this pausing, performance is generally great, and we're not disk bound or running out of ram (500mb free (used for caching) while machine is pausing): /etc/my.cnf: [mysqld] log-slow-queries skip-locking innodb_data_home_dir = /usr/local/mysql/data/innodb/data innodb_data_file_path = ibdata1:2000M;ibdata2:2000M;ibdata3:50M:autoextend set-variable = innodb_buffer_pool_size = 1200M set-variable = innodb_additional_mem_pool_size = 20M innodb_log_group_home_dir = /usr/local/mysql/data/innodb/logs innodb_log_arch_dir = /usr/local/mysql/data/innodb/logs innodb_log_archive = 0 set-variable = innodb_log_files_in_group = 3 set-variable = innodb_log_file_size = 150M set-variable = innodb_log_buffer_size = 4M innodb_flush_log_at_trx_commit = 0 set-variable = innodb_file_io_threads = 4 set-variable = innodb_lock_wait_timeout = 50 set-variable = record_buffer = 1M set-variable = sort_buffer = 2M set-variable = key_buffer=150M set-variable = tmp_table_size=4M set-variable = table_cache=500 set-variable = myisam_sort_buffer_size=64M set-variable = thread_cache=8 set-variable = thread_concurrency=4 default-table-type=InnoDB set-variable = long_query_time=5 log-bin server-id=1 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Restoring log file enteries.
Charitha, Thursday, April 04, 2002, 1:35:57 PM, you wrote: C> I am having the mysql log file which is having all the queries which C> affects the data base. C> I have to restore those queries in the table in some remote server. C> Is that possible. Yes, you can update database from update logs using following command: shell> ls -1 -t -r file_name.[0-9]* | xargs cat | mysql You can read about it in the manual: http://www.mysql.com/doc/U/p/Update_log.html C> Any ideas are welcome. C> Thanks in advance -- For technical support contracts, goto https://order.mysql.com/ This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Restoring log file enteries.
On Thu, 4 Apr 2002 16:05:57 +0530 (IST) Charitha <[EMAIL PROTECTED]> wrote: > > > Hello all, > > I am having the mysql log file which is having all the queries which > affects the data base. > I have to restore those queries in the table in some remote server. > Is that possible. YAP !!! ;-) > Any ideas are welcome. > Thanks in advance You can also do MySQL Replication ... to be more real-time ... :D -- How do you power off this machine? -- Linus, when upgrading linux.cs.helsinki.fi, and after using the machine for several months - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Restoring log file enteries.
Hello all, I am having the mysql log file which is having all the queries which affects the data base. I have to restore those queries in the table in some remote server. Is that possible. Any ideas are welcome. Thanks in advance -- Regards, Charitha - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: where are my.cnf anf mysql log file.
I don't know if this will help you but try this: # mysqld --help | grep "dir:" basedir: / datadir: /var/lib/mysql/ tmpdir: /tmp/ So, you'll find mysql log files in your datadir (is this case, /var/lib/mysql/). my.cnf is usually at /etc/my.cnf If you don't have it, find a configuration sample file: # find -name my*.cnf and copy one (which is better for you) to /etc/. Maybe there are better ways to do this... But i think this will do the trick. On Thu, 2002-03-14 at 17:56, Jianping Zhu wrote: > I installed following two files > > MySQL-VERSION.i386.rpm > MySQL-client-VERSION.i386.rpm > > but I can not fild my.cnf and mysql log files. > > Why? > > Thanks > > > Jianping Zhu > Department of Computer Science > Univerity of Georgia > Athens, GA 30602 > Tel 706 5423900 > > > > - > Before posting, please check: >http://www.mysql.com/manual.php (the manual) >http://lists.mysql.com/ (the list archive) > > To request this thread, e-mail <[EMAIL PROTECTED]> > To unsubscribe, e-mail <[EMAIL PROTECTED]> > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > -- dsoares (sql) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
where are my.cnf anf mysql log file.
I installed following two files MySQL-VERSION.i386.rpm MySQL-client-VERSION.i386.rpm but I can not fild my.cnf and mysql log files. Why? Thanks Jianping Zhu Department of Computer Science Univerity of Georgia Athens, GA 30602 Tel 706 5423900 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
where is my binary log file
hi, i have a lamer question: where is my binary log file? i can't find it. i am sure it exists because grows crazy, when i restore a database from dumpfile. i found nothing about binary log in my.cnf. version: mysql 3.23.32-log install path: /usr/local (default) thanx, ati - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Log file size
Kenneth Kopelson wrote: > > Look into the Linux "logrotate" daemon. It allows you to configure what > happens with logs. That would work if the problem I'm looking to solve was predictable - i.e. I have a busy site and I run logrotate three times a day to make sure the logs haven't gotten too big. The problem I'm trying to solve is to avoid someone (either accidentally or intentionally) doing an unexpected DOS on any services that requires space on the log device to function correctly (i.e. kernel accounting, exim, mySQL, etc.) by making mySQL log a tremendous amount of data to its logs through rapid, successive queries. I was wondering if there was a way to have mySQL halt its logging (similar to the way the kernel does) if the log device gets too full or perhaps limit the total log file size. For example, Oracle will rotate a fixed number of redo logs based upon their size so I know what the absolute maximum total size of the logs will ever be and can provide space for them. My main concern here (and maybe I should report this to the bugs list) is that someone could DOS a server running mySQL fairly easily by hammering away at a dynamic Web page. Pete -- http://www.elbnet.com ELB Internet Services, Inc. Web Design, Computer Consulting, Internet Hosting - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Log file size
Look into the Linux "logrotate" daemon. It allows you to configure what happens with logs. At 06:44 AM 6/6/01 -0400, Peter Billson wrote: >I'm running mySQL on Linux and was wondering is there a way to limit the >maximum log file size? > > From time to time I have written a bad script that will query mySQL in >a loop (BTW - mySQL can do *lots* of queries/second!) without me >realizing my mistake until I run out of room on my log partition which >causes all kinds of Bad things to happen. > I don't want to reduce the log detail, because normally my logs are >just fine, just would like to be able to suspend logging when there is >only x% of disk space left. > >Pete >-- >http://www.elbnet.com >ELB Internet Services, Inc. >Web Design, Computer Consulting, Internet Hosting > >- >Before posting, please check: >http://www.mysql.com/manual.php (the manual) >http://lists.mysql.com/ (the list archive) > >To request this thread, e-mail <[EMAIL PROTECTED]> >To unsubscribe, e-mail ><[EMAIL PROTECTED]> >Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Log file size
I'm running mySQL on Linux and was wondering is there a way to limit the maximum log file size? From time to time I have written a bad script that will query mySQL in a loop (BTW - mySQL can do *lots* of queries/second!) without me realizing my mistake until I run out of room on my log partition which causes all kinds of Bad things to happen. I don't want to reduce the log detail, because normally my logs are just fine, just would like to be able to suspend logging when there is only x% of disk space left. Pete -- http://www.elbnet.com ELB Internet Services, Inc. Web Design, Computer Consulting, Internet Hosting - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Log File Reporting
Hi all, I'd like to be able to analyse the log files that my MySQL server produces. Basically, I want to find out how many logins every account is doing, how many queries are being performed against each database (although not necessarily per-table) and how many slow queries each account is doing. All of these figures I want to be able to quantify against a certain time period - for example, a 24-hour period. Does anyone know of any log reporting software that might be able to do the job? Maybe somebody has already written something themselves? Initially I thought of using Analog (which I already use for my web, FTP and RealServer logs), but even that's not customisable to the extent I need. Something like Webalizer would be great (with its graphing), but that too is tailored for web logs. Ideally, it'd be great to get MySQL logging to another MySQL database - which I could then use PHP for to query and generate reports, but that seems slightly silly and a bit overkill... :) Also, I notice that the slow query log doesn't record which database was being queried (I'm using version 3.23.32). Why not? Surely this is an essential bit of info? Regards, Basil Hussain ([EMAIL PROTECTED]) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
