Hi lib and barwizi,

-reindex option worked like a charm!

New set of nodes (added manually straight to to the config file) suggested by lib helped to fix the "no block source" problem.

All in all, wallet resynchronised again.

Thank you both!

Hi,

This morning when I tried to run protoshares-qt.exe I got the message "Error loading block database. Do you want to rebuild the block?". IRCC protosjares-qt was properly closed last time I used it.

Here is the debug.log:

ProtoShares version v0.8.5.0-unk-beta (Nov  7 2013, 12:07:19)
Using OpenSSL version OpenSSL 1.0.1e 11 Feb 2013
Startup time: 2014-01-15 07:39:53
Default data directory C:\users\roger\Application Data\ProtoShares
Using data directory C:\users\roger\Application Data\ProtoShares
Using at most 125 connections (2048 file descriptors available)
Using 2 threads for script verification
init message: Verifying wallet...
dbenv.open LogDir=C:\users\roger\Application Data\ProtoShares\database ErrorFile=C:\users\roger\Application Data\ProtoShares\db.log
Bound to [::]:3888
Bound to 0.0.0.0:3888
init message: Loading block index...
Opening LevelDB in C:\users\roger\Application Data\ProtoShares\blocks\index
Opened LevelDB successfully
Opening LevelDB in C:\users\roger\Application Data\ProtoShares\chainstate
Opened LevelDB successfully
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: LoadBlockIndex() : CheckIndex failed: CBlockIndex(pprev=02EE7B70, pnext=00000000, nHeight=40982, merkle=bf59006d38733cf29acacd8daef24ce39760459f26524e0fe2d3ad319134b840, hashBlock=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff)


Questions:
1) what does this "ERROR: CheckProofOfWork() : hash doesn't match nBits" mean? Which can be the causes?
2) Is save to "rebuild the block"? Which are the consequences?
3) If "rebuild the block" is not the way to go, what do you recomend me to do?
4) Last one, are my PTS save?

Thanks in advance.

Hi,

After a couple of days mining everything seems to be in place. I.e. wallet transactions look fine and http://pts.syware.de negative values frequency has increased.

Thx for you attention.

Hi donschoe,

Quote from: donschoe on January 01, 2014, 06:29:54 PM
It's a bug on systats i think.

Did you check your stats on beeeeer.org?

I know the following places:

http://ptsweb.beeeeer.org/user/PiuZ92rCsT5VUbdJHaFWnordY89k16iyfQ
http://pts.syware.de/?a=PiuZ92rCsT5VUbdJHaFWnordY89k16iyfQ

The last three payments have had a negative balance and there hasn't been any update since more than 12 hours ago. Really disturbing  because yesterday I decided to move all my miners (not less than 140s/m) to beeeeer.org. Obviously if the situation continues to be the same I will have to move the miners back.

No body else in this situation?

BTW: should I move this thread to what seems to be the "main" PTS discussion thread (https://bitsharestalk.org/index.php?topic=234.0) or it is ok to continue it here?

Regards.

@PYneer, thx for the reply & the post's URL!

Unfortunately,

1st) the post is six weeks old and somehow indicates that the problem should be fixed

2nd) If I'm correct, an overpayment would imply a positive amount greater than the absolute value of the negative amount, but it is not the case: +0.2063  vs. -0.7937

3rd) Negative values have appeared again in the last payments:

Last 100 payments:
Block   Date      Total   Add   Balance
37225   01.01. 0:52   12.68   +0.246   -0.754 PAID!
37065   31.12. 13:51   12.43   +0.1684   0.3167 PAID!
37047   31.12. 12:30   12.26   +0.1483   0.1483
37028   31.12. 11:31   12.11   +0.2929   -0.7071 PAID!
36879   31.12. 1:19   11.82   +0.2953   0.3676 PAID!

so...

Hey,

what does a negative balance reported by pts.syware.de mean? Is this a bug?

Here are the initial lines of the payments report. The negative balance is in the first line:

Last 100 payments:
Block   Date      Total   Add   Balance
36178   29.12. 0:32   10.32   +0.2063   -0.7937 PAID!
36177   29.12. 0:31   10.12   +0.1284   0.2586 PAID!
36168   28.12. 23:48   9.99   +0.1302   0.1302
36137   28.12. 20:25   9.86   +0.1366   0.3131 PAID!

Thanks!