• Remote system is BUSY

    From Flavio Bessa@4:801/188 to All on Sat Jan 9 19:44:58 2021

    My system is working as a Hub, I run Mystic here.

    One of the nodes that connect to me runs Synchronet on Linux and uses
    binkd. Every now and then present the follwing message when I try to poll it:

    Remote system is BUSY

    What does it mean?

    --- Mystic BBS v1.12 A42 2019/02/01 (Windows/64)
    * Origin: Saturn's Orbit BBS - Rio de Janeiro, Brasil (4:801/188)
  • From Alan Ianson@1:153/757.2 to Flavio Bessa on Sat Jan 9 15:03:38 2021
    Re: Remote system is BUSY
    By: Flavio Bessa to All on Sat Jan 09 2021 07:44 pm

    Remote system is BUSY

    What does it mean?

    It is a busy signal.. :)

    It means your links available "maxservers ??" are busy ATM.

    It will probably be clear in a minute or two.

    Ttyl :-),
    Al

    ... Reality is for those who can't handle computers.
    --- SBBSecho 3.12-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)
  • From Flavio Bessa@4:80/1 to Alan Ianson on Sun Jan 10 15:49:52 2021
    On 09 Jan 2021, Alan Ianson said the following...

    It means your links available "maxservers ??" are busy ATM.

    It will probably be clear in a minute or two.

    Actually the remote system is responding BUSY to me since yesterday.

    In Mystic, usually it's due to a .BSY file that's left at semaphore directory after a crash.

    Does binkd has a similar directory?

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Fido R80 Internet Gateway (4:80/1)
  • From Alan Ianson@1:153/757.2 to Flavio Bessa on Sun Jan 10 11:40:34 2021
    Re: Re: Remote system is BUSY
    By: Flavio Bessa to Alan Ianson on Sun Jan 10 2021 03:49 pm

    Actually the remote system is responding BUSY to me since yesterday.

    That sounds like some stale .bsy files created by a tosser or binkd, I can't say.

    My binkd includes "kill-old-bsy 12h", so old .bsy files should be removed after 12 hours if they get left behind for some reason.

    In Mystic, usually it's due to a .BSY file that's left at semaphore directory after a crash.

    Yes, I have seen that.

    Does binkd has a similar directory?

    Yes, these .bsy files are created in the outbound by binkd or a tosser, the same as Mystic although binkd does not have a semaphore directory. I have never known binkd to leave stray .bsy files behind. I think that could happen in the case of an abnormal shutdown by a tosser or binkd, but I have never seen it.

    Ttyl :-),
    Al

    ... Why do we drive on parkways and park on driveways?
    --- SBBSecho 3.12-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)
  • From mark lewis@1:3634/12 to Flavio Bessa on Tue Jan 12 06:43:02 2021
    Re: Re: Remote system is BUSY
    By: Flavio Bessa to Alan Ianson on Sun Jan 10 2021 15:49:52


    Actually the remote system is responding BUSY to me since yesterday.

    In Mystic, usually it's due to a .BSY file that's left at semaphore directory after a crash.

    Does binkd has a similar directory?

    yes, the BSO is where those files are written by all binkp mailers... this is how/why you can run multiple binkp mailers all using the same BSO... they all use the same bsy/?lo/?ut files... if they see a bsy, they know the
    node with that address is ummm... busy...


    )\/(ark
    --- SBBSecho 3.11-Linux
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)