pinarello
Full Member
 
Offline
Activity: 266
Merit: 100
NXT is the future
|
 |
December 22, 2013, 05:55:24 PM |
|
|
|
|
|
klee
Legendary
Offline
Activity: 1498
Merit: 1000
|
 |
December 22, 2013, 05:56:45 PM |
|
|
|
|
|
davethetrousers
|
 |
December 22, 2013, 05:57:01 PM |
|
I am on a chain with 22264 as last block, and it looks legit generally.
|
|
|
|
laowai80
Member

Offline
Activity: 98
Merit: 10
|
 |
December 22, 2013, 05:57:13 PM |
|
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...
|
|
|
|
Come-from-Beyond
Legendary
Offline
Activity: 2142
Merit: 1010
Newbie
|
 |
December 22, 2013, 05:58:00 PM |
|
Well, we should run more nodes. For now let's just watch which chain wins.
|
|
|
|
Come-from-Beyond
Legendary
Offline
Activity: 2142
Merit: 1010
Newbie
|
 |
December 22, 2013, 05:58:41 PM |
|
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.
|
|
|
|
abctc
Legendary
Offline
Activity: 1806
Merit: 1038
|
 |
December 22, 2013, 06:00:42 PM |
|
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): [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
|
██████████████████████████████████████████████████ ████████████████████████████████████████████████████ ██████████████████████████████████████████████████████ ████████████████████████████████████████████████████████ ████████████████████████████████████████████████████████ ████████████████████████████████████████████████████████████████████ ████████████████████████████████████████████████████████████ ██████████████████████████████████████████████████████████████ ████████████████████████████████████████████████████████████████ ██████████████████████████████████████████████████████████████████ ████████████████████████████████████████████████████████████████████ | , the Next platform. Magis quam Moneta (More than a Coin) |
|
|
|
colinistheman
|
 |
December 22, 2013, 06:00:54 PM |
|
I don't know if I am reporting the right number but it looks like I am presently seeing block # 22310.
But it also looks like it hasn't updated a new block in 25 minutes.
|
|
|
|
Come-from-Beyond
Legendary
Offline
Activity: 2142
Merit: 1010
Newbie
|
 |
December 22, 2013, 06:01:26 PM |
|
I don't know if I am reporting the right number but it looks like I am presently seeing block # 22310
Good
|
|
|
|
Pablito89
|
 |
December 22, 2013, 06:01:41 PM |
|
I don't know if I am reporting the right number but it looks like I am presently seeing block # 22310
like most of us
|
|
|
|
laowai80
Member

Offline
Activity: 98
Merit: 10
|
 |
December 22, 2013, 06:02:58 PM |
|
Put values of lastBlockchainFeeder reported above into wellKnownPeers.
What is lastBlockchainFeeder? It's not in the web.xml file and not reported int he terminal.
|
|
|
|
davethetrousers
|
 |
December 22, 2013, 06:04:46 PM |
|
One quick question: How is the client supposed to know when I can and cannot generate blocks? E.g., You can generate the next block in "9 hours 16 minutes 15 seconds".
Isn't that supposed to be a random distribution, with the fraction of my stake vs the overall coin count times average minutes per block?
P.S.: Last block 22269, looking healthy from here.
|
|
|
|
pinarello
Full Member
 
Offline
Activity: 266
Merit: 100
NXT is the future
|
 |
December 22, 2013, 06:05:12 PM |
|
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. Oh we playing the big league now. Pin
|
|
|
|
klee
Legendary
Offline
Activity: 1498
Merit: 1000
|
 |
December 22, 2013, 06:05:16 PM |
|
I don't know if I am reporting the right number but it looks like I am presently seeing block # 22310
like most of us 
|
|
|
|
colinistheman
|
 |
December 22, 2013, 06:05:31 PM |
|
I sent myself some NXT coin to my wallet from the dgex.com exchange and it hasn't showed up for almost an hour now. Is this normal? When should it be showing up?
|
|
|
|
Come-from-Beyond
Legendary
Offline
Activity: 2142
Merit: 1010
Newbie
|
 |
December 22, 2013, 06:06:05 PM |
|
Put values of lastBlockchainFeeder reported above into wellKnownPeers.
What is lastBlockchainFeeder? It's not in the web.xml file and not reported int he terminal. Guys reported output of getState upthread. Copy values of "lastBlockchainFeeder" returned by getState into "wellKnownPeers".
|
|
|
|
Renatusmc
Newbie
Offline
Activity: 3
Merit: 0
|
 |
December 22, 2013, 06:06:11 PM |
|
depends on how many coins you have and how many active useres run the client. and of course number of transactions :-)
|
|
|
|
leek_rs
Newbie
Offline
Activity: 23
Merit: 0
|
 |
December 22, 2013, 06:06:34 PM |
|
Watching this thread
|
|
|
|
colinistheman
|
 |
December 22, 2013, 06:06:56 PM |
|
depends on how many coins you have and how many active useres run the client. and of course number of transactions :-)
i just did a test of 100 coins
|
|
|
|
laowai80
Member

Offline
Activity: 98
Merit: 10
|
 |
December 22, 2013, 06:08:48 PM |
|
Guys reported output of getState upthread. Copy values of "lastBlockchainFeeder" returned by getState into "wellKnownPeers".
88.198.134.190 this one?
|
|
|
|
|