Ping Timeout

[everythingdaniel]

Hi, I have an eggdrop bot that has been working great. However, as of tonight, it cant stay connected, it keeps falling off the server in a ping timeout.


What are some of the causes for this? Too many scripts? Too many channels? Incorrect configuration?


Thanks for the help!


--Daniel L

[raider2k]

connect to partyline and see what it is saying when that happens, OR see your logfile, paste both in here if possible.

[everythingdaniel]

Hi, I can't dcc into the bot from my client, and I have never done telnet beofre, so I can't do party line.


Config file shows...

Code: Select all

[05:45] -opsb (opsb@stats.maximum-hosting.org)- Your Host is being Scanned for Open Proxies
[05:45] CTCP VERSION:  from SecureServ (TS@stats.maximum-hosting.org)
[05:45] AR_Bot joined #amusement-radio.
[05:45] Flood from @maximum-hosting.org!  Placing on ignore!
[05:45] AR_Bot joined #AR_Help.
[05:45] AR_Bot joined #AR_Staff.
[05:46] shoutcast: checking if stream is online
[05:47] Writing user file...
[05:47] Writing channel file...
[05:47] * TERMINATE SIGNAL -- SIGNING OFF

But, while it times out on the server, I have to go into the terminal and kill the process before I restart, so it still running.


Thanks!


EDIT: Here is the log with it logging everything possible,

Code: Select all

[06:10] main: entering loop
[06:10] DNS resolved irc.amusementradio.com to 72.20.28.241
[06:10] net: connect! sock 7
[06:10] AR_Bot joined #amusement-radio.
[06:10] Flood from @maximum-hosting.org!  Placing on ignore!
[06:10] Tcl error [autolog_join]: reached max # of logfiles
[06:10] AR_Bot joined #AR_Help.
[06:10] AR_Bot joined #AR_Staff.
[06:11] shoutcast: checking if stream is online
[06:12] Writing user file...
[06:12] Writing channel file...
[06:12] * TERMINATE SIGNAL -- SIGNING OFF

--Daniel L[/code]

[Brou]

does the bot just disconnects and eventually reconnect by himself, or you need to go to the shell to restart it everytime? or you are running botchk script to restart it automatically?

* TERMINATE SIGNAL -- SIGNING OFF -> My first guess would be someone or something is sending your bot a kill -HUP signal and you have set die-on-sighup 1 or something like that.

reached max # of logfiles -> you might want to check that, but I don't think that's causing the bot to die...

from your shell, try this: telnet <botip> <botuserport>
where botip is the IP of the server the bot is running on or if the server has multiple ips, the ip set in "set my-ip" in your eggdrop config
and botuserport is the port you set as "listen <port> all" or "listen <port> users"
This should get you to the partyline, so you can see the console messages, if the bot starts, connects, and die immediately, you might want to try starting the bot with the -nt flag at the command line so it doesn't go in background.

-Brou