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

XF 1.5 Continue Import SQL Errors

Discussion in 'Installation, Upgrade, and Import Support' started by thenashy, Oct 13, 2016.

  1. thenashy

    thenashy Member

    Just wondering how I get around this when I'm trying to continue an import that I started last night.

    Anyway around it?

    Server Error
    Mysqli statement execute error : Lock wait timeout exceeded; try restarting transaction
    Zend_Db_Statement_Mysqli->_execute() in Zend/Db/Statement.php at line 297
    Zend_Db_Statement->execute() in Zend/Db/Adapter/Abstract.php at line 479
    Zend_Db_Adapter_Abstract->query() in XenForo/Model/Import.php at line 1675
    XenForo_Model_Import->importTag() in XenForo/Importer/vBulletin4x.php at line 273
    XenForo_Importer_vBulletin4x->stepContentTags() in XenForo/Importer/Abstract.php at line 124
    XenForo_Importer_Abstract->runStep() in XenForo/ControllerAdmin/Import.php at line 189
    XenForo_ControllerAdmin_Import->_runStep() in XenForo/ControllerAdmin/Import.php at line 137
    XenForo_ControllerAdmin_Import->actionImport() in XenForo/FrontController.php at line 351
    XenForo_FrontController->dispatch() in XenForo/FrontController.php at line 134
    XenForo_FrontController->run() in /home/broncos/public_html/xen/admin.php at line 13
  2. Slavik

    Slavik XenForo Moderator Staff Member

    Getting a lock wait timeout on import would suggest a more serious problem that needs to be investigated with regards to the MySQL server and potentially some stuck queries.

    You can run SHOW ENGINE INNODB STATUS\G to see whats going on.
  3. thenashy

    thenashy Member

    Bugger. I might forward this straight to the guy that manages my server.
  4. thenashy

    thenashy Member

    My tech has taken a look and can find nothing problematic on that side of things.

    A brand new install tonight, and I'm stuck at the same point trying to import tags.

    I ran the above command, but it's all gibberish to me.

    *************************** 1. row ***************************
      Type: InnoDB
    161014 23:45:18 INNODB MONITOR OUTPUT
    Per second averages calculated from the last 28 seconds
    srv_master_thread loops: 26251 1_second, 26249 sleeps, 2397 10_second, 2338 background, 2338 flush
    srv_master_thread log flush and writes: 26368
    OS WAIT ARRAY INFO: reservation count 21468, signal count 69108
    Mutex spin waits 142870, rounds 868562, OS waits 10634
    RW-shared spins 24682, rounds 383671, OS waits 6298
    RW-excl spins 6314, rounds 259378, OS waits 4091
    Spin rounds per wait: 6.08 mutex, 15.54 RW-shared, 41.08 RW-excl
    Trx id counter 1E3E2D1
    Purge done for trx's n:o < 1E3E284 undo n:o < 0
    History list length 665
    ---TRANSACTION 0, not started
    MySQL thread id 68964, OS thread handle 0x7fead6d06700, query id 21512398 localhost root
    ---TRANSACTION 1E3E280, ACTIVE 100 sec
    34 lock struct(s), heap size 6960, 407 row lock(s), undo log entries 95399
    MySQL thread id 69268, OS thread handle 0x7fead923b700, query id 21512397 localhost broncos_xen2
    Trx read view will not see trx with id >= 1E3E281, sees < 1E3E281
    FILE I/O
    I/O thread 0 state: waiting for completed aio requests (insert buffer thread)
    I/O thread 1 state: waiting for completed aio requests (log thread)
    I/O thread 2 state: waiting for completed aio requests (read thread)
    I/O thread 3 state: waiting for completed aio requests (read thread)
    I/O thread 4 state: waiting for completed aio requests (read thread)
    I/O thread 5 state: waiting for completed aio requests (read thread)
    I/O thread 6 state: waiting for completed aio requests (write thread)
    I/O thread 7 state: waiting for completed aio requests (write thread)
    I/O thread 8 state: waiting for completed aio requests (write thread)
    I/O thread 9 state: waiting for completed aio requests (write thread)
    Pending normal aio reads: 0 [0, 0, 0, 0] , aio writes: 0 [0, 0, 0, 0] ,
     ibuf aio reads: 0, log i/o's: 0, sync i/o's: 0
    Pending flushes (fsync) log: 0; buffer pool: 0
    263284 OS file reads, 424241 OS file writes, 57707 OS fsyncs
    46.39 reads/s, 16384 avg bytes/read, 10.07 writes/s, 3.89 fsyncs/s
    Ibuf: size 1, free list len 6150, seg size 6152, 7395 merges
    merged operations:
     insert 62242, delete mark 2082833, delete 87967
    discarded operations:
     insert 0, delete mark 0, delete 0
    Hash table size 276707, node heap has 63 buffer(s)
    300444.38 hash searches/s, 5653.19 non-hash searches/s
    Log sequence number 12365288622
    Log flushed up to   12365133424
    Last checkpoint at  12362220502
    0 pending log writes, 0 pending chkp writes
    26504 log i/o's done, 1.50 log i/o's/second
    Total memory allocated 137363456; in additional pool allocated 0
    Dictionary memory allocated 6393817
    Buffer pool size   8192
    Free buffers       1
    Database pages     8128
    Old database pages 2980
    Modified db pages  149
    Pending reads 0
    Pending writes: LRU 0, flush list 0, single page 0
    Pages made young 524687, not young 0
    206.46 youngs/s, 0.00 non-youngs/s
    Pages read 262539, created 66264, written 383340
    46.39 reads/s, 4.14 creates/s, 7.43 writes/s
    Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000
    Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
    LRU len: 8128, unzip_LRU len: 0
    I/O sum[2040]:cur[0], unzip sum[0]:cur[0]
    0 queries inside InnoDB, 0 queries in queue
    2 read views open inside InnoDB
    Main thread process no. 22442, id 140646637958912, state: sleeping
    Number of rows inserted 2402858, updated 2417191, deleted 619600, read 1089595243
    21.50 inserts/s, 699.08 updates/s, 0.00 deletes/s, 303949.97 reads/s
  5. thenashy

    thenashy Member

    At the moment it seems to be working. It's extremely slow.
  6. thenashy

    thenashy Member

    It failed again with the same errors.

    So what do I do from here? Can I somehow force this to skip the tags? This is a massive spanner in our plans.

Share This Page