From 890a56d1b9f5d102f7097d428cab27caef072a2d Mon Sep 17 00:00:00 2001
From: Yolanda Robla <yolanda.robla-mota@hp.com>
Date: Mon, 21 Dec 2015 16:58:13 +0100
Subject: [PATCH] Add instructions on how to troubleshoot bots

Change-Id: I18ed46a1f1a87d6545541502f499eeab5e80c692
---
 doc/source/irc.rst | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/doc/source/irc.rst b/doc/source/irc.rst
index f8c2cf621a..5214b8848c 100644
--- a/doc/source/irc.rst
+++ b/doc/source/irc.rst
@@ -317,3 +317,27 @@ Tips
    the new channel.
  * Don't leave the channel until everything is done, it's non-trivial to
    rejoin because you've set up a forward!
+
+Troubleshooting
+===============
+
+Bots may stop responding, common steps to troubleshoot the problem are:
+
+1. Check status of the bot, with:
+
+    service xxxbot status
+
+If 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.
+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