Bot Issue

intel · Post by **intel** » Wed Jun 03, 2009 11:14 pm

First I am running eggdrop 1.6.19 under VMware (debian Linux). I have done this before without an issue. The bot compiles fine. I can start it with
./eggdrop -m eggdrop.conf Nothing happens after that. When I look in the logs dir and open eggdrop.log I just see * TERMINATE SIGNAL -- SIGING OFF

I dont know what I am missing here. Any help is appreciated.

Post by **nml375** » Thu Jun 04, 2009 1:00 pm

Are you using some kind of resource limiter on that system? Simply put, your eggdrop stops running because some process (or someone) is sending the TERM (sigterm) signal to your eggdrop's process, telling it to gently stop running.

intel · Post by **intel** » Thu Jun 04, 2009 1:51 pm

Not that I am aware of. Where would I look for that? I did a basic install of Debian Lenny so I do not think there are any restrictions. I setup my vmware session like I always do.

Any suggestions would be appreciated.

Post by **nml375** » Thu Jun 04, 2009 2:01 pm

Unfortunately, tracking down signals can be a real b*tch :/
There is always the strace command that does monitor all system calls and signals for a given process.. unfortunately that means it'll log a lot more than just the sigterm. I'm not sure if it'll provide the source of the signal though.

One thing to check early on though, are you using SELinux?

intel · Post by **intel** » Thu Jun 04, 2009 2:38 pm

Nope I am not running that. Its just weird that I can surf, I can connect to IRC using XCHAT so I am just stumped as to what and why eggdrop is being blocked.

Lukan · Post by **Lukan** » Fri Aug 14, 2009 2:41 am

try loading the bot in the foreground.

Code: Select all

./eggdrop -n -m CONFIG-FILE

That should help you see what is happening in the sequence of commands.

You might also want to try the configuration in this post.

This cleared up a lot of my problems that I was having due to my TCL being threaded.

Luk