Hey all,
Some of you may know our belowed robot, which is working as a slave in some of our dev channels. Unfortunately, freenode as well as wikimedia labs is a bit unstable, when it comes to network connectivity. So both freenode servers as well as internet connectivity of labs are occasionally down. This is causing some troubles to wm-bot who isn't really able to reconnect, given to laziness of its developers as well as complexity of multiple bouncers it is using.
For this reason, it would be nice if we could have more operators of this bot, who will not just bring it back up in case some of its instances die, but who would also help to its users and participate in general bot maintenance.
The bot is running on wikimedia labs on ubuntu instance, and is written in c#, which in fact is irrelevant, because for its operation you don't need to have knowledge of c#. Ideal operator candidate should be trusted user (because you may have access to some private data, such as ip addresses of irc users who have no cloak, raw network logs of wm-bot as well as its freenode credentials and more), should have a rather good or excellent knowledge of unix (wm-bots components are not configured as services, so restarting them is not as easy as doing sudo service wm-bot restart) and a good knowledge of how irc networks and botnets work.
If you are interested in joining our small team, lemme know, preferably by e-mail :-) thank you
Le 11/10/13 09:24, Petr Bena a écrit :
wm-bots components are not configured as services, so restarting them is not as easy as doing sudo service wm-bot restart
Seems you might want to make them upstart services. That will ease maintenance, and AFAIK, Ubuntu upstart would even make sure the service is up and running.
I agree, but it requires some work, which I am too lazy for, especially since manual restart is almost as hard as typing sudo service wm-bot restart, it's just like 2 different commands
writing whole upstart script for bouncers and core is lot of work... Maybe when I have a lot of time I could think of that :P
On Fri, Oct 11, 2013 at 8:45 AM, Antoine Musso hashar+wmf@free.fr wrote:
Le 11/10/13 09:24, Petr Bena a écrit :
wm-bots components are not configured as services, so restarting them is not as easy as doing sudo service wm-bot restart
Seems you might want to make them upstart services. That will ease maintenance, and AFAIK, Ubuntu upstart would even make sure the service is up and running.
-- Antoine "hashar" Musso
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
also the problem is not that service wouldn't be up. Service IS UP but it's not connected to freenode (nothing upstart could fix) it's problem in wm-bot source code. It actually can reconnect when connection die, but problem is that wm-bot is using bouncer, and this bouncer doesn't forward signal when remote server disconnect. This needs to be fixed by some more coding and that again requires some other petan who isn't that lazy :)
On Fri, Oct 11, 2013 at 10:49 AM, Petr Bena benapetr@gmail.com wrote:
I agree, but it requires some work, which I am too lazy for, especially since manual restart is almost as hard as typing sudo service wm-bot restart, it's just like 2 different commands
writing whole upstart script for bouncers and core is lot of work... Maybe when I have a lot of time I could think of that :P
On Fri, Oct 11, 2013 at 8:45 AM, Antoine Musso hashar+wmf@free.fr wrote:
Le 11/10/13 09:24, Petr Bena a écrit :
wm-bots components are not configured as services, so restarting them is not as easy as doing sudo service wm-bot restart
Seems you might want to make them upstart services. That will ease maintenance, and AFAIK, Ubuntu upstart would even make sure the service is up and running.
-- Antoine "hashar" Musso
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On 10/11/2013 06:51 AM, Petr Bena wrote:
It actually can reconnect when connection die, but problem is that wm-bot is using bouncer, and this bouncer doesn't forward signal when remote server disconnect. This needs to be fixed by some more coding and that again requires some other petan who isn't that lazy
Alternately, if it used a bouncer that was on our network, and that connected to dickson.freenode.net it'd be pretty much insulated from network burps and splits which would help a lot.
-- Marc
I don't understand, some better explanation would be nice.
What is dickson server? Why it works better? The bouncers are running on same server as bot core, only reason for bouncers to exist is that I can upgrade the bot without having to reconnect it (I can restart the core process anytime and bot is still on-line)
On Fri, Oct 11, 2013 at 1:20 PM, Marc A. Pelletier marc@uberbox.org wrote:
On 10/11/2013 06:51 AM, Petr Bena wrote:
It actually can reconnect when connection die, but problem is that wm-bot is using bouncer, and this bouncer doesn't forward signal when remote server disconnect. This needs to be fixed by some more coding and that again requires some other petan who isn't that lazy
Alternately, if it used a bouncer that was on our network, and that connected to dickson.freenode.net it'd be pretty much insulated from network burps and splits which would help a lot.
-- Marc
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On 10/11/2013 09:30 AM, Petr Bena wrote:
What is dickson server? Why it works better?
dickson.freenode.net as also known as dickson.wikimedia.org: the freenode node that is on our network. (Which isn't advertized or in the round robins yet because it is still in burn-in).
It doesn't necessarily work "better", but it's on the same network we are so the likelihood of a network break is low (and in our power to fix).
-- Marc
That is rather nice to know!
On 11 October 2013 15:57, Marc A. Pelletier marc@uberbox.org wrote:
On 10/11/2013 09:30 AM, Petr Bena wrote:
What is dickson server? Why it works better?
dickson.freenode.net as also known as dickson.wikimedia.org: the freenode node that is on our network. (Which isn't advertized or in the round robins yet because it is still in burn-in).
It doesn't necessarily work "better", but it's on the same network we are so the likelihood of a network break is low (and in our power to fix).
-- Marc
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Petr Bena benapetr@gmail.com wrote:
Hey all,
Some of you may know our belowed robot, which is working as a slave in some of our dev channels. Unfortunately, freenode as well as wikimedia labs is a bit unstable, when it comes to network connectivity. So both freenode servers as well as internet connectivity of labs are occasionally down. This is causing some troubles to wm-bot who isn't really able to reconnect, given to laziness of its developers as well as complexity of multiple bouncers it is using.
Petr,
I was running a couple of recentchanges minibots (based on the UDP logging -> urdrec.c -> Python IRC module) pretty reliably.
The code is here https://bitbucket.org/plwiki/bot/src/ ("irc" module) but of course I am happy to help with hosting/reducing complexity and getting my hands finaly on C# if needed.
//Saper
wikitech-l@lists.wikimedia.org