Error on delete

  • Affected App
    WoltLab Suite Filebase

    98% of the time such things are caused by internal server issues. However, 2% of the time its an underlying issue with code. The fact that I get this instantly (less than 1 second) makes me suspect code. This happens anytime you move an item to the trash or attempt to delete. Trash completes, but delete does not.




    edit: Above is what was displayed in an overlay. Below is the full error log in AdminCP.




    Edited once, last by Aslan ().

  • The other error I found was this. Against, it happens instantly (less than 1 second).


    I am of course investigating the host and will follow up. But as it only happens on delete and it happens instantly... It could be either or.


  • It's not always cut and dry like that. 98 or 99% of the time it is hosting issue, but there is that 1 or 2% margin of error when it could be code.

    General error: 2006 MySQL server has gone aw
    Ask your hoster...

    vBulletin 5 is good example of code gone wrong.


    In this case concerning WBB, the only thing I did was update. Before that all was working.


    (I am of course checking with the host and will follow up)

  • It isn't a MariaDB database server, is it? Because MariaDB seems to causes many strange "DB crashs".

    It is a MariaDB Server, but I've never had any issue with MariaDB.


    That said... My host and I came to the conclusion that the issue appears to be WoltLab with MariaDB 10.0.21


    MySQL Problem


    I would think is more of a WoltLab issue as it does not affect Ip.Board, XenForo, vBulletin, phpBB, SMF, FluxBB, or any other forum software free or paid that I have encountered.

  • It's a problem with the innoDB solution offered by mariadb...
    The other softwares using MyISAM and this isn't affected by those random crashs.

  • It's a problem with the innoDB solution offered by mariadb...
    The other softwares using MyISAM and this isn't affected by those random crashs.


    Incorrect. The other software is using InnoDB.


    Both Ip.Board and XenForo for example use InnoDB exclusively as does WoltLab. The issue is only with WoltLab.

  • Interesting, but do they use foreignkeys with ondelete cascade ?
    As far as i know they all run on both, myisam and innodb so i think they are not exclusivly optimized for innodb only like wbb

  • Interesting, but do they use foreignkeys with ondelete cascade ?
    As far as i know they all run on both, myisam and innodb so i think they are not exclusivly optimized for innodb only like wbb

    (By excluse I meant by default)


    The only MyIsam tables are their search tables, everything else is InnoDB... which is the same with WoltLab.


    Upon a fresh install of either IP.Board, XenForo, or WoltLab you will end up with all your tables in InnoDB format. Only WoltLab is having this issue with MariaDB.

  • Are you self hosting the forum?


    Thought you changed to shared hosting so why are you using MariaDB

    Shared host is using MariaDB. Even if I moved to a VPS or Dedicated, I too would be using MariaDB.


    All of which is irrlevent to the problem.

  • Well the thing is its a bug with the version 10.0.21 of mariadb, using version 10.0.20 will solve your problems (which isn't possible by using a shared hosting, i know).
    And i just think it has to do something with the foreign keys used by wbb to clean up all data when deleting anything within the software. I also thought that xenforo doesn't use those foreign keys with on delete cascade, but last time i'll checkt a xenforo db was with version 1.2 so maybe they have changed it...

  • The issue came with MariaDB 10.0.21 and is a bug in that version, downgrading to 10.0.20 fixes it while you wait for the next update.

    The error is exclusive to WoltLab and downgrading is not possible.


    Talking to MariaDB Development...


    Quote

    have them check their code before pointing fingers

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!