• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

V12 Testing Thread

crowning said:
Code: 
2015-08-02 18:07:07 ERROR: ContextualCheckBlockHeader : forked chain older than last checkpoint (height 1)
2015-08-02 18:07:07 ERROR: ProcessNewBlock : AcceptBlock FAILED
2015-08-02 18:07:07 Misbehaving: 188.226.223.5:19999 (0 -> 100) BAN THRESHOLD EXCEEDED

That's all I get from a freshly installed client...not a single block synced so far.
I guess I just have to wait until some compatible clients show up.

Edit:
Code: 
if (pcheckpoint && nHeight < pcheckpoint->nHeight)
  return state.DoS(100, error("%s : forked chain older than last checkpoint (height %d)", __func__, nHeight));

nHeight == 1 will be a problem for all peers syncing from scratch.
Click to expand...
Yep, same here
eduffield looks like this https://github.com/dashpay/dash/com...75#diff-7ec3c68a81efff79b6ca22ac1f1eabbaR3110 broke it. Uncommented it and sync started.

EDIT: now wallet stoped syncing for some time after "failed to lock cs_main" in log, then disconnected the last single peer, waited, found a new one, and everything repeats after a while... smth wrong with https://github.com/dashpay/dash/commit/171c0b145a5a5644f2b955b3196c1a66093801f5 (and https://github.com/dashpay/dash/commit/64aad03485844b2c79c177911daa0a428da11c92)
 
Last edited by a moderator:
UdjinM6 said:
Yep, same here
eduffield looks like this https://github.com/dashpay/dash/com...75#diff-7ec3c68a81efff79b6ca22ac1f1eabbaR3110 broke it. Uncommented it and sync started.

EDIT: now wallet stoped syncing for some time after "failed to lock cs_main" in log, then disconnected the last single peer, waited, found a new one, and everything repeats after a while... smth wrong with https://github.com/dashpay/dash/commit/171c0b145a5a5644f2b955b3196c1a66093801f5 (and https://github.com/dashpay/dash/commit/64aad03485844b2c79c177911daa0a428da11c92)
Click to expand...

Hmm, I've enabled the caching again.

Are you mining? I've only seen that cs_main issue when mining
 
One of the wallets I used to test v12 keeps getting stuck at block 75799... I've tried to run it with -reindex twice.
 
Question: I have no iptable set up for my testnet server. I've basically left my server open, but I think that's only for denial of service attacks, no? So my question is, could someone have hacked into my server and messed something up? If so, how would they have done that? What, besides IP tables, would I need to protect my servers?

I am not getting any syncing, and before I just overwrite everything and reinstall the OS, I really want to understand what happened exactly, if possible. Or at least see if someone messed with my OS. I get a few connections, but no syncing happens.

Any suggestions? This would be devastating if it happened to me on main net. Well, maybe not devastating, but it would cause me much anxiety and loss of sleep, LOL. I want to avoid it by understanding now ;P
 
TanteStefana said:
Question: I have no iptable set up for my testnet server. I've basically left my server open, but I think that's only for denial of service attacks, no? So my question is, could someone have hacked into my server and messed something up? If so, how would they have done that? What, besides IP tables, would I need to protect my servers?

I am not getting any syncing, and before I just overwrite everything and reinstall the OS, I really want to understand what happened exactly, if possible. Or at least see if someone messed with my OS. I get a few connections, but no syncing happens.

Any suggestions? This would be devastating if it happened to me on main net. Well, maybe not devastating, but it would cause me much anxiety and loss of sleep, LOL. I want to avoid it by understanding now ;P
Click to expand...

Reinstall from scratch!

- Protect your server with iptables (open only used/safe ports)
- ban unwanted traffic with fail2ban
- use SSH publickeys instead of password
 
eduffield said:
Try killing blocks/chainstate/database and resync from scratch.
Click to expand...
Thanks, Evan, that's what I'm trying to do with this wallet.
Now I have another wallet that was created for v11, got synced fine earlier but now it's stuck at block 78031 (0 hours behind).

EDIT: eduffield - now it's ok... lol
 
Last edited by a moderator:
was getting a lot of
Code: 
2015-08-02 21:31:42 CMasternodePaymentWinner::IsValid - Unknown Masternode 712f7ab7035912ac2c7b5e6e58feb94f589a6f950eac4e42861066ec95592813-1
2015-08-02 21:31:42 mnw - invalid message - Unknown Masternode 712f7ab7035912ac2c7b5e6e58feb94f589a6f950eac4e42861066ec95592813-1


so i rm .dash/mn*.dat and seems to have resolved.

but i am still seeing

Code: 
2015-08-02 21:41:37 CActiveMasternode::SendMasternodePing() - Relay Masternode Ping vin = CTxIn(COutPoint(17fc0c59a645dcc6035df0abb679cb3b9f377a677b649bb88c5b78bdab49af61, 0), scriptSig=)
2015-08-02 21:41:37 CActiveMasternode::ManageStatus() - Error on Ping: Too early to send Masternode Ping

EDIT: just had a successful ping.
 
Last edited by a moderator:
cwnage said:
was getting a lot of
Code: 
2015-08-02 21:31:42 CMasternodePaymentWinner::IsValid - Unknown Masternode 712f7ab7035912ac2c7b5e6e58feb94f589a6f950eac4e42861066ec95592813-1
2015-08-02 21:31:42 mnw - invalid message - Unknown Masternode 712f7ab7035912ac2c7b5e6e58feb94f589a6f950eac4e42861066ec95592813-1


so i rm .dash/mn*.dat and seems to have resolved.

but i am still seeing

Code: 
2015-08-02 21:41:37 CActiveMasternode::SendMasternodePing() - Relay Masternode Ping vin = CTxIn(COutPoint(17fc0c59a645dcc6035df0abb679cb3b9f377a677b649bb88c5b78bdab49af61, 0), scriptSig=)
2015-08-02 21:41:37 CActiveMasternode::ManageStatus() - Error on Ping: Too early to send Masternode Ping

EDIT: just had a successful ping.
Click to expand...
Both messages are ok while network upgrades.
First one means that that masternode was not announced on new network and second one - MN is trying to send ping too early after MN self-activate but it should reactivate anyway and send ping later (and it did as far as I see from your "edit" so this part still works :smile:)
 
scratchy said:
Reinstall from scratch!

- Protect your server with iptables (open only used/safe ports)
- ban unwanted traffic with fail2ban
- use SSH publickeys instead of password
Click to expand...
Thanks Scratchy, I'm protected on my mainnet, just not here ;P I guess there is nothing for it, I'll reinstall my os :p
 
eduffield said:
Try killing blocks/chainstate/database and resync from scratch.
Click to expand...
That wallet would not sync at all. I also tried it with a new fresh wallet but still it would not sync one block.

upload_2015-8-2_18-37-37.png


EDIT: Build 249 solves this problem: https://dashpay.atlassian.net/builds/browse/DASHW-DEV-249/artifact/JOB1/gitian-win-dash-dist/
 
Last edited by a moderator:
can anyone tell me what this means:

"EXCEPTION: St12out_of_range \nCInv::GetCommand() : type=15 unknown type \ndash in ProcessMessages() \n"

I'm just starting a new node with 11.2.23 first. Is that the message when the network is running different protocols? It is finally syncing though :)


Oh shit, the one node, the one on my windows machine, that I thought was running fine all this time, stopped syncing at 78097. It acts as if it's finished syncing so it must have gotten hooked on an earlier fork. Hummm.

I really want to get 11.2.23 up and running on testnet before switching. But if everyone has already switched to 12.35, then I may not be able to sync, eh?
 
Last edited by a moderator:
MangledBlue said:
Evan released 35 so I got it running Qt is all
stuck at 19 hours

edit: reboot Qt - not stuck now
78098
Click to expand...
Yah, but I really wanted to sync up the old 11.2.23 and test the upgrade, but I was gone all day yesterday and apparently even my windows testnet wallet never sync'd so I have nothing to try upgrading with. I'm hoping I can still get 11.2.23 to sync so I can upgrade and see if it works smoothly. Ugh!
 
You must log in or register to reply here.
Back
Top