lruttl warn and error logs

get-help
1

Hello guys,

I’ve updated to the latest de version and I’m seeing some warn and error logs. Along side these, I also have some transients with these kind of messages:
451 4.4.4 failed to resolve queue <campaign>:<tenant>@<redacted>.com: shaping_data lookup for (Some(ConfigEpoch(10)), '[[\'/opt/kumomta/etc/shaping.toml\',\'/opt/kumomta/etc/shaping_automation.toml\',\'http://127.0.0.1:8008/get_config_v1/shaping.toml\'],null]') sema was closed but state is still pending stack traceback: [C]: in local 'poll' [string '?']:4: in main chunk (...tail calls...) /opt/kumomta/share/policy-extras/shaping.lua:510: in function </opt/kumomta/share/policy-extras/shaping.lua:504>
after several transients, it eventually gets delivered.
Any ideas what could be the cause here ?

I’m using this configuration for office365 and they were way more than 5 ready-queues so a lot of them were limited

match=[{MXSuffix=".mail.protection.outlook.com"}]
max_deliveries_per_connection = 50
provider_connection_limit = 5```
[message.txt|attachment](upload://14SDbHxvQw9f29TuAYVleZ2vkQd.txt) (4.11 KB)
4

Can you run validate on your shaping files?

5

here’s the output:

WARNING: domain gmail.com is also matched by provider(s): google
INFO: approx memory used = 928 KiB
OK```
6

That’s one to address but not likely the source.

7

Seeing reports from a customer that a restart stopped the error messages, Wez is looking into it.

8

a restart did stop the error messages, thanks !

9

lruttl: potentially squash sema/eviction errors from logs · KumoCorp/kumomta@5b3d94e · GitHub should resolve this