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)

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)

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)

SEEN-BY: 116/116 123/25 150 755 135/300 153/7715 154/10 261/38 3634/15 27 50 SEEN-BY: 3634/119 123/50 300/4 123/170 180 40 299/6 123/190 35 115 3634/12 0 SEEN-BY: 18/0 123/0 1/120

SEEN-BY: 3634/12 135/210 211 212 205 388 395 390 385 366 115 0

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)

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)

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)