Steps to replicate the issue (include links if applicable):
What happens?:
Nothing (no information about the edit).
What should have happened instead?:
wm-bot informed that the edit was made.
Other information
T295487 happening again?
FYI: This is fairly urgent for the steward elections channel (the elections will start in a couple of weeks).
LOG [1/1/2023 5:08:52 AM] [ERROR]: ModuleRC: redis is empty for 10 seconds
This is what I’m seeing in the logs
Previous comments (T306076#8333384 / @Legoktm) about the IRC integration is to look at alternative bots, Unless someone has stepped up to look after xmlrcs side of things.
There are at least 2-3 snitch clones running these days, I can help you find one or set up your own if you'd like. (It's been a while since I closely followed the SE process, but it's not clear to me an IRC feed is what's truly desired vs some external tool.)
Thanks for the offer @Legoktm. Fortunately, we (SE2023 ElectCom) managed to find an alternate bot to do the job (thanks @Operator873 for the help with it), so it’s no longer having any impact on us. The IRC feed is used to monitor the elections, and considering by the number of people joining the election channels, it’s an used feature. If desired, priority can probably be reset at this point.
So I believe the error I posted above means that redis on the xmlrcs server needs restarting. Xmlrcs is not fully down or else the wm-bot module would have failed to load upon a restart.
Hello, the problem was with python script that uses event source and forward data to redis. This event source system is not very reliable (which is one of main reasons why xmlrcs was created so that tools like wm-bot can use that instead of implementing unreliable protocol).
Normally it fixes itself - there is a job that autokill the hanging python script, but it seems to have failed for some reason this time. Manual kill of that python script resolved the issue.