Why is this happening?This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
Why?
Are you sure it's not running?
Try typeing "ps x", that should give you an answer.
The only other explanation is that a script on the system is periodicaly killing user processes. You should contact the admin to find out why.
Note, try staying on the partyline, and wait till the bot dies. You may get a more meaningfull message then as well.
Try typeing "ps x", that should give you an answer.
The only other explanation is that a script on the system is periodicaly killing user processes. You should contact the admin to find out why.
Note, try staying on the partyline, and wait till the bot dies. You may get a more meaningfull message then as well.
If the eggdrop is dieing, with no apparent reason what so ever, it is most likely due to the fact it is being killed.
You should make a clear note, of the exact times it does, and see if there is a pattern. Even if there isn't, after 2 or 3 times, you should then e-mail the shell admin, and explain the following.
Say that you eggdrop is dieing with no apparent reason. Give times and dates, that this occuring. Ask the admin if he uses software, to make sure a user is within his proces limit, and/or if he uses one to deny the running of certain software. Ask if he/she could look into the problem, see if they can see why this is happening.
Note, it may not be a process limiter, it could allways be a memory/CPU time limiter. Maybe the eggdrop is starting to hog up system resources. This is one major reason of admins killing a user process.
It could be a connection limiter. Some shell providers do not like users having too many listening ports open (EG, keep you listen commands down to 1 "listen all"), nor do they like too many outgoing connections. This is somthing else to ask.
There maybe a bandwidth limiter, detecting if you are going to go over a certain limit each day, based on averages.
You should make a clear note, of the exact times it does, and see if there is a pattern. Even if there isn't, after 2 or 3 times, you should then e-mail the shell admin, and explain the following.
Say that you eggdrop is dieing with no apparent reason. Give times and dates, that this occuring. Ask the admin if he uses software, to make sure a user is within his proces limit, and/or if he uses one to deny the running of certain software. Ask if he/she could look into the problem, see if they can see why this is happening.
Note, it may not be a process limiter, it could allways be a memory/CPU time limiter. Maybe the eggdrop is starting to hog up system resources. This is one major reason of admins killing a user process.
It could be a connection limiter. Some shell providers do not like users having too many listening ports open (EG, keep you listen commands down to 1 "listen all"), nor do they like too many outgoing connections. This is somthing else to ask.
There maybe a bandwidth limiter, detecting if you are going to go over a certain limit each day, based on averages.