KumoMTA Frozen Error

KumoMTA Troubleshooting
1 
Dec 03 21:57:17 mta3 kumod[3268]:         [string "/opt/kumomta/etc/policy/init.lua"]:107: in function <[string "/opt/kumomta/etc/policy/init.lua"]:104>. Ignoring message until kumod is restarted.
Dec 03 21:57:17 mta3 kumod[3268]: 2025-12-03T21:57:17.350399Z ERROR          spoolin-1 kumod::spool: failed to resolve queue email_specter.log_hook: runtime error: [string "/opt/kumomta/etc/policy/init.lua"]:107: attempt to concatenate a nil value (local 'zoneId')
Dec 03 21:57:17 mta3 kumod[3268]: stack traceback:

Looks like it is not sending any emails, just printing that message.

3

Dec 03 22:03:58 mta3 kumod[4249]: 2025-12-03T22:03:58.085546Z ERROR spoolin-0 kumod::spool: failed to resolve queue email_specter.log_hook: resolving egress pool ‘pool-unknown’: deserialize error: invalid type: nil, expected table, while processing null

How do I delete this queue all together?

4

Dec 03 22:22:05 mta3 kumod[7989]: 2025-12-03T22:22:05.876134Z ERROR disk-space-monitor kumo_server_common::disk_space: meta spool path /var/spool/kumomta/meta has issue(s): 0% inodes available but minimum is 10%
Dec 03 22:22:05 mta3 kumod[7989]: 2025-12-03T22:22:05.876179Z ERROR disk-space-monitor kumo_server_common::disk_space: log dir /var/log/kumomta path /var/log/kumomta has issue(s): 0% inodes available but minimum is 10%

5

yikesss

6

No spools have been defined

7

welp

8

Ooof.

9

aha, might need to create that directory

10

Directory? You’re out of inodes, fix that first.

11

hmm, created a new directory, didn’t help

12

yeah, im clearing up stuff in the meantime

13

had to fix the permission

14

its back up that’s nice

15

Any ideas what this refers to?

Dec 03 20:19:03 mta3 kumod[1704917]: 2025-12-03T20:19:03.450274Z ERROR          logging-0 kumod::logging::hooks: failed to log: expected user@domain
Dec 03 20:19:03 mta3 kumod[1704917]: 2025-12-03T20:19:03.450373Z ERROR          logging-0 kumod::logging::hooks: failed to log: expected user@domain
Dec 03 20:19:03 mta3 kumod[1704917]: 2025-12-03T20:19:03.450421Z ERROR          logging-0 kumod::logging::hooks: failed to log: expected user@domain
Dec 03 20:19:03 mta3 kumod[1704917]: 2025-12-03T20:19:03.450436Z ERROR          logging-0 kumod::logging::hooks: failed to log: expected user@domain
Dec 03 20:19:03 mta3 kumod[1704917]: 2025-12-03T20:19:03.450452Z ERROR          logging-0 kumod::logging::hooks: failed to log: expected user@domain
Dec 03 20:19:03 mta3 kumod[1704917]: 2025-12-03T20:19:03.450489Z ERROR          logging-0 kumod::logging::hooks: failed to log: expected user@domain
Dec 03 20:19:03 mta3 kumod[1704917]: 2025-12-03T20:19:03.450854Z ERROR          logging-0 kumod::logging::hooks: failed to log: expected user@domain
Dec 03 20:19:03 mta3 kumod[1704917]: 2025-12-03T20:19:03.450927Z ERROR          logging-0 kumod::logging::hooks: failed to log: expected user@domain
Dec 03 20:19:03 mta3 kumod[1704917]: 2025-12-03T20:19:03.450983Z ERROR          logging-0 kumod::logging::hooks: failed to log: expected user@domain
Dec 03 20:19:03 mta3 kumod[1704917]: 2025-12-03T20:19:03.451086Z ERROR          logging-0 kumod::logging::hooks: failed to log: expected user@domain
16

image.png
image.png855×434 10.2 KB

17

I don’t know why it kept printing that again and again

18

if you see expected user@domain it’s most likely a bug that was present in the main branch for a little bit and you need to upgrade to a newer version of kumomta.

19

Oof. Any ideas what could have gone wrong though?

20

Our KumoMTA legit exhausted all the space in the server and then refused to process anything

21

it’s most likely a failure to load metadata during logging