1. Forum
  2. fsxNet
  3. FSX MYS

  • first ssh connection after mis start daemon mode

    From Embalmed@21:4/166 to All on Thu Mar 19 11:26:28 2020
    So I know I saw someone else post about this a while ago, but I also am
    seeing the first SSH connection fail after starting MIS in daemon mode. I am still on A45, I don't *believe* anything related to this has changed in A46, but I haven't tried it out yet.

    In the logs, what I see is

    --------------------- Mystic v1.12 A45 2020/02/18 Thu, Mar 19 2020 (loglevel 2)
    + 2020.03.19 10:56:53 MANAGER Starting event system
    + 2020.03.19 10:56:53 MANAGER Starting 5 server(s)
    + 2020.03.19 10:56:53 TELNET Listening on IPV4 port 4023 using interface "0.0.0.0"
    + 2020.03.19 10:56:53 MANAGER Starting servers in DAEMON mode
    + 2020.03.19 10:56:53 NNTP Listening on IPV4 port 4119 using interface "0.0.0.0"
    + 2020.03.19 10:56:53 BINKP Listening on IPV4 port 24554 using interface "0.0.0.0"
    + 2020.03.19 10:56:53 SSH Listening on IPV4 port 4022 using interface "0.0.0.0"
    + 2020.03.19 10:56:53 HTTP Using Webroot: /opt/mystic/webroot/
    + 2020.03.19 10:56:53 HTTP Listening on IPV4 port 8080 using interface "0.0.0.0"
    + 2020.03.19 10:56:54 SENDMAIL Relaying mail to 127.0.0.1
    + 2020.03.19 10:56:54 EVENT Starting 5 event(s)
    + 2020.03.19 10:57:12 SSH > Connect on slot 1/5 (50.54.137.105)
    + 2020.03.19 10:57:12 SSH 1-HostName 50-54-137-105.evrt.wa.frontiernet.net
    + 2020.03.19 10:57:12 SSH 1-Negotiating SSH session
    + 2020.03.19 10:57:12 SSH Cannot load private key
    + 2020.03.19 10:57:12 SSH Cannot load certificate
    + 2020.03.19 10:57:12 SSH 1-Session failed

    If i connect again, it works fine, so it's just the very first connection
    after it starts up that does this.

    |07E|10m|07b|10a|07l|10m|07e|10d |12-----------------------------------------------------
    |09Black Lodge Research BBS |11blacklodgeresearch.org:4022
    |11fsx|08Net: |0721:4/166 |11sci|08Net: |0777:1/133

    --- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
    * Origin: Black Lodge Research BBS (21:4/166)
  • From ryan@21:1/168 to Embalmed on Fri Mar 20 00:11:38 2020
    If i connect again, it works fine, so it's just the very first connection after it starts up that does this.

    I think these two lines are good indications:

    1-Negotiating SSH session + 2020.03.19 10:57:12 SSH Cannot load private key + 2020.03.19 10:57:12 SSH Cannot load certificate

    I assume what's happening is mis is creating the key that it notices is missing, but it's only doing this after the first attempt to connect via ssh. There's probably a key file in the data dir, I would think. Maybe you can see if it's in there, try to login, see if it appears and then your second login works.

    --- Mystic BBS v1.12 A46 2020/03/18 (Linux/64)
    * Origin: monterey bbs (21:1/168)