1. Forum
  2. fsxNet
  3. FSX MYS

  • Having to kill fidopoll

    From PalKat@21:4/137 to All on Tue Feb 25 21:25:38 2020
    So I have been running the A45 for a week now and every 2-3 days my fidopoll still gets locked up being busy. After I issue a fidopoll killbusy it resumes just fine for 2-3 days till I have to killbusy again.

    So would creating an Event in mystic to run either hourly or daily and set
    the Shell of the event to "fidopoll killbusy" be a safe solution?

    I am just trying to think of the easiest way to get fidopoll to resume
    polling with out me having to go to the BBS machine daily to issue the
    fidopoll killbusy.

    This issue seems to have gotten more regular over the past few months, yet nothing has changed on my configuration of the BBS machine.

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
    * Origin: 8-Bit Boyz BBS! -=[ bbs.8bitboyz.com port:6502 ]=- (21:4/137)
  • From ryan@21:1/168 to PalKat on Tue Feb 25 20:56:04 2020
    So I have been running the A45 for a week now and every 2-3 days my fidopoll still gets locked up being busy. After I issue a fidopoll killbusy it resumes just fine for 2-3 days till I have to killbusy again.

    anything in logs? anything in your windows system event viewer?

    --- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
    * Origin: monterey bbs (21:1/168)
  • From g00r00@21:1/108 to PalKat on Wed Feb 26 11:57:18 2020
    fidopoll still gets locked up being busy. After I issue a fidopoll killbusy it resumes just fine for 2-3 days till I have to killbusy again.

    I've never had to do it even once in the past year or so that my BBS was on the Linux laptop that it was on. But thats in Linux so maybe it could be specific to Windows?

    Are you using [FileToss] by chance? Someone suggesting they think there is actually a problem with that function.

    Either way, any stale BSY file is removed after 2 hours so it seems like the issue could be something else.

    So would creating an Event in mystic to run either hourly or daily and
    set the Shell of the event to "fidopoll killbusy" be a safe solution?

    As long as you can guarentee that everything is offline as far as echomail goes, then that can work. Run fidopoll killbusy all when everything is shut down. But you have to make sure its actually shut down (MIS, fidopoll and MUTIL cannot be running - running this stuff when any of those things are running can cause this issue not help it)

    This issue seems to have gotten more regular over the past few months,
    yet nothing has changed on my configuration of the BBS machine.

    What version of Windows?

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/64)
    * Origin: Sector 7 (21:1/108)
  • From PalKat@21:4/137 to g00r00 on Tue Feb 25 22:26:22 2020
    On 26 Feb 2020, g00r00 said the following...

    Are you using [FileToss] by chance? Someone suggesting they think there is actually a problem with that function.

    Yes, my mailin.ini is using FileToss.

    What version of Windows?

    Windows 7 32bit. It is the same build I have been using for almost 3 years now.

    Is there something I should be looking for in the logs specific to this? if
    so which log file?

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
    * Origin: 8-Bit Boyz BBS! -=[ bbs.8bitboyz.com port:6502 ]=- (21:4/137)
  • From g00r00@21:1/108 to PalKat on Wed Feb 26 19:36:18 2020

    Are you using [FileToss] by chance? Someone suggesting they think th is actually a problem with that function.

    Yes, my mailin.ini is using FileToss.

    Thanks. I start with looking into FileToss a bit more as that was the only thing in any sort of recent time that had changes to the BSY file system.

    Is there something I should be looking for in the logs specific to this? if so which log file?

    No not really. The files should be fine on their own and even if they ever
    did get stuck they should unstick themselves after 2 hours, so something is going on here.

    I had a "busylog.txt" active for probably 2 years and in that time no one was reporting much of anything to me for many many months, so I recently removed it.

    Go figure! Now I don't have an easy way to diagnose if there is a potential issue or if its use error (like shutting down the system with mutil or fidopoll or a MIS BINKP connection, etc) or putting killbusy in a batch file.

    But we'll get to the bottom of it! I've been recently rewriting some Windows side of the code that handles files that potentially have race conditions like this and it seems to have worked really favorably in other areas such as Bink queue files and ghost nodes - so its time to see what I can do with BSY files too.

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/64)
    * Origin: Sector 7 (21:1/108)
  • From PalKat@21:4/137 to g00r00 on Wed Feb 26 11:37:42 2020
    On 26 Feb 2020, g00r00 said the following...

    Thanks. I start with looking into FileToss a bit more as that was the only thing in any sort of recent time that had changes to the BSY file system.

    No not really. The files should be fine on their own and even if they ever did get stuck they should unstick themselves after 2 hours, so something is going on here.

    The only other thing I could think of causing issue is the windows 7 VM. But the server running the VM does not show that VM being power cycled/restarted abruptly let alone during the time fidopoll is locked up busy. That server
    is also my PLEX server so I know its on 24/7 and sits in my office so I know
    no one is messing with it.

    I had a "busylog.txt" active for probably 2 years and in that time no
    one was reporting much of anything to me for many many months, so I recently removed it.

    Go figure! Now I don't have an easy way to diagnose if there is a potential issue or if its use error (like shutting down the system with mutil or fidopoll or a MIS BINKP connection, etc) or putting killbusy in
    a batch file.

    hahaha, go figure...I often tell folks I have the same luck as Homer Simpson and once again this proves it.

    But we'll get to the bottom of it! I've been recently rewriting some Windows side of the code that handles files that potentially have race conditions like this and it seems to have worked really favorably in
    other areas such as Bink queue files and ghost nodes - so its time to
    see what I can do with BSY files too.

    Well I appreciate (like many others) all the work you do on this! And for listening/looking into my current fidopoll issue.

    I will wait with much anticipation for a future release that might help this, in the mean time anything else you need me to look at on my end or you need
    to just let me know.

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
    * Origin: 8-Bit Boyz BBS! -=[ bbs.8bitboyz.com port:6502 ]=- (21:4/137)