-
-
Notifications
You must be signed in to change notification settings - Fork 660
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: daemon dies unexpectedly - Error: read ECONNRESET (Re-Opened) #3400
Comments
For clarification, this issue was marked resolved before while I mentioned I would test the proposed solution. The proposed solution did not workout as anticipated. We are now collecting debug logs to try and identify the issue. |
Well, 0 new insights lol. With debugging on it produce no new information surrounding the crash. In this cash all three workers crashed or rather the 2 workers and the supervisor.
Any insight would be help. I am having a rough time troubleshooting this. |
I am also seeing this issue a few times a month. I'll be happy to troubleshoot; I just don't know where to start. I've looked at the connections preceding the crash but nothing stands out. I guess my first question is how can I determine which connection caused this?
|
I recently ran into a similar (maybe the same) issue. I didn't have time to figure out what's going on and fix it, but I have temporarily resolved it by disabling OCSP. diff --git a/tls_socket.js b/tls_socket.js
index 9fcbb6e8..1b29acb1 100644
--- a/tls_socket.js
+++ b/tls_socket.js
@@ -538,6 +538,7 @@ exports.ensureDhparams = done => {
}
exports.addOCSP = server => {
+ return;
if (!ocsp) {
log.debug(`addOCSP: 'ocsp' not available`);
return;
|
Duplicate of #3398
Describe the bug
While running Haraka in daemon mode, after some time, hours, the daemon dies with a very short message.
Expected behavior
The expected behavior would be to not die... However, more clearly would be to log the issue and move along as in a daemon environment no human eyes are babysitting it to ensure it does stop.
Observed behavior
While the daemon is running, the daemon will die and post to the log the following output.
Steps To Reproduce
Frankly, I enabled demonize in
smtp.ini
and ran it. I let it run over night and sometime in the evening it dies. This happens during the day as well. So far, every 6 hours or so.System Info
Additional context
I would not be trying to run this as a daemon indefinitely if I could get the service to work. There is a whole lot of documentation missing from hark.service to drop it in and go lol. I am trying to work through it but omg this one is rough. Im likely missing something obvious but yeah.
The text was updated successfully, but these errors were encountered: