egghelp/eggheads community

Egg 1.6.16 continuosly dead

2004-06-09T23:27:29-04:00

CORE & DEBUG don't end up in ~logs but in main bot folder.

Statistics: Posted by Alchera — Wed Jun 09, 2004 11:27 pm

Egg 1.6.16 continuosly dead

2004-06-06T09:30:29-04:00

Hi Wcc.
The network is IRCNet.
I don't know if the file "core" is produced...i've deleted 1.6.16 dir beacouse bored of the problem
The same of DEBUG file : i have compiled using make debug but the only 'debug' i see is on the partyline as reported before.The LOG dir was empty.
The set net-type is set to 1 (IRCNET)

Please believe me : i'm running eggs from many versions later, always upgraded from the beginning of 1.6 to 1.6.15 and i have this problem only with this version. My botnet count about 100 eggs with 1.6.15 and it's like a swiss watch for structure precision,speed and stability.For this i've decided to write here but at the moment seems to be the only having this problem. In each case i appreciate the time you waste for helping me

Don't go crazy : i still using 1.6.15 and waiting for 1.6.17

Statistics: Posted by cucciolo — Sun Jun 06, 2004 9:30 am

Egg 1.6.16 continuosly dead

2004-06-05T04:37:04-04:00

What IRC network is this on? Did the bot produce a file called "core"? Is there even a DEBUG file? What do you have net-type set to?

Wcc

Statistics: Posted by Wcc — Sat Jun 05, 2004 4:37 am

Egg 1.6.16 continuosly dead

2004-06-04T19:39:04-04:00

as suggested no one tcl scripts was been loaded
the egg run 'as is'
no linked not shared...isolated...
surely was a problem of my isp but never had problem like this since 1.6.12 so my opinion is that't bugged
but i'm happy to get in wrong
thanks to all for support

Statistics: Posted by cucciolo — Fri Jun 04, 2004 7:39 pm

Egg 1.6.16 continuosly dead

2004-06-04T16:34:43-04:00

this is the result.
On partyline :
[03.06.04 @ 20.10] <)PARTYLINE> [11:10] * Last context: tclhash.c/688 []
[03.06.04 @ 20.10] <)PARTYLINE> [11:10] * Please REPORT this BUG!
[03.06.04 @ 20.10] <)PARTYLINE> [11:10] * Check doc/BUG-REPORT on how to do so.

That looks as an error in tcl scripts, but 100% i'm not sure.

Statistics: Posted by KrzychuG — Fri Jun 04, 2004 4:34 pm

Egg 1.6.16 continuosly dead

2004-06-04T16:05:31-04:00

IMHO 1.6.16 is bugged

I have 17 v1.1.16 eggies running under *BSD and RH EL, I also have 2 v1.1.16 windrops running under .NET Server 2003 and I get none of what cucciolo is apparently experiencing.

Causes: A script? A setting change on his shell? Disk quota full maybe?

Statistics: Posted by Alchera — Fri Jun 04, 2004 4:05 pm

Egg 1.6.16 continuosly dead

2004-06-04T11:54:05-04:00

After the last process automatically dead,
i'm back to 1.6.15

IMHO 1.6.16 is bugged

Thanks to all for support

Statistics: Posted by cucciolo — Fri Jun 04, 2004 11:54 am

Egg 1.6.16 continuosly dead

2004-06-03T14:04:24-04:00

i'll do it
tnx

this is the result.
On partyline :
[03.06.04 @ 20.10] <)PARTYLINE> [11:10] * Last context: tclhash.c/688 []
[03.06.04 @ 20.10] <)PARTYLINE> [11:10] * Please REPORT this BUG!
[03.06.04 @ 20.10] <)PARTYLINE> [11:10] * Check doc/BUG-REPORT on how to do so.

After, on IRC
[03.06.04 @ 20.12] *** BOTTEST (######@??.???.??.??) è uscito dal canale IRC (Ping timeout)

The process is up but with a very high CPU LOAD (77% !!)
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
BOTTEST 93251 77.1 0.7 3968 3472 p1 R 10:57AM 5:39.99 ./eggdrop bt.conf (eggdrop-1.6.16)

???

Statistics: Posted by cucciolo — Thu Jun 03, 2004 2:04 pm

Egg 1.6.16 continuosly dead

2004-06-03T12:33:20-04:00

How can i set a DEBUG LOG?
How can i see if the problem is for a TCL or egg ?

Compile using "make debug" instead of just "make". Remove all TCL scripts and start the eggdrop (1.6.16), if it works blame your scripts.

Statistics: Posted by dollar — Thu Jun 03, 2004 12:33 pm

Egg 1.6.16 continuosly dead

2004-06-03T12:14:40-04:00

If you can tell me how can i make a debug file, i can try it.
I'm not a Egg Guru : i have reported my problem with this version just for see if somebody have the same problem. I don't know how to set a debug : i have "stupidly" compiled like i make from years...and always work.
How can i set a DEBUG LOG?
How can i see if the problem is for a TCL or egg ?
All i know is that the process ends for EOF...
I'm sorry but i'm not advanced : i only see that all my eggs with 1.6.16 dead while i'm back to 1.6.15 all works fine so , i suppose, there's something in 1.6.16 that kill my eggs.
Simply not ?

Statistics: Posted by cucciolo — Thu Jun 03, 2004 12:14 pm

Egg 1.6.16 continuosly dead

2004-06-03T05:23:11-04:00

Yeah.. more info would be helpful. Is there a core file in the bot's directory? A DEBUG file? What network/server is your bot on?

Wcc

Statistics: Posted by Wcc — Thu Jun 03, 2004 5:23 am

Egg 1.6.16 continuosly dead

2004-06-02T19:49:01-04:00

too bad you dont include any actual info in your posts, or maybe we could have helped you...

Statistics: Posted by greenbear — Wed Jun 02, 2004 7:49 pm

Egg 1.6.16 continuosly dead

2004-06-02T19:10:51-04:00

Update.
No one more dead for EOF with 1.6.15.
I suppose 1.6.16 have something that don't go in the right way.
This is the 3 OS used :

1) FreeBSD 4.10-RELEASE (FreeBSD)
2) FreeBSD 4.10-PRERELEASE
3) Debian Adamantix

In all 3 *ALL* process dead for EOF e resurrect thanks to crontab...

Statistics: Posted by cucciolo — Wed Jun 02, 2004 7:10 pm

Egg 1.6.16 continuosly dead

2004-06-02T16:23:57-04:00

is empty...
now i'm back to 1.6.15 and all works fine.
No more dead for EOF....
...what mistery...

Statistics: Posted by cucciolo — Wed Jun 02, 2004 4:23 pm

Egg 1.6.16 continuosly dead

2004-06-02T15:02:26-04:00

where i can find the log you say?

~logs

Also, in main folder where bot config is look for 'DEBUG'.

Statistics: Posted by Alchera — Wed Jun 02, 2004 3:02 pm