1. Forum
  2. Fidonet
  3. MYSTIC

  • Is fsxnet down

    From Richard Fairman@3:770/3 to All on Mon Nov 25 02:33:54 2019
    I'm getting node busy errors on two fsxnet nodes and havnt had an info pack since 10 November Is it a problem from my end that I can fix?
    If it on the fsxnet end i will be patient as fsxnet is a great network

    Richard

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Jeff Smith@1:14/6 to Richard Fairman on Mon Nov 25 07:17:31 2019
    Hello Richard!

    25 Nov 19 02:33, you wrote to all:

    I'm getting node busy errors on two fsxnet nodes and havnt had an info pack since 10 November Is it a problem from my end that I can fix? If
    it on the fsxnet end i will be patient as fsxnet is a great network

    Fsxnet as a net? No, as I can connect fine to my Fsxnet feed for mail and files. Could one or both of the systems you referenced being having a
    problem? Possibly.

    Seems it would be prudent to contact one or both systems to acertain their status. Either via netmail IF connecting is still possible or email if a
    direct connection isn't possible at the moment.

    Jeff


    --- Mystic v1.12 A43 (2019/03/02) GoldED+/LNX 1.1.5-b20170303
    * Origin: The Twisted Balloon - bbs.twisted-balloon.org (1:14/6)
  • From Oli@2:280/464.47 to Richard Fairman on Mon Nov 25 16:10:41 2019
    I'm getting node busy errors on two fsxnet nodes and havnt had an info pack since 10 November Is it a problem from my end that I can fix? If
    it on the fsxnet end i will be patient as fsxnet is a great network

    As Jeff said, it's not a general fsxnet problem. From the info you provided it's not clear what kind of busy error you are getting. It could be a .bsy file
    on your machine, which would prevent Maystic to connect at all (look in the oubound directory) or it could be a remote busy error (The connection is established, but then the remote sends an M_BSY command and disconnects).

    If we should forward a message from you to one of the nodes let us know.


    * Origin: kakistocracy (2:280/464.47)
  • From Richard Fairman@3:770/3 to All on Mon Nov 25 07:34:20 2019
    Thanks Avon and Dan are looking in to it for me

    Regards

    Richard

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Richard Fairman@3:770/3 to All on Mon Nov 25 08:26:17 2019
    Thanks for the help now fixed I found 2 .bsy files in the echomail out directory I assume they should have been cleared down as part of a mutil mailin
    routine. I also found a .fol file and a .sue file Not sure what those are for

    Any way thanks to all including Avon and Dan

    Regards

    Richard

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Jeff Smith@1:282/1031 to Richard Fairman on Mon Nov 25 11:58:06 2019
    Hello Richard,

    Thanks for the help now fixed I found 2 .bsy files in the echomail out
    directory I assume they should have been cleared down as part of a mutil maili
    routine. I also found a .fol file and a .sue file Not sure what those are for

    Occasionally Mystic here has had an issue with stale .bsy files. When the problem occurs it is related to a dropped connection from a non-Mystic remote system that incorrectly ending the connection. In the interim I have added language to my bash file(s) that control Mystic functions to manage the .bsy files.


    Jeff

    --- BBBS/Li6 v4.10 Toy-4
    * Origin: Fidonet: The Ouija Board - Anoka, MN - bbs.ouijabrd.net (1:282/1031)