-
Notifications
You must be signed in to change notification settings - Fork 19
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
ERRO pool superslacker event buffer overflowed, discarding event 34443 #11
Comments
@bugcy013 you're not looking at the right log; the one resulting from |
I also got same error as above. Is there any solution for it? |
I got the same error in
Slack messages are not coming in... Thx. EDIT: From what I can see, buffer overflow error is only thrown after the 5th on 8th supervisor process stop. As doc says:
My guess is that the listener works correctly. First STOPPED event (from 1st to 5th process) are processed, but 6th to 8th trigger the overflow error. when running "supervisorctl status", I see a "superslacker" instance next to the one I configured. It was stopped. I tried to start it, then stop only mine, but no notification. Even if superslack is seen as "RUNNING" in supervisorctl status. But I have a new error :
Seems the authentication is an issue.
I tried with all, nothing works. I think the buffer issue is OK. Now it's slack auth I guess. EDIT2: I also tried with the --webhook parameter, providing a valid webhook URL to one of my slack channel. Same error. Thanks ! I'm not that far I think :) |
Hi Guys,
When we try the superslacker with supervisord I am getting this error. Also it not sending the slack messages
I my supervisord.conf I have this
In logs I can see the
can you please guide me. How to fix this.
-Dhanasekaran.
The text was updated successfully, but these errors were encountered: