Pinging Out Problem

[Zorb]

For some reason it seems that some of my bots get ping timeout when I'm away. Is there any known reasons why an eggdrop may ping out?

[Sir_Fz]

Could be a problem from the IRC server or from your Eggdrop's ISP.

[nml375]

One possibility might be some tcl-script or module that does some heavy data-processing without handing control back to eggdrop.
(Running ie. pisg from withing eggdrop can cause this if you're not careful, and have large logfiles)

[awyeah]

Try using tcl script which pings the server continuously, say with a frequency of say 2-5mins/ping to the server. You can find a pinging script on egghelp's tcl archive.

Also this script with a public trigger can help you check your bots lag:

Code: Select all

bind pub - !lagcheck lagcheck
bind raw - 421 laganswer

proc lagcheck {n u h c t} {
    set ::laganswer([set ticks [clock clicks -milliseconds]]) $c
    putserv "$ticks"
}

proc laganswer {f k t} {
    if {[info exists ::laganswer([set ticks [lindex [split $t] 1]])]} {
        putserv "PRIVMSG $::laganswer($ticks) :Lag: [expr [clock clicks -milliseconds] - $ticks] ms"
    }
}

[YooHoo]

this might be way too obvious, but have you tried using different servers? I know firsthand how lame some server's are, but then with a simple .jump, all is better.

[pitbull]

A friend of mine is having a similar issue with his bot. The bot (v. 1.6.18 ) is running on a home server, I believe it is connected via cable-modem. The server is running Ubuntu. The bot continually pings out (And the timeout is always 260 seconds). The bot times out at least 10-15 times per day. It doesn't seem to have any patterns on how often it disconnects, but is usually every hour or two. However, the bot never disconnects from the botnet, only the IRC server. Also, the owner also runs an IRC client on the same machine, connecting to the same IRC servers the bot uses, and doesn't experience any connectivity issues. He has tried the server ping tcl script, to no avail, and also has the realname variable set. He has tried disabling all TCL scripts, and the bot still times out.. Any ideas?

Thanks!

[nml375]

Does he get any "Timer drift -- spun N minutes" messages in his logs? (where N being a positive number)

[pitbull]

I don't have access to the logs, but I'll mention this.. What does it mean if it deos have this?

[nml375]

It basically means that the eggie was "halted" for several minutes, and thus unable to interact with the irc server. Causes for this might be limited resources on the system (eggdrop got swapped out of memory for some time) or some tcl-script took long time to complete and thus blocked the eggdrop (such as calling "exec pisg" with large logfiles).

[pitbull]

There were no Timer drift lines in the log file... Any other ideas anyone?