• File transfer areas broken

    From Weatherman@1:103/705 to All on Wed Feb 23 11:11:54 2022
    Hey all, recently updated my SynchroNet code from 3.18 to 3.19, and it seems I managed to screw up my file transfer areas. The transfer areas are all listed, but when viewing the file directories from within SynchroNet they are all empty.
    I checked and verified that the expected files exist on the hard drive exactly where they are expected to be, it seems that the SynchroNet related *.dab, *.dat,
    and *.ixb files are where they should be, but they don't seem to be being read.

    I know I can probably do ADDFILES and restore the files but then I'd lose the descriptions and would have to manually add them. I'd really not like to have to
    do that.

    Permissions issue? Known upgrade issue? Is there a relatively easy fix to get the file listings back?

    Thanks for your time!
    Regards,
    -==*>Weatherman<*==-

    ---
    þ Synchronet þ The Lost Chord BBS - Cheyenne, WY
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Weatherman@1:103/705 to Weatherman on Wed Feb 23 11:25:16 2022
    Hey all, recently updated my SynchroNet code from 3.18 to 3.19, and it seems I managed to screw up my file transfer areas. The transfer areas are all listed, but when viewing the file directories from within SynchroNet they are all empty.
    I checked and verified that the expected files exist on the hard drive exactly where they are expected to be, it seems that the SynchroNet related *.dab, *.dat,
    and *.ixb files are where they should be, but they don't seem to be being read.

    I know I can probably do ADDFILES and restore the files but then I'd lose the descriptions and would have to manually add them. I'd really not like to have to
    do that.

    Permissions issue? Known upgrade issue? Is there a relatively easy fix to get the file listings back?

    Thanks for your time!
    Regards,
    -==*>Weatherman<*==-

    Sorry.. I imagine it would help if I mentioned that the operating system is Linux.
    Regards,
    -==*>Weatherman<*==-

    ---
    þ Synchronet þ The Lost Chord BBS - Cheyenne, WY
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Weatherman on Wed Feb 23 20:10:52 2022
    Re: Re: File transfer areas broken
    By: Weatherman to Weatherman on Wed Feb 23 2022 11:25 am

    Hey all, recently updated my SynchroNet code from 3.18 to 3.19, and it seems I managed to screw up my file transfer areas. The transfer areas are all listed, but when viewing the file directories from within SynchroNet they are all empty.
    I checked and verified that the expected files exist on the hard drive exactly where they are expected to be, it seems that the SynchroNet related *.dab, *.dat,
    and *.ixb files are where they should be, but they don't seem to be being read.

    I know I can probably do ADDFILES and restore the files but then I'd lose the descriptions and would have to manually add them. I'd really not like to have to
    do that.

    Permissions issue? Known upgrade issue? Is there a relatively easy fix to get the file listings back?

    Thanks for your time!
    Regards,
    -==*>Weatherman<*==-

    Sorry.. I imagine it would help if I mentioned that the operating system is Linux.

    I think you just didn't run 'jsexec update.js'.

    The readme included with the upgrade and https://wiki.synchro.net/history:newfilebase both include this instruction.
    --
    digital man (rob)

    Breaking Bad quote #14:
    First name of Emlio - that's at least half a beaner, let you off for $10 - Hank Norco, CA WX: 44.9øF, 62.0% humidity, 2 mph NE wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Weatherman@1:103/705 to Digital Man on Sun Feb 27 00:42:00 2022
    Digital Man wrote to Weatherman <=-



    Hey all, recently updated my SynchroNet code from 3.18 to 3.19, and it seems I managed to screw up my file transfer areas. The transfer areas are all listed, but when viewing the file directories from within SynchroNet they are all empty.
    I checked and verified that the expected files exist on the hard drive exactly where they are expected to be, it seems that the SynchroNet related *.dab, *.dat,
    and *.ixb files are where they should be, but they don't seem to be being read.

    I know I can probably do ADDFILES and restore the files but then I'd lose the descriptions and would have to manually add them. I'd really not like to have to
    do that.

    Permissions issue? Known upgrade issue? Is there a relatively easy fix to get the file listings back?

    Thanks for your time!
    Regards,
    -==*>Weatherman<*==-

    Sorry.. I imagine it would help if I mentioned that the operating system is Linux.

    I think you just didn't run 'jsexec update.js'.

    The readme included with the upgrade and https://wiki.synchro.net/history:newfilebase both include this instruction. --
    digital man (rob)

    Hey Rob.. Thanks for the reply. I was pretty sure I hadn't skipped that step, so upon receipt of your message I ran it again to make sure. Didn't seem to make a difference. Even ran it with / 'upgrade_to_319' and still the transfer areas show as "empty" even though they should show files. Any other ideas?


    ... So easy, a child could do it. Child sold separately.
    --- MultiMail/Linux v0.49
    þ Synchronet þ The Lost Chord BBS - Cheyenne, WY
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Weatherman on Sun Feb 27 12:15:14 2022
    Re: Re: File transfer areas b
    By: Weatherman to Digital Man on Sun Feb 27 2022 12:42 am

    Hey Rob.. Thanks for the reply. I was pretty sure I hadn't skipped that step, so upon receipt of your message I ran it again to make sure. Didn't seem to make a difference. Even ran it with / 'upgrade_to_319' and still the transfer areas show as "empty" even though they should show files. Any other ideas?

    When you ran 'upgrade_to_319' (it's actually "upgrade_to_v319"), what does it report?

    Do you have *.shd, *.sid files in your data/dirs directory now (upgrade_to_v319 will create them)?

    The files you mentioned previously:

    exactly where they are expected to be, it seems that the SynchroNet related *.dab, *.dat,
    and *.ixb files are where they should be, but they don't seem to be being read.

    ... are not used once you upgrade to v3.19. This is detailed on the wiki page I pointed you to:

    The readme included with the upgrade and https://wiki.synchro.net/history:newfilebase both include this instruction. --
    --
    digital man (rob)

    Synchronet "Real Fact" #97:
    Synchronet v3.13a was released in September of 2005 (9 months after v3.12a) Norco, CA WX: 72.6øF, 9.0% humidity, 9 mph NE 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 Weatherman on Mon Feb 28 11:40:06 2022
    Re: Re: File transfer areas b
    By: Weatherman to Digital Man on Mon Feb 28 2022 09:26 am

    Hey Rob.. Thanks for the reply. I was pretty sure I hadn't skipped that


    When you ran 'upgrade_to_319' (it's actually "upgrade_to_v319"), what does it report?


    This is the output, doesn't look like it's doing anything in the file transfer areas:

    raymond@thelostchord:/sbbs/repo/exec$ /sbbs/exec/jsexec ./update.js / 'upgrade_to_v319'

    So run exec/upgrade_to_v319 directly, not via 'jsexec' or 'update.js'.

    Do you have *.shd, *.sid files in your data/dirs directory now (upgrade_to_v319 will create them)?

    All the transfer areas appear to have a corresponding *sid and *.shd file, but the *.sid files are zero length and the *.shd files are all uniformly 32 bytes in length.

    That's because you ran the BBS without running 'jsexec update' or upgrade_to_v319 first. Running exec/upgrade_to_v319 directly (not via jsexec) will convert the old filebases to the new foramt.
    --
    digital man (rob)

    Synchronet/BBS Terminology Definition #22:
    DOCSIS = Data Over Cable Service Interface Specification
    Norco, CA WX: 76.4øF, 12.0% humidity, 5 mph NW wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Weatherman@1:103/705 to Digital Man on Mon Feb 28 09:26:18 2022
    Hey Rob.. Thanks for the reply. I was pretty sure I hadn't skipped that


    When you ran 'upgrade_to_319' (it's actually "upgrade_to_v319"), what does it report?


    This is the output, doesn't look like it's doing anything in the file transfer areas:

    raymond@thelostchord:/sbbs/repo/exec$ /sbbs/exec/jsexec ./update.js / 'upgrade_to_v319'

    JSexec v3.19c-Linux master/acd808d37 - Execute Synchronet JavaScript Module Compiled Jan 28 2022 14:11:39 with GCC 11.2.0

    Loading configuration files from /sbbs/ctrl
    JavaScript-C 1.8.5 2011-03-31
    JavaScript: Creating runtime: 16777216 bytes

    Reading script from /sbbs/repo/exec/./update.js
    /sbbs/repo/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 Logon List module: System daily event already set to: '?logonlist - m'
    Updating [General] Text File Section indexes
    0 indexes updated.
    Updating (compiling) Baja modules
    Checking for v3.19 file bases
    /sbbs/repo/exec/./update.js executed in 0.05 seconds

    JavaScript: Destroying context
    JavaScript: Destroying runtime
    raymond@thelostchord:/sbbs/repo/exec$



    Do you have *.shd, *.sid files in your data/dirs directory now (upgrade_to_v319 will create them)?

    All the transfer areas appear to have a corresponding *sid and *.shd file, but the *.sid files are zero length and the *.shd files are all uniformly 32 bytes in length.


    Regards,
    -==*>Weatherman<*==-

    ---
    þ Synchronet þ The Lost Chord BBS - Cheyenne, WY
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Weatherman@1:103/705 to Digital Man on Tue Mar 1 14:04:28 2022
    Re: Re: File transfer areas b
    By: Weatherman to Digital Man on Mon Feb 28 2022 09:26 am

    Hey Rob.. Thanks for the reply. I was pretty sure I hadn't skipped that


    When you ran 'upgrade_to_319' (it's actually "upgrade_to_v319"), what does it report?


    This is the output, doesn't look like it's doing anything in the file transfer areas:

    raymond@thelostchord:/sbbs/repo/exec$ /sbbs/exec/jsexec ./update.js / 'upgrade_to_v319'

    So run exec/upgrade_to_v319 directly, not via 'jsexec' or 'update.js'.

    Do you have *.shd, *.sid files in your data/dirs directory now (upgrade_to_v319 will create them)?

    All the transfer areas appear to have a corresponding *sid and *.shd file, but the *.sid files are zero length and the *.shd files are all uniformly 32 bytes in length.

    That's because you ran the BBS without running 'jsexec update' or upgrade_to_v319 first. Running exec/upgrade_to_v319 directly (not via jsexec) will convert the old filebases to the new foramt.
    --
    digital man (rob)


    That's what it was alright.

    Missed the line where it says to run the jsupdate before restarting the BBS, restarted the BBS and THEN went back to the dev update steps about running jsupdate. Guess this is what happens when you do stuff at 1am....

    Regards,
    -==*>Weatherman<*==-

    ---
    þ Synchronet þ The Lost Chord BBS - Cheyenne, WY
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)