Author

Topic: NXT :: descendant of Bitcoin - Updated Information - page 2299. (Read 2761629 times)

legendary
Activity: 1792
Merit: 1038
Thx guys.

Change some settings in ur web.xml.

Put hosts listed in lastBlockchainFeed about into "wellKnownPeers". Set other parameters to:

connectTimeout = 2000
readTimeout = 2000
pushThreshold = 1
pullThreshold = 1
- do that, and get (v.  0.4.2):
Code:
[2013-12-22 17:57:36.370] Loading transactions...
[2013-12-22 17:57:38.545] ...Done
[2013-12-22 17:57:38.546] Loading blocks...
[2013-12-22 17:57:41.193] ...Done
[2013-12-22 17:57:41.193] Scanning blockchain...
[2013-12-22 17:57:45.474] ...Done
2013-12-22 17:57:45.517:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@a2e02b2{/,file:/root/nxt/webapps/root/,AVAILABLE}{/root}
2013-12-22 17:57:45.598:INFO:oejs.ServerConnector:main: Started ServerConnector@17be8e6c{HTTP/1.1}{0.0.0.0:7874}
2013-12-22 17:57:47.834:INFO:oejs.ServerConnector:main: Started ServerConnector@2d8b20a0{SSL-http/1.1}{0.0.0.0:7875}
2013-12-22 17:57:59.767:WARN:oejh.HttpParser:qtp1313211444-36: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@738aa857{r=1,a=IDLE,uri=-}
2013-12-22 17:58:21.487:WARN:oejh.HttpParser:qtp1313211444-48: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@3466386e{r=11,a=IDLE,uri=-}
2013-12-22 17:58:22.000:WARN:oejs.HttpChannel:Scheduler-1568884390: Commit failed
java.util.concurrent.TimeoutException: Idle timeout expired: 5189/5000 ms
        at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:153)
        at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Killed

EDIT:  my mistake, that was 0.4.2
legendary
Activity: 2142
Merit: 1010
Newbie
Thx guys.

Change some settings in ur web.xml.

Put hosts listed in lastBlockchainFeed about into "wellKnownPeers". Set other parameters to:

connectTimeout = 2000
readTimeout = 2000
pushThreshold = 1
pullThreshold = 1

ok, trying, terminal is freezing... where is lastBlockchainFeed? not in web.xml...

Put values of lastBlockchainFeeder reported above into wellKnownPeers.
legendary
Activity: 2142
Merit: 1010
Newbie
Well, we should run more nodes. For now let's just watch which chain wins.
member
Activity: 98
Merit: 10
Thx guys.

Change some settings in ur web.xml.

Put hosts listed in lastBlockchainFeed about into "wellKnownPeers". Set other parameters to:

connectTimeout = 2000
readTimeout = 2000
pushThreshold = 1
pullThreshold = 1

ok, trying, terminal is freezing... where is lastBlockchainFeed? not in web.xml...
full member
Activity: 196
Merit: 100
I am on a chain with 22264 as last block, and it looks legit generally.
full member
Activity: 266
Merit: 100
NXT is the future
legendary
Activity: 1946
Merit: 1035
So 22310 is the last block in the "good" chain right?
legendary
Activity: 1498
Merit: 1000
22305
legendary
Activity: 2142
Merit: 1010
Newbie
Restarted again and still stuck at 22303 - any idea what is going on?

Yes, dos attack, network is fragmented. Leave it as is, it will find the longest chain eventually. Rate of orphaned blocks will be high though.
legendary
Activity: 1367
Merit: 1000
Node with 22310 says
Code:
Generated an incorrect block. Waiting for the next one...
legendary
Activity: 2142
Merit: 1010
Newbie
Thx guys.

Change some settings in ur web.xml.

Put hosts listed in lastBlockchainFeed about into "wellKnownPeers". Set other parameters to:

connectTimeout = 2000
readTimeout = 2000
pushThreshold = 1
pullThreshold = 1
legendary
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
Restarted again and still stuck at 22303 - any idea what is going on?
legendary
Activity: 1792
Merit: 1038

I am on 22310
- me too.
Code:
		22310		4747512364439223888		22.12.2013 21:34:25	
1 0 + 1 134 B
1 6149600228563548577 495 %
full member
Activity: 157
Merit: 100
well, i've got this

Code:
{"lastBlock":"16527276160970732808","numberOfAliases":14579,"numberOfBlocks":22306,"lastBlockchainFeeder":"88.198.134.190","totalMemory":61845504,"freeMemory":16504352,"maxMemory":1037959168,"numberOfTransactions":23451,"numberOfUsers":3,"version":"0.4.2","numberOfOrders":0,"time":2440217,"availableProcessors":1,"numberOfAssets":0,"numberOfAccounts":2772}
full member
Activity: 266
Merit: 100
NXT is the future


{"lastBlock":"6149600228563548577","numberOfAliases":14555,"numberOfBlocks":22311,"lastBlockchainFeeder":"99.105.6.193","totalMemory":63225856,"freeMemory":33338768,"maxMemory":259522560,"numberOfTransactions":23424,"numberOfUsers":1,"version":"0.4.2","numberOfOrders":0,"time":2440129,"availableProcessors":4,"numberOfAssets":0,"numberOfAccounts":2772}
legendary
Activity: 1367
Merit: 1000
One node 22310 and no timer other 22291
full member
Activity: 378
Merit: 104
same, 22310 from 18:34:15
hero member
Activity: 695
Merit: 500

Code:
{"lastBlock":"6149600228563548577","numberOfAliases":14555,"numberOfBlocks":22311,"lastBlockchainFeeder":"95.85.22.142","totalMemory":105119744,"freeMemory":19035984,"maxMemory":954466304,"numberOfTransactions":23424,"numberOfUsers":5,"version":"0.4.2","numberOfOrders":0,"time":2440012,"availableProcessors":8,"numberOfAssets":0,"numberOfAccounts":2772}
hero member
Activity: 695
Merit: 500
Same here, I am on block 22310 and that for the last 12min about
Jump to: