Quote from: tiker on April 06, 2015, 02:22:32 PM

Both of my nodes seem to have gone off on a fork or something...
Recent blocks:

Code:

Height Date Amount Fee Nr TX Generator Payload Base Target
277935 06/04/2015 10:18:08 0 0 0 NAS-87P5-WQH2-4E4A-A7G8W 0 B 40498 %
277934 05/04/2015 10:01:21 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 20249 %
277933 05/04/2015 10:00:19 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 19596 %

My local node keep trying to forge block 277935 since it hasn't seen a block since yesterday. It seems that some of the other nodes are rejecting it.

My VPS is in agreement with my local node.

I'm restarting my nodes now to see if it helps.

Edit:
Patapato:
Are you running custom nodes? It looks like you or someone else is generating blocks with invalid signatures:

Code:

[2015-04-06 10:26:04.151] DEBUG: Will pop block 5937549519284143825 at height 277935
[2015-04-06 10:26:04.153] DEBUG: Blacklisting 89.247.146.250 because of: nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed
[2015-04-06 10:27:06.217] DEBUG: Will pop block 5937549519284143825 at height 277935
[2015-04-06 10:27:06.219] DEBUG: Blacklisting 88.130.194.138 because of: nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed
[2015-04-06 10:27:51.778] DEBUG: Will pop block 5937549519284143825 at height 277935
[2015-04-06 10:27:51.780] DEBUG: Blacklisting 89.247.161.67 because of: nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed
[2015-04-06 10:28:17.989] DEBUG: Blacklisting 89.247.161.163 because of: nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed
[2015-04-06 10:29:01.112] DEBUG: Will pop block 5937549519284143825 at height 277935
[2015-04-06 10:29:01.114] DEBUG: Blacklisting 88.130.194.55 because of: nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed

I think these messages "nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed" are because of my node:
* these IPs resolve to my internet provider
* My IP changes every day as i'm on dynamic IP
* The DNS name for my node is updated periodicaly
* the peer name, of my node, displayed on the client resolves to different IP. Don't know if the client stores also the IPs.
* As my IP changes, depending on the DNS update, blocks generated from my node should trigger these messages as the Signature is bound to the provided host name.

The network is still vulnerable to all kind if things, with only 2-3 nodes.
During the last couple of days i had some periodes where my node forged all the blocks.
Not sure if this was the exact network status or if it synced since then.
A couple of days back i had some similar strange things going on as suddenly the last block list updated itself.

My node seems to be relatively in sync with Patapatos:

Code:

279184 4/6/2015 21:03:14 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 14119 %
279183 4/6/2015 20:59:10 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 7060 %
279182 4/6/2015 20:57:52 0 0 0 NAS-H5AW-7J9F-7VCY-DJ8NB 0 B 5430 %
279181 4/6/2015 20:56:41 0 0 0 NAS-H5AW-7J9F-7VCY-DJ8NB 0 B 4589 %