I'm attempting to create a new server and update the BBS from v3.18 to v3.20.
I tar up the /sbbs folder on the old server and copy that to the new server in the same folder /sbbs
I'm having trouble after i do the git pull, then the make using setcap and symlinks with release=1.
I then do the /sbbs/exec/jsexec update and it doesn't seem to work.
if i run
the upgrade_to_v320 it says it migrates the users to user.tab and all that but i can't verify things are right because #1 when i run scfg it thinks this is a new installation when it should be an upgrade and i can't seem to get passed that.
!WARNING loading configuration files: 0 nodes configured in /sbbs/ctrl/main.ini
and of course i can see /sbbs/ctrl/main.ini and i can see the items inside of it, like bbs name and such, i can see the "nodes" in there too, so not sure why it shows 0 nodes configured.
This is where i try and run /sbbs/exec/scfg and it says a new installation is detected and i abort out of there because i dont want it to override any of my data.
I then do the /sbbs/exec/jsexec update and it doesn't seem to work.
What makes you say that? Is the update.js current (the latest from the Git repo)?
Look at the ctrl/main.ini file - does it have your BBS name, etc. in it? If not, then there was no conversion of the your old ctrl/*.cnf files to ctrl/*.ini, and if that's the case, then you
ran
the wrong update.js or something like that.
Re: Upgrading from v3.18 on CentOS7 to Ubuntu 25.04
By: Digital Man to Jason on Wed Oct 22 2025 10:01 pm
I then do the /sbbs/exec/jsexec update and it doesn't seem to work.
What makes you say that? Is the update.js current (the latest from the Git repo)?
I think this may be the problem, so im going to start over with the upgrade and try this. Question, after i compile with symlinks, it appears that it's symlinking the executables but not
any of the .js files. Is this right? Did i miss a step somewhere in the instructions? I would have thought it would have moved this stuff over?
Also, should it link the executables or create a symlink for the exec folder over to the exec folder inside of the repo directory? This is where it gets fuzzy for me because i'm not
reading
this in the instructions or im not understanding it properly. I am dense at times, so it's probably me, but im confused.. should i just move update.js script over by itself then?
For context, here is the header in my current exec/update.js file:
/* $Id: update.js,v 1.10 2020/05/05 01:09:27 rswindell Exp $ */
Here is the one in /sbbs/repo/exec:
/* Synchronet v3.15+ update script (to be executed with jsexec) */
So definitely a newer version there.
Also, the compile did create the symlinks for the update_to_v319 and update_to_v320 but not one for update.js
Here is the files from my /sbbs/exec folder:
-rw-r--r-- 1 sbbs sbbs 5244 Nov 10 2020 update.js
lrwxrwxrwx 1 root root 62 Oct 23 04:16 upgrade_to_v319 -> /sbbs/repo/src/sbbs3/gcc.linux.x64.exe.release/upgrade_to_v319
lrwxrwxrwx 1 root root 62 Oct 23 04:16 upgrade_to_v320 -> /sbbs/repo/src/sbbs3/gcc.linux.x64.exe.release/upgrade_to_v320
----
Look at the ctrl/main.ini file - does it have your BBS name, etc. in it? If not, then there was no conversion of the your old ctrl/*.cnf files to ctrl/*.ini, and if that's the case,
then
you ran
the wrong update.js or something like that.
Here is a sample of the first few fields in the main.ini up to my system password which i didn't copy here:
Hard Drive CafeHDCBBSMontgomery, Alabama!!!!!!!!!!!!JasonThe Guru
----
What I am going to do is attempt to re-do the update on this new server, manually copy over the new update.js file over to the /sbbs/exec directory and then attempt to run that and see
what
I get. Maybe this will solve all my issues. Still would like to know if i missed a step or something i didn't read right. But as always thanks DM for your quick response! You've always
been
great for me and I appreciate you!
Re: Upgrading from v3.18 on CentOS7 to Ubuntu 25.04
By: Digital Man to Jason on Wed Oct 22 2025 10:01 pm
I then do the /sbbs/exec/jsexec update and it doesn't seem to work.
What makes you say that? Is the update.js current (the latest from the Git repo)?
I think this may be the problem, so im going to start over with the upgrade and try this. Question, after i compile with symlinks, it appears that it's symlinking the executables but not any of the .js files. Is this right?
Did
i miss a step somewhere in the instructions? I would have thought it would have moved this stuff over?
Also, should it link the executables or create a symlink for the exec folder over to the exec folder inside of the repo directory? This is where it gets fuzzy for me because i'm not reading this in the instructions or im not understanding it properly. I am dense at times, so it's probably me, but im confused.. should i just move update.js script over by itself then?
Also, the compile did create the symlinks for the update_to_v319 and update_to_v320 but not one for update.js
Look at the ctrl/main.ini file - does it have your BBS name, etc. in it? If not, then there was no conversion of the your old ctrl/*.cnf files to ctrl/*.ini, and if that's the case, then you ran
the wrong update.js or something like that.
Here is a sample of the first few fields in the main.ini up to my system password which i didn't copy here:
Hard Drive CafeHDCBBSMontgomery, Alabama!!!!!!!!!!!!JasonThe Guru
What I am going to do is attempt to re-do the update on this new server, manually copy over the new update.js file over to the /sbbs/exec directory and then attempt to run that and see what I get. Maybe this will solve all my issues.
Still would like to know if i missed a step or something i didn't
read right. But as always thanks DM for your quick response! You've always been great for me and I appreciate you!
I have gone back and started over, and after compilation i did
cd /sbbs/repo/exec
cp *.js /sbbs/exec
then i run:
cd /sbbs/exec
./jsexec update
and it looks like it tries to work but i get one error besides the msgs.ini file which the docs says thats ok it will get created.. i get this
JSexec v3.21a-Linux master/1fecea061 - Execute Synchronet JavaScript Module Compiled Oct 17 2024 21:56 with GCC 14.2.0
Loading configuration files from /sbbs/ctrl
!ERROR loading configuration files: ERROR 2 (No such file or directory) opening /sbbs/ctrl/msgs.ini
JavaScript-C 1.8.5 2011-03-31
JavaScript: Creating runtime: 16777216 bytes
Reading script from /sbbs/exec/update.js
/sbbs/exec/update.js compiled in 0.00 seconds
Synchronet update.js revision 2.0
Updating exec directory: Success
Updating users ip_address field: 0 records updated
Updating users birthdate field: 0 records updated
Installing Avatars feature
!FAILED: No avatars collections (.bin files) found in avatars/
Installing Logon List Daily Event: Already installed
Installing Trashman Monthly Event: Successful
Updating [General] Text File Section indexes
0 indexes updated.
Updating (compiling) Baja modules
Checking for v3.19 file bases
Checking for v3.20 config files
Upgrading Synchronet v3.1x config files to v3.20
main.cnf -> main.ini
/sbbs/node1/node.cnf -> node.ini
!Error reading /sbbs/node1/node.cnf
Checking for v3.20 user base
No v3.20 user base found, running /sbbs/exec/upgrade_to_v320
upgrade - Upgrade Synchronet BBS to 3.21
Loading configuration files from /sbbs/ctrl
!ERROR loading configuration files: ERROR 2 (No such file or directory) opening /sbbs/ctrl/msgs.ini
/sbbs/exec/update.js executed in 28.28 seconds
JavaScript: Destroying context
JavaScript: Destroying runtime
-+-
then of course i try to run scfg and it's not giving errors like xtrn.ini not found or something like that.. so im still missing something or something isn't working right.
| Sysop: | Eric Oulashin |
|---|---|
| Location: | Beaverton, Oregon, USA |
| Users: | 95 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 00:11:23 |
| Calls: | 6,995 |
| Files: | 8,556 |
| D/L today: |
663 files (167M bytes) |
| Messages: | 368,812 |