Supybot 0.83.3 sometimes gets stuck in limbo when reconnecting to server, here's a log:
INFO 2012-06-30T11:32:18 supybot Reconnecting to efnet at 2012-06-30T11:32:28.
INFO 2012-06-30T11:32:28 supybot Connecting to irc.efnet.pl:6667.
INFO 2012-06-30T11:32:37 supybot Flushers flushed and garbage collected.
INFO 2012-06-30T12:32:37 supybot Flushers flushed and garbage collected.
INFO 2012-06-30T13:32:37 supybot Flushers flushed and garbage collected.
INFO 2012-06-30T14:32:37 supybot Flushers flushed and garbage collected.
INFO 2012-06-30T15:32:37 supybot Flushers flushed and garbage collected.
INFO 2012-06-30T16:32:37 supybot Flushers flushed and garbage collected.
INFO 2012-06-30T17:32:37 supybot Flushers flushed and garbage collected.
INFO 2012-06-30T18:32:37 supybot Flushers flushed and garbage collected.
INFO 2012-06-30T19:32:37 supybot Flushers flushed and garbage collected.
INFO 2012-06-30T19:37:05 supybot Exiting due to Ctrl-C. If the bot doesn't exit within a few seconds, feel free to press Ctrl-C again to make it exit without flushing its message queues.
As you can see, it attempted to connect at 11:32:28, then it just idled for several hours without timeout/reconnect. In case you're wondering, no, the bot wasn't connected to the server at this time. I had to kill it with Ctrl+C to get it to reconnect.
There is a workaround: call @disconnect, wait a few seconds, and then call @connect.
Sorry for my ignorance, but how can I give the bot commands if it's not connected to an IRC server?
note that 0.83.3 is a really old version. Try at least the latest release, 0.83.4.1. Or better yet, git head. and see if the problem persists.
Too bad 0.83.3 is the latest version that is prepackaged for CentOS 5 in EPEL. Anyway, I'll try to go for a manual installation of a newer version later...
Have you encountered this again since upgrading?