https://bugs.openldap.org/show_bug.cgi?id=9378
--- Comment #18 from Howard Chu <[email protected]> --- We've expanded the logging to include PIDs so we can more definitively show what's happening. But the problem remains: >514137:mdb_put: 0x558dac27e200, 3, 3[706572], 19480, 0 >514137:mdb_put: 0x558dac27e200, 2, 4[6d6f6e6f], 720, 0 >514137:mdb_put: 0x558dac27e200, 3, 4[6d6f6e6f], 1367, 0 >514137:mdb_put: 0x558dac27e200, 2, 5[4d74657874], 1482864, 0 >514137:mdb_put: 0x558dac27e200, 3, 5[4d74657874], 1853580, 0 >594170:mdb_env_create: 0x556435b8bdc0 >594170:mdb_env_set_maxdbs: 0x556435b8bdc0, 12 >594170:mdb_env_set_mapsize: 0x556435b8bdc0, 274877906944 >594170:mdb_env_open: 0x556435b8bdc0, /home/vm/.local/share/baloo/index, >16793600, 0664 >594170:mdb_txn_begin: 0x556435b8bdc0, (nil), 0 = 0x556435b8d1c0 >594170:mdb_dbi_open: 0x556435b8d1c0, postingdb, 262144 = 2 >594170:mdb_dbi_open: 0x556435b8d1c0, positiondb, 262144 = 3 >594170:mdb_dbi_open: 0x556435b8d1c0, docterms, 262152 = 4 >594170:mdb_dbi_open: 0x556435b8d1c0, docfilenameterms, 262152 = 5 >594170:mdb_dbi_open: 0x556435b8d1c0, docxatrrterms, 262152 = 6 >594170:mdb_dbi_open: 0x556435b8d1c0, idtree, 262152 = 7 >594170:mdb_dbi_open: 0x556435b8d1c0, idfilename, 262152 = 8 >594170:mdb_dbi_open: 0x556435b8d1c0, documenttimedb, 262152 = 9 >594170:mdb_dbi_open: 0x556435b8d1c0, documentdatadb, 262152 = 10 >594170:mdb_dbi_open: 0x556435b8d1c0, indexingleveldb, 262152 = 11 >594170:mdb_dbi_open: 0x556435b8d1c0, failediddb, 262152 = 12 >594170:mdb_dbi_open: 0x556435b8d1c0, mtimedb, 262204 = 13 >594170:mdb_txn_commit: 0x556435b8d1c0 >514137:mdb_put: 0x558dac27e200, 2, 4[64696167], 760, 0 >514137:mdb_put: 0x558dac27e200, 3, 4[64696167], 23186, 0 >514137:mdb_put: 0x558dac27e200, 2, 6[646576696365], 15944, 0 >514137:mdb_put: 0x558dac27e200, 3, 6[646576696365], 31281, 0 Process 514137 has an active write transaction, but process 594170 successfully opens a new write transaction. That can only happen if LMDB's write mutex has been removed out from under it. Things like this imply that that's exactly what is happening https://github.com/KDE/baloo/blob/6f480871cbae83e5f3d02380df40bee73acb820f/src/file/main.cpp#L56 -- You are receiving this mail because: You are on the CC list for the issue.
