Eggdrop Dies for no Reason

Post by **Sir_Fz** » Mon Apr 28, 2003 6:53 am

Nobody has access to the bot excess me so only i can use the .die command. but my eggdrop, for no reason, dies everyday... and everyday I have to logon into SSH to start the eggdrop again.

any reasons why's that happening ?

ppslim · Post by **ppslim** » Mon Apr 28, 2003 7:49 am

Bots don't die for no reason.

They can die however, when a fatal error occurs. This can be due to the fact there is no way to recover from it, or some script has cause the bot to die.

You will find information from 1 of 2 places.

1: The log files. See if they shed any excuse for the action taken

2: In your eggdrop dir, there might be a file called DEBUG (note the caps). This will contain information regarding the last crash (if it was a crash that is).

Post by **Sir_Fz** » Mon Apr 28, 2003 3:06 pm

ok, I have no file named DEBUG in the eggdrop's directory.

However i asked the shell company's founder he said its a problem in the box. (could it be ?)

thank you

ppslim · Post by **ppslim** » Mon Apr 28, 2003 6:46 pm

Could well be.

The provider could be doing checking, to see if a user is using to many BG processes.

This may kill of aiditon ones.

You may want to ask the shell company for more details on the issue, and again, try and find out what the bots says as the quit message on IRC, and on the partyline.

Post by **Sir_Fz** » Tue Apr 29, 2003 10:02 am

in the channels.log it shows nothing, in the partylines also nothing, and on the irc quitting it shows "Client Closed Connection" which is the quit message when someone kills pid.bot or when there's a tcl error, well its not a tcl error. Maybe this extra BG is the reason... but the founder is my friend so i think its a problem in the box

Eggdrop Dies for no Reason

Eggdrop Dies for no Reason

-