Forum archive
TKLBAM restore Error 5: Out of memory
I'm trying hard to restore a database with no success. I saw several posts that were similar to this but none that addressed this issue specifically. I've tried to throw more RAM at the problem but it doesn't seem to fix the issue. Anybody seen this problem and have any suggestions?
ERROR 5 (HY000) at line 4546: Out of memory (Needed 3298256 bytes)
Traceback (most recent call last):
File "/usr/bin/tklbam-restore", line 313, in <module>
main()
File "/usr/bin/tklbam-restore", line 301, in main
restore.database()
File "/usr/lib/tklbam/restore.py", line 106, in database
limits=self.limits.db, callback=mysql.cb_print())
File "/usr/lib/tklbam/mysql.py", line 402, in restore
fs2mysql(mysql(), myfs, **kws)
File "/usr/lib/tklbam/mysql.py", line 365, in fs2mysql
MyFS_Reader(myfs, limits, skip_extended_insert, add_drop_database).tofile(fh, callback)
File "/usr/lib/tklbam/mysql.py", line 359, in tofile
database.tofile(fh, callback)
File "/usr/lib/tklbam/mysql.py", line 252, in tofile
table.tofile(fh)
File "/usr/lib/tklbam/mysql.py", line 308, in tofile
fh.write("(%s)" % row)
IOError: [Errno 32] Broken pipe
Replies (4)
TKLBAM gives an error | Bigger than max_allowed_packet
Reply 1The original poster's bug was squashed...
Reply 2Could you provide more information?
Reply 3
==================
v1.2 Release Notes
==================
* Restore
- added embedded squid download cache to make it easier to retry
failed multi-GB restores without resorting to suicide
- fixed root cause of the mysql max packet issue by limiting extended
insert to 1MB chunks
Maybe we should start a new thread where you can describe the problem you are having in more detail? I don't think it's the same problem from 2012.mysqld
Reply 4Is it some mysqld tweaking?
The posting with the same title as the subject of this post is very similar to what I'm experiencing. I'm going to try and manually extract the mysqldump to see if that will get me working again.