• Update A46 -> A47 -> A48

    From Memo@21:3/207 to All on Fri Oct 10 06:50:18 2025
    Due to an interesting tip, I updated my BBS yesterday.

    Everything seemed to be working fine from 46 to 47, but on 48, no echomalis were polling anymore.

    Switched back to A47.

    Any idea why this might be?

    --- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
    * Origin: New Mystic BBS (21:3/207)
  • From Memo@21:3/207 to All on Fri Oct 10 10:34:31 2025
    Good morning / good afternoon.

    I updated my Mystic BBS from A46 to A47 and finally A48 (Linux Debian 12). Everything seems fine so far but mutil / mis poll.
    Lots of "Node BUSY" and no new echomails. Netmail seem to work.

    Switched back to A46 (and fidopoll?) and everything seems to be fine again.

    Does anyone have any idea what I could check?

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: New Mystic BBS (21:3/207)
  • From Memo@21:3/207 to Memo on Fri Oct 10 16:25:48 2025
    I'll say - very cautiously - that it seems to be working now.
    At least I've already received an echomail response to one of my posts.

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: New Mystic BBS (21:3/207)
  • From fusion@21:1/616 to Memo on Fri Oct 10 16:49:01 2025
    On 10 Oct 2025, Memo said the following...

    Due to an interesting tip, I updated my BBS yesterday.

    Everything seemed to be working fine from 46 to 47, but on 48, no echomalis were polling anymore.

    Switched back to A47.

    don't bother and stick with A47? heh

    unless there's some sort of exploit or something truly broken it's not worth the effort imo

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
    * Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)
  • From Memo@21:3/207 to fusion on Fri Oct 10 22:53:02 2025
    Too late - I guess. If I'm right, I found the troublemaker ;)

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: New Mystic BBS (21:3/207)
  • From Bucko@21:4/131 to Memo on Fri Oct 10 20:37:24 2025

    On 10 Oct 2025, Memo said the following...

    Too late - I guess. If I'm right, I found the troublemaker ;)

    I've been running A48 for well over a year. It runs fine. A49 is a early alpha which was causing some folks issues.. Once g00r00 gets back to things I am sure he will pop out a bunch of updates..


    |11 Bucko |14- |06Wrong Number Family Of BBS' |07- |03www.wrgnbr.com

    ... A Meteor is an example of a rock star.

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)
  • From Memo@21:3/207 to Bucko on Sat Oct 11 05:38:37 2025
    Once g00r00 gets back to things I am sure he will pop out a bunch of
    updates..

    That would be really fantastic. :)

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: New Mystic BBS (21:3/207)
  • From Memo@21:3/207 to Memo on Sat Oct 11 08:09:54 2025
    FYI: I was able to figure it out myself.

    It was a file permission / owner issue. I was running a crontab (instead of event editor) as root. Since A47 the echofile packet owner must be the bbs user.

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: New Mystic BBS (21:3/207)