Blocks found field in web UI counts blocks multiple times when restarting the pool about monero-pool HOT 5 CLOSED

How many blocks are in your blocks table? You can use the included tool (option -m) to inspect.

from monero-pool.

I removed the db once I noticed, mined a block, restarted. There was one block, so it added one other on restart.

$ ./inspect-data -m data/
1635879 cfbe...0919 LOCKED 0.000000 2021-03-14 19:08:39
1635880 067a...ba71 LOCKED 0.000000 2021-03-14 19:08:49
1635881 b9c9...4a07 LOCKED 0.000000 2021-03-14 19:09:33
1635882 6cae...1331 LOCKED 0.000000 2021-03-14 19:09:53
1635883 fd3e...d18b LOCKED 0.000000 2021-03-14 19:10:11
1635884 1304...2b81 LOCKED 0.000000 2021-03-14 19:10:22

The UI reports:

Blocks found: | 5

Restarting...

Now says:

Blocks found: | 6

The tool now says:

1635879 cfbe...0919 LOCKED 0.000000 2021-03-14 19:08:39
1635880 067a...ba71 LOCKED 0.000000 2021-03-14 19:08:49
1635881 b9c9...4a07 LOCKED 0.000000 2021-03-14 19:09:33
1635882 6cae...1331 LOCKED 0.000000 2021-03-14 19:09:53
1635883 fd3e...d18b LOCKED 0.000000 2021-03-14 19:10:11
1635884 1304...2b81 LOCKED 0.000000 2021-03-14 19:10:22

So it looks like it's just out of date, not duplicating...

The chain height is 1635885. Block 1635884 was mined about 1.5 hours ago, and indeed the web UI now says:

Last block found: | 2 hours ago

I restarted again and it's keeping to 6. When I restared before, it jumped ~2k at once, from like 15.5k to 18k or so, so it's not just an increment somewhere.

from monero-pool.

Thinking about it, that last could be if I stopped the pool after it found a block but before the web UI updated. It doens't explain the 2k jump from before though, which happens a few times.

from monero-pool.

Trying again, it doesn't seem to happen anymore. I think my second post was just about stopping the pool before the web UI updated, and was not the same as the 2.5k increases from earlier.

from monero-pool.

I think it's best to ignore this for now, it might be my fault, I'll close for now, and reopen if I'm not sure it's not my fault :)

from monero-pool.