Greetings all.. Figured this sub would be chock full of messages..
perhaps this is just a super new board.

Anyway - after going through all of the current (and lots of non current)
bbs software I decided that the best thing to do was to write my own. Unfortunately the time I have to spend on such an endeavor is pretty
small - so I took the next less involved step - and chose Mystic -
Running on my Pi4/8.

I've gotten things installed, ran the config app, etc.. But when I run "./mystic -(whatever the switch is to run the bbs)"

it just takes me back to a shell prompt.. I followed everything in the
dox, but I'm wondering if things such as opening the SSH port are things
that I need to do on my own rather than something that the bbs can do on
its own.. I will keep dicking around with it and sure I will figure it
out eventually, but thought I would ask the collective here about it.

Hopefully the activity on this sub/site will increase.. This is kind of discouraging...


--- Talisman v0.53-dev (Linux/armv7l)
* Origin: 6th Choice Core (21:1/152.2)

On 18 Apr 2024, lucidphreak said the following...

I've gotten things installed, ran the config app, etc.. But when I run "./mystic -(whatever the switch is to run the bbs)"

usually you run "mis" and it spawns the mystic nodes as necessary when someone telnets in.

--- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
* Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)

I've gotten things installed, ran the config app, etc.. But when I run "./mystic -(whatever the switch is to run the bbs)"

I also run a Mystic BBS and what I have done is to write a little
batch file to start the BBS. It looks like this:

cd c:\mystic\semaphore
del mis.bsy
cd c:\mystic
mis -server

... There will be a rain dance Friday night, weather permitting!

--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: From the depths of Bunker 3 (21:1/130)

Twas Friday, April 19th when lucidphreak said...

I've gotten things installed, ran the config app, etc.. But when I run "./mystic -(whatever the switch is to run the bbs)"

it just takes me back to a shell prompt..

I don't know what the problem is, but anytime I have any such problem, especially with something closed source like mystic, is to use strace(1) and just see what OS calls the software is doing, "strace -v ./mystic -[..]" more about it here https://opensource.com/article/19/10/strace

You might see,

- searching and failing to find the configuration files in an alternate path
- attempting to open devices or files but denied by permission
- attempting to fork and exec, but failing to execute

The bottom of the logfile is the most important, whatever it did before exit is a very strong hint as to why it (silently) quit.

Also run "echo $?" and see what the exit code was and compare, https://tldp.org/LDP/abs/html/exitcodes.html

I would also suggest running "dmesg" and searching for any kernel messages about denying executiong due to SELinux permissions. I don't know if its the joke anymore, but they would say the first thing you need to do on RedHat/CentOS is disable SELinux. Gosh I remember things so simple as "ssh-keygen" failing to write a file to ~/.ssh/id_rsa, the program just silently doesn't write the file, you have to run "dmesg" to see that it was denied access to write to ~/.ssh by SELinux Policy, because god forbid the program actually does what you want it to do.

And you can either figure out how to modify and reload your SELinux Policy and learn a new set of tools and DSL syntax for that or do what everyone else does and google "how to disable SELinux" :)

--- ENiGMA 1/2 v0.0.14-beta (linux; x64; 18.18.2)
* Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)

I've gotten things installed, ran the config app, etc.. But when I ru "./mystic -(whatever the switch is to run the bbs)"

I also run a Mystic BBS and what I have done is to write a little
batch file to start the BBS. It looks like this:

cd c:\mystic\semaphore
del mis.bsy
cd c:\mystic
mis -server

If you want, I have a systemd service I can share.

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Clutch BBS * telnet://clutchbbs.com (21:1/199)

We're mystic on Pi3B+ here.

So all the suggestions have been good stuff.

I would just double check that you're in the directory and use sudo when running the mystic internet server when you're ready to go live.

sudo ./mis server

Don't know why but I've found this runs better as a sudo command. Also I've had problems in the events manager with the tick box to insert the ./ for linux builds. I left that turned off and wrote in the ./mis poll ##/##.## as an example. Again never figured out why but it worked.

So, hope you're making progress and that it's been a good Friday there.

--------------------------------
][ de N2QFD ][
][ Queen City BBS ][
][ queencitybbs.ddns.net:607 ][

--- Mystic BBS v1.12 A48 (Raspberry Pi/32)
* Origin: Queen City BBS (21:1/154)