hi,

mutil is always telling me it can't perform what importing or exporting messages bcs some nodes are busy.

in the /echomail dir always 63 .bsy files showing up just in the second i
start mutil. also a mutil.bsy shows up in /semaphore - what i expect so far.

but the 63 .bsy files are creepy :)

i flushed the complete /echomail dir. mbbsutil -fixindex and mutil with
purging messages. all without effects. mutil starts, and hangs by busy nodes.

if i delete the 63 .bsy files by hand mutil will run from importing messages without errors to exporting messages and hangs again. if i also kill .bs
files in this step of mutils work it will do its job and export all messages.

is there a file or something else that is wrongly telling mutil node are polling right now?

what can i do, that my board can toss messages without my help by deleting
.bsy files?

need help - thx!

(:. BlackICE BBS <-> BlackICE.BBSIndex.com:23 <-> BlackICEbbs.de.vu .:) -----------------------------------------------------------------------------
twitter.com/BlackICEbbs - bbsfse.de.vu - bbs-list-europe.de.vu

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: BlackICE BBS (BlackICE.BBSindex.com:23) (2:240/8001)

On 12/25/17, Vitus Zeel said the following...

hi,

mutil is always telling me it can't perform what importing or exporting messages bcs some nodes are busy.

in the /echomail dir always 63 .bsy files showing up just in the second i start mutil. also a mutil.bsy shows up in /semaphore - what i expect so far.

One of the easiest vs by hand will be ./fidopoll killbusy, and if needed but should not be ./fidopoll killbusy all.

Hope this helps, happy holidays!
Pequito

--- Mystic BBS v1.12 A37 2017/12/23 (Linux/64)
* Origin: Twinkle BBS # (1:317/2)

One of the easiest vs by hand will be ./fidopoll killbusy, and if needed but should not be ./fidopoll killbusy all.
Hope this helps, happy holidays!

thx! but it helps not to solve my problem. the issue is, that mutil produces
at the start those .bsy files. mis is not running. no other mutil instance is running. if i start mutil it will create the 63 .bsy files.

ok now i can kill them faster with fidopoll killbusy - but finaly it didn't solve the problem.

anyway i'm very thankful for the hint.

happy hollydays :)

(:. BlackICE BBS <-> BlackICE.BBSIndex.com:23 <-> BlackICEbbs.de.vu .:) -----------------------------------------------------------------------------
twitter.com/BlackICEbbs - bbsfse.de.vu - bbs-list-europe.de.vu

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: BlackICE BBS (BlackICE.BBSindex.com:23) (2:240/8001)

Hey Vitus Zeel,

I had an issue with the .bsy files as well. It started for me with a37. My only
option was to revert to a36 (which for me was just reinstalling everything from
scratch). I don't know why it kept happening, it didn't really make any sense. It was creating
these .bsy files even when there was no message traffic to route.

There may be a file in your mystic dir called "busylog.txt" - this could potentially shed some light on what's happening, but I don't know. Good luck!

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 12/26/17, Vitus Zeel said the following...

One of the easiest vs by hand will be ./fidopoll killbusy, and if nee but should not be ./fidopoll killbusy all.
Hope this helps, happy holidays!

thx! but it helps not to solve my problem. the issue is, that mutil produces at the start those .bsy files. mis is not running. no other
mutil instance is running. if i start mutil it will create the 63 .bsy files.

ok now i can kill them faster with fidopoll killbusy - but finaly it didn't solve the problem.

anyway i'm very thankful for the hint.

happy hollydays :)

My only other suggestion is to upgrade to a36 or a pre-alpha a37 which I know resolves this issue.

Cheers!
Pequito

--- Mystic BBS v1.12 A37 2017/12/23 (Linux/64)
* Origin: Twinkle BBS # (1:317/2)

Issue is solved.

I got a new node for fidonet. my NC told me by accident an aka that was
already busy with another bbs. so i had 2 different systems with the same aka.

to prevent issues like that it would be very nice if mystic could dupecheck AKAs in the config. A prompt "This AKA is already set up" or something like that.

I don't know how many nodes a avg. mystic board is serving. in case of the blackice bbs the list is very long. the boards servers many nodes and points from many networks and processes this year 1mio mails.

that means i have not all AKAs in a view and a prompt will help other sysops dealing with similar problems in the future.

(:. BlackICE BBS <-> BlackICE.BBSIndex.com:23 <-> BlackICEbbs.de.vu .:) -----------------------------------------------------------------------------
twitter.com/BlackICEbbs - bbsfse.de.vu - bbs-list-europe.de.vu

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: BlackICE BBS (BlackICE.BBSindex.com:23) (2:240/8001)

to prevent issues like that it would be very nice if mystic could dupecheck AKAs in the config. A prompt "This AKA is already set up" or something like that.

Done!

The next build will pop up a window that says "Address already exists (ID #)" after editing a node. The ID should help you quickly locate the node that has the conflict since you can just type in the node ID in the listbox to jump to it.

This will only happen when two nodes are marked as Active with the same address.

--- Mystic BBS v1.12 A37 2017/12/27 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)

On 12/28/17, g00r00 pondered and said...

Done!

The next build will pop up a window that says "Address already exists
(ID #)" after editing a node. The ID should help you quickly locate the

Good feature add - great suggestion too

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

Ryan Fantus wrote to All <=-

Hey Vitus Zeel,

I had an issue with the .bsy files as well. It started for me with a37.
My only
option was to revert to a36 (which for me was just reinstalling everything from scratch). I don't know why it kept happening, it didn't really make any sense. It was creating
these .bsy files even when there was no message traffic to route.

There may be a file in your mystic dir called "busylog.txt" - this
could potentially shed some light on what's happening, but I don't
know. Good luck!

Yeah, same thing here. Not sure why these files are appearing and I
thought that it was something on my end, but now that I see that the same
thing is happening to other Mystic sysops as well..

... Modern Latin: "Motorolus interruptus." (Hold on, I'm going into a tunnel.) ___ MultiMail/Win32 v0.50

--- Mystic BBS/QWK v1.12 A37 2017/12/28 (Windows/32)
* Origin: How about a piece of Pi? (1:116/18)

Christopher Malo wrote to Vitus Zeel <=-

On 12/26/17, Vitus Zeel said the following...

One of the easiest vs by hand will be ./fidopoll killbusy, and if nee but should not be ./fidopoll killbusy all.
Hope this helps, happy holidays!

thx! but it helps not to solve my problem. the issue is, that mutil produces at the start those .bsy files. mis is not running. no other
mutil instance is running. if i start mutil it will create the 63 .bsy files.

ok now i can kill them faster with fidopoll killbusy - but finaly it didn't solve the problem.

anyway i'm very thankful for the hint.

happy hollydays :)

My only other suggestion is to upgrade to a36 or a pre-alpha a37 which
I know resolves this issue.

I believe this issue STARTED with A37, unless there was something released very, very recently.

Cheers!
Pequito

--- Mystic BBS v1.12 A37 2017/12/23 (Linux/64)
* Origin: Twinkle BBS # (1:317/2)

... So easy, a child could do it. Child sold separately.
___ MultiMail/Win32 v0.50

--- Mystic BBS/QWK v1.12 A37 2017/12/28 (Windows/32)
* Origin: How about a piece of Pi? (1:116/18)

My only other suggestion is to upgrade to a36 or a pre-alpha a37 whic I know resolves this issue.

I believe this issue STARTED with A37, unless there was something
released very, very recently.

This was a known issue in an earlier version where the '.bsy' extension was left off when deleting a BUSY semaphore, but its not a known issue now. You would be the only one reporting it in current version (to my knowledge).

Of course if you kill 9 the servers, X out console windows, interrupt the mailer or tosser process on your own, force shutdowns of the OS with stuff still running (etc) you'll still end up seeing this issue... but those are all operator errors. If your server crashes that could cause it too.

Anyway, the point is that with typical operation its not a known issue, so let me know if it is for you and lets get it resolved. We're working hard to make the new server stable as can be before official release, and fsxNet is pushing it *hard* these days as you can see by this Status window of active concurrent BINKP connections:

SERVER USER STATUS ORIGIN
────── ─────────────── ───────────────────── ────────────────────────────
BINKP 21:1/154@fsxnet Raiders Inc BBS 68.103.73.149
BINKP 21:1/165@fsxnet Miskatonic BBS 80.181.77.178
BINKP 21:2/100@fsxnet Tholian fsxHUB [NET2] 108.204.225.235
BINKP 21:1/107@fsxnet The ByteXchange BBS 204.12.198.27
BINKP 21:1/141@fsxnet Pie33 107.170.38.150
BINKP 21:1/189@fsxnet Kernel Error Networks 2604:A880:0400:00D0::4BC4:10
BINKP 21:1/111@fsxnet Another Droid BBS 2.84.76.122
BINKP 21:1/173@fsxnet Sinclair Retro BBS 93.91.140.60
BINKP 21:1/186@fsxNET Castle Rock BBS 67.61.21.181
BINKP 21:1/172@fsxnet the facility bbs 173.170.129.51
BINKP 21:1/166@fsxnet DATANET 180.222.24.135
BINKP 21:1/150@fsxnet BadTaste-BBS 138.68.181.199
BINKP 21:1/176@fsxnet Radio Freqs & Geeks B 67.246.59.46

If there is a legit busy issue typically we'll see it pretty quickly on FSX because of the crazy load it puts on Mystic! :)

--- Mystic BBS v1.12 A37 2017/12/29 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)

g00r00 wrote to Warp 4 <=-

I believe this issue STARTED with A37, unless there was something
released very, very recently.

This was a known issue in an earlier version where the '.bsy' extension was left off when deleting a BUSY semaphore, but its not a known issue now. You would be the only one reporting it in current version (to my knowledge).

Yeah, it looks like it is ok now. It looks like it happens when MIS runs
the inbound mail tossing file when mail is downloaded. I run FIDOPOLL again when that is all done and it works just fine.

... MultiMail, the new multi-platform, multi-format offline reader!
___ MultiMail/OS/2 v0.50

--- Mystic BBS/QWK v1.12 A37 2017/12/28 (Windows/32)
* Origin: How about a piece of Pi? (1:116/18)

Done!

sounds perfect - thx!

(:. BlackICE BBS <-> BlackICE.BBSIndex.com:23 <-> BlackICEbbs.de.vu .:) -----------------------------------------------------------------------------
twitter.com/BlackICEbbs - bbsfse.de.vu - bbs-list-europe.de.vu

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: BlackICE BBS (BlackICE.BBSindex.com:23) (2:240/8001)