{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibertx42ixtseqxur5jdwlg2jb22rrqxkh5wxvyumj7md3gejoyga",
    "uri": "at://did:plc:pvz7ox4x2ehjiezsahttqyyz/app.bsky.feed.post/3mhfm5e3obm22"
  },
  "path": "/viewtopic.php?p=450101#p450101",
  "publishedAt": "2026-03-18T17:24:54.000Z",
  "site": "https://forum.luanti.org",
  "tags": [
    "ref",
    "Blockhead"
  ],
  "textContent": "> The server failed to restart because the previous process didn't release the file lock,\n\nDid you ever figure out what the previous process was? A Lua mod crash is not usually also a crash of the whole server process, but in dedicated server mode it will usually end the process safely. Was the server crashing with the railbuilder-related error before you started this thread?\n\n\n> [*] Code Fix: Patched railbuilder_ui.lua with a nil-check for player positions to prevent the specific crash from recurring.\n\nPlease post the patch so it can be reviewed and, if useful, shared.\n\n\n>\n> The situation was exacerbated by a misconfiguration in minetest.conf: sqlite_synchronous = 1 (NORMAL). On a server with a large 10GB database and heavy mods like AdvTrains, this caused an I/O bottleneck. When the crash happened, the SQLite checkpoint failed, leaving a massive 8.5GB -wal file and locking the database.\n>\n> [*] Config Tuning: Set sqlite_synchronous = 0` and adjusted map_save_interval to 20s to prevent future I/O deadlocks on SATA SSD storage.[/list]\n>\n> Status: Server fully recovered with zero data loss.\n\nref. So now the database is more likely to corrupt in future. It's not a misconfiguration, it's actually a safer configuration. The default is FULL(2), a higher level.\n\nOn a multiplayer server with that size, it's time to think about moving to PostgreSQL since it will perform better.\n\nStatistics: Posted by Blockhead — Wed Mar 18, 2026 17:24\n\n* * *",
  "title": "Problems • Re: Server crashed for problem about DB",
  "updatedAt": "2026-03-18T17:24:54.000Z"
}