Last modified: 2013-12-05 23:58:50 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T56821, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 54821 - Prevent repeated quit/join of malfunctional bots in #pt.wikimedia on irc.wikimedia.org
Prevent repeated quit/join of malfunctional bots in #pt.wikimedia on irc.wiki...
Status: NEW
Product: Wikimedia
Classification: Unclassified
IRC (Other open bugs)
wmf-deployment
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: ops
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-01 10:50 UTC by Alchimista
Modified: 2013-12-05 23:58 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Alchimista 2013-10-01 10:50:14 UTC
On #pt.wikipedia there's a malfuctioning bot that's flooding the channel, quiting and joining on every new message (yahoo_agentXXXX (~yahoo_age@anonymous.user)), wich cause some obvious disturbs, could it be kiked or banned for a while? 

This brings another question, shouldn't be a prevention mecanism to prevent situations like this, lets say, preventing more than X reconects per minute?
Comment 1 Andre Klapper 2013-10-01 12:07:16 UTC
Component description says

Issues with Recent Changes feeds on irc.wikimedia.org. Bot issues should go to "Tools→WM-Bot", "Wikimedia→wikibugs IRC bot", or "General" for other bots. Freenode Cloak/channel requests etc should go to https://meta.wikimedia.org/wiki/IRC/Group_Contacts

...so I guess the last option applies here. CC'ing the listed people.
Comment 2 Barras 2013-10-01 12:11:11 UTC
#pt.wikipedia sounds like a channel on wikimedia's own IRC network on which we (Group contacts for irc.freenode.net) have no influence.
Comment 3 Alchimista 2013-10-01 14:08:35 UTC
Barras is right, the channel in stake belongs to irc.wikimedia.org (notice on the bug title), where the recent changes feed throws the information, and the problematic bot is not, as far as i can tell, an wikimedia one, so it's everything ok with the infrastructure, it's an external reader bot with a malfunction that floods the channel.
Comment 4 Andre Klapper 2013-10-01 14:14:03 UTC
Uhm, sorry for my failure to read. :-(
Comment 5 Kunal Mehta (Legoktm) 2013-10-01 16:37:16 UTC
Not sure how practical/difficult this would be, but it might be better to just not show part/join's for clients other than yourself. There are plenty of legitimate bots that occasionally will flood off and require the operator to fix it and they might not come online for a few hours or days. Tracking down a sysadmin to ban (and then unban) a bot would be a pain.
Comment 6 Alchimista 2013-10-02 16:03:08 UTC
The wikimedia's irc channels are a great place to monitor a project globally. I use it to check if anti-vandalism bots are working, if there is a lot of people patrolling pages, using huggle, if bot accounts are operating without permission and even strange events. When a 66% of that channel traffic is a reconnect/quit message from a single account that kind of sucks. I've developed some bots for irc, and sometimes they had reconnect several times, but with a special care not to cause too many noise. I could disable the joins/quit, but it whould disable it for all channels, and so i couldn't know when some newbie is entering on help channels.
Comment 7 Alchimista 2013-10-31 20:27:49 UTC
Any development? The bot remains with problems, for more than one month. Almost 2/3 of the channel traffic is generated by the bot's in/out.
Comment 8 Andre Klapper 2013-12-05 23:58:50 UTC
<greg-g> I'm not sure it's that big of an issue, can just ignore joins/parts
<MaxSem> is ignoring it absolutely not an option?
<^d> Anyway, that requires a root. Nobody else has access to it afaik (the config file is in the private puppet repo, looks like)
<^d> to fix your bug--you'll need a root opsen.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links