Suddenly Disconnecting from IRC

what · Post by **what** » Wed Jan 12, 2005 1:50 am

I have this problem with my eggie, it disconnted from my irc hannel to often sometimes it gaves me a bugg erorr...

[06:43] Disconnecting from server.
[06:44] Identd: Listening On Port 113, Replying as TheBoa***
[06:44] Trying server 193.109.122.77:6667
[06:44] Connected to 193.109.122.77
[06:44] -NOTICE- *** Looking up your hostname...
[06:44] -NOTICE- *** Checking Ident
[06:44] Identd: Connect from 193.109.122.77:1943...
[06:44] -NOTICE- *** Found your hostname
[06:44] Identd: Replied: 2000 , 6667 : USERID : UNIX : TheBoa90
[06:44] Identd: Disabled.
[06:44] -NOTICE- *** Got Ident response
[06:44] Identd Already Disabled. (Tried to Close)
[06:44] CTCP VERSION: from nlbot (monitor@monitor.efnet.nl)
[06:44] TheBoa joined #channel.

Alchera · Post by **Alchera** » Wed Jan 12, 2005 8:28 am

You're running a Windrop. It's possible the problem is due to connection problems with your ISP or a setting needs looking at again.

[06:43] Disconnecting from server

Normally there is another line before the above, sometimes "Server got stoned" etc, that should give you a clue also.

what · Post by **what** » Wed Jan 12, 2005 9:19 am

Alchera wrote:You're running a Windrop. It's possible the problem is due to connection problems with your ISP or a setting needs looking at again.
[06:43] Disconnecting from server
Normally there is another line before the above, sometimes "Server got stoned" etc, that should give you a clue also.

Hi thx for replaying...

Yes im running newest windrop and no im not getting any more line above that it just said disconnecting =(.

New issue

And now i found another prob i dont now if this has to do with windrop or dekuf script for raiden that im runing. When i join my irc channel then my bot says "[14:10] -Theboa- -RW- DeKuF on Mine Ftp Server. Welcome to #channel , use !Site help to view the avaliable commands, use !FuK_NFO to receive site nfo"

The prob is only i can see that mess, and only i can use !site trigger... as you sad maybe ive configured anything wrong

Edit: yes ive put couple of user in the bot and gave them flop flags and autoop in channel if that would help, but no it doesnt

Alchera · Post by **Alchera** » Wed Jan 12, 2005 10:01 am

There's a bug in a couple of the Cygwin libraries in the official Windrop package. You can download a 'bug' free copy from here. Re-visit Setting up an Eggdrop and then run it bare bones (no extra scripts other than those required to get Windrop up and running and connected). Keep an eye on it for a few days to make sure it's stable and then add your scripts.

what · Post by **what** » Wed Jan 12, 2005 11:31 pm

Alchera wrote:There's a bug in a couple of the Cygwin libraries in the official Windrop package. You can download a 'bug' free copy from here. Re-visit Setting up an Eggdrop and then run it bare bones (no extra scripts other than those required to get Windrop up and running and connected). Keep an eye on it for a few days to make sure it's stable and then add your scripts.

okey ill try that new one

here is more bugs the eggie gave me couple of min ago...

[04:20] * Last context: tclhash.c/688 []
[04:20] * Please REPORT this BUG!
[04:20] * Check doc/BUG-REPORT on how to do so.

De Kus · Post by **De Kus** » Thu Jan 13, 2005 6:01 pm

what wrote:okey ill try that new one

here is more bugs the eggie gave me couple of min ago...

[04:20] * Last context: tclhash.c/688 []
[04:20] * Please REPORT this BUG!
[04:20] * Check doc/BUG-REPORT on how to do so.

check the file "DEBUG", it should hopefully contain some debug code. if a custom tcl script is mentioned try to disabled it and the do as the message says ^-^.

btw. connection losts to IRC are most likly not the fault of the bot but of your ISP routing or the IRC server itself. at least my windrop has about the same problems as mIRC.

what · Post by **what** » Thu Jan 13, 2005 7:00 pm

De Kus wrote:
what wrote:okey ill try that new one

here is more bugs the eggie gave me couple of min ago...

[04:20] * Last context: tclhash.c/688 []
[04:20] * Please REPORT this BUG!
[04:20] * Check doc/BUG-REPORT on how to do so.
check the file "DEBUG", it should hopefully contain some debug code. if a custom tcl script is mentioned try to disabled it and the do as the message says ^-^.

btw. connection losts to IRC are most likly not the fault of the bot but of your ISP routing or the IRC server itself. at least my windrop has about the same problems as mIRC.

about the IRC disconnect prob, i found out that if i start the bot then both will crash... my mirc have been up now for almost a whole day without crashing why is that? cuse i never started eggdrop today. Ive installed the new one "http://www.ballarat.us/modules.php?name ... tit&lid=16" from there.

i dont know what to do if it start acts as the further one.

Alchera · Post by **Alchera** » Thu Jan 13, 2005 7:47 pm

De Kus wrote:check the file "DEBUG", it should hopefully contain some debug code. if a custom tcl script is mentioned try to disabled it and the do as the message says ^-^.

Kirben · Post by **Kirben** » Thu Jan 13, 2005 9:05 pm

Alchera wrote:There's a bug in a couple of the Cygwin libraries in the official Windrop package. You can download a 'bug' free copy from here. Re-visit Setting up an Eggdrop and then run it bare bones (no extra scripts other than those required to get Windrop up and running and connected). Keep an eye on it for a few days to make sure it's stable and then add your scripts.

What bug are you referring to ? the Windrop binaries were updated to resolve the DNS module issue (Caused by minires 1.0), as I mentioned in earlier thread.

what · Post by **what** » Fri Jan 14, 2005 2:04 am

De Kus wrote:
what wrote:okey ill try that new one

here is more bugs the eggie gave me couple of min ago...

[04:20] * Last context: tclhash.c/688 []
[04:20] * Please REPORT this BUG!
[04:20] * Check doc/BUG-REPORT on how to do so.
check the file "DEBUG", it should hopefully contain some debug code. if a custom tcl script is mentioned try to disabled it and the do as the message says ^-^.

btw. connection losts to IRC are most likly not the fault of the bot but of your ISP routing or the IRC server itself. at least my windrop has about the same problems as mIRC.

Here is the bugg ibe got 2mins ago

[07:00] * Last context: tclhash.c/684 [Tcl proc: trialcheck, param: $_time1 $_time2 $_time3 $_time4 $_time5]
[07:00] * Please REPORT this BUG!
[07:00] * Check doc/BUG-REPORT on how to do so.
[07:00] * Wrote DEBUG
[07:00] * SEGMENT VIOLATION -- CRASHING!

Debug (eggdrop v1.6.17) written Fri Jan 14 07:00:00 2005
Full Patch List:
Tcl library: C:/Windrop/lib/tcl8.4
Tcl version: 8.4.7 (header version 8.4.7)
Compile flags: gcc -pipe -mwin32 -g -O2 -Wall -I.. -I.. -DHAVE_CONFIG_H
Link flags: gcc -pipe -mwin32
Strip flags: strip
Context: tclhash.c/684, [Tcl proc: *raw:irc:315, param: $_raw1 $_raw2 $_raw3]
tclhash.c/688, []
tclhash.c/680, []
tclhash.c/684, [Tcl proc: <null>, param: $_raw1 $_raw2 $_raw3]
tclhash.c/688, []
tclhash.c/680, []
tclhash.c/684, [Tcl proc: *raw:303, param: $_raw1 $_raw2 $_raw3]
tclhash.c/688, []
tclhash.c/680, []
tclhash.c/684, [Tcl proc: *raw:303, param: $_raw1 $_raw2 $_raw3]
tclhash.c/688, []
tclhash.c/680, []
tclhash.c/684, [Tcl proc: *raw:303, param: $_raw1 $_raw2 $_raw3]
tclhash.c/688, []
tclhash.c/680, []
tclhash.c/684 [Tcl proc: trialcheck, param: $_time1 $_time2 $_time3 $_time4 $_time5]

SOCK ADDR PORT NICK HOST TYPE
---- -------- ----- --------- ----------------- ----
3 53E2D1F2 3333 (telnet) * lstn 3333
4 00000000 0 (dns) dns (ready)
10 53E2D1F2 4650 Nick chat flags: cPtEp/0
8 C1A3DC03 6661 (server) 193.163.220.3 serv (lag: 0)

Compiled without extensive memory debugging (sorry).
Open sockets: 3 (listen), 4 (passed on), 8, 10, 11 (file), done.