#29680 closed defect (fixed)

Deploy our own Meetbot

Reported by: phoul Owned by: anarcat
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Normal Keywords:
Cc: anarcat Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Following up on discussion with anarcat:

We currently rely on Debian's Meetbot to archive our IRC team meetings, as well as other events.

Deploying our own instance of Meetbot would allow for easier control of log backups, as well as the ability to directly troubleshoot when the service goes offline.

Child Tickets

Change History (5)

comment:1 Changed 20 months ago by anarcat

it seems that the debian folks are aware of the problem and may be working on it. there's been some movement to move debconf infrastructure towards the commonly managed debian.org / DSA managed infrastructure. in parallel, bytemark was bought out, staff was slashed and they're having networking problems.

what we're seeing is a result of the mix of all of that. the debian folks also depend on the service, so it's likely to come back eventually.

the maintainer of the service is darst on irc, and he's also unable to help as he doesn't have access to the machine. no one exactly knows when this will return.

the bot is documented here:


it's mostly a plugin in the venerably supybot bot. the last known copy of the source code is here:


setting that up would be fairly trivial, but I would wait a little longer until we're sure debian folks can't bring it back up.

comment:2 Changed 20 months ago by anarcat

Owner: changed from tpa to anarcat
Status: newassigned

the bot apparently came back up, according to @nickm, this morning. i'll see what's up

comment:3 Changed 20 months ago by anarcat

Resolution: wontfix
Status: assignedclosed

well, it looks like http://meetbot.debian.net is back, but not the bot itself, i asked darst what's up, but hopefully we won't have to run this ourselves anymore.

i did ask darst to publish the most recent source code somewhere so we have a copy in case of an emergency.

in the meantime, i'll close this because we shouldn't be rebuilding services that are available elsewhere while we have other fires to put out. hopefully we'll be able with this when it's real trouble.

i can always put up a bot in a pinch, it's one of my super-powers. ;)

comment:4 Changed 20 months ago by anarcat

Resolution: wontfix
Status: closedreopened

latest news here is that OFTC might take on the service and host it for all OFTC members instead of having everyone run their own bot.

in the meantime, MeetBot is back in #tor-meeting, so I think we can consider this fully fixed.

comment:5 Changed 20 months ago by anarcat

Resolution: fixed
Status: reopenedclosed
Note: See TracTickets for help on using tickets.