-
-
Notifications
You must be signed in to change notification settings - Fork 661
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 at status plugin #3118
Comments
This error message doesn't look to me like the problem is in the status plugin. It looks more like |
Hmm, I see. So it seems, when a worker restarted it can't access the port
it used before?
Because I don't use the port other than for the haraka process.
…On Mon, Dec 12, 2022 at 7:54 AM Matt Simerson ***@***.***> wrote:
This error message doesn't look to me like the problem is in the status
plugin. It looks more like Creating TLS server on [::0]:465 is where
things go awry.
—
Reply to this email directly, view it on GitHub
<#3118 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIYFEYMINL5BWPNQ6JF23LWMZZUNANCNFSM6AAAAAAS24ROKA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
But I am still suspecting status plugin because our latest error show this
Error: Resource not currently part of this pool are normally happen when socket is being closed, and it doesn't shutting down haraka completely. But ERR_IPC_CHANNEL_CLOSED seems did send shutting down signal. We use this plugin at other server but didn't have issue, same node and os version too. But this happen, on only 2 of our relay. |
Please can you create PR to handle this situation? I am afraid I would not able to reproduce the bug and I can't fix that only with backtrace. |
@analogic problem is, I still don't know how to fix it. Also because it only happen on 2 server, I and my team haven't successfully find what kind of trigger that could reproduce the issue. |
I merged a PR earlier that will solve this problem |
@msimerson so far it haven't happen again. thanks. |
Describe the bug
Haraka shutting down when there are error at status plugin
Expected behavior
Should be restarted worker normally
Steps To Reproduce
Haraka worker restarted because others issue then somehow status plugin acting up
System Info:
Additional context
Log
some context when searching about the error log message
https://stackoverflow.com/questions/68638613/error-err-ipc-channel-closed-channel-closed-when-replacing-backend-service-wi
This happen when not activating ignore_bad_plugin configuration, and currently activating this option, let'see what happen.
The text was updated successfully, but these errors were encountered: