• update from 3.19 to 3.20 fails if node.cnf missing from some node dire

    From Bob Roberts@1:103/705 to GitLab issue in main/sbbs on Wed May 3 14:32:01 2023
    open https://gitlab.synchro.net/main/sbbs/-/issues/560

    The jsexec update process will fail if one or more /sbbs/nodeXX directories do not have a node.cnf file. In my case many of my node directories were missing the .cnf file because no user had ever logged into them. (I believe the cnf gets created on first login to a node.) If the node.cnf is missing from a node directory the update process terminates and important ini files are not created, and then SBBS fails to start.As a workaround I copied my node.cnf from node2 to all other nodes and then re-ran the jsesec update, and everything was ok.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Thu May 4 11:26:12 2023
    https://gitlab.synchro.net/main/sbbs/-/issues/560#note_3554

    It is weird/unexpected that you would have node directories without a node.cnf file in them. The *nix and Windows install methods copy the contents of the node1 directory to the node[2-4] directories.I can update update.js to not fail in this scenario, but I am curious how you ended up in this state to begin with.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Thu May 4 14:36:21 2023
    https://gitlab.synchro.net/main/sbbs/-/issues/560#note_3555

    Adding nodes in SCFG->Nodes also copies the highest node's config file (.cnf or .ini in v3.20) to the new node directory. So, this is a mystery to me.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Bob Roberts@1:103/705 to GitLab note in main/sbbs on Thu May 4 16:19:58 2023
    https://gitlab.synchro.net/main/sbbs/-/issues/560#note_3556

    I can't remember exactly, this install is at least 2 years old. I think by default SBBS comes configured for 4 nodes. I had previously expanded it to 12 by adjusting it in SCFG and editing the sbbs config file for the terminal server. I never manually created the node directories; they were created magically. This is linux symlinks type install.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Thu May 4 17:45:48 2023
    https://gitlab.synchro.net/main/sbbs/-/issues/560#note_3557

    Okay, that makes sense now: 2 years ago, this was an issue for *nix installs and fixed in commit 51ae69e6880
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab issue in main/sbbs on Thu May 4 19:02:15 2023
    close https://gitlab.synchro.net/main/sbbs/-/issues/560
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)