Hello Shitty!

On 31 Dec 2020, Shitty said the following...

the terminal became an unresponsive input - I had to press ctrl-z to get outof it.

Sounds like systemd us trying to start, it fails, it retries and retries (StartLimitIntervalSec=0 so it will try forever) every second (RestartSec=1). However I just noticed that the path to the PIDFile might be incorrect.

Try:

ExecStartPost=/usr/bin/timeout -k 1 5 /bin/bash -c "while :; do [ -e /home/mystic/semaphore/mis.bsy ] && break; /bin/sleep 1; done; exit 0"

...or even:

ExecStartPost=/usr/bin/timeout -k 1 5 /bin/bash -c "while :; do [ -e /home/pi/mystic/semaphore/mis.bsy ] && break; /bin/sleep 1; done; exit 0"

...to ensure that the path to the PIDFile is correct.

And don't forget to run:

sudo systemctl daemon-reload

...after changing the mis.service file to ensure that systemd notices the changes.

Best regards
Zip

--- Mystic BBS v1.12 A47 2020/12/04 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (77:2/107)
■ Synchronet ■ CRBBS QWK Test Site - bbs.castlerockbbs.com

Hello again Shitty!

On 01 Jan 2021, Zip said the following...

Try:
ExecStartPost=/usr/bin/timeout -k 1 5 /bin/bash -c "while :; do [ -e /home/mystic/semaphore/mis.bsy ] && break; /bin/sleep 1; done; exit 0"

...which matches the path to the PIDFile:

PIDFile=/home/mystic/semaphore/mis.bsy

(I mixed up your paths and Warpslide's paths in one of my previous messages...)

Best regards
Zip

--- Mystic BBS v1.12 A47 2020/12/04 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (77:2/107)
■ Synchronet ■ CRBBS QWK Test Site - bbs.castlerockbbs.com

PIDFile=/home/mystic/semaphore/mis.bsy

Thanks Zip, I confirmed that the paths were correct. Then I tried this again, and it looked better because when I did:

sudo systemctl enable mis

this time the screen didn't go black with an unresponsive prompt, this time it looked like everything was good, but when I rebooted, MIS server still hadn't loaded on its own.

It's all good though. I'm probably neglecting something, and hopefully in the near future I'll find my mistake.

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Compufuck | Binghamton, NY | compufuck.xyz (77:1/142)
■ Synchronet ■ CRBBS QWK Test Site - bbs.castlerockbbs.com

Hello Shitty!

On 02 Jan 2021, Shitty said the following...

time itlooked like everything was good, but when I rebooted, MIS server still hadn'tloaded on its own.

Check "sudo systemctl status mis" or "sudo journalctl -xea -u mis" to see what it says.

Also, the mis.log logfile from MIS might show something.

It'll be interesting to hear what you find there!

Best regards
Zip

--- Mystic BBS v1.12 A47 2020/12/04 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (77:2/107)
■ Synchronet ■ CRBBS QWK Test Site - bbs.castlerockbbs.com

Check "sudo systemctl status mis" or "sudo journalctl -xea -u mis" to
see what it says.

I did all this:

sudo ./mis shutdown
sudo systemctl enable mis
sudo systemctl start mis
sudo reboot
(waited for the server to come back up)
Was unable to connect via telnet

Checked mis.log:
MANAGER Starting event system
MANAGER Starting 1 server(s)
MANAGER Starting servers in DAEMON mode
TELNET Unable to open IPV4 port: Error -1 (13)
TELNET Unable to open IPV6 port: Error -1 (13)
MANAGER Cryptlib not detected; SSL/SSH capabilities disabled
EVENT Starting 1 event(s)

sudo systemctl status mis
mis.service - Mystic Internet Server
Loaded: loaded (/etc/systemd/system/mis.service; enabled; vendor present; enab
Active: active (running) since Sun 2021-01-03 17:13:41 UTC; 12min ago
Process: 848 ExecStartPost=/usr/bin/timeout -k 1 5 /bin/bash -c while :; do [
Process: 838 ExecStart=/home/admin/web/compufuck.xyz/public_html/mysic/mis
Main PID: 845 (mis)
Tasks: 1 (limit: 2303)
CGroup: /system.slice/mis.service
^-845 /home/admin/web/compufuck.xyz/public_html/mystic/mis daemon
Jan 03 17:13:40 vps-aa2bbee8.vps.ovh.us systemd[1]: Starting Mystic Internet S
Jan 03 17:13:40 vps-aa2bbee8.vps.ovh.us mis[777]: [2.1k blob data]
Jan 03 17:13:41 vps-aa2bbee8.vps.ovh.us systemd[1]: Started Mystic Internet Se

sudo journalctl -xea -u mis
-- This information indicated that "mis.service has finished starting up."
and "The start-up result is RESULT."

What I make of this: The mis.log indicated that it was unable to open ports
(at that moment) so I'm not sure why. Maybe the script is running too quickly after boot? That's just my guess.

Let me know if you have any suggestions based on this info. But no pressure! I can live without mis.service, but it would be cool if it worked.

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Compufuck | Binghamton, NY | compufuck.xyz (77:1/142)
■ Synchronet ■ CRBBS QWK Test Site - bbs.castlerockbbs.com

It's no big deal though. I appreciate what you guys are trying to hel with, but I can go without it. Starting mis manually is not a problem for me.

The other thing you can do if you wanted to start it automatically is
add it to /etc/rc.local

I tried that but I don't have that file for some reason.

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Compufuck | Binghamton, NY | compufuck.xyz (77:1/142)
■ Synchronet ■ CRBBS QWK Test Site - bbs.castlerockbbs.com

Let me know if you have any suggestions based on this info. But no pressure! I can live without mis.service, but it would be cool if it worked.

Try 'sudo setcap CAP_NET_BIND_SERVICE=+eip /path/to/mystic/mis'

This'll allow mis to bind to privileged ports.

Just remember to do the setcap thing again every time you upgrade.

--- Mystic BBS v1.12 A46 2020/08/06 (Linux/64)
* Origin: monterey bbs (77:1/128)
■ Synchronet ■ CRBBS QWK Test Site - bbs.castlerockbbs.com

Hello Shitty!

On 03 Jan 2021, Shitty said the following...

TELNET Unable to open IPV4 port: Error -1 (13)
TELNET Unable to open IPV6 port: Error -1 (13)

What I make of this: The mis.log indicated that it was unable to open ports(at that moment) so I'm not sure why. Maybe the script is running
too quicklyafter boot? That's just my guess.

Let me know if you have any suggestions based on this info. But no

Try changing:

After=network.target

...to:

After=network-online.target

Also, for the [Service] section, try adding:

AmbientCapabilities=CAP_NET_BIND_SERVICE

...as suggested by: https://unix.stackexchange.com/a/581337

Hope this helps!

Best regards
Zip

--- Mystic BBS v1.12 A47 2020/12/04 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (77:2/107)
■ Synchronet ■ CRBBS QWK Test Site - bbs.castlerockbbs.com

Ryan, Warpslide, Zip, thank you!

It's working now.

I did this:

After=network-online.target

and this:

AmbientCapabilities=CAP_NET_BIND_SERVICE

And mis starts automatically now. It's great! I don't reboot often, but next time I do, it's gonna be much more relaxing without having to log-in just to start doorparty & mis.

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Compufuck | Binghamton, NY | compufuck.xyz (77:1/142)
■ Synchronet ■ CRBBS QWK Test Site - bbs.castlerockbbs.com