• Door party?

    From The Godfather@21:3/165 to All on Sat Jul 27 19:23:12 2024
    Hey all, out of nowhere my doorparty is not working, even if I restart my services in systemctl .. It was working fine, no changes on my end, but when I try to load a game I just get black screen until I stop / restart services from CLI in Ubuntu Linux.

    I'm also having an issue where I'm able to connect the MRC client to 5001, and the mrc-stat shows how many systems are connected and users in chat .. however when I attempt to go into the MRC chat room, the mod
    locks up and my PC fan turns on. When I drop carrier (Netrunner or Syncterm,) stop MRC's client, the BBS is fine.

    I'm on Mystic v49 and linux .. again .. everything was working fine until the past two weeks.

    Any tips would be appreciated.

    |15-|12t|04G
    |15www|08.|15theun|07dergrou|08nd|07.|08us|15:|0810023

    ... Honk if you love peace and quiet!

    --- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
    * Origin: www.theunderground.us Telnet 10023 SSH 7771 (21:3/165)
  • From MeaTLoTioN@21:1/158 to The Godfather on Mon Jul 29 16:14:10 2024
    On 27 Jul 2024, The Godfather said the following...

    Hey all, out of nowhere my doorparty is not working, even if I restart my services in systemctl .. It was working fine, no changes on my end, but when I try to load a game I just get black screen until I stop /
    restart services from CLI in Ubuntu Linux.

    I'm also having an issue where I'm able to connect the MRC client to
    5001, and the mrc-stat shows how many systems are connected and users in chat .. however when I attempt to go into the MRC chat room, the mod
    locks up and my PC fan turns on. When I drop carrier (Netrunner or Syncterm,) stop MRC's client, the BBS is fine.

    I'm on Mystic v49 and linux .. again .. everything was working fine
    until the past two weeks.

    Any tips would be appreciated.

    Logs, what do they say? Look in the Mystic logs dir for the latest mis log, the node log for the node you were logged into and also /var/log/syslog.

    I would recommend tailing those before you try all the stuff, and then you can watch as you do stuff what the logs show.

    if you don't know what I mean by tailing, as an example;

    In one terminal, run;
    tail -f /var/log/syslog

    In another terminal, run;
    tail -f /path/to/mystic/logs/node1.log (assuming you're logged into node1)

    In another terminal, run;
    tail -f /path/to/mystic/logs/mis.20240729.log
    (assuming you have the logs rotated daily, but if not check for the latest log in that dir using ls -lhrt /path/to/mystic/logs/mis*.log)

    Once you have these tailing, log into the BBS and start using the things that caused a problem, between those three logs you should see the answer why and then be able to figure out a solution.

    Hope this helps! =)

    ---
    |14Best regards,
    |11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N // @meatlotion:erb.pw

    |07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
    |07ÄÄ |08[|10ark|08] |1510:104/2 |07ÄÙ

    ... You can learn many things from children... like how much patience you have

    --- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
    * Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (21:1/158)