1. Forum
  2. Fsxnet Message
  3. FSX MYS

  • Event question/problem

    From Scarecrow@21:4/111 to All on Wednesday, May 15, 2019 06:44:36
    Now that I have FsxNet setup, I'm having a problem with the associated events. From fresh reboot and/or restart of mis, everything works fine with polling event firing off hourly and tossing working when needed. However after a
    random number of hours the polling event starts failing with a res:127 exit code in the logs. Once that error occurs the event continues to fail with
    that same error. Restarting mis fixes the problem temporarily with it coming back eventually. Might run fine for hours, or fail on the next run, no rhyme
    or reason. Running fidopoll and the associated mutil scripts from the commandline works every time. It appears it's the events that a misbehaving. Any suggestions are appreciated!

    Dave

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/32)
    * Origin: Blue Northern Software (21:4/111)
  • From Black Panther@21:1/186 to Scarecrow on Wednesday, May 15, 2019 13:20:59
    On 15 May 2019, Scarecrow said the following...

    Now that I have FsxNet setup, I'm having a problem with the associated events. From fresh reboot and/or restart of mis, everything works fine with polling event firing off hourly and tossing working when needed. However after a random number of hours the polling event starts failing with a res:127 exit code in the logs. Once that error occurs the event

    Make sure that your commands within the event editor start with the ./ for Linux. That is something that most people miss, including me. I'll see the error 127 when it tries running a command without the ./ so that might be the issue.


    ---

    Black Panther(RCS)
    a.k.a. Dan Richter
    Sysop - Castle Rock BBS
    telnet://bbs.castlerockbbs.com
    http://www.castlerockbbs.com
    The sparrows are flying again....

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)
  • From esc@21:1/112 to Scarecrow on Thursday, May 16, 2019 00:06:19
    Now that I have FsxNet setup, I'm having a problem with the associated events. From fresh reboot and/or restart of mis, everything works fine

    Hi, I noticed you're running mystic for linux, 32 bit. I recently tried installing the latest Mystic version on Ubuntu 18.04, 32 bit, and once I enabled cryptlib/ssh, it started crashing every time I tried running 'mis'. There's definitely a problem with this build. Try using the previous version and see if it does the same thing, maybe?

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Black Flag <ACiD Telnet HQ> blackflagbbs.com (21:1/112)
  • From Steve Wolf@21:4/10 to esc on Thursday, May 16, 2019 10:09:00
    Re: Event question/problem
    By: esc to Scarecrow on Thu May 16 2019 12:06 am

    Hi, I noticed you're running mystic for linux, 32 bit. I recently tried installing the latest Mystic version on Ubuntu 18.04, 32 bit, and once I enabled cryptlib/ssh, it started crashing every time I tried running 'mis'. There's definitely a problem with this build. Try using the previous version and see if it does the same thing, maybe?

    There are permission problems with Ubuntu 18.04. I had problems with Ubuntu server and Lubuntu 18.04. I don't run mystic but I'm having problems with Synchronet running on an a Upgraded Ubuntu 18.04 sever.

    Steve Wolf
    HusTler
    Havens BBS havens.synchro.net (1:267/160)



    Steven

    ---
    þ Synchronet þ Sent from The Haven BBS: havens.synchro.net
    * Origin: fsxNet FTN<>QWK Gateway (21:4/10)
  • From ernie@21:1/999 to Steve Wolf on Thursday, May 16, 2019 14:58:19
    Hi, I noticed you're running mystic for linux, 32 bit. I recently tri installing the latest Mystic version on Ubuntu 18.04, 32 bit, and onc enabled cryptlib/ssh, it started crashing every time I tried running 'mis'. There's definitely a problem with this build. Try using the previous version and see if it does the same thing, maybe?

    Have you considering trying a 64-bit build of Ubuntu? (or are you limited by the hardware?)

    I'm running Ubuntu 19.04 64bit and have MysticBBS running in an LXC
    container. Seems to be working fine in that environment.

    ---
    Ernest J Gainey III - LostCause Halfway House BBS
    telnet://bbs.lostcause.house
    http://bbs.lostcause.house

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: LostCause Halfway House (21:1/999)
  • From Scarecrow@21:4/111 to Black Panther on Wednesday, May 15, 2019 19:07:28
    Thanks, Dan. I'm away from the shop so can't easily check it right now, but I think you ate right, I don't have a path in front of the command. I'll
    verify it when I get back later tonight. Thanks for the help!

    Dave

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/32)
    * Origin: Blue Northern Software (21:4/111)
  • From esc@21:1/112 to Steve Wolf on Friday, May 17, 2019 00:06:18
    There are permission problems with Ubuntu 18.04. I had problems with Ubuntu server and Lubuntu 18.04. I don't run mystic but I'm having problems with Synchronet running on an a Upgraded Ubuntu 18.04 sever.

    I'm running ubuntu 64 bit with mystic just fine, so not sure what particular issue you might be dealing with. Can you elaborate?

    For me, the problems with mystic only exist with 32 bit Ubuntu 18.04.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Black Flag <ACiD Telnet HQ> blackflagbbs.com (21:1/112)
  • From esc@21:1/112 to ernie on Friday, May 17, 2019 00:07:14
    Have you considering trying a 64-bit build of Ubuntu? (or are you
    limited by the hardware?)

    I personally prefer 32 bit for a bbs - better doorgame compatibility in
    dosemu. I see no real reason to use 64 bits with a BBS.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Black Flag <ACiD Telnet HQ> blackflagbbs.com (21:1/112)