do you have journal logs for that time as well?
Have you shared your configs somewhere? I was not able to find them.
Yeah: Mar 20 21:11:29 ip-172-31-17-90 kumod[451]: 2024-03-20T21:11:29.407372Z ERROR localset-0 kumod::http_server::admin_trace_smtp_server_v1: error in websocket: channel lagged b y 3
And the line before is one telling me that you cannot connect using ipv4 to ipv6
the smtp tracer isn’t intended to be able to keep up with following 100% of your production mail traffic, so if you’re sending fast/hard, you’ll need to adjust your expectations
(i disabled ipv6 for now, as I have had more issues then benefits from ipv6)
well it hangs the system even if I don’t trace
well I can load-balance the volume going into Kumo…
I would like more precision from you around specifically what you are observing when you say that something has locked up or hang; what specifically are you trying and what are you seeing?
ehm I am observing a complete lockup of kumo
debugging something like this without complete information (eg: configuration) is difficult
notthing works.. no API respons… smtp port doesn’t respons
kcli queue-summary does zero… but that is the same as the API
Aside from your configs, perhaps a Loom showing what you’re seeing then?
yeah I will create a zip of my config … maybe I have done a stupid loop somewhere
sorry a Loom? screenshot of the command line stuff I am seeing?
I want a Loom too! What is it?
Video recording, it’s a free way to share screen capture videos.
OOOOhhh ok