Warning: over maximum server queue!

[rosc2112]

I would use either timers for sending whatever you need to send, or event-driven responses, meaning, when you see a particular response from the server, then send the next bit of commands, when you get a response from that command, send the next, etc.

[rosc2112]

Might also help to use puthelp instead of putserv or putquick, if you're using those commands. puthelp uses a slower queue.

[awyeah]

Hi!

Just here with a little problem. My eggdrop bot is like a multi-tasking eggdrop. Has alot of tcls inside and some of them activate when the bot connects to the server, after identifying to NickServ on DALnet.

<adapter> [10:54] -NickServ (service@dal.net)- Password accepted for adapter.
<adapter> [10:54] adapter joined #awyeah.
<adapter> [10:54] #awyeah: mode change '+o adapter' by ChanServ!service@dal.net
<adapter> [10:55] @#awyeah (+tn) : [m/32 o/26 h/0 v/6 n/0 b/0 e/- I/-]
<adapter> [10:55] Warning: over maximum server queue!
<awyeah> .tcl queuesize
<adapter> Tcl: 300

After connecting to a server it gives me this warning:
<adapter> [10:55] Warning: over maximum server queue!

The maximum server queue is 300 I suppose as I checked. I was wondering is there anyway to check the listings of the queue? is there anyway to do that? (as to what is in the queue), so I can have an idea as to what can be removed in the queue to prevent this warning from occuring everytime the bot connects to the server.

Thanks!

All help is appreciated..
JD

[awyeah]

Follow up:

queuesize [queue]
Returns: the number of messages in all queues. If a queue is specified, only the size of this queue is returned. Valid queues are: mode, server, help.
Module: server

clearqueue <queue>
Description: removes all messages from a queue. Valid arguments are: mode, server, help, or all.
Returns: the number of deleted lines from the specified queue.
Module: server

These are the only two commands I found regarding the queue. 'clearqueue' will only clear the respective queue and 'queuesize' will only display the size of the respective queue.

JD

[awyeah]

Hi!

Umm thanks for the reply. I do know about puthelp since it is the slowest queue possible, however I just use putserv normally. Anyway I was looking if possibly I could view the queue, guess that seems unrealistic and impossible, only unless if the source code is modified.

Anyway thanks for your reply. Yeah, the only thing left is to use timers now, so the commands on connect and bot join can be delayed.

JD

[user]

.console +v

[awyeah]

Thanks, user.. works like a charm.

What can I say about you.. theres NO question which you can't answer.

JD

[awyeah]

When my bot joins a channel it does the following:
(1) /mode #chan +b (get banlist of channel)
(2) /mode #chan (get channel modes)
(3) /who #chan (who all the users in #chan)
(4) /whois all users in #chan

<adapter> [02:52] -NOTICE- *** Found your hostname
<adapter> [02:52] -NOTICE- *** Got Ident response
<adapter> [02:52] [!s] WHOIS adapter
<adapter> [02:52] [!m] MODE adapter +i-ws
<adapter> [02:52] [m->] MODE adapter +i-ws
<adapter> [02:52] [!s] JOIN #eggdrops
<adapter> [02:52] [!s] JOIN #adapter
<adapter> [02:52] [!s] JOIN #awyeah
<adapter> [02:52] -NickServ (service@dal.net)- Password accepted for adapter.
<adapter> [02:52] [s->] WHOIS adapter
<adapter> [02:52] [s->] JOIN #eggdrops
<adapter> [02:52] [!m] MODE #eggdrops +b
<adapter> [02:52] [m->] MODE #eggdrops +b
<adapter> [02:52] [!m] MODE #eggdrops
<adapter> [02:52] [m->] MODE #eggdrops
<adapter> [02:52] [!m] WHO #eggdrops
<adapter> [02:52] [!s] WHOIS adapter
<adapter> [02:52] [!s] WHOIS irwan
<adapter> [02:52] [!s] WHOIS Alchera-Away
<adapter> [02:52] [!s] WHOIS Almacherzo
<adapter> [02:52] [!s] WHOIS }{F_F_F}{
<adapter> [02:52] [!s] WHOIS lohis
<adapter> [02:52] [!s] WHOIS attack
<adapter> [02:52] [!s] WHOIS crypted
<adapter> [02:52] [!s] WHOIS Bluechip
<adapter> [02:52] [!s] WHOIS RizaL
<adapter> [02:52] [!s] WHOIS BhOgAzT
<adapter> [02:52] [!s] WHOIS ecliptik
<adapter> [02:52] [!s] WHOIS awyeah
<adapter> [02:52] [!s] WHOIS Q-Thing
<adapter> [02:52] [!s] WHOIS jiggy
<adapter> [02:52] [!s] WHOIS Exploid
<adapter> [02:52] [!s] WHOIS THBot
<adapter> [02:52] [!s] WHOIS
<adapter> [02:52] [m->] WHO #eggdrops

Is all of this the default for the eggdrop? Whenever it joins a channel, it has to perform the following steps? The thing is, my bot on connect to server joins some largely populated channels, and does each of these 4 steps on all, which gives it the warning message:

Warning: over maximum server queue!

atleast 3 or 4 times on connection to the irc server. Is there anyway to fix this problem then?

Thanks,
JD

[Sir_Fz]

Check out this topic.

[awyeah]

Thanks for digging out such an old yet very relevant and helpful post for me Sir_Fz

I guess this will be it then (if anyone else is looking for something similar), after a few modifications by myself. Will give it a go and see and consequences and chances for improvement:

Code: Select all

if {[string match *raw:irc:join* [binds]]} { unbind raw - JOIN *raw:irc:join }

bind raw - JOIN join:delay

proc join:delay {from keyword arg} {
  if {[string equal -nocase $from $::botname] && [string match -nocase *[string range $arg 1 end]* [channels]]} {
    putloglev d * "Delaying WHO: [string range $arg 1 end]"
    utimer 60 [list resetchan [string range $arg 1 end]]
    return 1
  } else {
    *raw:irc:join $from $keyword $arg
  }
}