Error in Spool

I have set up KumoMTA on Alma Linux 8.

I ran this command:

KUMOD_LOG=kumod=info /opt/kumomta/sbin/kumod --policy /opt/kumomta/etc/policy/init.lua --user kumod&

and got this

2024-04-21T12:42:52.756527Z ERROR localset-0 kumod::spool: Error in spool: Opening spool data: IO error: While lock file: /var/spool/kumomta/data/LOCK: Resource temporarily unavailable
2024-04-21T12:42:52.758005Z ERROR localset-0 kumod::spool: Error in spool: Opening spool meta: IO error: While lock file: /var/spool/kumomta/meta/LOCK: Resource temporarily unavailable
Error: Initialization raised an error: call init callback: callback error
stack traceback:
[C]: in local ‘poll’
[string “?”]:5: in function ‘kumo.start_http_listener’
[string “/opt/kumomta/etc/policy/init.lua”]:108: in function <[string “/opt/kumomta/etc/policy/init.lua”]:67>
caused by: listen on 0.0.0.0:8000: Address already in use (os error 98)

I then ran this

curl -H ‘Content-Type: application/json’ ‘http://127.0.0.1:8000/api/inject/v1’ -d '{

"envelope_sender": "arnoldp@flossnet.co.za",
"content": "Subject: hello\n\nHello there",
"recipients": [
    {
        "email": "arnoldp@flossnet.co.za"
    }
]

}’

I got this:

{“success_count”:0,“fail_count”:1,“failed_recipients”:[“arnoldp@flossnet.co.za”],“errors”:[“arnoldp@flossnet.co.za: callback error\nstack traceback:\n\t[C]: in function ‘kumo.reject’\n\t/opt/kumomta/share/policy-extras/dkim_sign.lua:162: in upvalue ‘do_dkim_sign’\n\t/opt/kumomta/share/policy-extras/dkim_sign.lua:271: in upvalue ‘dkim_signer’\n\t[string "/opt/kumomta/etc/policy/init.lua"]:184: in function <[string "/opt/kumomta/etc/policy/init.lua"]:180>\ncaused by: 552 5.6.0 DKIM signing requires a From header, but it is missing from this message”]}

I then checked the logs

/opt/kumomta/sbin/tailer --tail /var/log/kumomta

However, it just indicates that it is waiting for more files

Any assistance will be appreciated.

Hey there @congenial-porcupine, thanks for posting. Please read the “Troubleshooting” and “How to Ask for Help” buttons below. If you would like a 1:1 support session from the KumoMTA team, details are at the “Book a Support Session” button below.

Is your spool directory owned by kumod?

Hi Mike

I ran chown -R kumod:kumod spool in the /var directory

I ran the command again

[root@server var]# sudo KUMOD_LOG=kumod=info /opt/kumomta/sbin/kumod --policy /opt/kumomta/etc/policy/init.lua --user kumod&
[1] 15358
[root@server var]# 2024-04-21T15:59:27.797711Z INFO localset-2 kumod: NodeId is ad51f585-619b-4994-92d3-d3d7f61cfe2c
2024-04-21T15:59:27.943317Z ERROR localset-2 kumod::spool: Error in spool: Opening spool data: IO error: While lock file: /var/spool/kumomta/data/LOCK: Resource temporarily unavailable
2024-04-21T15:59:27.947449Z ERROR localset-2 kumod::spool: Error in spool: Opening spool meta: IO error: While lock file: /var/spool/kumomta/meta/LOCK: Resource temporarily unavailable
Error: Initialization raised an error: call init callback: callback error
stack traceback:
[C]: in local ‘poll’
[string “?”]:5: in function ‘kumo.start_http_listener’
[string “/opt/kumomta/etc/policy/init.lua”]:108: in function <[string “/opt/kumomta/etc/policy/init.lua”]:67>
caused by: listen on 0.0.0.0:8000: Address already in use (os error 98)

I delete a LOCK and lock file in the meta and data folders.

I ran the command again and received the following output and it hanged:

[root@server meta]# sudo KUMOD_LOG=kumod=info /opt/kumomta/sbin/kumod --policy /opt/kumomta/etc/policy/init.lua --user kumod&
[1] 16136
[root@server meta]# 2024-04-21T16:20:35.199753Z INFO localset-0 kumod: NodeId is ad51f585-619b-4994-92d3-d3d7f61cfe2c
Error: Initialization raised an error: call init callback: callback error
stack traceback:
[C]: in local ‘poll’
[string “?”]:5: in function ‘kumo.start_http_listener’
[string “/opt/kumomta/etc/policy/init.lua”]:108: in function <[string “/opt/kumomta/etc/policy/init.lua”]:67>
caused by: listen on 0.0.0.0:8000: Address already in use (os error 98)

You have a kumod already running

Find it and kill it