Wednesday, March 12, 2014

Myloader: resolving errors with no clear message

If you have a special configuration in mysqld (no default config) perhaps you will find these two cases of error working with myloader tool:

1) The first issue looks like a problem with the backup file...... but it is not. Message:
** (myloader:42526): CRITICAL **: cannot open file vcadminweb.message.sql.gz (24) * (myloader:46190): CRITICAL
In my case, I needed to check and to change the open files:
ulimit -n 10000        ..... and solved!
2) The second one looks like a problem accessing to the database.... but it is not. Message:
**: Error switching to database CMSB076 whilst restoring table multidevicevideo_players
In my case, it was a timewait very low in the mysqld config.
wait_timeout       = 300 
solved the issue for me.

5 comments:

  1. Thanks for this post! I was getting the "Error switching to database" error, the wait_timeout fix worked for me too

    ReplyDelete
    Replies
    1. Hey Paul... i am happy for you. It's great. Finally this post was useful for someone.... hehehe!

      Delete
  2. Good day,

    I was wondering if you could help me with the following error message:

    (myloader:15722): GLib-ERROR **: /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmem.c:165: failed to allocate 1073741824 bytes

    I get this every time I do a restore of the database and then MySQL rolls back the information updated and myloader loses connection to the server.

    ReplyDelete
    Replies
    1. I was only the packager. Currently I am not using it ever. It seems something like a memory limit. Did you check it loading only one table?

      Delete
    2. It does it with two different table, both containing binary data in the tables.

      Restoring it on the server it was backed up on works fine. I transfer the data to another AWS instance and restore there for a testing platform and then it bombs out with the restore.

      Both servers are running Ubuntu (14.04 and 16.04) for production and test, respectively. I have checked in top at the time it failed and the server did have sufficient memory available at the time it failed.

      Delete