1. Forum
  2. FidoNet
  3. MYSTIC

  • disconnecting even if timeouts are disabled

    From Edmund Wong@1:153/7083 to All on Tue Apr 5 08:18:23 2022
    Hi, I'm using Mystic 1.12 A47 and for some reasons it's disconnecting/jumping back into the prompt when I log in using "mystic -l"

    I've disabled timeouts.

    In the log I see:

    ------------------- Node 1 (Mystic v1.12 A47 2021/12/01)
    2022.04.02 15:47:15 Connect from local (local)
    2022.04.02 15:47:18 ewong logged in
    2022.04.02 15:47:18 Setting time left to 9999
    2022.04.02 15:47:23 MPL execute: /home/bbs/mystic/themes/default/scripts/bulletin.mpx
    2022.04.02 15:48:36 Posted #219: "time.." to NetMsg
    2022.04.02 15:50:12 Scan for new files
    2022.04.03 17:52:03 Shutting down
    2022.04.03 17:52:03 Cannot writeh to /mystic/data/chat1.dat. Code=2, PID=1270


    Now IIRC, when I reported this last year, g00r00 made a new binary which I
    used that fixed the issue. Now the problem is... I don't remember if I had overwritten that A47 binary with public release of A47. Or whether this
    is a regression of some sort or whether I had messed up my upgrade and
    killed some configuration.

    Any clarifications appreciated,

    Thanks

    Edmund

    ... When cheese gets its picture taken, what does it say?

    --- Mystic BBS v1.12 A47 2021/12/01 (Linux/32)
    * Origin: Eagle's BBS (1:153/7083)
  • From g00r00@1:129/215 to Edmund Wong on Tue Feb 8 12:40:50 2022
    Hi, I'm using Mystic 1.12 A47 and for some reasons it's disconnecting/jumping back into the prompt when I log in using "mystic
    -l"

    2022.04.03 17:52:03 Cannot writeh to /mystic/data/chat1.dat. Code=2, PID=1270

    I do remember this problem but I don't remember what we did to fix it. I'll have to try to jog my memory somehow. It would be rare but not impossible for a fix to have somehow got rolled back.

    ... Origin of Life? Just check my refrigerator...

    --- Mystic BBS v1.12 A48 2022/02/03 (Windows/64)
    * Origin: Sector 7 * Mystic WHQ (1:129/215)
  • From g00r00@1:129/215 to Edmund Wong on Wed Feb 9 12:38:58 2022
    2022.04.03 17:52:03 Cannot writeh to /mystic/data/chat1.dat. Code=2, PID=1270

    I do remember this problem but I don't remember what we did to fix it. I'll have to try to jog my memory somehow. It would be rare but not

    I tried and tried to reproduce this with the latest version and I cannot seem to make it happen.

    I did notice in your origin line you are not using the final version of A47. Your version is dated December 1st 2021 and the final version should read December 25th 2021. If you still have this issue after upgrading lets dive deeper.

    ... DOS=HIGH? I knew it was on something...

    --- Mystic BBS v1.12 A48 2022/02/03 (Windows/64)
    * Origin: Sector 7 * Mystic WHQ (1:129/215)