Actually, eggdrop bot goes offline.. at times it comes back... but sometimes i had to restart it manually using putty.. why is that so.. and any solution to get rid of this problem.. like the bot should restart automatically when it goes offline.
Passionate.
P.S: Sorry just incase if this question asked already.
Check your logs for errors, if there're no errors then it's probably from your shell. If it's the second case then ask your provider to solve it and if your shell supports crontab then check out this section for help in using crontab.
i know this was posted back in 2005 - but i am having the exact same issue today - and its not the box - as i have 2 other eggdrops on the same box and no issues from any of them.
is there a script that could make the eggdrop auto restart?
The botchk script and crontab are used to automatically restart the bot if the shell it's on reboots or if the bot process is killed for some other reason. You can find the botchk file in the scripts directory (in the directory you installed the bot to). Newer versions of Eggdrop (from 1.3.24i) have a script included that automatically configures botchk and crontab for you. In telnet, simply switch to the scripts directory and type chmod 700 autobotchk then ./autobotchk <config> -dir /home/botdir -noemail, where /home/botdir is the directory you installed the bot to and <config> is the name you chose for your config file.
the botchk file would be very helpful, if the bot had actually died, but that is not my issue here, when i log into the box - and do ps x -- the bot is still running - but it is NOT on my network, that is my issue. hence the reason i asked is there a script that could make the eggdrop auto restart? meaning make it rejoin my network since it is still running as a process on the shell.
ps: i already have the botchk set for each of my eggdrops so that they restart if the shell gets rebooted.
I believe I did post a watchdog-enabled botchk solution on the forum some time ago, havn't got a link right now, but a simple search should reveal it...
That said, it would seem to me that you've got some script that simply blocks your eggie. I'd recommend trying to find out which, and fix it.
Incith: I doubt that would be very useful, since apart from being locked out through a netsplit, I can't think of a situation where eggdrop wouldn't be able to make it's way back into the channel, should it not be "frozen"... (or well, very faulty scripting I suppose, but then the answer would be to fix that script)
If it is "frozen", however, no tcl-script running within the eggdrop will ever be able to restart/reboot it...
Same goes for network presence (assuming never-give-up and check-stoned are set to 1).
the eggdrop config i am using for the shoutcast echo is the same one i have used for awhile now - adn the eggdrop config is the same i use on all my drops adn they all stay online - so i know it aint the drop config or my other drops would all "freeze" up and yes never-give-up and check-stoned are set to 1 - not trying to be mean here - but i am not a n00b when it comes to eggdrops - i simply thought that others who are maybe more experienced in drops might have a clue as tyo what might be happening here.