• Update Problem

    From Melkor@1:103/705 to All on Sun Apr 4 14:22:05 2021
    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?

    ---
    þ Synchronet þ Star Frontiers BBS starfron.synchronetbbs.org
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Melkor on Sun Apr 4 12:03:44 2021
    Re: Update Problem
    By: Melkor to All on Sun Apr 04 2021 02:22 pm

    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.

    You need to run 'jsexec update' *after* you build the latest code. And then you should either have a copy of or symlink to 'upgrade_to_v319' in your exec directory.

    Try it again.
    --
    digital man

    This Is Spinal Tap quote #19:
    Oh then, maybe it's not green. Anyway this is what I sleep in sometimes.
    Norco, CA WX: 78.9øF, 28.0% humidity, 3 mph NNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Melkor@1:103/705 to Digital Man on Sun Apr 4 22:19:37 2021
    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.

    ---
    þ Synchronet þ Star Frontiers BBS starfron.synchronetbbs.org
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Melkor on Sun Apr 4 16:25:19 2021
    Re: Update Problem
    By: Melkor to Digital Man on Sun Apr 04 2021 10:19 pm

    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.
    --
    digital man

    Rush quote #57:
    He picks up scraps of information, he's adept at adaptation .. Digital Man Norco, CA WX: 78.9øF, 25.0% humidity, 10 mph E wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Melkor@1:103/705 to Digital Man on Mon Apr 5 00:11:59 2021
    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.

    ---
    þ Synchronet þ Star Frontiers BBS starfron.synchronetbbs.org
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Melkor on Sun Apr 4 18:30:27 2021
    Re: Update Problem
    By: Melkor to Digital Man on Mon Apr 05 2021 12:11 am

    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?
    --
    digital man

    Synchronet "Real Fact" #1:
    Development began in 1990 of the (unnamed at the time) Synchronet BBS software. Norco, CA WX: 72.8øF, 35.0% humidity, 6 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Melkor@1:103/705 to Digital Man on Mon Apr 5 02:28:32 2021
    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.

    ---
    þ Synchronet þ Star Frontiers BBS starfron.synchronetbbs.org
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Melkor on Sun Apr 4 20:01:31 2021
    Re: Update Problem
    By: Melkor to Digital Man on Mon Apr 05 2021 02:28 am

    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.

    You should not have to re-add any files. What are the sizes of the *.sid files in your data/dirs directory? Are they all 0 bytes?

    When update.js ran upgrade_to_v319, did it report that files had been migrated to the new configuration?

    You could try running upgrade_to_v319 again and copy/paste the results here. It sounds like it's not migrating the file listings for you for some reason. I of course want to get to the bottom fo that and resolve it not just for you but for other sysops that will be upgrading in the future.
    --
    digital man

    Sling Blade quote #5:
    Karl Childers (to father): You ought not killed my little brother...
    Norco, CA WX: 65.8øF, 48.0% humidity, 7 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Melkor@1:103/705 to Digital Man on Mon Apr 5 03:41:41 2021
    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.

    ---
    þ Synchronet þ Star Frontiers BBS starfron.synchronetbbs.org
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Melkor on Sun Apr 4 21:51:56 2021
    Re: Update Problem
    By: Melkor to Digital Man on Mon Apr 05 2021 03:41 am

    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.

    And the other question I asked:
    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.
    --
    digital man

    Synchronet/BBS Terminology Definition #4:
    ATASCII = ATARI Standard Code for Information Interchange
    Norco, CA WX: 62.0øF, 57.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Melkor@1:103/705 to Digital Man on Mon Apr 5 12:16:24 2021
    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.

    ---
    þ Synchronet þ Star Frontiers BBS starfron.synchronetbbs.org
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Melkor on Mon Apr 5 11:57:41 2021
    Re: Update Problem
    By: Melkor to Digital Man on Mon Apr 05 2021 12:16 pm

    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.

    Interesting. Okay, I'll keep an eye out for that.
    --
    digital man

    Synchronet "Real Fact" #52:
    Answers to Frequently Asked Questions: http://wiki.synchro.net/faq:index
    Norco, CA WX: 71.3øF, 46.0% humidity, 4 mph ESE wind, 0.00 inches rain/24hrs --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Tracker1@1:103/705 to Digital Man on Mon Apr 5 21:05:29 2021
    I got a note about missing: upgrade_to_v319
    --
    Michael J. Ryan - tracker1@roughneckbbs.com
    ---
    ï¿­ Synchronet ï¿­ Roughneck BBS - roughneckbbs.com
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Tracker1 on Mon Apr 5 22:52:00 2021
    Re: Re: Update Problem
    By: Tracker1 to Digital Man on Mon Apr 05 2021 09:05 pm

    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.
    --
    digital man

    This Is Spinal Tap quote #37:
    David St. Hubbins: We are Spinal Tap from the UK - you must be the USA!
    Norco, CA WX: 55.2øF, 84.0% humidity, 3 mph NE wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Tracker1@1:103/705 to Digital Man on Sun Apr 11 20:06:00 2021
    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.
    --
    Michael J. Ryan - tracker1@roughneckbbs.com
    ---
    ï¿­ Synchronet ï¿­ Roughneck BBS - roughneckbbs.com
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Tracker1@1:103/705 to Digital Man on Sun Apr 11 20:18:16 2021
    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.
    --
    Michael J. Ryan - tracker1@roughneckbbs.com
    ---
    ï¿­ Synchronet ï¿­ Roughneck BBS - roughneckbbs.com
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Tracker1 on Mon Apr 12 00:24:44 2021
    Re: Re: Update Problem
    By: Tracker1 to Digital Man on Sun Apr 11 2021 08:06 pm

    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?

    That seems... odd. But I suppose it *could* be copied by the install makefile.

    The docker image is built from source for each version.

    Okay. <shrug>
    --
    digital man

    Rush quote #27:
    Growing up it all seems so one-sided, opinions all provided
    Norco, CA WX: 53.8øF, 92.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Tracker1 on Mon Apr 12 00:25:40 2021
    Re: Re: Update Problem
    By: Tracker1 to Digital Man on Sun Apr 11 2021 08:18 pm

    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?

    I would try to use sbbs3/GNUmakefile instead.

    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.

    Okay but *installed* "each time" as well? Probably unnecessary.
    --
    digital man

    Synchronet "Real Fact" #26:
    The Synchronet Web Server was written predominantly by Stephen Hurd (Deuce). Norco, CA WX: 53.8øF, 92.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Mortifis@1:103/705 to Tracker1 on Mon Apr 12 19:04:33 2021
    Re: Re: Update Problem
    By: Tracker1 to Digital Man on Sun Apr 11 2021 08:06 pm

    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.

    I'm may be way off, but if you are build'n sbbs from source wouldn't it already be v3.19, therefore rendering the need for upgrade_to_v319 unnecessary?

    ---
    þ Synchronet þ AlleyCat! BBS Lake Echo, NS Canada alleycatbbs.com
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)