#825 Murmur Crash

Murmur (142)
Brenden Blosser

After quite awhile with no one on the server it seems like it crashes after this error: <F>2011-09-10 10:16:09.510 SQL Error [DELETE FROM slog WHERE msgtime < datetime('now','-31 days')]: unable to open database file Unable to fetch row

Server OS: Ubuntu 11.04 Natty Narwhal
Kernel: 2.6.38-8-server


  • Nicos Gollan
    Nicos Gollan

    The partition with the server database is full. You need to make some space, and possibly truncate the server log in the database.

  • The partition the server is on isn't even full:
    Filesystem Size Used Avail Use% Mounted on
    /dev/sda1 228G 6.9G 209G 4% /

    I don't know if it could relate to it with the home directory being encrypted.

  • Nicos Gollan
    Nicos Gollan

    Are you sure that you're looking at the right partition?

    The other possibility would be a corrupt DB.

  • Yes. It's in my /home partition. I just deleted my database...I guess I'll find out if it was corrupted or not.

  • The issue still occurs. It also seems to be not long after "Ending voice thread".

    <W>2011-09-11 22:14:10.888 1 => Ending voice thread
    <F>2011-09-12 14:59:24.511 SQL Error [DELETE FROM slog WHERE msgtime < datetime('now','-31 days')]: unable to open database file Unable to fetch row

  • fwaggle

    The "ending voice thread" is not likely to be related - that's just what happens when the last person disconnects. It's probably actually trying to log something else (the log cleanup stuff happens during a logging event, before the event is logged) but for some reason your sqlite database is breaking.

    When Murmur's DB goes away, for whatever reason, it simply gives up - life can't go on without a working DB (pretty sure that's what the <F> means: "fatal"). The question is what's causing the DB to fail (sqlite is pretty resilient usually, if there's only one thing accessing it which is how Murmur usually acts)?

    You might be able to get substantially more uptime by turning off DB logging (logdays=-1 in the .ini), but that still won't fix the underlying issue.

    What version of sqlite is installed? I highly doubt it's got anything to do with file system encryption unless the encryption layer doesn't support something that sqlite expects.

  • Kissaki

    • status: open --> invalid
    • Version: --> unspecified
  • Kissaki

    Sorry for the long inactivity in this ticket.
    Is this still an issue for you?
    If so, please create a new ticket on our new bug tracker.