Not sure if any of you have seen these messages, but I have just noticed these messages in my eggdrop bot's partyline after I have did a .restart due to it coming up with the wrong hostmask.
<Bot> [03:32] Warning: over maximum mode queue!
<Bot> [03:32] Warning: over maximum mode queue!
<Bot> [03:32] Warning: over maximum mode queue!
<Bot> [03:32] Warning: over maximum mode queue!
<Bot> [03:32] Warning: over maximum mode queue!
I'm not sure what these messages are, its the first time I have seen them since I have upgraded my eggdrop to version 1.6.18 and was wondering if someone could shed some light on this. It repeated it only five times and stopped.
It simply means your eggie has filled the internal queue of messages (see the max-queue-msg config variable).
eggdrop.conf wrote:# Set here the maximum number of lines to queue to the server. If you're
# going to dump large chunks of text to people over IRC, you will probably
# want to raise this. 300 is fine for most people though.
set max-queue-msg 300
nml375 wrote:It simply means your eggie has filled the internal queue of messages (see the max-queue-msg config variable).
eggdrop.conf wrote:# Set here the maximum number of lines to queue to the server. If you're
# going to dump large chunks of text to people over IRC, you will probably
# want to raise this. 300 is fine for most people though.
set max-queue-msg 300
Oh, didn't realize that. I just turned it up to 500 for now and restarted the bot. Seems to have gotten rid of those warning messages. I think that the reason my bot is getting a big number of lines to queue to the server is likely due to a number of TCL scripts I have on it.
I had that in a bot last week and figured out what was causing it but not the "cure".
The cause was another eggdrop kicking the bot (non-stop) and the resultant interaction with ChanServ.
The only way to solve that is find out why the other eggdrop is kicking your bot and stop it. I don't think that anyone wants to come into a channel where there is constant kicking (kick flooding) going on. Either deop the other bot, add your bot's hostmask to its user list with +f or some exemptable +flag, or ban the other bot from the channel as that doesn't look like proper channel management.
mcdarby: I solved the "problem" by removing my bot from the offending channel. I had no access to either the channel or the eggdrop that was doing all the kicking.
Add [SOLVED] to the thread title if your issue has been. Search | FAQ | RTM
