So, finalizing everything, if my real time is UTC+2 and it is correct, the difference in 1 hour of block AAAAA I see in blockchainexplorer and my client is normal and it is not the error I always get when I have a chance to forge but do not forge succesfuly?

That is my configuration I have, my timezone is UTC+2 and time synced with time server.

So you want to say, that difference in 1 hour what i see in my two chrome windows (the same block number in block explorer comparing with my client window) is normal and errors in forging a block doesn't related?

OK, I live in Lithuania, which is UTC+2. In blockchainexplorer block has timestamp of UTC+1. So here is a difference in 1 hour between blockchainexplorer timestamp and my client time.

A little bit confused:( here is my situation:

Chrome tab with blockchainexplorer:

42716   5848194006771653811    16.01.2014 15:12:50    6    105.99    6    0   14571285356259793594

Another chrome tab in client:

42716      14571285356259793594      1/16/2014 4:12:50 PM   
6      0 + 6      1'326 B   
2      5848194006771653811      106 %

So difference on the same PC is 1 hour. And I never forge a block, just always receive generating block errors. Is it like should be or it can be, that there some kind of bug regarding time zones?

Checked with time servers, my clock is correct, it's exactly.

My time zone is set correct to the location I am. Do you mean, I have to set my time zone not to the place where I live, but to the same blockchainexplorer is showing? Is it not a bug?

Is it possible, that I cannot forge any block during one month of running server and client, even that I had around 30 chances to do that? Maybe problem is in time zone? As I see, timestamps of blocks in blockexplorer ir UTC +1, my time zone is UTC+2, in other words blocks in my client is +1 hours.

Cool down and relax

CFB don't want to spread a fear or panic in market, he'll sell everything in steps, until 50000 block

Flaw will appear after 50000 block

I think CFB found very very critical-fatal-serious flaw in code, so he is selling all his NXT

I'd like to, but I don't know his address. Maybe we'll wait for coffeecoin

Received, thank you. I can say, that CFBgex exchange works perfectly and fast

Sent 0.473 BTC

Hi CFBdex

I'm interested too in 0.5 BTC to NXT

0.5 from 14NZZk2Gfz4QfgMwRokCqCGT2qmGxTxEBt to 4552966463117743023

The same with me, just I see you succeeded with the forging. I' not.

Client 0.5.5. It happens again:

2014-01-11 21:15:53.088:INFO:oejs.ServerConnector:main: Started ServerConnector@
621fb2b9{SSL-http/1.1}{0.0.0.0:7875}
[2014-01-12 09:24:45.048] Generated an incorrect block. Waiting for the next one
...
[2014-01-12 09:25:18.897] Re-scanning blockchain...
[2014-01-12 09:25:48.117] ...Done
[2014-01-12 10:28:58.823] Generated an incorrect block. Waiting for the next one
...
[2014-01-12 10:29:28.174] Re-scanning blockchain...
[2014-01-12 10:29:47.702] Generated an incorrect block. Waiting for the next one
...
[2014-01-12 10:29:48.707] Generated an incorrect block. Waiting for the next one
...
[2014-01-12 10:29:57.651] ...Done

I'm running my server and client from the end of December, 24/7. In this period I had many chances to forge blocks, but no one with success. Is it normal behaviour of my server?

P.S. After this error appears, there were minus recent blocks, a lot of unconfirmed transactions. F5 solved it, I didn't need to restart everything.

I'm stuck half an hour on block 37723. Restart made, stuck still.

Making transfer gives lot of jetty errors in command window. Version 0.5.4e