Panic on startup

[pvonmoradi]

Panic in the main Weechat thread: panicked at 'called `Result::unwrap()` on an `Err` value: MatrixError(StateStore(Sled(Corruption { at: None, bt: () })))', src/server.rs:758:72

Restarting doesn't fix it. Using master build c4d0f1e

[poljar]

This seems to indicate that the DB got corrupted, it's not quite clear why at would be None, this is coming from sled.

We should catch that error and not panic, but the bigger problem is that this happened at all.

What kind of hardware are you running this on? What OS/filesystem?

[pvonmoradi]

What kind of hardware are you running this on? What OS/filesystem?

OS: Ubuntu 18.04.5 LTS x86_64
Kernel: 5.4.0-81-generic
Host: Thinkpad T450s
Toshiba 2.5" HDD

FS is ext4

[poljar]

Nothing really unusual, removing the database under ~/.weechat/matrix-rust/$server-name should get you going again.

Perhaps it would be wise to keep a backup of the DB and report the issue upstream on the Sled github issue tracker.

[pvonmoradi]

Nothing really unusual, removing the database under ~/.weechat/matrix-rust/$server-name should get you going again.

Perhaps it would be wise to keep a backup of the DB and report the issue upstream on the Sled github issue tracker.

Up until recently, I always used /quit to exit weechat but very recently I just use a keybinding to close the parent terminal (Alacritty). Maybe this has something to do with it?

[pvonmoradi]

By the way, db is 357M which is very unusual for texts...

[poljar]

Possibly, depending on which signal Alacritty sends out, though I would have expected Sled to handle getting killed without getting corrupted, SQLite certainly handles this.

[aiobofh]

I noticed this too today...

Note: I'm running my own home-server (conduit.rs)

Reproduce like this: Be logged in with plugin. Use another client (in my case Element on desktop), join a federated room. In my case I joined the FOSDEM room on matrix.org.

Suddenly weechat start to hog around 50% constant, and disk accesses of 500kB/s.... for infinite time. Until disk is full. :(

Sadly... unloading and loading the plugin again still is stuck in the same state. Had to remove the matrix-rust folder and re-set-up everything. I kept the .conf-file but removed the folder. Then all joined rooms appear as normal and CPU usage is low again.

[aiobofh]

Addendum: unloading the plugin, and then removing the matrix-rust-sdk folder in .weechat/matrix-rust//, then load the plugin again also did the trick, (as a temporary work-around)