MySQL Forums
Forum List  »  Router & Proxy

"gmem.c:175: failed to allocate 32768 bytes" "died on signal=6"
Posted by: Michael Wood
Date: February 15, 2011 06:45AM

I'm trying out MySQL Proxy for substituting some queries for others. Not load balancing etc.

When trying to LOAD DATA LOCAL INFILE... a file with around 2.8m rows in it, I get errors saying that the connection was lost and in the MySQL error log I get:

110214 21:43:11 InnoDB: ERROR: the age of the last checkpoint is 9433887,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
110214 21:52:05 [Warning] Aborted connection 143 to db: 'testdb' user: 'root' host: 'localhost' (Got timeout reading communication packets)
110214 21:54:25 [Warning] Aborted connection 145 to db: 'testdb' user: 'root' host: 'localhost' (Got an error reading communication packets)
110214 22:36:20 InnoDB: ERROR: the age of the last checkpoint is 9435110,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
110214 22:50:28 InnoDB: ERROR: the age of the last checkpoint is 9437410,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
110214 23:37:37 InnoDB: ERROR: the age of the last checkpoint is 9434374,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
110215 3:07:11 [Warning] Aborted connection 150 to db: 'testdb' user: 'root' host: 'localhost' (Got timeout reading communication packets)
110215 3:09:28 [Warning] Aborted connection 149 to db: 'testdb' user: 'root' host: 'localhost' (Got an error reading communication packets)
110215 3:09:28 [Warning] Aborted connection 154 to db: 'testdb' user: 'root' host: 'localhost' (Got an error reading communication packets)
110215 6:43:02 [Warning] Aborted connection 156 to db: 'testdb' user: 'root' host: 'localhost' (Got timeout reading communication packets)

Around the same time in the MySQL proxy log, I get these:

2011-02-14 21:54:16: ((error)) gmem.c:175: failed to allocate 32768 bytes
2011-02-14 21:54:25: (critical) unix-daemon.c:189: [angel] PID=99790 died on signal=6 (it used 0 kBytes max) ... waiting 3
min before restart
2011-02-15 03:09:20: ((error)) gmem.c:175: failed to allocate 32768 bytes
2011-02-15 03:09:28: (critical) unix-daemon.c:189: [angel] PID=98874 died on signal=6 (it used 0 kBytes max) ... waiting 3
min before restart

I have since increased the InnoDB log size, and stopped doing the LOAD DATA via the proxy. It was not my intention to do the LOAD DATA via the proxy, but should this cause a problem? What causes this? Does it mean the proxy could not allocate some memory?

Thanks.

Options: ReplyQuote


Subject
Views
Written By
Posted
"gmem.c:175: failed to allocate 32768 bytes" "died on signal=6"
2853
February 15, 2011 06:45AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.