Hi All,

I haven't run my board for a bit and last night restored the board from a backup from 05/15/2020. I think the board ran for a while after that date, but that is the latest backup I have. I have a gap in the dove net messages. I logged into Vert with my dovenet account and set the scan pointers back to 5/14/2020, but it seems that all the messages from that date are not being returned. I have some messages going back to 01/01/2022 so I'm certain that some of the messages have been filled in but I would expect to have recieved all the messages from 5/14/2020.

Does anyone know why I didn't recive messages from before 01/01/2022?

Thanks,
Electrosys

---
þ Synchronet þ Digital Aquarium - digiaqua.synchro.net - So much fun...
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Setting scan pointers back to 5/14/2020 doesn't return all msgs back.
By: Electrosys to All on Sun Mar 20 2022 12:32 pm

Hi All,

I haven't run my board for a bit and last night restored the board from a backup from 05/15/2020. I think the board ran for a while after that date, but that is the latest backup I have. I have a gap in the dove net messages. I logged into Vert with my dovenet account and set the scan pointers back to 5/14/2020, but it seems that all the messages from that date are not being returned. I have some messages going back to 01/01/2022 so I'm certain that some of the messages have been filled in but I would expect to have recieved all the messages from 5/14/2020.

Does anyone know why I didn't recive messages from before 01/01/2022?

It's possible, in some message areas, that I don't have messages older than that. I don't retain *all* messages forever on Vertrauen, most just imposing some artifical limit (say, 1000 messages) per message area.
--
digital man (rob)

Rush quote #15:
I can't pretend a stranger is a long-awaited friend
Norco, CA WX: 67.2øF, 44.0% humidity, 4 mph ESE wind, 0.01 inches rain/24hrs --- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Setting scan pointers back to 5/14/2020 doesn't return all msgs back.
By: Digital Man to Electrosys on Sun Mar 20 2022 02:02 pm

Does anyone know why I didn't recive messages from before 01/01/2022?

It's possible, in some message areas, that I don't have messages older than that. I don't retain *all* messages forever on Vertrauen, most just i

I see for example in the Dovenet Synchronet Sysops Only that the oldest messages is Oct/2019, so I would have expected messages from 5/14/2020 to Today to all be downloaded to my board at DIGIAQUA.

Any other insights?

Thanks,
Electrosys
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Setting scan pointers back to 5/14/2020 doesn't return all msgs back.
By: Electrosys to Digital Man on Sun Mar 20 2022 02:28 pm

Re: Setting scan pointers back to 5/14/2020 doesn't return all msgs back.
By: Digital Man to Electrosys on Sun Mar 20 2022 02:02 pm

Does anyone know why I didn't recive messages from before 01/01/2022?

It's possible, in some message areas, that I don't have messages older than that. I don't retain *all* messages forever on Vertrauen, most just i

I see for example in the Dovenet Synchronet Sysops Only that the oldest messages is Oct/2019, so I would have expected messages from 5/14/2020 to Today to all be downloaded to my board at DIGIAQUA.

Any other insights?

Login via QWK and set your new-scan-date for that sub-board back to Oct-2019. --
digital man (rob)

Synchronet/BBS Terminology Definition #49:
KD = King Drafus (Allen Christiansen)
Norco, CA WX: 68.4øF, 43.0% humidity, 5 mph ESE wind, 0.01 inches rain/24hrs --- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Setting scan pointers back to 5/14/2020 doesn't return all msgs back.
By: Digital Man to Electrosys on Sun Mar 20 2022 02:35 pm

Re: Setting scan pointers back to 5/14/2020 doesn't return all msgs back.
By: Electrosys to Digital Man on Sun Mar 20 2022 02:28 pm

Re: Setting scan pointers back to 5/14/2020 doesn't return all msgs back.
By: Digital Man to Electrosys on Sun Mar 20 2022 02:02 pm

Does anyone know why I didn't recive messages from before 01/01/2022?

It's possible, in some message areas, that I don't have messages older than that. I don't retain *all* messages forever on Vertrauen, most just i

I see for example in the Dovenet Synchronet Sysops Only that the oldest messages is Oct/2019, so I would have expected messages from 5/14/2020 to Today to all be downloaded to my board at DIGIAQUA.

Any other insights?

Login via QWK and set your new-scan-date for that sub-board back to Oct-2019.

Oh, also, double-check your SCFG->Message Options->Maximum QWK Message Age. If you have that set, that'll limit how old a message can be. Your logs will say if messages were filtered (ignored) based on this setting, so that shouln't be surprise.
--
digital man (rob)

Synchronet "Real Fact" #95:
Synchronet v3.15b was released in October of 2011 (5 years after v3.14a)
Norco, CA WX: 68.4øF, 43.0% humidity, 5 mph ESE wind, 0.01 inches rain/24hrs --- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Setting scan pointers back to 5/14/2020 doesn't return all msgs back.
By: Digital Man to Electrosys on Sun Mar 20 2022 02:37 pm

Login via QWK and set your new-scan-date for that sub-board back to
Oct-2019.

Oh, also, double-check your SCFG->Message Options->Maximum QWK Message Age. If you have that set, that'll limit how old a message can be. Your lo

I will give it a try again. But I do have the following options set in the message config:

Maximum QWK Messages 10000
Maximum QWK Message Age Unlimited

Thanks,
Electrosys
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Setting scan pointers back to 5/14/2020 doesn't return all msgs back.
By: Electrosys to Digital Man on Sun Mar 20 2022 02:58 pm

Login via QWK and set your new-scan-date for that sub-board back to
Oct-2019.

Oh, also, double-check your SCFG->Message Options->Maximum QWK
Message Age. If you have that set, that'll limit how old a message
can be. Your lo

I will give it a try again. But I do have the following options set in the message config:

Maximum QWK Messages 10000
Maximum QWK Message Age Unlimited

I tried setting the scan pointer back to Oct 2019. But I still don't see any messages between 5/15/2020 and 1/1/2022. I saw a number of messages come in and were marked as duplicates. Also a number of messages were updated and I saw only about 23 messages added. Previously I set the scan pointer to 5/14/2020 so I think setting it to oct 7 2019 imported a few messsages.

If you have any additional insights that would be great.

Thanks,
Electrosys
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Setting scan pointers back to 5/14/2020 doesn't return all msgs back.
By: Electrosys to Digital Man on Sun Mar 20 2022 03:13 pm

Re: Setting scan pointers back to 5/14/2020 doesn't return all msgs back.
By: Electrosys to Digital Man on Sun Mar 20 2022 02:58 pm

Login via QWK and set your new-scan-date for that sub-board back to
Oct-2019.

Oh, also, double-check your SCFG->Message Options->Maximum QWK
Message Age. If you have that set, that'll limit how old a message
can be. Your lo

I will give it a try again. But I do have the following options set in the message config:

Maximum QWK Messages 10000
Maximum QWK Message Age Unlimited

I tried setting the scan pointer back to Oct 2019. But I still don't see any messages between 5/15/2020 and 1/1/2022. I saw a number of messages come in and were marked as duplicates. Also a number of messages were updated and I saw only about 23 messages added. Previously I set the scan pointer to 5/14/2020 so I think setting it to oct 7 2019 imported a few messsages.

If you have any additional insights that would be great.

Disable duplicate message checking in SCFG for the sub-board(s) if you want to re-import old messages that you may have already imported but were deleted (e.g. purged due to age or exceeded max msgs for the sub).
--
digital man (rob)

Sling Blade quote #7:
Karl: I don't reckon the Good Lord would send anybody like you to Hades.
Norco, CA WX: 69.0øF, 43.0% humidity, 11 mph E wind, 0.01 inches rain/24hrs
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Setting scan pointers back to 5/14/2020 doesn't return all msgs back.
By: Digital Man to Electrosys on Sun Mar 20 2022 03:17 pm

Disable duplicate message checking in SCFG for the sub-board(s) if you want re-import old messages that you may have already imported but were deleted (e.g. purged due to age or exceeded max msgs for the sub).

I didn't see any new messages imported after setting "Duplicate Checking" from 10000 to 25000.

Maximum Messages 25000
Purge by Age Disabled
Duplicate Checking Enabled (25000 message CRCs)


3/20 04:57:32p QNET Finished Importing QWK Network Packet from VERT: (0 msgs) in 256 seconds (0 msgs/sec), 220 errors, 4954 dupes

Are you suggesting that I set the "Duplicate Checking" to 0 to turn it off completly?

Thanks,
Electrosys

---
þ Synchronet þ Digital Aquarium - digiaqua.synchro.net - So much fun...
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Setting scan pointers back to 5/14/2020 doesn't return all msgs back.
By: Electrosys to Digital Man on Sun Mar 20 2022 05:08 pm

Re: Setting scan pointers back to 5/14/2020 doesn't return all msgs back.
By: Digital Man to Electrosys on Sun Mar 20 2022 03:17 pm

Disable duplicate message checking in SCFG for the sub-board(s) if you want re-import old messages that you may have already imported but were deleted (e.g. purged due to age or exceeded max msgs for the sub).

I didn't see any new messages imported after setting "Duplicate Checking" from 10000 to 25000.

Maximum Messages 25000
Purge by Age Disabled
Duplicate Checking Enabled (25000 message CRCs)

3/20 04:57:32p QNET Finished Importing QWK Network Packet from VERT: (0 msgs) in 256 seconds (0 msgs/sec), 220 errors, 4954 dupes

Are you suggesting that I set the "Duplicate Checking" to 0 to turn it off completly?

Correct.
--
digital man (rob)

This Is Spinal Tap quote #30:
Big bottom, big bottom / Talk about mud flaps, my girl's got 'em!
Norco, CA WX: 61.5øF, 44.0% humidity, 2 mph S wind, 0.01 inches rain/24hrs
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Setting scan pointers back to 5/14/2020 doesn't return all msgs back.
By: Digital Man to Electrosys on Sun Mar 20 2022 08:47 pm

Are you suggesting that I set the "Duplicate Checking" to 0 to turn it of completly?

Correct.

I tried setting the "Duplicate Checking" to 0 and still was not able to fill
in the messages that are missing on my system.

Would it be appropriate to run FIXSMB on this message base (Synchronet Sysops Only) as well?

Here are my current seetings for the message base.

Long Name Synchronet Sysops Only
Short Name Synchronet Sysops
QWK Name SyncSysops
Internal Code SYNC_SYS
FidoNet Area Tag
Newsgroup Name
Access Requirements LEVEL 90 OR REST Q
Reading Requirements
Posting Requirements
Operator Requirements
Moderated Posting User
Maximum Messages 40000
Purge by Age Disabled
Duplicate Checking Disabled

Thanks,

P.S. I'm just curious as to why this isn't working as expected, obviously its not the end of the world but I always like to figure out why things don't work as expected.

Electrosys

---
þ Synchronet þ Digital Aquarium - digiaqua.synchro.net - So much fun...
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Setting scan pointers back to 5/14/2020 doesn't return all msgs back.
By: Electrosys to Digital Man on Sun Mar 20 2022 09:34 pm

Re: Setting scan pointers back to 5/14/2020 doesn't return all msgs back.
By: Digital Man to Electrosys on Sun Mar 20 2022 08:47 pm

Are you suggesting that I set the "Duplicate Checking" to 0 to turn it of completly?

Correct.

I tried setting the "Duplicate Checking" to 0 and still was not able to fill in the messages that are missing on my system.

So all that is going to do is prevent duplicate messages from being detected and filtered. You would still have to reset your scan pointers on the hub (Vertrauen) and download those same messages *again*. And if the message-IDs were previously imported, those would still be stored in your data/subs/*.hash files, so you'd need to delete those hash files too.

Would it be appropriate to run FIXSMB on this message base (Synchronet Sysops Only) as well?

Only if it's corrupted. Run chksmb to find out.

Thanks,

P.S. I'm just curious as to why this isn't working as expected, obviously its not the end of the world but I always like to figure out why things don't work as expected.

It sounds like it's a combination of things. If you want to just start fresh and download all the messages in DOVE-Net on Vertrauen, then delete your data/subs/dove*.* files and reset all your scan pointers on Vertrauen and download the QWK packets again. It would multiple QWK packets to get all the messages, but that would insure that you get every single message.
--
digital man (rob)

Synchronet/BBS Terminology Definition #21:
DM = Digital Man (Rob Swindell) or Dungeon Master
Norco, CA WX: 59.4øF, 42.0% humidity, 2 mph WSW wind, 0.01 inches rain/24hrs --- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Setting scan pointers back to 5/14/2020 doesn't return all msgs back.
By: Digital Man to Electrosys on Sun Mar 20 2022 10:29 pm

P.S. I'm just curious as to why this isn't working as expected,
obviously its not the end of the world but I always like to figure out
why things don't work as expected.

It sounds like it's a combination of things. If you want to just start fresh and download all the messages in DOVE-Net on Vertrauen, then delete your data/subs/dove*.* files and reset all your scan pointers on Vertrauen

That sounds like the best route to take at this juncture.

Thanks,
Electrosys
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)