Guys what's the cause of this error?


? 09 Jul 21:17:09 [57136] Secure AKA 1:317/2@fidonet busy, drop the session
+ 09 Jul 21:17:09 [57136] done (from 1:317/2@fidonet, failed, S/R: 0/0 (0/0 bytes))

Thanks, Paul

--- Mystic BBS v1.12 A26 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)

Hi Paul!

Saturday July 09 2016 you wrote to this area the following:

Guys what's the cause of this error?

Stale .bsy in your outbound.

Yours
Andrew Kolchoogin.

... Those who sacrifices freedom for security deserves neither
--- Pen on parchment
* Origin: -= Castle of Silence =- (2:5020/290.22)

Hi Paul!

09 Jul 2016 21:56, from Paul Hayton -> All:

Guys what's the cause of this error?
? 09 Jul 21:17:09 [57136] Secure AKA 1:317/2@fidonet busy, drop the session

You can limit the number of sessions.
I guess that happens when the other end reached the maximum sessions allowed. Simply retry at a later point in time.

CU, Ricsi

--- GoldED+/LNX
* Origin: Hardware Independent: Won't work on ANY hardware! (2:310/31)

On 07/09/16, Richard Menedetter pondered and said...

You can limit the number of sessions.
I guess that happens when the other end reached the maximum sessions allowed. Simply retry at a later point in time.

Just discovered the other end may be presenting the same address twice, could that lead to this error also?

Best, Paul

--- Mystic BBS v1.12 A26 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)

09 Jul 16 21:56, you wrote to All:

Guys what's the cause of this error?

? 09 Jul 21:17:09 [57136] Secure AKA 1:317/2@fidonet busy, drop the session
+ 09 Jul 21:17:09 [57136] done (from 1:317/2@fidonet, failed, S/R: 0/0

(0/0

bytes))

technically it is not an error... without more info it looks like there's a bsy
flag indicating the systems are in session...

i see this on one or two systems i connect with because they have more than one
domain and i've set up to try them on all... what happens is that my system makes two connections at the same time and one gets blocked similar to above...

it may be that one system or the other has a stuck bsy file... shut down binkd and delete all the bsy files... then restart binkd and all should be fine... if
the problem is on the remote end and this is what you are seeing, then they need to clean their bsy files as described...

)\/(ark

Always Mount a Scratch Monkey

... Waffles are no more than a vehicle for butter & syrup.
---
* Origin: (1:3634/12.73)

Hi Paul!

09 Jul 2016 22:43, from Paul Hayton -> Richard Menedetter:

I guess that happens when the other end reached the maximum
sessions allowed. Simply retry at a later point in time.

Just discovered the other end may be presenting the same address
twice, could that lead to this error also?

Could be ... honestly do not know ...

CU, Ricsi

--- GoldED+/LNX
* Origin: Life is a series of very rude awakenings (2:310/31)

On 07/09/16, mark lewis pondered and said...

technically it is not an error... without more info it looks like
there's a bsy flag indicating the systems are in session...

Hi Mark,

Thanks for all the info and thinking behind it.

I found the system was presenting the same aka twice, they removed it and the issue seemed to disappear.

Best, Paul

--- Mystic BBS v1.12 A27 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)

On 07/10/16, Richard Menedetter pondered and said...

Could be ... honestly do not know ...

They removed it and it seems to have worked :)

Thanks for the reply and your thoughts :)

Best, Paul

--- Mystic BBS v1.12 A27 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)

Hi Paul!

10 Jul 2016 21:50, from Paul Hayton -> Richard Menedetter:

They removed it and it seems to have worked :)

Great - so you solved the problem.

BTW I would have thought that BinkD is more intelligent than to let you enter two identical addresses ... was it really BinkD that the other party used??

CU, Ricsi

--- GoldED+/LNX
* Origin: Plankton lobbyist: "NUKE THE WHALES!" (2:310/31)

10 Jul 16 21:47, you wrote to me:

technically it is not an error... without more info it looks like
there's a bsy flag indicating the systems are in session...

Thanks for all the info and thinking behind it.

you're welcome...

I found the system was presenting the same aka twice, they removed it
and the issue seemed to disappear.

that makes sense... the real question is how/why was a system presenting the same address more than once... i can maybe see that in a text file based config
like binkd but most all others use a configuration program of some sort and you'd think that they'd check for dupes in cases like this...

anyway, glad you figured it out :)

)\/(ark

Always Mount a Scratch Monkey

... Let joy keep you. Reach out your hands and take it when it runs by.
---
* Origin: (1:3634/12.73)

On 07/10/16, Richard Menedetter pondered and said...

BTW I would have thought that BinkD is more intelligent than to let you enter two identical addresses ... was it really BinkD that the other
party used??

No it was a Mystic system...

--- Mystic BBS v1.12 A27 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)