Panic during spool enumeration on the latest dev build

get-help
1

I’m getting a panic when starting the latest dev build on ubuntu 22.04 (I think it has something to do with spool enumeration?):

root@send:/opt/kumomta/sbin# ./kumod --version
kumod 2024.10.15-9cae055a
root@send:/opt/kumomta/sbin# ./kumod --validate --user kumod
Issues found in the combined set of shaping files:
 - /opt/kumomta/share/policy-extras/shaping.toml
 - /opt/kumomta/etc/policy/config/shaping.toml
 - /opt/kumomta/etc/policy/config/shaping-custom.toml
 - http://127.0.0.1:8008/get_config_v1/shaping.toml
WARNING: Ignoring http://127.0.0.1:8008/get_config_v1/shaping.toml because skip_remote is set to true
WARNING: multiple domain blocks alias to the same site: (mx1|mx2)?.(mxge|mx1a1|mx1c1|mx1h1|mx2a1|mx2c1|mx2h1).comcast.net: comcast.net, comcast.net
WARNING: multiple domain blocks alias to the same site: (mx00|mx01).mail.com: mail.com, mail.com
WARNING: multiple domain blocks alias to the same site: smtp-in.orange.fr: orange.fr, orange.fr
WARNING: domain outlook.com is also matched by provider(s): outlook
WARNING: domain zeema.fund is also matched by provider(s): google
WARNING: domain gmail.com is also matched by provider(s): google
WARNING: domain live.com is also matched by provider(s): outlook
WARNING: domain yahoo.com is also matched by provider(s): yahoo

Output from journalctl -u kumomta:

3

Downgraded to kumod 2024.09.02-c5476b89 and the panic went away.

4

hmm, this is the panic message:

Oct 16 21:24:30 send kumod[1474917]: thread 'smtpsrv-0' panicked at crates/spool/src/lib.rs:59:16:
Oct 16 21:24:30 send kumod[1474917]: set_meta_spool has not been called
Oct 16 21:24:30 send kumod[1474917]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

so it sounds like the spool hasn’t been configured. In your init.lua, are you starting the listener before the spool is configured? If so, try swapping them around so that the spool is configured first.

This is an unintended consequence of making the reception no longer block on the completion of the spool setup

5

startup: partially restore waiting for spool startup · KumoCorp/kumomta@6359820 · GitHub should resolve this

6

Yes, the spool was defined after starting the listeners, but I can confirm that the last commit has fixed the issue so that it works without changing the order of listener / spool definitions in init.lua. Thanks!