Hello.
Please, could you explain what does it mean 'Signal 11 without fail'.
Usually after receiving such a signal MySQL crashes. Of course, it
should do this in normal circumstances. What is in the error log? Check
if the problem still exists on official binaries of 5.0.18.
Ian Sales (DBA)
Gleb Paharenko wrote:
Hello.
Please, could you explain what does it mean 'Signal 11 without fail'.
Usually after receiving such a signal MySQL crashes. Of course, it
should do this in normal circumstances. What is in the error log? Check
if the problem still exists on official binaries of
Hello.
Resolve a stack trace and provide it to the list. See:
http://dev.mysql.com/doc/refman/5.0/en/crashing.html
http://dev.mysql.com/doc/refman/5.0/en/using-stack-trace.html
Now about the replication problem. As I've understood you have
triggers only on the slave. In my opinion, to solve
Gleb Paharenko wrote:
Hello.
Resolve a stack trace and provide it to the list. See:
http://dev.mysql.com/doc/refman/5.0/en/crashing.html
http://dev.mysql.com/doc/refman/5.0/en/using-stack-trace.html
- resolving the stack dump gives me this:-
0x8150650 + 135595600
0xe420 + -7136
Hi,
I'm running a 5.0.16 instance on a Debian box (2.6.13 kernel). The
following statement causes a signal 11 without fail, and each time when
mysqld_safe restarts the daemon, no socket file is created:
UPDATE X_Products.product_details AS pd ,
X_Products.tblMaxProductStockDisplay AS sd SET
