~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
+FreefallHeavens
+Over
+Xeha
+bak83
+cancername
+cumlord
+hk
+poriori
+profetikla
+uop23ip
+weko
An0nm0n
Arch
Danny
DeltaOreo
Irc2PGuest52850
Irc2PGuest53061
Irc2PGuest88897
Meow
Nausicaa
Onn4l7h
Onn4|7h
T3s|4
acetone_
anu
boonst
enoxa
mareki2pb
not_bob_afk
plap
shiver_
simprelay
solidx66
u5657
T3s|4_
dr|z3d: if you're about; had a horrible time connecting to IRC recently with many `you java.net.NoRouteToHostException: Unsupported encryption options`. Is either postman's or echelon's servers unstable atm?
dr|z3d
T3s|4: sounds like an issue with dual leasesets. we had that before, sounds like segmented dbs has brought it back.
dr|z3d
elg/ecies
T3s|4_
alright dr|z3d - I've only seen it on one rig (so far) with only ecies enabled...but I'll let you know
eyedeekay
I've seen it too, should be able to fix it at the same time I fix the lifecycle stuff zzz filed
eyedeekay
It's basically the same bug
dr|z3d
sorry, probably a thing with old dsa leasesets being served as a placeholder rather than dual crypto, no, eyedeekay?
dr|z3d
eyedeekay: can we get those patches into the master branch a bit quicker, and ideally not all at once? more eyes on them then? :)
dr|z3d
I've been cherrypicking various merge proposals ahead of them appearing in master, but that's less than ideal.
dr|z3d
I've also provisionally moved all RI lookups to mainNetDb()
eyedeekay
The lifecycle stuff is the hardest part but I'm almost there, I'll probably merge all the other memory management stuff before that though
T3s|4_
thanks eyedeekay and dr|z3d - I just reverted the problematic rig/IRC tunnel to ecies only - and it finally re-connected, so I cannot reproduce the error 100% of the time
dr|z3d
T3s|4: we had the same issue before I think, well, different cause, same effect. DSA leasesets conflicting with newer leasesets.
dr|z3d
postman said he'd reported the issue, locally it mainifests as errors about leaseset keys not matching.
eyedeekay
Yeah I have to make the dbid always match the primary session then it should go away
eyedeekay
It's looking in the wrong bucket
T3s|4_
dr|z3d: I've been on the latest 23+ for 1-2 days on this rig with only eices; despite several kernel upgrade reboots in the interim. Never saw that IRC connection ^error until today, but was able to connect to quite a few IRC sessions without issue
dr|z3d
Yeah, I don't think it's controversial to say that the new segmented db stuff is a bit of a monster, T3s|4 :)
T3s|4
np dr|z3d - if it's a problem worth sorting, who knows what other interesting things might be learned along that path :)