View Issue Details

IDProjectCategoryView StatusLast Update
0002319unrealdocumentationpublic2006-04-16 18:38
Reporter_JaCE Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version3.2.2 
Summary0002319: [BUG] trying to add fd #-1 to 0x814a0e0 (0x814e8c0/0x814b200/0x814a0e0/0x814d8a0), range is 0..1024
Description[BUG] trying to add fd #-1 to 0x814a0e0 (0x814e8c0/0x814b200/0x814a0e0/0x814d8a0), range is 0..1024

im gettin that when try to link 2 diff servers one free bsd other fedora 2. both dropped off today, tryed to relink found they died, restarted, they died again w/ no error in ircd.log, started fresh "new install" and [BUG] trying to add fd #-1 to 0x814a0e0 (0x814e8c0/0x814b200/0x814a0e0/0x814d8a0), range is 0..1024 is the error i get when i start them. same config, and same setup as ive had and do have w/ the other 9 servers linked.

ty in advcance
3rd party modules

Activities

syzop

2005-02-03 15:23

administrator   ~0009009

Thanks, looks interesting.

Just to be clear, do you mean with 'they died' that the server actually crashed? If so, do you have (a) core file(s)?

paradigm

2005-05-08 23:18

reporter   ~0009905

I'm having the same basic problem trying to link a new server (Suse 9.1) to an established network (also suse9.1)

_JaCE

2005-05-09 16:12

reporter   ~0009909

na im sorry syzop i just found out that this shell company has a crontab to reboot the server every 15 mins.. i have never heard of bs like that b4 so i shut down that leaf. i am sorry for wasteing your time im sure you have better things to fix

_JaCE
RevolutionIrc.net

syzop

2005-05-09 16:33

administrator   ~0009911

that's ok, I figured it would be "just" (but an important / bad!) warning anyway :).

Issue History

Date Modified Username Field Change
2005-02-03 15:14 _JaCE New Issue
2005-02-03 15:23 syzop Note Added: 0009009
2005-05-08 23:18 paradigm Note Added: 0009905
2005-05-09 16:12 _JaCE Note Added: 0009909
2005-05-09 16:33 syzop Note Added: 0009911
2006-04-16 18:38 syzop Status new => closed
2006-04-16 18:38 syzop Resolution open => no change required