From c6137dce82267a88e7981db98c9e80479064b18f Mon Sep 17 00:00:00 2001 From: Jeremy Stanley Date: Wed, 2 Jun 2021 17:21:37 +0000 Subject: [PATCH] Update IRC bot troubleshooting doc for OFTC The troubleshooting section of our IRC doc had examples specific to Freenode, update those. Further, drop the bit about /etc/hosts on eavesdrop, since OFTC offers an IPv4-only round-robin name we can use directly in our meetbot configuration to work around the TwistedPython+SSL+IPv6 DNS resolution bug without resorting to hard-coding addresses on the server. Change-Id: I7ac1542dcd0a4f088b8c475756338851994f5433 --- doc/source/irc.rst | 12 ++---------- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/doc/source/irc.rst b/doc/source/irc.rst index 0ed063b219..5b56dc6a5b 100644 --- a/doc/source/irc.rst +++ b/doc/source/irc.rst @@ -376,19 +376,11 @@ Bots may stop responding, common steps to troubleshoot the problem are: If the bot is stopped, start it again. Restart the bot if you see it's running but not operating properly. -2. On bot restart, it may show problems connecting to chat.freenode.net. +2. On bot restart, it may show problems connecting to irc.oftc.net. If bot logs show it's stopped on connection, you can manually try with:: - telnet chat.freenode.net 6667 - -3. For bots on the eavesdrop server: if you don't have connection to - that port, check entries on ``/etc/hosts`` for - ``chat.freenode.net``, until you find one server that is operative. - Switch the entries on ``/etc/hosts`` to choose the right one, and - restart the service with:: - - sudo service xxxbot restart + telnet irc.oftc.net 6667 Registering a Nick for a New Bot ================================