Hi All,

I have installed Mystic on my Raspberry Pi, and i have problems with Mutil
when tossing this is what i see into my log files how can this be fixed ?

----------------- MUTIL v1.12 A31 Fri, Jan 06 2017 (loglevel 1)
+ Jan 06 07:43:52 Startup using mutil.ini
+ Jan 06 07:43:52 Process: Importing EchoMail
+ Jan 06 07:44:52 Results: Cannot import. Some nodes are BUSY in 60.27s
! Jan 06 07:44:52 Status: FATAL
+ Jan 06 07:44:52 Process: Exporting EchoMail
! Jan 06 07:45:52 Cannot export. Some nodes are BUSY
+ Jan 06 07:45:52 Results: Cannot export. Some nodes are BUSY in 60.11s
! Jan 06 07:45:52 Status: FATAL

Thanks!

Rudi

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: X-TReMe BBS (2:292/140)

On 01/06/17, Rudi Timmermans pondered and said...

I have installed Mystic on my Raspberry Pi, and i have problems with
Mutil when tossing this is what i see into my log files how can this be fixed ?

Rudi try

./fidopoll killbusy all

Then try again :)

Best, Paul

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

Hi Paul,

On 01/06/17, Rudi Timmermans pondered and said...
Rudi try
./fidopoll killbusy all
Then try again :)

Thanks ! Yes i have done that but i have this problem more then ones a day so i'm think i will add that command to my events.

I think it's comming that i use one point number for myself, and everytime i run the event ./fidopoll send i'm keep this bsy file, so i dont know if i do everytime with the event killbusy all that my mail for my point number is still
there and i get this on my point number when i poll with that?

Rudi

--- BBBS/Li6 v4.10 Toy-3
* Origin: Prism bbs (1:261/38)

Rudi Timmermans wrote to All <=-

Hi All,

I have installed Mystic on my Raspberry Pi, and i have problems with
Mutil when tossing this is what i see into my log files how can this be fixed ?

----------------- MUTIL v1.12 A31 Fri, Jan 06 2017 (loglevel 1)
+ Jan 06 07:43:52 Startup using mutil.ini
+ Jan 06 07:43:52 Process: Importing EchoMail
+ Jan 06 07:44:52 Results: Cannot import. Some nodes are BUSY in
60.27s ! Jan 06 07:44:52 Status: FATAL
+ Jan 06 07:44:52 Process: Exporting EchoMail
! Jan 06 07:45:52 Cannot export. Some nodes are BUSY
+ Jan 06 07:45:52 Results: Cannot export. Some nodes are BUSY in
60.11s ! Jan 06 07:45:52 Status: FATAL

Hi Rudi,
you have to run ./fidopoll killbusy command.

Tony

... DalekDOS v(overflow): (I)Obey (V)ision impaired (E)xterminate
--- MultiMail/Darwin v0.49
* Origin: = Laser BBS = London = mbse.laserbbs.co.uk:2323 = (2:250/5)

Hi Tony,

you have to run ./fidopoll killbusy command.

Yes i know, i have changed my events that it run before a poll toss en after now everything works fine ;

Thanks!

Rudi

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: X-TReMe BBS (2:292/140)

On 01/06/17, Rudi Timmermans pondered and said...

you have to run ./fidopoll killbusy command.

Yes i know, i have changed my events that it run before a poll toss en after now everything works fine ;

The idea behind the bsy files is to prevent a process from running before another has finished correctly.

[snip]

+ MUTIL now creates a mutil.bsy file in the semaphore directory. If this file
exists, MUTIL will refuse to run - preventing multiple instances of MUTIL
to
be executed at the same time. If the BSY file has existed for more than a
day, MUTIL will remove it and run as expected.

+ FIDOPOLL now creates a "fidopoll.bsy" in the Semaphore directory while its
running. This works in the same way as MUTIL does to prevent multiple
instances of itself from running.

+ MIS now creates a "mis.bsy" in the Semaphore directory while its running.
This works the same way as MUTIL and FIDOPOLL to prevent multiple instances
of itself from being executed.

+ FIDOPOLL and MIS BINKP now use a .BSY file system. These files are created
alongside the .out files when queuing and sending mail for a node. If the
.BSY file already exists for that node, Mystic will not queue mail for that
node. If the .BSY file is more than a day old, Mystic will assume the .BSY
file was accidentally left over from a stopped process and will exchange
mail for that node as requested.

+ MUTIL echo export will now create and check for .BSY flags when exporting
messages. It will wait for up to 3 minutes for all downlinks to NOT be
busy prior to exporting, while flagging any echomail nodes as owned by
MUTIL as they become freed up by other processes. This continues until
MUTIL "owns rights" to every echomail node, so that it can toss mail
without
interfering with any other mail process (BINKP server, client, FTP, etc).

If the 3 minutes expire, MUTIL will exit because it cannot process mail
when
nodes are exchanging by BINKP/FTP. MUTIL will not remove semaphores in
this
case, so the cycle can continue until the export is processed successfully.

Like other areas, if a .BSY flag stays for more than a day, it will
automatically be removed and assumed to be a result of a stuck process.

This system works hand in hand with BINKP server and FIDOPOLL (and even
BINKD) so that no nodes will transfer mail when MUTIL is tossing mail
to them, and MUTIL will not toss mail while a node is picking up mail.

[snip]


and

[snip]

+ FIDOPOLL now has a "killbusy" command which will delete any existing .bsy
flags for all echomail nodes. Note that this does not remove the program
specific bsy files for MUTIL, MIS, FIDOPOLL, etc, just the echomail nodes.

For now you can also run "killbusy all" and it will kill even the .BSY
flags for the various tools such as MIS MUTIL and FIDOPOLL. But this is
undocumented and HIGHLY NOT RECOMMENDED to use. In no circumstance should
a .BSY file ever be removed when MUTIL MIS or FIDOPOLL is running. This is
a convience feature because the BSY system is new and may have quirks.

[snip]

Use of fidopoll killbusy all is *not* recommended as part of a batch file
etc to try and fix a bigger problem.

Best, Paul

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

Rudi Timmermans wrote to Tony Comandini:

Hi Tony,

you have to run ./fidopoll killbusy command.

Yes i know, i have changed my events that it run before a poll toss en after
now everything works fine ;

Oh...nice hear thas Rudi...probably there were too much process running in the same time and the RPI was struggeling mades semaphores :-)


Greetings, Tony Comandini

... "Luke... Luke... Use the MOUSE, Luke" - Obi Wan Gates

--- MBSE BBS v1.0.6.9 (GNU/Linux-x86_64)
* Origin: = Laser BBS = London = mbse.laserbbs.co.uk:2323 = (2:250/5)

Hi Paul,

Use of fidopoll killbusy all is *not* recommended as part of a batch file etc to try and fix a bigger problem.

I have also read this into the docs, but Mystic was running fine for a few
days here on the Raspberry PI, but after a few days my message base got bad
and i lost everything i have remove and remake all echo area's again and have done a rescan on my hub, so everything is ok with that, but this .bsy file keeps getting me problems i dont run a telnet nodes or other nodes only as a mailer no BBS local use only for myself. So this .bsy keep comming back everythime here i dont know why ... so now a run this killbusy all options
into my events otherway's it dont works here.

I need to wait till James is back so i can talk to him.

Thanks again for the helps!

Rudi

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: X-TReMe BBS (2:292/140)

Hi Tony,

Oh...nice hear thas Rudi...probably there were too much process running
in the same time and the RPI was struggeling mades semaphores :-)

Look on my reply to Paul what was happen here, i know the solution i use now
is also not good, and i dont know why i getting this .bsy files always on the Raspbery PI, I run only one task that's MIS as BINKP mailer no BBS just that, the only thing i have is my own point number and what i have see is when i
use the orginal events fidopoll forced that fidopoll always try to get out
the mail to my point number but he can not do that becoss there is no host configuret into the config. So i think it's that's cause the problem but i
can not found the correct info anywhere how to config a correct point number into Mystic so i have set my point number under nodes as i think that's the correct way...

Rudi

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: X-TReMe BBS (2:292/140)

On 01/06/17, Rudi Timmermans said the following...

Hi Paul,

Use of fidopoll killbusy all is *not* recommended as part of a batc file etc to try and fix a bigger problem.

I actually run a Windows logoff script when it does its scheduled two week server restart, and the only thing I've found that's "kill-friendly" for MIS
is just Windows' taskkill without the /f switch. It works, and until I
started using that recently I just restarted the VM with MIS still running.

Since it might have had semaphores still extant, I would also run the
killbusy on server restart. taskkill seems a lot more graceful than just popping MIS out of existence on restart, but I'm always a bit worried that those semaphores still remain. Hence, I still have killbusy on the startup script.

No issues that I've seen, and it's been like that on my server since g00r00 implemented it. Of course, I have it run before MIS is started back up, so maybe the possible issue was running it while MIS was up? Not sure.

--- Mystic BBS v1.12 A31 (Windows)
* Origin: http://www.throwbackbbs.com -\- meriden, ct -\- (1:142/799)