Count of Blocks and kst mined missing about 1-100ish

[rangerdude]

Using Kristforge 3.1.5 and KristMiner v 2.1

After some days of testing counts are more likely to be off the first 2 minutes of mining. About 2 minutes I have seen it 1 of at about 150+ So its less likely to happen before 2 minutes. But I can recreate this 6 out of 10 times starting and stopping.

**NOTE I am not starting just after stopping, I get it time in between test periods.

Really example start of mining ./kristforge mine k*** Submitting solution for block 000000000c23 (nonce T2U--%!A#')) Submitting solution for block 000000007872 (nonce ;;I:$)!A#')) Submitting solution for block 000000003cdb (nonce PJ0#'1!A#')) Submitting solution for block 000000003cdb (nonce %W,@=1!A#')) Submitting solution for block 0000000015dd (nonce 5EJ,)9!A#')) Mined 3 KST for kb** Current target: Block #1835130 (shorthash 000000005ea0, work 33210)

[Lemmmy]

Are you saying that some blocks are not being submitted by your miner? If so, do you have an exact timestamp (UTC) of an example of when this happened?

What 'counts' are you talking about? Is this in KristWeb or Kristforge?

[rangerdude]

2021-08-02T03:30:37.000Z

Looks like kristforge miner report 3 KST / Website shows 4 KST but 5 where completed and submitted.

This was a quick example. I will try a few more times of the next week if needed. I have noticed this for about 2 weeks, but thought possibly my system i/o was heavy at the time. This time 23ms time to krist.club, my i/o was very low nothing else happening.

[Lemmmy]

Submitting solution for block 000000003cdb (nonce PJ0#'1!A#')) Submitting solution for block 000000003cdb (nonce %W,@=1!A#'))

Two of these are a duplicate hash, which means one of the blocks would've failed to submit. So the website's count of 4 KST is correct - you mined 4 blocks there.

As for why Kristforge is saying 3 KST, I think that's a bug with Kristforge, but Dana can prove me wrong

[rangerdude]

Ahh. yes I was only looking at nonce.
If I see it again I will watch for that.

Thanks for looking.

[dmarcuse]

Can you share your log file, from ~/.local/share/kristforge/kristforge.log so I can investigate the mined KST mismatch further?

[rangerdude]

this was a pretty good example.

@.** ~/kst> ./kristforge mine kbghkwv6ye Submitting solution for block 000000008f64 (nonce ,XRMV;Q:J=%) Submitting solution for block 000000012697 (nonce J]O<5>Q:J=%) Submitting solution for block 00000000b388 (nonce A8P,0?Q:J=%) Submitting solution for block 000000001be0 (nonce D5QP(AQ:J=%) Submitting solution for block 000000001be0 (nonce OMG0CQ:J=%) Submitting solution for block 00000000de55 (nonce ,?"Y^FQ:J=%) Submitting solution for block 00000000e104 (nonce E!G^4HQ:J=%) Submitting solution for block 00000000db3e (nonce I;96\IQ:J=%) Mined 5 KST for kbghkwv6ye Current target: Block #183

web shows it did 6KST so 2 where missed.

Thanks Brett

On 8/2/21 9:06 AM, Dana Marcuse wrote:

Can you share your log file, from |~/.local/share/kristforge/kristforge.log| so I can investigate the mined KST mismatch further?

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/tmpim/kristforge/issues/17#issuecomment-891102090, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFNFMLPWBGP3MWZZ7W5URCLT22X7ZANCNFSM5BL5JEAA.

-- Brett -- @.***

[rangerdude]

After I looked at the logs,,

Looks like kristfroge is sending the solution 3 times , 2 after solving and getting and OK from the server.

On 8/2/21 5:37 PM, Brett P wrote:

this was a pretty good example.

@.** ~/kst> ./kristforge mine kbghkwv6ye Submitting solution for block 000000008f64 (nonce ,XRMV;Q:J=%) Submitting solution for block 000000012697 (nonce J]O<5>Q:J=%) Submitting solution for block 00000000b388 (nonce A8P,0?Q:J=%) Submitting solution for block 000000001be0 (nonce D5QP(AQ:J=%) Submitting solution for block 000000001be0 (nonce OMG0CQ:J=%) Submitting solution for block 00000000de55 (nonce ,?"Y^FQ:J=%) Submitting solution for block 00000000e104 (nonce E!G^4HQ:J=%) Submitting solution for block 00000000db3e (nonce I;96\IQ:J=%) Mined 5 KST for kbghkwv6ye Current target: Block #183

web shows it did 6KST so 2 where missed.

Thanks Brett

On 8/2/21 9:06 AM, Dana Marcuse wrote:

Can you share your log file, from |~/.local/share/kristforge/kristforge.log| so I can investigate the mined KST mismatch further?

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/tmpim/kristforge/issues/17#issuecomment-891102090, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFNFMLPWBGP3MWZZ7W5URCLT22X7ZANCNFSM5BL5JEAA.

-- Brett -- @.***

-- Brett -- @.***

[dmarcuse]

I need the actual log file contents, not the command-line output - the log file contains extra information about specifically what network traffic occurred. Can you find it at ~/.local/share/kristforge/kristforge.log and copy the contents here, or into pastebin or such?

[rangerdude]

kristforge.log.gz

I guess replying to email does not allow attachments. First time I have ever done that. I did send them in email a few times.

[rangerdude]

Is this related to #57

[dmarcuse]

If you mean tmpim/Krist#57, probably not. However, looking through the logs, it looks like there may be a different bug in the Krist server. I've opened tmpim/Krist#59 to track this.