I updated to 3.19 from git. After following the directions everything compiled fine. I ran update.js as instructed but all my file areas are now saying they are empty. Any ideas?
It sounds like 'upgrade_to_v319' did not run. The output of 'jsexec update' (you can run it again) should say if it tried to run upgrade_to_v319 and if it was successful or not.I just recompiled after a git pull. The bbs says im running 3.19a compiled today. jsexec update.js shows the following updating exec directory successful, updating user ip addresses none updated, updating user birthday field none updated, updating general text file index's none updated, installing login list module already set, checking for 3.19 file areas, then it exits so its not showing it executing the upgrade_to_v319. That is in my exec dir. I compiled the src using the command make RELEASE=1 symlinks.
Re: Update Problem
By: Digital Man to Melkor on Sun Apr 04 2021 12:03 pm
It sounds like 'upgrade_to_v319' did not run. The output of 'jsexec update' (you can run it again) should say if it tried to run upgrade_to_v319 and if it was successful or not.I just recompiled after a git pull. The bbs says im running 3.19a compiled today. jsexec update.js shows the following updating exec directory successful, updating user ip addresses none updated, updating user birthday field none updated, updating general text file index's none updated, installing login list module already set, checking for 3.19 file areas, then it exits so its not showing it executing the upgrade_to_v319. That is in my exec dir. I compiled the src using the command make RELEASE=1 symlinks.
What files do you have in your data/dirs directory? A sample of the file listing will do, I don't need to know *all* the files in there.sysop.dab, sysop.dat, sysop.exb, sysop.ini, sysop.ixb, sysop.sdt, sysop.shd, sysop.sid and the actual dir sysop. Appears to be the same for all my file areas.
Re: Update Problem
By: Digital Man to Melkor on Sun Apr 04 2021 04:25 pm
What files do you have in your data/dirs directory? A sample of the file listing will do, I don't need to know *all* the files in there.sysop.dab, sysop.dat, sysop.exb, sysop.ini, sysop.ixb, sysop.sdt, sysop.shd, sysop.sid and the actual dir sysop. Appears to be the same for all my file areas.
That looks good then. And you say when you list the directories, they're empty? How exactly are you attempting to list the directories? --When I go to the transfer menu and list files it shows 0 there. The files are still physicaly (sp?) there just not being listed by the BBS. I could ;upload but some of my areas have a lot of files and typing the description would take awhile.
Re: Update Problem
By: Digital Man to Melkor on Sun Apr 04 2021 06:30 pm
That looks good then. And you say when you list the directories, they're empty? How exactly are you attempting to list the directories? --When I go to the transfer menu and list files it shows 0 there. The files are still physicaly (sp?) there just not being listed by the BBS. I could ;upload but some of my areas have a lot of files and typing the description would take awhile.
files in your data/dirs directory? Are they all 0 bytes?Yes. All the other files except the .sid have a file size all the .sid are 0 bytes.
Re: Update Problem
By: Digital Man to Melkor on Sun Apr 04 2021 08:01 pm
files in your data/dirs directory? Are they all 0 bytes?Yes. All the other files except the .sid have a file size all the .sid are 0 bytes.
When update.js ran upgrade_to_v319, did it report that files had been migrated to the new configuration (filebases)?I dont remember seeing anything about it when I ran update.js. Manually running upgrade_to_v319 shows it successfully completed to migration and now all my files are showing up in the directory listings from the transfer menu. Not sure why it did not work when I ran update.js but it worked now.
Assuming you don't have that scrollback available, just run upgrade_to_v319 again, manually, and let me know what it reports. --
Re: Update Problem
By: Digital Man to Melkor on Sun Apr 04 2021 09:51 pm
When update.js ran upgrade_to_v319, did it report that files had been migrated to the new configuration (filebases)?
Assuming you don't have that scrollback available, just run upgrade_to_v319 again, manually, and let me know what it reports. --I dont remember seeing anything about it when I ran update.js. Manually running upgrade_to_v319 shows it successfully completed to migration and now all my files are showing up in the directory listings from the transfer menu. Not sure why it did not work when I ran update.js but it worked now.
I got a note about missing: upgrade_to_v319
I got a note about missing: upgrade_to_v319
You need a copy of or a symlink-to upgarde_to_v319 in your
Synchronet exec directory.
I got a note about missing: upgrade_to_v319
You need a copy of or a symlink-to upgarde_to_v319 in your Synchronet
exec directory.
On 4/5/2021 10:52 PM, Digital Man wrote:
I got a note about missing: upgrade_to_v319
You need a copy of or a symlink-to upgarde_to_v319 in your
Synchronet exec directory.
Where is it? And shouldn't the unix install/build script have it?
The docker image is built from source for each version.
On 4/5/2021 10:52 PM, Digital Man wrote:
I got a note about missing: upgrade_to_v319
You need a copy of or a symlink-to upgarde_to_v319 in your Synchronet exec directory.
In my Dockerfile, I'm running the build/install via make in /sbbs/repo/install
Should I be doing this a different way?
https://github.com/bbs-io/synchronet-docker/blob/master/docker/Dockerfile
Note: the Dockerfile is meant to completely build sbbs from
scratch/source each time.
On 4/5/2021 10:52 PM, Digital Man wrote:
I got a note about missing: upgrade_to_v319
You need a copy of or a symlink-to upgarde_to_v319 in your
Synchronet exec directory.
Where is it? And shouldn't the unix install/build script have it?
The docker image is built from source for each version.
| Sysop: | Weed Hopper |
|---|---|
| Location: | Clearwater, FL |
| Users: | 14 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 232:44:49 |
| Calls: | 55 |
| Calls today: | 1 |
| Files: | 50,128 |
| D/L today: |
35 files (4,430K bytes) |
| Messages: | 275,425 |