1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

XF 1.1 Lock Wait Timeout on InnoDB

Discussion in 'Troubleshooting and Problems' started by Ghan_04, Feb 13, 2012.

  1. Ghan_04

    Ghan_04 Active Member

    So I've taken a default Xenforo install and imported two phpBB 3.0 boards into it. Database size is now about 750 MB.
    Merging the two boards has resulted in about 450 usergroups that we want to clean out. However, when we use the ACP to delete a group, the request hangs and I eventually get:

    I've got the timeout set to 50 seconds. It should not be taking this long on a database of this size. I've checked the InnoDB status and it appears that the transaction running this query hangs waiting for a lock to be released from somewhere. Looks like a deadlock. I'm not really sure where to go. This might be a bug that needs reporting.

    To add some info, I have another Xenforo install running with InnoDB on the same server (though it is smaller) and do not have this issue - I can create a delete usergroups just fine.

    Also, I've tried copying this site over to a completely different server and I still encounter the same issue.

    Any ideas?
     
  2. Brogan

    Brogan XenForo Moderator Staff Member

    That many user groups is going to cause problems with rebuilds when deleting.

    If at all possible, you should try optimising the user groups before importing.
     
  3. Jake Bunce

    Jake Bunce XenForo Moderator Staff Member

    I agree with Brogan. Definitely try to clean that out before importing.

    Long rebuilds are a known design issue when you have lots of nodes / groups.

    If you have root access to the server then you can edit the my.cnf file (usually at /etc/my.cnf) to increase the value of innodb_lock_wait_timeout. Increasing that limit should avoid this error. If you don't have root access then you need to ask your host or server person to do this.
     
  4. Ghan_04

    Ghan_04 Active Member

    This is a VPS that I run myself so I can make any changes I need to. I was more interested in finding out why exactly it was taking so long to do this. At least this seems to be expected behavior, so I at least know that it is not something simple I overlooked. Thanks for the help, guys. :)
     
  5. yavuz

    yavuz Well-Known Member

    I'm getting this error too while deleting an addon:


    I haven't innodb_lock_wait_timeout this in my.conf what should I set this to?
     
  6. Jake Bunce

    Jake Bunce XenForo Moderator Staff Member

Share This Page