Code: Select all
Trying server irc.anoxs.net:6667
DNS resolved irc.anoxs.net to 202.3.110.144
[m->] NICK Phoenix
[m->] USER phoenix . . :channel eggdrop bot with the power to ban you!
net: connect! sock 12
Connected to irc.anoxs.net
-NOTICE- *** Looking up your hostname...
-NOTICE- *** Found your hostname (cached)
-NOTICE- *** Checking ident...
-NOTICE- *** Received identd response
[@] zeus.au.oc.swiftirc.net 001 Phoenix :Welcome to the SwiftIRC IRC Network Phoenix!De_Kus@venus.isix.net
Trying server irc.swiftirc.net:6667
DNS resolved irc.swiftirc.net to 85.8.136.114
[m->] NICK Phoenix
[m->] USER phoenix . . :channel eggdrop bot with the power to ban you!
net: connect! sock 12
Connected to irc.swiftirc.net
-NOTICE- *** Looking up your hostname...
-NOTICE- *** Found your hostname (cached)
-NOTICE- *** Checking ident...
-NOTICE- *** Received identd response
[@] manticore.uk.eu.SwiftIRC.net 001 Phoenix :Welcome to the SwiftIRC IRC Network Phoenix!De_Kus@venus.isix.net
Trying server irc.anoxs.net:6667
DNS resolved irc.anoxs.net to 202.3.110.144
[m->] NICK Phoenix
[m->] USER phoenix . . :channel eggdrop bot with the power to ban you!
net: connect! sock 12
Connected to irc.anoxs.net
...
[@] ERROR :Closing Link: [87.117.192.75] (Throttled: Reconnecting too fast) -Email tim@swiftirc.net for more information.
-ERROR from server- Closing Link: [87.117.192.75] (Throttled: Reconnecting too fast) -Email tim@swiftirc.net for more information.
Disconnecting from server.
- The paste has been cut a little removing duplicated lines due to the raw and normal logging. However it's correct to see the bot connecting to the next server in list (there are only 2) without any notice after the welcome message.
- Everything happens within a few seconds until the throttled error. When this error comes up it waits patiently the server-cycle-wait of 60sec. The server-timeout is set to 30sec.
- The bot runs (or rather tries) a static compilation of 1.6.18 using thread TCL 8.4.16 (Debian unstable).
- Before configuring and compiling I ran make distclean on the source.
- It ran fine using the same configuration on another server (which is down now).
- Maybe an important information is that the bot once joined the 2 channels it is supposed to join for a few seconds without me seen any raw logs about sending the JOIN command... this one was really like a ghost story.
- Others seem to be able to run eggdrops in general on the server
- the error persists since yesterday
So now you have a totally confused user of an eggdrop sitting before the telnet raw-log. Can you give me any valuable hints how to solve this or at least track down the source of the evil?