Mystic BBS says BUSY
reddit / bbs

----------------------------------------------------------------------
garyb122 · 2021-10-20 18:57

I think I screwed something up. When I try to run my Mystic BBS
locally from the command line in Linux, I get an error message that
says “BUSY”. And that’s it. Just all caps BUSY.

I’ve found that I can run it if I give sudo powers, like this: sudo
./mystic -l but I shouldn’t have to do that. I didn’t have to use sudo
before.

I’m thinking that I’ve somehow got all the nodes occupied
accidentally, or I have a process hung up somewhere, but my noob level
Linux expertise can’t fix it. I’ve tried everything I know to do. Help
please!

----------------------------------------------------------------------
dperry324 · 2021-10-20 19:05

Check to see if there's any chatX.dat files in your data directory. If
there are, run nodespy and select the nodes and kill them.
Optionally, you can just delete the data/chat?.dat files manually.

----------------------------------------------------------------------
garyb122 · 2021-10-20 20:15

That did it! Thanks :)

----------------------------------------------------------------------
notaname45 · 2021-11-09 15:15

I had this same issue, check your folder permissions. Make sure you
run ./mystic -l as the user who owns the binary. By default, if you
used sudo to install mystic, it will be owned by root, so you'll need
to \`chown\` the binaries.

In my case, this is what I did:

\- installed mystic to /srv/mystic

\- created a new user \`sudo useradd mystic\` because I prefer having
a user for each server

\- gave mystic a password with \`sudo passwd mystic\` so it can login

\- gave ownership of /srv/mystic to that user \`sudo chown -r
mystic:mystic /srv/mystic\`

\- now to access the bbs without root privileges, either log in to the
mystic user, or \`su mystic\` in order to run as that user, then

\- \`/srv/mystic/mystic -l\` and voila! No root privileges and a
functioning Mystic local node. You can also use this with
\`/srv/mystic/mystic -cfg' or any other binaries in that folder, since
chown -r set everything inside that folder to the same user.