Hello all. Something weird is happening on my system with A34 . When I run MUTIL it keeps saying "Waiting for busy nodes" even though I do a FIDOPOLL KILLBUSY. Any ideas what may be wrong? Thanks.

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 07/10/17, Necromaster said the following...

Hello all. Something weird is happening on my system with A34 . When I run MUTIL it keeps saying "Waiting for busy nodes" even though I do a FIDOPOLL KILLBUSY. Any ideas what may be wrong? Thanks.

I've had that same problem. Check the echomail in and out directory. If mis.bsy is here, just remove it and run fidopoll again.

Thanks!
Orbitman (Allen)
telnet://orbitbbs.ddns.net:7210
Opp, Alabama, USA

--- Mystic BBS v1.12 A34 (Linux/32)
* Origin: Orbit BBS--telnet:orbitbbs.ddns.net:7210 (AL) (21:2/131)

On 07/09/17, Orbitman pondered and said...

Thanks!

FIDOPOLL KILLBUSY. Any ideas what may be wrong? Thanks.

I've had that same problem. Check the echomail in and out directory. If mis.bsy is here, just remove it and run fidopoll again.

im on the road but cant help check in :-)

i would not delete that but try fidopoll killbusy all

best Paul

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

I've had that same problem. Check the echomail in and out directory. If mis.bsy is here, just remove it and run fidopoll again.

Thanks I will try that.

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Well it's still saying "Waiting on busy nodes" for both echomail import and export. I ran fidopoll killbusy all but nothing. I wonder what could be wrong? :(

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Well it's still saying "Waiting on busy nodes" for both echomail import and export. I ran fidopoll killbusy all but nothing. I wonder what
could be wrong? :(

Try to remove the files out of your semaphore directory. If killbusy can't remove busy files then that would imply that either you don't have access rights to those files or that there really is another process open using those files.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 07/10/17, Necromaster said the following...

Hello all. Something weird is happening on my system with A34 . When I run MUTIL it keeps saying "Waiting for busy nodes" even though I do a FIDOPOLL KILLBUSY. Any ideas what may be wrong? Thanks.

Suggest doing the command:
fidopoll killbusy all

This will clear all bsy files even for your nodes.

Cheers!
Pequito

--- Mystic BBS v1.12 A34 (Linux/32)
* Origin: Twinkle BBS # (21:1/126)

On 07/11/17, Necromaster said the following...

Well it's still saying "Waiting on busy nodes" for both echomail import and export. I ran fidopoll killbusy all but nothing. I wonder what
could be wrong? :(

fidopoll killbusy all did nothing for me either. I just removed the mis.bsy files and it went back to work. Won't hurt it. Try using MIS 2 for telnet
and MIS for binkp. Since I started doing that, haven't seen that issue
anymore.

Thanks!
Orbitman (Allen)
telnet://orbitbbs.ddns.net:7210
Opp, Alabama, USA

--- Mystic BBS v1.12 A34 (Linux/32)
* Origin: Orbit BBS--telnet:orbitbbs.ddns.net:7210 (AL) (21:2/131)

On 07/11/17, Night Stalker pondered and said...

On 07/10/17, Necromaster said the following...

Hello all. Something weird is happening on my system with A34 . Whe run MUTIL it keeps saying "Waiting for busy nodes" even though I do a FIDOPOLL KILLBUSY. Any ideas what may be wrong? Thanks.

fidopoll killbusy all so it checks all outbound for .bsy files

I do that before running MUTIL and it does clear them. But once MUTIL is ran it creates all those .bsy files in various echo message areas in outbound and keeps returning that waiting on busy nodes messages and does not import or export anything. It was working fine.

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Hello g00r00, sorry to bother you. Is Mutiul suppose to create all these
.bsy files in the network message areas? I run Fidopoll killbusy all just before mutil and it clears these .bsy files but once Mutil is ran they are created again and that's when I get that waiting on busy nodes messages. Thanks.

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 07/13/17, Necromaster said the following...

Hello g00r00, sorry to bother you. Is Mutiul suppose to create all these .bsy files in the network message areas? I run Fidopoll killbusy all
just before mutil and it clears these .bsy files but once Mutil is ran they are created again and that's when I get that waiting on busy nodes messages. Thanks.

If I am not mistaken it is fidopoll that creates those .bsy files you are speaking about, after you run a fidopoll forced to check and poll nodes add a fidopoll killbusy all before mutil and should be OK.

Sounds like one or more of your nodes is hanging and causing a problem.

Cheers!
Pequito

--- Mystic BBS v1.12 A34 (Linux/32)
* Origin: Twinkle BBS # (21:1/126)

If I am not mistaken it is fidopoll that creates those .bsy files you are speaking about, after you run a fidopoll forced to check and poll nodes add a fidopoll killbusy all before mutil and should be OK.

Sounds like one or more of your nodes is hanging and causing a problem.

Cheers!

I run fidopoll killbusy all before Mutil and it keeps doing the same thing.
I have checked to make sure no nodes are active and nothing. This is weird. The only way I can get mutil to do it's job is to open 2 CMD and run mutil in one then on the other I run fidopoll killbusy twice and it works.

--- Mystic BBS v1.12 A34 (Windows/64)
* Origin: Necronomicon BBS - necrobbs.strangled.net (21:1/122)

Remove bsy files. You either have stuck bsy files, permission issues, or you are actually running fidopoll.

In my Linux scripts I delete the fidopoll bsy on my hourly mail processing script.

Most of my scripts are semaphore enabled so, if something is causing that's it's a stuck process and can simply be fixed with a rm -f fidopoll.bsy in
your semaphore dir (that's Linux I don't care to see what windows is cause, well I hate windows)

My scripts and servers never get those errors because I check for them. You
can even get more fancy and only so it if it finds a fidopoll.bsy file
through bash or perl scripts.

:)

On 23:54 10/07 , Necromaster wrote:

Well it's still saying "Waiting on busy nodes" for both echomail import and >export. I ran fidopoll killbusy all but nothing. I wonder what could be >wrong? :(

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A34 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

On 07/15/17, Nugax pondered and said...

Remove bsy files. You either have stuck bsy files, permission issues, or you are actually running fidopoll.

I do have my scripts remove the .bsy file with fidopoll killbusy all.

It's weird, but if I remove the last three nodes I added, it seems to work fine. Once added again and I run MUTIL it does it again.

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 07/13/17, Necromaster said the following...

Hello g00r00, sorry to bother you. Is Mutiul suppose to create all these .bsy files in the network message areas? I run Fidopoll killbusy all
just before mutil and it clears these .bsy files but once Mutil is ran they are created again and that's when I get that waiting on busy nodes messages. Thanks.

Are you having collisions with multiple copies of fidopoll and/or mutil
running from events?

For mail processing you really only need to concern yourself with 2 events
that check for semaphores and only run when necessary

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: internal dimension ÷ idbbs.dlinkddns.com ÷ port 59 (21:1/178)