--000feaee5d5ff4ae300485b7fcd7
Content-Type: text/plain; charset=ISO-8859-1
Please help me to understand more about the mysql transaction log (
mysqlbinlog) file and its contents. Will it support only the innodb or all
the storage engine types like MyISAM, InnoDB?
Thanks,
Arsh Paul
--000feaee5d5ff4ae300485b7fcd7--
I think you've got it a little wrong. In MySQL, transaction log is different from bin-log. Transaction logs are used only for Innodb while bin-logs are optional and capture data related to all the storage engines. I believe, you cannot read thru the transaction logs and these logs files (used in cyclic fashion) are only for the purpose of Instance recovery other than providing transaction support. Bin logs, on the other hand are used mainly for two purposes - replication and PTR (point-in-time recovery). A small utility called mysqlbinlog can read through the bin logs and generate SQL file which is very handy if you need to take up PTR or just want to verify any details.
Hope that helps!
Regards,
Nitin
----- Original Message ----
From: Angelina Paul
To: mysql@lists.mysql.com
Sent: Tue, May 4, 2010 3:49:35 AM
Subject: mysql transaction log
Please help me to understand more about the mysql transaction log (
mysqlbinlog) file and its contents. Will it support only the innodb or all
the storage engine types like MyISAM, InnoDB?
Thanks,
Arsh Paul
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org
Any help greatly appreciated.
Our mysql is restarting a LOT!
Here is what is in the log, it doesn't seem to give much help.
--start of log--
InnoDB: Warning: a long semaphore wait:
101203 15:12:40 - mysqld got signal 11;
This could be because you hit a bug. It is also possible that this =
binary
or one of the libraries it was linked against is corrupt, improperly =
built,
or misconfigured. This error can also be caused by malfunctioning =
hardware.
We will try our best to scrape up some info that will hopefully help =
diagnose
the problem, but since we have already crashed, something is definitely =
wrong
and this may fail.
key_buffer_size=3D1073741824
read_buffer_size=3D16773120
max_used_connections=3D601
max_connections=3D600
threads_connected=3D27
It is possible that mysqld could use up to=20
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections =
=3D 20706971 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=3D(nil)
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
frame pointer is NULL, did you compile with
-fomit-frame-pointer? Aborting backtrace!
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
--end of log--
So before you ask if we have 20G of memory we are running this on =
amazons :
High-Memory Quadruple Extra Large Instance 68.4 GB of memory, 26 EC2 =
Compute Units (8 virtual cores with 3.25 EC2 Compute Units each), 1690 =
GB of local instance storage, 64-bit platform
We are using Fedora Core 8, with MySQL 5.0.45.
these mysql packages are installed.
mysql.x86_64 =
5.0.45-6.fc8 =
installed
mysql-libs.x86_64 =
5.0.45-6.fc8 =
installed
mysql-server.x86_64 =
5.0.45-6.fc8 =
installed
It seems odd to me that we get a InnoDB error when this server doesn't =
have a single InnoDB table.
I also did notice the max_used_connections but from the last 20 or so =
restarts only 2 hit 601, others where as low as approx 150.
I'm hopeful that someone has a idea or two.
Basil
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg
------=_20101203151745_98982
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
On Fri, December 3, 2010 14:11, Basil Daoust wrote:
> Any help
greatly appreciated.
>
> Our mysql is restarting a
LOT!
> Here is what is in the log, it doesn't seem to give much
help.
>
> --start of log--
> InnoDB: Warning: a
long semaphore wait:
> 101203 15:12:40 - mysqld got signal 11;
> This could be because you hit a bug. It is also possible that this
binary
> or one of the libraries it was linked against is corrupt,
improperly
> built,
> or misconfigured. This error can
also be caused by malfunctioning
> hardware.
> We will try
our best to scrape up some info that will hopefully help
>
diagnose
> the problem, but since we have already crashed,
something is definitely
> wrong
> and this may fail.
>
> key_buffer_size=1073741824
>
read_buffer_size=16773120
> max_used_connections=601
>
max_connections=600
> threads_connected=27
> It is
possible that mysqld could use up to
> key_buffer_size +
(read_buffer_size + sort_buffer_size)*max_connections =
> 20706971
K
> bytes of memory
> Hope that's ok; if not, decrease
some variables in the equation.
>
> thd=(nil)
>
Attempting backtrace. You can use the following information to find out
> where mysqld died. If you see no messages after this, something
went
> terribly wrong...
> frame pointer is NULL, did you
compile with
> -fomit-frame-pointer? Aborting backtrace!
>
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
> information that should help you find out what is causing the
crash.
> --end of log--
>
> So before you ask if
we have 20G of memory we are running this on amazons
> :
>
High-Memory Quadruple Extra Large Instance 68.4 GB of memory, 26 EC2
> Compute Units (8 virtual cores with 3.25 EC2 Compute Units each),
1690 GB
> of local instance storage, 64-bit platform
>
> We are using Fedora Core 8, with MySQL 5.0.45.
> these
mysql packages are installed.
> mysql.x86_64
> 5.0.45-6.fc8
> installed
> mysql-libs.x86_64
> 5.0.45-6.fc8
> installed
> mysql-server.x86_64
> 5.0.45-6.fc8
>
installed
>
> It seems odd to me that we get a InnoDB
error when this server doesn't
> have a single InnoDB table.
> I also did notice the max_used_connections but from the last 20 or
so
> restarts only 2 hit 601, others where as low as approx
150.
>
> I'm hopeful that someone has a idea or two.
> Basil
You might check your my.cnf file to see if InnoDB engine
is enabled.
SOURCE IP FROM HEADER:
************************************************
*Please block this
account's access to the *
*internet until its cleaned up. We are
basing *
*this on an analysis of the header NOT the FROM*
*address. *
************************************************
------
William R. Mussatto
Systems Engineer
http://www.csz.com
909-920-9154
------=_20101203151745_98982--
In infinite wisdom Basil Daoust
> Any help greatly appreciated.
>
> Our mysql is restarting a LOT!
> Here is what is in the log, it doesn't seem to give much help.
>
Do you have the coredump from this crash? If yes, can you load the core
dump into gdb and run "bt" (backtrace) and see what it produces?
Check this link to see what steps are required
--
Raj Shekhar
-
If there's anything more important than my ego around, I want it
caught and shot now.
-
Read the latest at my blog: "Humor in the bookstore"
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org
--20cf3054a2a51d9a840497f7735d
Content-Type: text/plain; charset=UTF-8
Hi.
Can you show me some of your critical system logs?
David Yeung, In China, Beijing.
My First Blog:http://yueliangdao0608.cublog.cn
My Second Blog:http://yueliangdao0608.blog.51cto.com
My Msn: yueliangdao0608@gmail.com
2010/12/7 Raj Shekhar
> In infinite wisdom Basil Daoust
>
> > Any help greatly appreciated.
> >
> > Our mysql is restarting a LOT!
> > Here is what is in the log, it doesn't seem to give much help.
> >
>
> Do you have the coredump from this crash? If yes, can you load the core
> dump into gdb and run "bt" (backtrace) and see what it produces?
>
> Check this link to see what steps are required
> <
> http://ronaldbradford.com/blog/how-to-crash-mysqld-intention ally-2010-03-05/
> >
>
>
>
> --
> Raj Shekhar
> -
> If there's anything more important than my ego around, I want it
> caught and shot now.
> -
> Read the latest at my blog: "Humor in the bookstore" <
> http://rajshekhar.net/blog/archives/391-Humor-in-the-booksto re.html>
>
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
> http://lists.mysql.com/mysql?unsub=yueliangdao0608@gmail.com
>
>
--20cf3054a2a51d9a840497f7735d--