Database locked

[laissezfarrell]

brunnhilde-error.txt

Attached is an error I'm getting running Brunnhilde in BitCurator 1.8.12 (VM running in Hyper-V). The Brunnhilde is attempting to write the output files to a CIFS volume. Linux mounts the volume with full read/write/execute permissions, but it seems that Brunnhilde breaks when it attempts to create the SQL db.

Brunnhilde works fine when writing to the VM's virtual storage, so we have a workaround. I'm just wondering if you've seen anything like this before.

Related question: is it possible for the user to disable the SQL DB creation step?

[tw4l]

Hi farrell. From some googling around, it looks like you're not the only person having database locking issues with sqlite3 and cifs/samba shares. Seems that it has something to do with support (or lack thereof) of fcntl() locks. Here's a Chris Adams article about the different types of file locks, which mentions the issue I think you're running into.

Personally, I haven't run into this as an issue yet, even when writing to a samba volume from a dedicated BitCurator machine. But I will keep an eye out now and do some testing.

I'm glad you have a workaround - I'm not quite sure at this point what a real solution might look like, though I'll certainly do some research.

For your last question, no - the sqlite db is pretty crucial to the whole thing working. Without that step there are no reports, so functionally it would basically just be running Siegfried and ClamAV for you.

[laissezfarrell]

hahaha. Well, yes, sounds like the sqlite db is necessary.

Our workaround is fine (drop brunnhilde output on the VM desktop and copy to the share when finished).

[tw4l]

@laissezfarrell 4+ years later, would you like a solution to this issue? It occurs to me now that I could add a flag that would use an in-memory sqlite database, if that's still useful/of interest!

[tw4l]

@laissezfarrell Brunnhilde 1.9.3 now has an --in-memory-db flag which will create and use the database in RAM :)