Subj : Re: Ports Locking Up
To   : metalhead
From : Zip
Date : Sun Feb 23 2020 05:54:08

Hello metalhead!

On 22 Feb 2020, metalhead said the following...
 me> The first time I did this, I configured Mystic to listen on port 2323.
 me> 
 me> It was fine - but then I needed to make changes to Mystic, so I
 me> downloaded the folder, made changes, and uploaded it back to the server
 me> again.
 me> 
 me> Then, when I ran "mis server" Mystic indicated that there was an error,
 me> 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)

.