Since I upgraded to 1.6.12, quite a few times my bot 'thinks' it is in a channel, when it really isnt. .channel #chan will even give me a userlist, of the chan the last time it was really IN there.. It has even happened in a channel where there is no chance it got kicked and the channels are not desynced. A simple .tcl putserv "PART #CHAN" will make it join, with a returned message of 'Server says I'm not in #blah..' Has anybody else experianced this with .12?
I can't reproduce the damned situation for the life of me either. Also, the bot never thinks it has ops while it thinks its there but isnt.
This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
Bot not 'really' in the channel
This usually happens with bits sitting on servers that have broken /who reply. One such exampl ewould be a missconfigured Conferencr Room IRCd. It can be set to *not* answer /who replies including even people who are visible to the bot (share the common channel, or a privmsg). What network is your bot sitting on?
Ignorant and lazy people will save 30 minutes by chosing simple config file. Smart ones will save 3000 minutes of *everyone's* time by opting for complete config file.
Um, efnet shouldn't make any problems, but just to make sure, is it:
a) Bot *is* on channel but doesnt realize that, or
b) Bot *is NOT* on channel, but thinks it is.. ?
a) Bot *is* on channel but doesnt realize that, or
b) Bot *is NOT* on channel, but thinks it is.. ?
Ignorant and lazy people will save 30 minutes by chosing simple config file. Smart ones will save 3000 minutes of *everyone's* time by opting for complete config file.
Can you try connecting your bot to a comstud server, and see if this has any effect.
This is one of the long list of items, ranging from updating no!spam, more on the effects of non-linking bots and getting laid.
It seems to happen, only on certain servers, from what I can see so far, but until I get my home machines setup, with net access, I can't tell.
If you can give the exaxt server details, including ports (I beleive one or two efnet servers, use 3 or 4 machines to operate there service, each one on a seperate port, with port 6667 setup to load balance), and I will put this within my todo list.
This is one of the long list of items, ranging from updating no!spam, more on the effects of non-linking bots and getting laid.
It seems to happen, only on certain servers, from what I can see so far, but until I get my home machines setup, with net access, I can't tell.
If you can give the exaxt server details, including ports (I beleive one or two efnet servers, use 3 or 4 machines to operate there service, each one on a seperate port, with port 6667 setup to load balance), and I will put this within my todo list.
It is rare, but when it happens, the bot is NOT in the channel, but thinks it is and also has stale .channel info. Most times this bot is on servercentral.net (port 6667). It actually has not happened since I posted it here, so many it was just a problem with the ircd or something. I would try to test it on other servers, but I cant reproduce it when I want to on servercentral. There should be no tcls interfering with this, nothing has really been added before this problem started (except the upgrade).
I think it hit the nail right on the head - unfortunatly I was rarely around or rarely noticed the missing bot(s), so I could never pinpoint why it happened until the past week or two. Whenever theres a fight between botnets my 1.6.12 bots (most of them) would get kicked a few times, and then just not rejoin, but think they were joined (stale channel info etc). Most of the time, a .tcl putserv "JOIN #chan" would send them back in though. I joined two botnets to a channel today and tried my hardest to reproduce it after upgrading to .13 and could not, and there was some excessive kicking going on. I didn't think it got kicked (triggering this 'bug') at first, but theres always the chance that it did. Anywho, thanks wcc and slennox! 
-
cchrone
hope 1.6.13 fixs it.
used to have the same problems too hehe get kicked from the channel and didn't rejoin.
on DALnet port 7000
on DALnet port 7000