superslacker
superslacker copied to clipboard
ERRO pool superslacker event buffer overflowed, discarding event 34443
Hi Guys,
When we try the superslacker with supervisord I am getting this error. Also it not sending the slack messages
2018-09-07 19:29:55,164 ERRO pool superslacker event buffer overflowed, discarding event 34443
I my supervisord.conf I have this
[eventlistener:superslacker]
command=superslacker --token="XXXXXX-XXXXXX-XXXXXX" --channel="#qa" --hostname="dvserver26" --events="BACKOFF,STOPPING,EXITED,STOPPED,UNKNOWN"
events=PROCESS_STATE,TICK_5
In logs I can see the
$ tail superslacker-stdout---supervisor-hvKFKm.log
RESULT 2
OKREADY
RESULT 2
OKREADY
RESULT 2
OKREADY
RESULT 2
OKREADY
RESULT 2
OKREADY
can you please guide me. How to fix this.
-Dhanasekaran.
@bugcy013 you're not looking at the right log; the one resulting from stderr
is way more expressive. I'm not facing the same issue as you, but you'll probably find some answers there.
I also got same error as above. Is there any solution for it?
I got the same error in supervisord.log
ERRO pool superslacker event buffer overflowed, discarding event XX
.
superslacker-stdout---supervisor-gYTKJD.log
contains :
RESULT 2
OKREADY
RESULT 2
OKREADY
RESULT 2
OKREADY
RESULT 2
OKREADY
RESULT 2
OKREADY
superslacker-stderr---supervisor-YvamkJ.log
is empty.
Slack messages are not coming in... Thx.
EDIT:
From research about "buffer overflow", I added
buffer_size=200
below the superslack event line, and i'm able to get something new (see auth error below).
From what I can see, buffer overflow error is only thrown after the 5th on 8th supervisor process stop. As doc says:
The event listener pool’s event queue buffer size. When a listener pool’s event buffer is overflowed (as can happen when an event listener pool cannot keep up with all of the events sent to it), the oldest event in the buffer is discarded.
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 :
File "/usr/local/lib/python2.7/dist-packages/slacker/__init__.py", line 102, in _request
raise Error(response.error)
slacker.Error: invalid_auth
Seems the authentication is an issue. What token is exactly needed ?
- Oauth Token from https://api.slack.com/apps/XXXXX/install-on-team?
- Or the verification token from https://api.slack.com/apps/XXXXX ?
- The one from https://api.slack.com/apps/XXXXX/oauth? (same I think)
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. Question: how does package choose between Oauth auth, and webhook post ?
Thanks ! I'm not that far I think :)