GOod news everyone, I was able to figure out my lastread pointer issue. TUrns out that when I did the upgrade from 3.16c to 3.17 and ran the upgardejs, I noticed that all of my echo's were gone. The files stillr esided on the disk, but not in sbbscfg, so, I took the msg.cnf file from my backup and overwrote the one that was in the ctrl directory. A few days ago, in attempting to get to the bottom of this lastread pointer being randomly messed up, I re-ran the upgrade.js file.

Bingo, Bango, lastread pointers fixed. I now see new messages as I should and not randonly reset every time I logegd in.

... A bachelor never makes the same mistake once.

---
* Synchronet * Split Infinity BBS - Rupert, WV
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Hello Buckaroo,

On Thu Jan 19 2017 12:11:16, Buckaroo Banzai wrote to All:

Bingo, Bango, lastread pointers fixed. I now see new messages as I
should and not randonly reset every time I logegd in.

There was also an issue with DDMsgReader.js about this specific topic that has since been fixed, so you may want to upgrade that as well.

When I switched to the stock newscan, everything worked fine. So my issue was with DDMsgReader. Seems you may have had a little more of an issue than I did, since the stock newscan didn't work for you either. Glad you got that sorted out!

Regards,
Nick

... "?? ????. ? ????? ?????? ???????."
--- GoldED+/LNX 1.1.5-b20161221
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Re: Lastread pointers
By: Accession to Buckaroo Banzai on Thu Jan 19 2017 12:17:04

I had alerady upgraded DDMsgReader and thanks for pointing that out, it would have been bad if I had missed that.

---
* Synchronet * Split Infinity BBS - Rupert, WV
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Has anyone noticed anythign with Syncchronet 3.17 (Latest build as of 1/6/2017) having issues with the last read pointers on the message bases?

Consistently, when logging in via SyncTerm and doing a new message scan, I will be presented with a message base, that I know I have read before to the end of the mnessages at that time, where my "new" message has been "reset", if you will, to the first message in the message base. It's happening randonly across all the networks I carry, not just one.

I'm also running the DDMessageReader mod to read with. I was using GOldEd as an offline reader but it does not handle Dove-Net messages with voting info in it it appears and I thought it might have been that causing the issue.

I've run chksmb and fixsmb to correct any issues that I had with the message databases.

---
* Synchronet * Split Infinity BBS - Rupert, WV
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Hello Buckaroo,

On Mon Jan 09 2017 09:20:22, Buckaroo Banzai wrote to All:

Has anyone noticed anythign with Syncchronet 3.17 (Latest build as of 1/6/2017) having issues with the last read pointers on the message
bases?

Yes. I'm still seeing it here. I originally thought it may have been something to do with DDMsgReader, but Nightfox is not seeing the same issues I am, so I had chalked it up as something specific to my own system, until you came along!

Consistently, when logging in via SyncTerm and doing a new message
scan, I will be presented with a message base, that I know I have read before to the end of the mnessages at that time, where my "new"
message has been "reset", if you will, to the first message in the
message base. It's happening randonly across all the networks I carry,
not just one.

I'm also running the DDMessageReader mod to read with. I was using
GOldEd as an offline reader but it does not handle Dove-Net messages
with voting info in it it appears and I thought it might have been
that causing the issue.

I've run chksmb and fixsmb to correct any issues that I had with the message databases.

Exact same scenario, exact same results, oddly enough. I've also even completely wiped the message bases when I moved everything to a Raspberry Pi 3 (haven't touched the new message bases with Golded+ at all), and I'm still seeing the issues in select and random sub-boards.

Regards,
Nick

... "?? ????. ? ????? ?????? ???????."
--- GoldED+/LNX 1.1.5-b20161221
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Re: Lastread pointers
By: Nicholas Boel to Buckaroo Banzai on Mon Jan 09 2017 08:58 am

Yes. I'm still seeing it here. I originally thought it may have been something to do with DDMsgReader, but Nightfox is not seeing the same issues I am, so I had chalked it up as something specific to my own system, until you came along!

Consistently, when logging in via SyncTerm and doing a new message
scan, I will be presented with a message base, that I know I have
read before to the end of the mnessages at that time, where my "new"

I havent updated ANYTHING from the 3.17 suite EXCEPT scfg, since the voting feature was added and I'm not having those issues, so maybe roll back to an older SBBS 3.17, and see if you can backtrace the issue.

--

Tim Smith (KK4QBN)
KK4QBN BBS

---
* Synchronet * KK4QBN BBS - (706)422-9538 - kk4qbn.synchro.net, Chatsworth GA US
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Hello KK4QBN,

On Mon Jan 09 2017 11:43:10, KK4QBN wrote to Nicholas Boel:

I havent updated ANYTHING from the 3.17 suite EXCEPT scfg, since the voting feature was added and I'm not having those issues, so maybe
roll back to an older SBBS 3.17, and see if you can backtrace the
issue.

I'm not a roll-backer. :)

Regards,
Nick

... "-Y-| -+-+-#-A. -> -+-|-|-U-i -e-+-+-i-|-+ -C-#-#-+-e-#-A."
--- GoldED+/LNX 1.1.5-b20161221
# Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1)
* Synchronet * thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: Lastread pointers
By: Accession to KK4QBN on Mon Jan 09 2017 12:00 pm

I havent updated ANYTHING from the 3.17 suite EXCEPT scfg, since the
voting feature was added and I'm not having those issues, so maybe
roll back to an older SBBS 3.17, and see if you can backtrace the
issue.

I'm not a roll-backer. :)

I try not to be, but do long enough to test and see what the issues is, while keeping my sytem online, sometimes on multiple machines.

--

Tim Smith (KK4QBN)
KK4QBN BBS

---
* Synchronet * KK4QBN BBS - (706)422-9538 - kk4qbn.synchro.net, Chatsworth GA US
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Hello KK4QBN,

On Mon Jan 09 2017 15:43:00, KK4QBN wrote to Accession:

I'm not a roll-backer. :)

I try not to be, but do long enough to test and see what the issues
is, while keeping my sytem online, sometimes on multiple machines.

I'm using Linux, and upgrade directly from CVS. So rather than chasing down and

replacing an earlier version of a specific .js script or better yet, an actual .c or .cpp file, I'd rather try to work it out, gather a good description for the specific developer that needs the information, and get it fixed that way so

I can just upgrade again with the fixes in place.

In this case, I'm not certain what would need to be rolled back. Since I have no idea where the issue lies just yet.

Regards,
Nick

... "-Y-| -+-+-#-A. -> -+-|-|-U-i -e-+-+-i-|-+ -C-#-#-+-e-#-A."
--- GoldED+/LNX 1.1.5-b20161221
# Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1)
* Synchronet * thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Hello Buckaroo,

On Mon Jan 09 2017 09:20:22, Buckaroo Banzai wrote to All:

Has anyone noticed anythign with Syncchronet 3.17 (Latest build as of 1/6/2017) having issues with the last read pointers on the message
bases?

Sorry to bring this up again, but I've been doing some trial and error stuff on

it, since it is quite annoying.

Consistently, when logging in via SyncTerm and doing a new message
scan, I will be presented with a message base, that I know I have read before to the end of the mnessages at that time, where my "new"
message has been "reset", if you will, to the first message in the
message base. It's happening randonly across all the networks I carry,
not just one.

I'm guessing it is something specific to our systems, and not an issue everyone

is experiencing.

I'm also running the DDMessageReader mod to read with. I was using
GOldEd as an offline reader but it does not handle Dove-Net messages
with voting info in it it appears and I thought it might have been
that causing the issue.

Are you by chance sending messages from Synchronet to a separate message base carrying system via FTN means (ie: tosser/mailer) to access with Golded? Or are

you just accessing your Synchronet message bases with Golded?

Otherwise both of our descriptions of this matter are very similar. However I'm

transferring my messages via FTN to another system and back. If you're not doing this, then I can't imagine it being an sbbsecho or FTN related issue, but

definitely didn't start happening until the voting stuff was added. I just don't know yet if it's Synchronet itself, or DDMsgReader just yet - although Nightfox has mentioned in the past not having any issues like we are.. so I don't know for sure.

Regards,
Nick

... "-Y-| -+-+-#-A. -> -+-|-|-U-i -e-+-+-i-|-+ -C-#-#-+-e-#-A."
--- GoldED+/LNX 1.1.5-b20161221
# Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1)
* Synchronet * thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: Lastread pointers
By: Nicholas Boel to Buckaroo Banzai on Mon Jan 09 2017 08:58:00

Still looking for help on this one. I've removed DDMessageReader, no change. I've updated to the latest build release, no change.

Issue is that the lastread pointers for users are not getting set or are getting reset on random echos. I do a new scan, read to the last message and move to the next echo until completed. If I do a new read, all echos show as no new messages. If I log off and then log back in anytime after that, last read popinters on random echos will have been set to the first message in that echo.

Win32, Synchronet 3.17a 1/11/17 biuld. All scripts and run files have been updated to the latest versions as well.

---
* Synchronet * Split Infinity BBS - Rupert, WV
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: Lastread pointers By: Nicholas Boel to Buckaroo Banzai on Mon Jan 09 2017 08:58:00 Still looking for help on this one. I've removed DDMessageReader, no change. I've updated to the latest build release, no change. Issue is that the lastread pointers for users are not getting set or are getting reset on random echos. I do a new scan, read to the last message and move to the next echo until completed. If I do a new scan again during thesame call, the lastread pointers on random echos will have been set to thefirst message in that echo. Win32, Synchronet 3.17a 1/11/17 biuld. All scripts and run files have been updated to the latest versions as well.

---
* Synchronet * Split Infinity BBS - Rupert, WV
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Yes. I'm still seeing it here. I originally thought it may have been something to do with DDMsgReader, but Nightfox is not seeing the same issues I am, so I had chalked it up as something specific to my own system, until you came along!

Often I do a new-to-me scan but don't often do the regular newscan. I'll have to do some more newscan testing with DDMsgReader and debug it more.

Nightfox

---
* Synchronet * Digital Distortion: digitaldistortionbbs.com
* Origin: Vertrauen - vert.synchro.net (1:103/705)

I'm not a roll-backer. :)

I think it's a good habit to keep backups of previous binaries when you upgrade so that if you encounter any issues with the new version, you can roll back easily. That can happen sometimes with a project like Synchronet where daily beta builds are provided while it's still in development.

I've had to roll back a couple times after upgrading to a daily build until the issue was fixed.

Nightfox

---
* Synchronet * Digital Distortion: digitaldistortionbbs.com
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Hello Nightfox,

On Thu Jan 12 2017 15:33:16, Nightfox wrote to Accession:

I'm not a roll-backer. :)

I think it's a good habit to keep backups of previous binaries when
you upgrade so that if you encounter any issues with the new version,
you can roll back easily. That can happen sometimes with a project
like Synchronet where daily beta builds are provided while it's still
in development.

I completely agree that it's a good habit. However, I usually don't go about it that way. :)

I've had to roll back a couple times after upgrading to a daily build until the issue was fixed.

If it's not life or death, I don't see the need. At this time there's specific developers here that do a great deal for us in a short amount of time, especially when there's a problem. If it can be fixed within a day or so (when the developer finally gets the right information from the person reporting issues), I can wait.

Livin' on the edge! :)

Regards,
Nick

... "?? ????. ? ????? ?????? ???????."
--- GoldED+/LNX 1.1.5-b20161221
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

I completely agree that it's a good habit. However, I usually don't go about it that way. :)

If it's not life or death, I don't see the need. At this time there's specific developers here that do a great deal for us in a short amount of time, especially when there's a problem. If it can be fixed within a day or so (when the developer finally gets the right information from the person reporting issues), I can wait.

I agree. I've seen one bug creep in once where Synchronet would crash on startup though.. So, just in case of bugs like that is why I like to make backups before I upgrade.

Nightfox

---
* Synchronet * Digital Distortion: digitaldistortionbbs.com
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Hello Buckaroo,

On Thu Jan 12 2017 17:06:48, Buckaroo Banzai wrote to Nicholas Boel:

Still looking for help on this one. I've removed DDMessageReader, no change. I've updated to the latest build release, no change.

Issue is that the lastread pointers for users are not getting set or
are getting reset on random echos. I do a new scan, read to the last message and move to the next echo until completed. If I do a new read,
all echos show as no new messages. If I log off and then log back in anytime after that, last read popinters on random echos will have been
set to the first message in that echo.

Win32, Synchronet 3.17a 1/11/17 biuld. All scripts and run files have
been updated to the latest versions as well.

So you're saying you've removed DDMsgReader completely, and using Synchronet's stock newscan feature gave you the same results over time? If that's the case, DM may have to be made aware as well. I have not tested without DDMsgReader, so

I can't verify that.

However, DDMsgReader's newscan feature is definitely different from Synchronet's stock one. So if the issue lies in both, I wouldn't know where to look.

Regards,
Nick

... "-Y-| -+-+-#-A. -> -+-|-|-U-i -e-+-+-i-|-+ -C-#-#-+-e-#-A."
--- GoldED+/LNX 1.1.5-b20161221
# Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1)
* Synchronet * thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Hello Nightfox,

On Thu Jan 12 2017 16:36:36, Nightfox wrote to Accession:

If it's not life or death, I don't see the need. At this time
there's specific developers here that do a great deal for us in a
short amount of time, especially when there's a problem. If it can
be fixed within a day or so (when the developer finally gets the
right information from the person reporting issues), I can wait.

I agree. I've seen one bug creep in once where Synchronet would crash
on startup though.. So, just in case of bugs like that is why I like
to make backups before I upgrade.

I do definitely backup the exec directory, as per the instructions for updating
on Linux. If a problem like that were to come up, then of course I would put the old binaries in place until I could safely upgrade again.

Regards,
Nick

... "?? ????. ? ????? ?????? ???????."
--- GoldED+/LNX 1.1.5-b20161221
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)