• unable to ssh to BBS after latest build

    From Nigel Reed@1:103/705 to GitLab issue in main/sbbs on Tue Feb 27 18:16:05 2024
    open https://gitlab.synchro.net/main/sbbs/-/issues/727

    ```
    Feb 27 19:47:36 bbs synchronet: term 0030 SSH [192.138.210.158] Attaching to Node 1
    Feb 27 19:47:36 bbs synchronet: term Node 1 constructor using socket 30 (settings=8212)
    Feb 27 19:47:36 bbs synchronet: term Node 1 temporary file directory: /sbbs/node1/TEMP/
    Feb 27 19:47:36 bbs synchronet: term Node 1 passthru listen socket 33 opened Feb 27 19:47:36 bbs synchronet: term Node 1 passthru socket listening on port 36969
    Feb 27 19:47:36 bbs synchronet: term Node 1 passthru connect socket 34 opened Feb 27 19:47:36 bbs synchronet: term Node 1 input thread started
    Feb 27 19:47:36 bbs synchronet: term Node 1 thread started
    Feb 27 19:47:36 bbs synchronet: term Node 1 JavaScript: Creating node runtime: 134217728 bytes
    Feb 27 19:47:36 bbs synchronet: term Node 1 output thread started
    Feb 27 19:47:36 bbs synchronet: term Node 1 outbuf highwater mark tuned to 20000 based on MSS
    Feb 27 19:47:36 bbs synchronet: term Node 1 19:47 Tue Feb 27 2024 Node 1
    Feb 27 19:47:36 bbs synchronet: term Node 1 SSH bbs.endofthelinebbs.com [192.138.210.158]
    Feb 27 19:47:36 bbs synchronet: term Node 1 0030 SSH Setting attribute: SESSINFO_ACTIVE
    Feb 27 19:47:39 bbs synchronet: term Node 1 0030 SSH dbg 'No algorithm compatible with the remote system's selection was found: 'ssh-ed25519'' (-50) setting session active
    Feb 27 19:47:39 bbs synchronet: term Node 1 SSH login: 'nelgin'
    Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH Setting attribute: SESSINFO_AUTHRESPONSE
    Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH Setting attribute: SESSINFO_ACTIVE
    Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH [192.138.210.158] waiting for channel type.
    Feb 27 19:47:39 bbs synchronet: term Node 1 SSH WARNING: attempt to use channel 'shell' (1 != -1 or -1)
    Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH ERROR 'Cannot close last remaining channel without closing the overall session' (-21) closing channel
    Feb 27 19:47:39 bbs synchronet: term Node 1 SSH ERROR 'Cannot close last remaining channel without closing the overall session' (-21) popping data from input_thread
    Feb 27 19:47:39 bbs synchronet: term Node 1 input thread terminated (received 0 bytes in 0 blocks)
    Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH [192.138.210.158] height 136
    Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH [192.138.210.158] height 49
    Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH [192.138.210.158] term: xterm
    Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> nelgin #1 System password attempt: ''
    Feb 27 19:47:39 bbs synchronet: term Node 1 passthru socket disconnected
    Feb 27 19:47:39 bbs synchronet: term Node 1 output thread terminated
    Feb 27 19:47:40 bbs synchronet: term Node 1 thread terminated (0 node threads remain, 3 clients served)
    Feb 27 19:47:40 bbs synchronet: term Node 1 destructor begin
    Feb 27 19:47:40 bbs synchronet: term Node 1 JavaScript: Destroying context
    Feb 27 19:47:40 bbs synchronet: term Node 1 JavaScript: Destroying runtime
    Feb 27 19:47:40 bbs synchronet: term Node 1 destructor end

    ```

    When I ssh with SyncTerm it connects and then disconnects after a second or two.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab note in main/sbbs on Wed Feb 28 08:46:22 2024
    https://gitlab.synchro.net/main/sbbs/-/issues/727#note_5000

    One of my users said that he was unable to login using ssh this morning so no, this does not appear resolved.

    ```
    Feb 28 10:27:24 bbs synchronet: term 0052 SSH [xx.xx.xx.xx] Connection accepted on 192.138.210.158 port 22 from port 44094
    Feb 28 10:27:24 bbs synchronet: term 0052 SSH Cryptlib Session: 6028 created Feb 28 10:27:24 bbs synchronet: term 0052 SSH [xx.xx.xx.xx] Hostname: 63-155-65-80.eugn.qwest.net
    Feb 28 10:27:24 bbs synchronet: term 0052 SSH [xx.xx.xx.xx] Attaching to Node 5 Feb 28 10:27:24 bbs synchronet: term Node 5 constructor using socket 52 (settings=8212)
    Feb 28 10:27:24 bbs synchronet: term Node 5 temporary file directory: /sbbs/node5/TEMP/
    Feb 28 10:27:24 bbs synchronet: term Node 5 passthru listen socket 55 opened Feb 28 10:27:24 bbs synchronet: term Node 5 passthru socket listening on port 38835
    Feb 28 10:27:24 bbs synchronet: term Node 5 passthru connect socket 56 opened Feb 28 10:27:24 bbs synchronet: term Node 5 output thread started
    Feb 28 10:27:24 bbs synchronet: term Node 5 outbuf highwater mark tuned to 1428 based on MSS
    Feb 28 10:27:24 bbs synchronet: term Node 5 input thread started
    Feb 28 10:27:24 bbs synchronet: term Node 5 thread started
    Feb 28 10:27:24 bbs synchronet: term Node 5 JavaScript: Creating node runtime: 134217728 bytes
    Feb 28 10:27:24 bbs synchronet: term Node 5 10:27 Wed Feb 28 2024 Node 5
    Feb 28 10:27:24 bbs synchronet: term Node 5 SSH xx.xx.xx.xx [xx.xx.xx.xx]
    Feb 28 10:27:24 bbs synchronet: term Node 5 0052 SSH Setting attribute: SESSINFO_ACTIVE
    Feb 28 10:27:28 bbs synchronet: term Node 5 0052 SSH dbg 'Need resource to proceed' (-50) setting session active
    Feb 28 10:27:28 bbs synchronet: term Node 5 SSH login: 'Xuser'
    Feb 28 10:27:28 bbs synchronet: term Node 5 <Xuser> 0052 SSH Setting attribute: SESSINFO_AUTHRESPONSE
    Feb 28 10:27:28 bbs synchronet: term Node 5 <Xuser> 0052 SSH Setting attribute: SESSINFO_ACTIVE
    Feb 28 10:27:28 bbs synchronet: term Node 5 <Xuser> 0052 SSH [xx.xx.xx.xx] waiting for channel type.
    Feb 28 10:27:28 bbs synchronet: term Node 5 SSH WARNING: attempt to use channel 'session' (1 != -1 or -1)
    Feb 28 10:27:28 bbs synchronet: term Node 5 <Xuser> 0052 SSH ERROR 'Cannot close last remaining channel without closing the overall session' (-21) closing channel
    Feb 28 10:27:28 bbs synchronet: term Node 5 SSH ERROR 'Cannot close last remaining channel without closing the overall session' (-21) popping data from input_thread
    Feb 28 10:27:28 bbs synchronet: term Node 5 input thread terminated (received 0 bytes in 0 blocks)
    Feb 28 10:27:29 bbs synchronet: term Node 5 output thread terminated
    Feb 28 10:27:31 bbs synchronet: term Node 5 <Xuser> 0052 SSH [xx.xx.xx.xx] TIMEOUT waiting for channel type.
    Feb 28 10:27:31 bbs synchronet: term Node 5 <Xuser> 0052 SSH [xx.xx.xx.xx] session establishment failed
    Feb 28 10:27:32 bbs synchronet: term Node 5 thread terminated (4 node threads remain, 329 clients served)
    Feb 28 10:27:32 bbs synchronet: term Node 5 destructor begin
    Feb 28 10:27:32 bbs synchronet: term Node 5 JavaScript: Destroying context
    Feb 28 10:27:32 bbs synchronet: term Node 5 JavaScript: Destroying runtime
    ```

    I have asked him to provide the version of ssh he's using since he's using a linux terminal to connect

    $ ssh -l XUser -o pubkeyauthentication=false endofthelinebbs.com Bencollver@endofthelinebbs.com's password:
    Connection to endofthelinebbs.com closed.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab note in main/sbbs on Fri Mar 1 17:49:47 2024
    https://gitlab.synchro.net/main/sbbs/-/issues/727#note_5030

    I believe this was fixed.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab issue in main/sbbs on Fri Mar 1 17:49:47 2024
    close https://gitlab.synchro.net/main/sbbs/-/issues/727
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)