Error on kumo-tsa-daemon: UNIQUE constraint failed

get-help
1

Hello,

First of all, I want to thank the entire team for this powerful MTA. It has been a great tool.

I am facing an issue with the kumo-tsa-daemon. The error message I’m receiving is as follows:

2024-12-30T12:00:52.781339Z ERROR localset-0 tsa_daemon::http_server: while processing /publish_log_v1: UNIQUE constraint failed: event_history.rule_hash, event_history.record_hash (code 19)

I am struggling to understand the root cause of this issue. Below is a copy of my init.lua configuration for your reference:

[https://gist.github.com/chattouti/c62d0067f27190f00c0a7d28b3e8cfaa]

Thank you in advance for your assistance.

4

I also ran the command systemctl status kumo-tsa-daemon, and here is the output:

5

Dec 30 12:58:41 systemd[1]: Started kumo-tsa-daemon.service - KumoMTA Traffic Shaping Automation service.
Dec 30 12:58:41 tsa-daemon[1166057]: 2024-12-30T12:58:41.832442Z INFO localset-0 kumo_server_runtime: localset pool starting with 2 threads
Dec 30 12:58:41 tsa-daemon[1166057]: 2024-12-30T12:58:41.845375Z INFO localset-0 kumo_server_common::http_server: http listener on 0.0.0.0:8008
Dec 30 12:58:41 tsa-daemon[1166057]: 2024-12-30T12:58:41.845454Z INFO localset-0 kumo_server_common::start: initialization complete

6

Dec 30 13:00:25 tsa-daemon[1166057]: 2024-12-30T13:00:25.462299Z ERROR localset-1 tsa_daemon::http_server: while processing /publish_log_v1: UNIQUE constraint failed: event_history.rule_hash, event_history.record_ha>

7

I have not been able to reproduce this, but I am guessing that you have the same data writing to the same TSA db for some reason.

8

Hello @faithful-ostrich ,

Thank you for your response. A simple update to the dev version resolved the issue. I couldn’t pinpoint the exact cause, but it’s working fine now.