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<*==-
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.
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?
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.
--The readme included with the upgrade and https://wiki.synchro.net/history:newfilebase both include this instruction. --
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?
Do you have *.shd, *.sid files in your data/dirs directory now (upgrade_to_v319 will create them)?
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'
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.
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)
| Sysop: | Weed Hopper |
|---|---|
| Location: | Clearwater, FL |
| Users: | 12 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 11:38:06 |
| Calls: | 113 |
| Calls today: | 1 |
| Files: | 50,349 |
| D/L today: |
53 files (10,144K bytes) |
| Messages: | 297,148 |