1. Forum
  2. FSXNet
  3. FSX BBS

  • Ports Locking Up

    From metalhead@21:1/157 to All on Sat Feb 22 22:10:10 2020
    I'm running Mystic on a VPS, and to keep it running, I'm using "screen" in
    the linux terminal.

    The first time I did this, I configured Mystic to listen on port 2323.

    It was fine - but then I needed to make changes to Mystic, so I downloaded
    the folder, made changes, and uploaded it back to the server again.

    Then, when I ran "mis server" Mystic indicated that there was an error, so I changed the port from 2323 to 2324 and it started working again.

    Is there anything obviously wrong with what I did? Did I cause my web host to block port 2323?

    I understand that there might not be enough information in what I've
    described to say for sure what I'm doing wrong - but does anything stand out?

    --- Mystic BBS v1.12 A45 2020/02/16 (Windows/32)
    * Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (21:1/157)
  • From Al@21:4/106 to metalhead on Sat Feb 22 19:22:36 2020
    Then, when I ran "mis server" Mystic indicated that there was an
    error, so I changed the port from 2323 to 2324 and it started
    working again.

    mis should have no trouble listening on whatever port you choose, unless
    it can't bind the port for some reason.

    Did mis give any indication of what the problem was?

    Ttyl :-),
    Al

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Zip@21:1/202 to metalhead on Sun Feb 23 05:54:09 2020
    Hello metalhead!

    On 22 Feb 2020, metalhead said the following...
    The first time I did this, I configured Mystic to listen on port 2323.

    It was fine - but then I needed to make changes to Mystic, so I
    downloaded the folder, made changes, and uploaded it back to the server again.

    Then, when I ran "mis server" Mystic indicated that there was an error,
    so I changed the port from 2323 to 2324 and it started working again.

    Did you close down the old Mystic before launching the new one? Otherwise the new one will try to listen to the same port as the old one (and only one can listen to the same port number at one time -- actually there are exceptions
    to that, but in general...).

    Also, after stopping the old Mystic, you might have to wait up to 120 second before launching the new one (due to TCP lingering / no socket reuse flags
    when Mystic initializes the listening) -- although I think Mystic actually
    does set the appropriate socket reuse flags to avoid this. But this
    potential limitation can be good to know of.

    Other than that, hopefully the error message (or the mis.log logfile) gives some indication on what went wrong.

    Best regards
    Zip

    --- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
  • From metalhead@21:1/157 to Vk3jed on Mon Feb 24 00:47:18 2020
    Why are you using screen to keep Mystic in the background instead of
    ./mis DAEMON?

    I'm new to using Linux terminal. Thanks for this info though. I was under the impression that I wouldn't be able to return to the process with daemon. I've never used it before, but now that you've mentioned it, I'm gonna read all about it.

    Secondly, are you sure you terminated mis properly? Sounds like the original incarnation is still running on port 2323.

    My bad - yes, that's exactly my mistake.

    --- Mystic BBS v1.12 A45 2020/02/16 (Windows/32)
    * Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (21:1/157)
  • From ryan@21:1/168 to Vk3jed on Sun Feb 23 23:43:40 2020
    Why are you using screen to keep Mystic in the background instead of
    ./mis DAEMON?

    I prefer doing this myself but mostly because I can reattach the screen
    session and have an interactive WFC of sorts.

    --- Mystic BBS v1.12 A44 2020/02/04 (Linux/64)
    * Origin: monterey bbs (21:1/168)
  • From Vk3jed@21:1/109 to metalhead on Mon Feb 24 20:31:00 2020
    On 02-24-20 00:47, metalhead wrote to Vk3jed <=-

    Why are you using screen to keep Mystic in the background instead of
    ./mis DAEMON?

    I'm new to using Linux terminal. Thanks for this info though. I was
    under the impression that I wouldn't be able to return to the process
    with daemon. I've never used it before, but now that you've mentioned
    it, I'm gonna read all about it.

    Daemons are meant to run in the background. You normally monitor daemons through log files or in the case of mis, Nodespy can be used.

    Secondly, are you sure you terminated mis properly? Sounds like the original incarnation is still running on port 2323.

    My bad - yes, that's exactly my mistake.

    Suspected as much. ;)


    ... Men invented computers to drive women crazier!
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Vk3jed@21:1/109 to ryan on Mon Feb 24 20:32:00 2020
    On 02-23-20 23:43, ryan wrote to Vk3jed <=-

    Why are you using screen to keep Mystic in the background instead of
    ./mis DAEMON?

    I prefer doing this myself but mostly because I can reattach the screen session and have an interactive WFC of sorts.

    Yeah I don't bother, because my system runs on a headless Pi, but I can use Nodespy when I want to see what's going on. :)


    ... Love is grand. Divorce is fifty grand.
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From ryan@21:1/168 to Vk3jed on Mon Feb 24 05:53:24 2020
    I prefer doing this myself but mostly because I can reattach the scre session and have an interactive WFC of sorts.

    Yeah I don't bother, because my system runs on a headless Pi, but I can use Nodespy when I want to see what's going on. :)

    Mine's also headless, but the TUI is lightweight and screen's virtual tty handles it fine. *shrug* to each his/her own :)

    --- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
    * Origin: monterey bbs (21:1/168)
  • From Vk3jed@21:1/109 to ryan on Tue Feb 25 08:43:00 2020
    On 02-24-20 05:53, ryan wrote to Vk3jed <=-

    Mine's also headless, but the TUI is lightweight and screen's virtual
    tty handles it fine. *shrug* to each his/her own :)

    Yeah I prefer daemons for things that run in the background, and nodespy does the job if I do want to see what's happening. :)


    ... People say I'm apathetic, but I don't care.
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)