Subj : Re: Usurper Linux To : Zip From : Shitty Date : Sun Jan 03 2021 17:38:00 Zi> Check "sudo systemctl status mis" or "sudo journalctl -xea -u mis" to Zi> 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 .