View Issue Details

IDProjectCategoryView StatusLast Update
0003415unrealircdpublic2015-10-28 17:32
Reportervonitsanet Assigned Tosyzop  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version3.2.6 
Summary0003415: LEAF server bug?
DescriptionI saw a strange bug yesterday..

1)Connect a leaf to a hub server (defined as leaf on hub .conf)
2)Connect another server to the leaf server and the hub server will squit the leaf server
3)Now try to connect the leaf again without another server behind it. It will not connect with "server exist" error.

I dont have a log right now but next time it happened i'll post it.
3rd party modules

Activities

vonitsanet

2007-07-04 15:48

reporter   ~0014439

Okay.. Here we are...
I'm oper on SERVER3 and i see these:

(SNotice) Lost connection to SERVER1[xx.xx.xx.xx]: SSL_read(): Underlying syscall error

(SNotice) (link) Secure ZIPlink SERVER2 -> SERVER1[@xx.x.xx.xx.53527] established (SSLv3-AES256-SHA-256bits)

(SNotice) *** LocOps -- Link SERVER2 cancelled, is Non-Hub but introduced Leaf SERVER1

(SNotice) *** Notice -- Connection to SERVER1[xx.xx.xx.xx] activated.

(SNotice) *** Notice -- (link) Secure ZIPlink SERVER3 -> SERVER1[@xx.xx.xx.xx.58724] established (SSLv3-AES256-SHA-256bits)

(SNotice) (link) Secure ZIPlink SERVER1 -> SERVER3[@xx.xx.xx.xx.0] established (SSLv3-AES256-SHA-256bits)

(SNotice) *** LocOps -- ERROR :from SERVER1[xx.xx.xx.xx] -- Server SERVER3 already exists from SERVER3

(SNotice) *** LocOps -- ERROR :from SERVER1[xx.xx.xx.xx] -- Closing Link: [xx.xx.xx.xx] (Server Exists)

(SNotice) Lost connection to SERVER1[xx.xx.xx.xx]: SSL_read(): Underlying socket operation returned zero

syzop

2015-10-28 17:31

administrator   ~0018812

Tried your exact scenario and can't reproduce on 4.0.0-rc2 so must have been fixed.

Issue History

Date Modified Username Field Change
2007-07-04 09:19 vonitsanet New Issue
2007-07-04 15:48 vonitsanet Note Added: 0014439
2007-07-04 16:15 stskeeps Status new => acknowledged
2015-10-28 17:31 syzop Note Added: 0018812
2015-10-28 17:31 syzop Status acknowledged => closed
2015-10-28 17:32 syzop Assigned To => syzop
2015-10-28 17:32 syzop Resolution open => fixed