I had a server crash over the weekend and discovered that I don't know
as much about MySQL error logging as I thought. The error logs were
empty because of FLUSH LOGS.
What I learned today is if I specify the log-errors parameter in
/etc/mysql/my.cnf, every time there's a FLUSH LOGS
alert that the slave had
stopped again. This time, it seems like the relay log is definitely
corrupt. I was able to run mysqlbinlog /dev/null on all the master
logs, none are corrupt (including the one it had read up to on the
slave). The relay log on the slave is though - it reports
[EMAIL
, today I was greeted with a nagios alert that the slave had
stopped again. This time, it seems like the relay log is definitely
corrupt. I was able to run mysqlbinlog /dev/null on all the master
logs, none are corrupt (including the one it had read up to on the
slave). The relay log on the slave
. This time, it seems like the relay log is definitely
corrupt. I was able to run mysqlbinlog /dev/null on all the master
logs, none are corrupt (including the one it had read up to on the
slave). The relay log on the slave is though - it reports
[EMAIL PROTECTED] mysql]# mysqlbinlog mysql02-relay
.
Ultimately we had to perform a RESET SLAVE (back up those relay logs
first, just in case) and reset the master log position (see Baron's
CHANGE MASTER TO statements below) to the point where it failed. We
also increased the max allowed packet size on both the master and the
slave, as it seemed like
Hemphill wrote:
I have executed a strategy for backup where I stop a slave and do a
mysqldump with --master-data. Both master and slave are 4.1.20
My assumption was that the log coordinates in the dump file would
provide me with the place to replay the log for a point in time recovery
Hi List,
Anybody knows a tool for viewing mysql server general query log in
linux.
Thanks
Ashok
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Boyd Hemphill wrote:
I have executed a strategy for backup where I stop a slave and do a mysqldump
with --master-data. Both master and slave are 4.1.20
My assumption was that the log coordinates in the dump file would provide me with the place to replay the log for a point in time recovery
I have executed a strategy for backup where I stop a slave and do a mysqldump
with --master-data. Both master and slave are 4.1.20
My assumption was that the log coordinates in the dump file would provide me
with the place to replay the log for a point in time recovery.
What I learned today
Is it possible to log information to the general log file only for a specific
database?
We are currently running MySQL 4.0.15. We are planning on moving to a new
server so and will upgrade MySQL. What is the latest most stable version that
is recommended?
Thanks for any information
I don't think there is any way to lock down the general log to a
single database.. perhaps if you tell us what you are trying to
accomplish, we might be able to propose something..
As of today, 5.0.45 is the recommended install version.
http://dev.mysql.com/downloads/mysql/5.0.html
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
We have general logging enabled on our mysql server via a my.cnf
setting. The log records an entry when the server restarts, but does not
record any queries. Is this a bug? or have I missed something.
In my.cnf
[mysqld]
log=query.log
Contents
, causing binlog index to be reset,
ALL logs deleted and new log file created, thats ok, we have a full backup)
4. Unlock the database
[/Full backup script]
[Incremental backup script actions]
1. Flush logs
2. backup all logs except the last one via compress and transfer
3. purge all
I would like to empty the slow query log without restarting MySQL.
If I simply delete lines, the server will no longer write to the file. I have
tried leaving the header, but still no writes unless I restart MySQL.
I am on RHEL4.
The group and owner of the file are correct:
4 -rw-rw
On 8/7/07, Boyd Hemphill [EMAIL PROTECTED] wrote:
I would like to empty the slow query log without restarting MySQL.
If I simply delete lines, the server will no longer write to the file. I
have tried leaving the header, but still no writes unless I restart MySQL.
I am on RHEL4.
The group
set these options in the option file under the [mysqld] section
log-slow-queries=
log=
log= is the general query log
i am not sure what you mean by the mysql log. if you mean the error
log than that would be
log-error=
if you mean the binary log that would be
log-bin=
if you don't enter
of course you'll need to restart the server after making the changes
to the options file..
On 7/30/07, Christian High [EMAIL PROTECTED] wrote:
set these options in the option file under the [mysqld] section
log-slow-queries=
log=
log= is the general query log
i am not sure what
Hi All,
Please tell my how to activate the general log, mysql log and slow query
log.
Regards,
Krishna
On Wed, Jul 18, 2007 at 06:13:10PM -0400, I wrote:
This afternoon, both slaves stopped at the same place, with the same error:
070718 17:28:00 [ERROR] Error reading packet from server: error reading log
entry ( server_errno=1236)
070718 17:28:00 [ERROR] Got fatal error 1236: 'error reading
MySQL 5.0.27 from RPM, on Redhat EL4.
One master, two slaves, one database. Slaves have been up for 5 days.
This afternoon, both slaves stopped at the same place, with the same error:
070718 17:28:00 [Note] Slave SQL thread initialized, starting replication in
log 'hlgbinlog-oil.15
Hi Alex,
Thank you for the response,
But i took the dump from slave and slave was in sync with master, so should
i still be doing the restore from bin-log 3 from position 311.
regards
anandkl
On 7/8/07, Alex Arul Lurthu [EMAIL PROTECTED] wrote:
On 7/6/07, Ananda Kumar [EMAIL PROTECTED
. The master log file will be
mysql-bin.29 . But your show slave output status doesnt show the
exe_master_log position. You need to use that position for setting up a new
slave of your master.
2. Setup a slave of your slave
To do this use the binglog positions in your mysqldump output.
P.S: Make
that were
dumped out are that of the slave. Now you might do 2 things :
1. Setup a slave of your master
To do this use the binlog positions that you obtained using the
command show slave status on your slave. The master log file will be
mysql-bin.29 . But your show slave output status
status on your slave. The master log file will be
mysql-bin.29 . But your show slave output status doesnt show the
exe_master_log position. You need to use that position for setting up a new
slave of your master.
2. Setup a slave of your slave
To do this use the binglog positions
positions that
were dumped out are that of the slave. Now you might do 2 things :
1. Setup a slave of your master
To do this use the binlog positions that you obtained using the
command show slave status on your slave. The master log file will be
mysql-bin.29 . But your show
On 7/6/07, Ananda Kumar [EMAIL PROTECTED] wrote:
-- CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.03',
MASTER_LOG_POS=311;
As see in the mysqldump is saying to start recovery from bin-log file '
mysql-bin.03' and position=MASTER_LOG_POS=311,
You need to use the positions specified
, it showing as
-- CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.03', MASTER_LOG_POS=311;
But before i started the mysqldump, I did the below on slave db.
show slave status\G
Master_Log_File: mysql-bin.29
Read_Master_Log_Pos: 106683511
Relay_Log_File: relay-log.039071
Relay_Log_Pos: 106683648
Guys,
I would like to know if there is a way to have individual databases
under the same instance or server write to separate binary log
files. The idea is to have multiple binary log file for each
database on the same server. The problem that I experiencing is
sorting through the binary
Hi All,
We are having a very strange problem with two of our slave servers,
here is what is happening
mysql select version();
5.0.30-Debian_1~bpo.1-log
1) we backup our slave every night, and when we do that we stop the slave,
and start a remote mysqldump from the backup machine..
2
On 6/26/07, Brown, Charles [EMAIL PROTECTED] wrote:
The MYSQL general query log does not include timestamp of queries that
it logs because queries are logged many many seconds before they are
executed.
Which version of MySQL are you running? I'm running 5.0.22 on my
desktop, but I'm fairly
The MYSQL general query log does not include timestamp of queries that
it logs because queries are logged many many seconds before they are
executed. Can someone help me associated queries found in the query log
with wall clock? I am trying to get a list of queries that were executed
within
Thanks a bunch for the suggested workaround. This method was exactly
what I was looking for.
Thanks again.
CL
At 01:33 AM 6/20/2007, Ananda Kumar wrote:
One possible way is to spool the contents of bin-log into a file.
mysqlbinlog oca-bin.000554 binlog_sql.sql.
This will give you all
Guys,
I'm attempting to reapply a number of bin-log files in a effort to
restore all changes that was made to a database. I'm performing the
following command, but continue to get a foreign key constraint error
message when doing so. Has anyone ever ran into this issue, and if
so, what
One possible way is to spool the contents of bin-log into a file.
mysqlbinlog oca-bin.000554 binlog_sql.sql.
This will give you all the data present in oca-bin.000554. Then you can set
the
foreign key check to 0 at the session level and then apply the
binlog_sql.sql.
Comment our everything
Hi Michale, all
[EMAIL PROTECTED] wrote:
most likely you just need to redirect STDERR to tee as well so it's not
a mysql problem:
mysql -u -p -f eof 21 | tee ttt.txt
...
assuming it's Bourne or ksh, don't remember what's csh for 21
It is an appended '': prog file
with --flush-logs --master-data=2
- do a bunch of stuff that writes data
- drop the database, and recreate it, flushing the log
- make a copy of the binary log made since the mysqldump
- import the mysqldump I made locally
= now I have all data correctly restored up to that point
Now, I attempt
data
- drop the database, and recreate it, flushing the log
- make a copy of the binary log made since the mysqldump
- import the mysqldump I made locally
= now I have all data correctly restored up to that point
Now, I attempt to restore the binary log and this happens
of stuff that writes data
- drop the database, and recreate it, flushing the log
- make a copy of the binary log made since the mysqldump
- import the mysqldump I made locally
= now I have all data correctly restored up to that point
Now, I attempt to restore the binary log and this happens
Hi All,
I have written a script to connect to mysql and all the command results is
spooled into a file.
But when an error occurs in mysql, it stops at that point and does not
proceed to the next command, also these error command is not written to the
output file.
Can you please tell me what i
: Thu, 26 Apr 2007 8:15 AM
Subject: spool data/log into a file.
Hi All,
I have written a script to connect to mysql and all the command results
is
spooled into a file.
But when an error occurs in mysql, it stops at that point and does not
proceed to the next command, also these error command
engine.
[...]
The errors are due to InnoDB being disabled. As far as I can tell, this
has happened as the InnoDB log file ib_logfile0 is the wrong size. This
took me to the description for adding and removing log files at:
http://dev.mysql.com/doc/refman/5.0/en/adding-and-removing.html
of stuff that writes data
- drop the database, and recreate it, flushing the log
- make a copy of the binary log made since the mysqldump
- import the mysqldump I made locally
= now I have all data correctly restored up to that point
Now, I attempt to restore the binary log and this happens
I'm running MySQL version 5.0.22-community-nt on a Windows 2003 server. I a
noticing A LOT of errors in there like the following:
C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Incorrect information
in file: '.\nfcamp\societies.frm'
This spans multiple databases and tables. I am
.
The server is running Windows Server 2003 and MySQL version
5.0.24a-community-nt installed using the xampp package.
The relevant sections of the MySQL log file are below, after which it
went into a near endless cycle of 'Incorrect information in file:' errors.
The errors are due to InnoDB
, InnoDB has been disabled, which left the data
inaccessible. The database was restored using the most recent backup,
but all tables are now using the MyISAM engine.
[...]
The errors are due to InnoDB being disabled. As far as I can tell, this
has happened as the InnoDB log file ib_logfile0
Hi all,
Just wondering how people are dealing with tables that are used for logging,
ie: insert only tables supporting occasional queries used for audit or event
logs.
These tables will keep growing and there is no need to keep them that large
so what is the best strategy in managing the data
Hi all,
Just wondering how people are dealing with tables that are used for
logging, ie: insert only tables supporting occasional queries used for
audit or event logs.
These tables will keep growing and there is no need to keep them that
large so what is the best strategy in managing the
On 2/6/07, Yong Lee [EMAIL PROTECTED] wrote:
Hi all,
Just wondering how people are dealing with tables that are used for
logging, ie: insert only tables supporting occasional queries used for audit
or event logs.
These tables will keep growing and there is no need to keep them that
large
Hi,
I'm experiencing some sporadic connection refused from mysql-max server.
I'd like to keep track of these events, so is there a way to log on the
server
these 3 items?
- date and time
- ip of the client
- reason of the refusal
Thanks,
Nico
--
Email.it, the professional e-mail, gratis
all,
I have been tasked with upgrading a critical 3.23.55 database to 5.0(.27-ish).
short version is it's never been upgraded because authors have moved on and
nobody's sure of everything that uses it.
I enabled the general log a few days ago and have a good body of data with
which to go code
On 1/25/07, Sid Lane [EMAIL PROTECTED] wrote:
all,
I have been tasked with upgrading a critical 3.23.55 database to 5.0
(.27-ish).
short version is it's never been upgraded because authors have moved on
and
nobody's sure of everything that uses it.
I enabled the general log a few days ago
MySQL5 becomes so slowly when bin log is open.
I used sysbench to test mysql.
MySQL version is mysql-standard-5.0.27-linux-i686-icc-glibc23.tar.gz
OS is RHEL 4.0
my.cnf is :
[mysqld]
#log-bin=icc
max_connections=3000
innodb_log_file_size=50M
max_prepared_stmt_count=32765
#log=Buddha.log
-Original Message-
From: Colin Charles [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 17, 2007 9:08 PM
To: Kristen G. Thorson
Cc: mysql@lists.mysql.com
Subject: Re: Log Warnings Level
Kristen G. Thorson wrote:
Hi!
But all I really get from this reading is 0 turns it off
the documentation
there
is on this?
What kind of additional information are you looking about the --W (or
--log-warnings=N) option?
Thank you for the response.
I was looking for information on how high the level can go - 2? 5? 200?
- and what types of warnings are logged for a given level?
AFAIK
the documentation there
is on this?
What kind of additional information are you looking about the --W (or
--log-warnings=N) option?
I'd pay attention to aborted connections, as MySQL Network's monitoring
service actually does do so
kind regards
--
Colin Charles, Community Engineer
MySQL AB
The manual indicates that you can specify a specific level to control
what types of warnings are logged:
http://dev.mysql.com/doc/refman/5.0/en/server-options.html
(See section on log-warnings.)
But all I really get from this reading is 0 turns it off, 1 prints some
warnings, and 2 prints level
Hello,
Is it possible to extract transactional data from InnoDB log files?
InnoDB kept crashing and trying to insert the same record (replayed
from the log after the crash I assume). I'd like to try and extract
the record from log to reconstruct the query and try to break it again
in case
format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1
[mysql.server]
user=mysql
basedir=/var/lib
[mysqld_safe]
err-log=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
==
But /var/log/mysqld.log doesn't have
(those using the mysqlclient10 compatibility package).
old_passwords=1
[mysql.server]
user=mysql
basedir=/var/lib
[mysqld_safe]
err-log=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
==
But /var/log/mysqld.log doesn't have anything more recent than October
2006. Yesterday, the mysqld
for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1
[mysql.server]
user=mysql
basedir=/var/lib
[mysqld_safe]
err-log=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
==
But /var/log/mysqld.log doesn't have anything more recent
Ratheesh,
if the database otherwise looks ok (no crashes, no corrupt tables), then
the easiest way to fix the wrong log sequence number (lsn) is to
artificially inflate the log sequence number. If your log sequence
number is 4 GB too small, then inserting and deleting 4 GB worth of rows
Thanks,
I have the previous ib_log* files on the app server. And every thing on the cnf
file was perfect. Only the ib_log file's size was a mismatch. Whats the best
work around?
Can I copy the log files of the App server to the DB server and change the
innodb_log_file_size to 256M
from the app server). But when Mysql was
installed the ib_logfile0 ib_logfile1 and ib_logfile2 were created freshly on
the DB serever. Each of these log files were created with 5M size. on the app
server these files were 256M in size (innodb_log_file_size = 256M). On the DB
server
(which were copied from the app server). But when Mysql was
installed the ib_logfile0 ib_logfile1 and ib_logfile2 were created freshly on
the DB serever. Each of these log files were created with 5M size. on the app
server these files were 256M in size (innodb_log_file_size = 256M). On the DB
password.
*
If these kinds of things happen, it might indicate that someone is
trying to break into your server!
I see that this event is written to the general log. Is there a way to
log such an event to the error log?
Amit
--
MySQL General Mailing List
For list
Hi:
I'm going use MySQL to log transactions so that I can report on them
later.
Ex:
CREATE TABLE statistics (
id BIGINT UNSIGNED NOT NULL AUTO_INCREMENT
, user_id BIGINT UNSIGNED
, entity_id INT UNSIGNED
, transaction_type INTEGER(2) UNSIGNED
, datetime_logged
In the last episode (Nov 10), James Tu said:
I'm going use MySQL to log transactions so that I can report on them
later.
Ex:
CREATE TABLE statistics (
id BIGINT UNSIGNED NOT NULL AUTO_INCREMENT
, user_id BIGINT UNSIGNED
, entity_id INT UNSIGNED
, transaction_type
Dear all,
I know that there is a MERGE engine in mysql.
It's great.
I want to know is there a way to make new log tables and new merge table
based on some criteria.
Let me explain more with an example.
I have a log_2004_09_01 table and a MERGE table on it called log.
I want to automatically make
Hi,
The system variable expire_logs_days removes the binary logs automatically
after the given number of days. The default is 0, which means no automatic
removal. Possible removals happen at startup and at binary log rotation.
For transactions, it never causes rotation instead it writes
: Thursday, October 19, 2006 4:00 PM
Subject: Re: bin-log with expire_logs_days
Hi,
The system variable expire_logs_days removes the binary logs
automatically after the given number of days. The default is 0, which
means no automatic removal. Possible removals happen at startup and at
binary log
Thanks Dan.
According to the docs, the BEFORE option was introduced in 4.1.
I just tried the purge with the to option :
PURGE MASTER LOGS TO 'db1-bin.002';
Query OK, 0 rows affected (0.01 sec)
so I think I will just purge a couple log files at a time until I can
get the disk space down
Hi All,
I have a **high traffic** mysql 4.0.18-standard-log server running with
bin-logging enabled.
Right now, this must be using a default setting for expire_log_days. I
do not see this anyway in
show variables or show status
$ echo show variables | sql |grep bin
binlog_cache_size
On 10/18/06, George Law [EMAIL PROTECTED] wrote:
Hi All,
I have a **high traffic** mysql 4.0.18-standard-log server running with
bin-logging enabled.
Right now, this must be using a default setting for expire_log_days. I
do not see this anyway in
show variables or show status
$ echo show
Hi Guys,
Need some pointers. I've got a MySQL server (5.0.22) which is basically
pulling data from SQL Server into a file and then I'm using mysqlimport
to load the data into the DB.
The updates are being generated like every 2 to 5 seconds.
Due to this, my Binary Log files are huge! (and many
Before I do this, I just wanted to check with you all to see if this
is the correct command:
/etc/rc.d/init.d/mysqld restart --log-slow-queries
If so, where exactly will I find the slow query log?
Will the slow query log be turned off by default next time I restart it?
--
MySQL General
Brian Dunning wrote:
Before I do this, I just wanted to check with you all to see if this is
the correct command:
/etc/rc.d/init.d/mysqld restart --log-slow-queries
If so, where exactly will I find the slow query log?
Will the slow query log be turned off by default next time I restart
hi...
i changed the mysql my.cnf to provide log files. i restarted mysql, but i
don't see the log files...
any idea as to what i may have missed. i'm running FC4, mysql 4.1.
the my.cnf is:
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
set-variable = max_connections=1000
set
bruce wrote:
hi...
i changed the mysql my.cnf to provide log files. i restarted mysql, but i
don't see the log files...
any idea as to what i may have missed. i'm running FC4, mysql 4.1.
the my.cnf is:
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
set-variable
bruce wrote:
chris...
hate to tell you.. .but you can have the log files set as i described..
the real issue was due to permission issues on the dir/file for the mysql
lol.. i'm not having much luck answering questions lately ;)
Thanks for letting us know about the fix.
--
MySQL General
I have specified
log-slow-queries
long-query-time=10
in my.cnf and restarted my server. After that I see statements logged
into the slow-log-file.
But it seems that mysql logs too much into that file.
When executing this statement:
mysql show variables like %tx
It is likely you are also logging any queries not using an index (doing
full table scans). Check the configuration variable: log_long_format
Cheers,
Jay
On Tue, 2006-08-15 at 14:45 +0200, Dominik Klein wrote:
I have specified
log-slow-queries
long-query-time=10
in my.cnf and restarted
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
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
:
Hi,
If you relay log is lost try out the this :-
Run the Change Master Position script, See the log output from where did the
replication stopped.
So you can start your replication.
Thanks Regards
Dilipkumar
- Original Message -
From: Kenji HIROHAMA [EMAIL PROTECTED]
To: mysql
Hi,
First reset slave and then change master to script run it.
Thanks Regards
Dilipkumar
- Original Message -
From: Kenji HIROHAMA [EMAIL PROTECTED]
To: Dilipkumar [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com
Sent: Wednesday, August 02, 2006 3:29 PM
Subject: Re: Relay Log Lost
Dear MySQL,
I am getting an unexpected crash in MySQL 5.1.6, with nothing written to
the log.
This happens with InnoDB tables and an Foreign Key error.
Tables are something like:
CREATE TABLE tax (
`type` varchar(8) NOT NULL,
PRIMARY KEY (`type`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
to
the log.
This happens with InnoDB tables and an Foreign Key error.
Tables are something like:
CREATE TABLE tax (
`type` varchar(8) NOT NULL,
PRIMARY KEY (`type`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
CREATE TABLE `service` (
`service_code` varchar(16) NOT NULL default '',
`country_code
[EMAIL PROTECTED]
Cc: mysql@lists.mysql.com
Sent: Wednesday, August 02, 2006 3:29 PM
Subject: Re: Relay Log Lost on Slave
Hi Dilipkumar,
I checked the output of show slave status, and memorize;
RELAY_MASTER_LOG_FILE, and EXEC_MASTER_LOG_POS.
Then,
change master to
master_log_file='xx
Hi,
Under my replication environment, what should I do if I lose the
current relay-log file on slave side?
1. one master and one slave replication is working
2. stop the master and the slave
3. remove the current relay log file manually
4. I can't start replication with start slave command
Hi,
If you relay log is lost try out the this :-
Run the Change Master Position script, See the log output from where did the
replication stopped.
So you can start your replication.
Thanks Regards
Dilipkumar
- Original Message -
From: Kenji HIROHAMA [EMAIL PROTECTED]
To: mysql
My MySQL server (4.0.20, Linux) was running slowly. I checked the slow queries
log, and found many of these during the problem period:
# Time: 060730 20:44:40
# [EMAIL PROTECTED]: xxx []
# Query_time: 68 Lock_time: 0 Rows_sent: 0 Rows_examined: 2
# administrator command: Quit;
# [EMAIL
TK wrote:
My MySQL server (4.0.20, Linux) was running slowly. I checked the slow queries
log, and found many of these during the problem period:
# Time: 060730 20:44:40
# [EMAIL PROTECTED]: xxx []
# Query_time: 68 Lock_time: 0 Rows_sent: 0 Rows_examined: 2
# administrator command: Quit
A
are replicated to slave A, and inserts on master B are replicated to slave
B). However, queries that are run on master A, do *not* make it all the
way to slave B. The queries execute on master B but I have verified that
they are not being written to master B's binary log. Hence, slave B is not
seeing
Hi,
In ur cnf file mention the log file path as
log=/mysql/logs/mysqllog/qry.log .
log-slow-queries=/mysql/logs/mysqllog/slowqry.log
and restart mysql.
Thanks Regards
Dilipkumar
- Original Message -
From: Adam Rosi-Kessel [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Sunday
I'm running MySQL 4.0.23 on a Debian Sarge system.
Often, when I reboot twice in a short time period, MySQL doesn't seem to
shut down gracefully -- it takes a long time for it to come up fully, and
if I reboot before that, I get a lot of log messages. I think it takes
about an hour to come up
one on your own blog!
About page. Here you can learn what the heck a carnival of the vanities is
and how to participate in this one:
http://www.pythian.com/blogs/about-log-buffer/
Log Buffer #1, edited by our very own Dave Edwards:
http://www.pythian.com/blogs/224/log-buffer-1-a-carnival
Hi -
I was wondering if there was a way to have a less verbose --log. All I
want to see is connects, disconnects, and if they're successful or not.
The reason I ask is because this server runs thousands of queries a
minute, and I'd rather not log *all* data for reasons of performance
execute hundreds of thousands of time/day to suddeny
slow log (w/such low Rows_% #s) across multiple MySQL nodes then just as
suddenly stop?
I would like to log the execution time for each query in my MySQL server
.Is there any possible way?
If you are using MySQL to serve an application, then it is advisable to do
the logging through the application scripts. For in most cases, you might
require more information other than time
Saha, Mukul (Cognizant) schrieb:
Hi,
I would like to log the execution time for each query in my MySQL server
.Is there any possible way?
Please not that, the - log-slow-queries option will not suffice for my
requirement.
Thanks Regards
Mukul Saha
Hi,
Well there is no option
301 - 400 of 1127 matches
Mail list logo
