I’ve been having instances where kumod locks up completely. I am using the web api to inject messages and sometimes everything just freezes up, and the web/api interface stops responding to requests. It doesn’t deny connections, just hangs such that requests to it time out. At that point nicely killing the kumod process doesn’t work either - only forcibly kill -9
Q 1. What is the best way to track down what exactly is causing this. It is sporadic and not consistent as far as I can tell. Other than enabling trace logging, is there anything else I should be doing to try to catch what is going on?
Q 2. The inject api was being fed an email template with 1000 recipients and choked. (After numerous successful requests in this manner). Is it safe to assume if a “Reception” callback is never received that a particular message has not made it into the system?
Hey there @impressive-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.
First ensure you are on the latest -dev release, there have been multiple improvements on this front. Generally speaking it is resource exhaustion, so pushing harder than the hardware can handle. I’d check the logs to know more about the state of that injection.