https://dl.dropboxusercontent.com/u/67242472/nxtfiles.zip contains
22456 2584657662098653454 23.12.2013 1:16:28
10 0 + 10 1'485 B
1 2790184772903108984 5670 %
Topic: NXT :: descendant of Bitcoin - Updated Information - page 2288. (Read 2761632 times)
Code:
2013-12-23 02:13:11.504:WARN:oejs.HttpChannel:qtp729770861-47: Commit failed
java.util.concurrent.TimeoutException: Idle timeout expired: 30007/30000 ms
at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:15
3)
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)
2013-12-23 02:13:41.578:WARN:oejs.ServletHandler:qtp729770861-49: /nxt
java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired
: 30007/30000 ms
at org.eclipse.jetty.util.BlockingCallback.block(BlockingCallback.java:1
01)
at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:734)
at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:307)
at java.io.OutputStream.write(Unknown Source)
at Nxt.doGet(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696
)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java
:526)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.j
ava:143)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.jav
a:568)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandl
er.java:221)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandl
er.java:1110)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:
453)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandle
r.java:183)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandle
r.java:1044)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.j
ava:141)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(Cont
extHandlerCollection.java:199)
at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerColl
ection.java:109)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper
.java:97)
at org.eclipse.jetty.server.Server.handle(Server.java:459)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:280)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.jav
a:229)
at org.eclipse.jetty.io.AbstractConnection$1.run(AbstractConnection.java
:505)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPoo
l.java:607)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool
.java:536)
at java.lang.Thread.run(Unknown Source)
Caused by:
java.util.concurrent.TimeoutException: Idle timeout expired: 30007/30000 ms
at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:15
3)
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)
The CLOSE_WAIT problem is back...
Then it just stops responding, there is no exception in the log, CPU load is very low, but nothing is happening. Only restart of jetty fixes it.
Code:
nxt@n02:~$ netstat -a -n | grep CLOSE | wc
91692 550152 7335360
i'm at 22425
Are we on a net split again? I have
22441 10105875265190846103 12/22/2013 9:46:51 PM
21 0 + 22 3'159 B
1 1982145270283694244 5792 %
and
22443 9423488697815909938 12/22/2013 10:01:02 PM
99 501'247 + 108 13'942 B
1 6729130164786521364 23170 %
Last one is
22452 2584657662098653454 12/22/2013 10:12:06 PM
1 0 + 1 156 B
1 1038686344906257040 5642 %
22441 10105875265190846103 12/22/2013 9:46:51 PM
21 0 + 22 3'159 B
1 1982145270283694244 5792 %
and
22443 9423488697815909938 12/22/2013 10:01:02 PM
99 501'247 + 108 13'942 B
1 6729130164786521364 23170 %
Last one is
22452 2584657662098653454 12/22/2013 10:12:06 PM
1 0 + 1 156 B
1 1038686344906257040 5642 %
yeah, looks like it.
yes, massive, working on it, online again in a few minutes.
22441 id 5750397643914585440 5792 % you see this?
no, box is down, massive http-bot-requests + node zombies on a tiny single core vps.
wonder it was able to withstand such a long time. iptables doesn't help either.
online again in ~30 min.
So much traffic. Set "readTimeout" and "connectTimeout" to 5000.
Are we on a net split again? I have
22441 10105875265190846103 12/22/2013 9:46:51 PM
21 0 + 22 3'159 B
1 1982145270283694244 5792 %
and
22443 9423488697815909938 12/22/2013 10:01:02 PM
99 501'247 + 108 13'942 B
1 6729130164786521364 23170 %
Last one is
22452 2584657662098653454 12/22/2013 10:12:06 PM
1 0 + 1 156 B
1 1038686344906257040 5642 %
22441 10105875265190846103 12/22/2013 9:46:51 PM
21 0 + 22 3'159 B
1 1982145270283694244 5792 %
and
22443 9423488697815909938 12/22/2013 10:01:02 PM
99 501'247 + 108 13'942 B
1 6729130164786521364 23170 %
Last one is
22452 2584657662098653454 12/22/2013 10:12:06 PM
1 0 + 1 156 B
1 1038686344906257040 5642 %
Quote
the rich guys buying up is believable, yet still, its a very stupid way to be buying coins lol.
Why is buying on dgex.com stupid?
I'm sorry. Its really annoying to the ones who read all these pages in this thread ( I am aware of that cause of another thread I am active). Anyway I cannot read 270 pages for the problem I got and I cannot figure out how to solve it:
"Generated an incorrect block. Waiting for the next one"
Somewhere I have read it is an issue with some experimental version of the "wallet". True? I am using 0.4.2 (downloaded today on that laptop, downloaded today java). Everything is fine except that error.
Any ideas?
Thanks in advance!
"Generated an incorrect block. Waiting for the next one"
Somewhere I have read it is an issue with some experimental version of the "wallet". True? I am using 0.4.2 (downloaded today on that laptop, downloaded today java). Everything is fine except that error.
Any ideas?
Thanks in advance!
Still stuck on: 22292 2159498187382012684 22/12/2013 18:05:06
for more than an hour. Client 0.4.2
How again is this refreshed(restarted/updated?) to the most recent block?
for more than an hour. Client 0.4.2
How again is this refreshed(restarted/updated?) to the most recent block?
Use https://dl.dropboxusercontent.com/u/67242472/nxtfiles.zip
this file doesnt have all .nxt files. should we delete all our curren .nxt files in our existing nxt folder before copying the 3 files in this new nxtfiles.zip file to our existing nxt folder?
Overwriting does the same thing as first deleting these 3 files and copying new ones. Ergo - just overwrite.
You don't actually need these 3 files from "nxtfiles.zip". You need the client (0.4.2) from the first page.
false statement - if you just copy those new files, the old ones that dont have updates stay where they are. I remember in the past that CfB would tell us to not do this - to keep all .nxt files synced when you write them. But he didnt give any guidance here one deleting the old ones
am I on ann invalid chains? my last block I see is 22425 at 11712% and Im forging quite a few blocks in a shorrt period of time
Could you help with and guide me how to start the forging, please?
I don't know how but it happened...
my first block mined.
Very exciting... 5 nxt reward not bad!
[EDIT]
Two blocks... in few minutes, i have no words!
my first block mined.
Very exciting... 5 nxt reward not bad!
[EDIT]
Two blocks... in few minutes, i have no words!
who's got which last block?
22443 7542917420413518667 Sonntag, 22. Dezember 2013 22:59:37
0 0 + 0 0 B
1 14984706285971634025 446629 %
who's got which last block?
I don't know how but it happened...
my first block mined.
Very exciting... 5 nxt reward not bad!
[EDIT]
Two blocks... in few minutes, i have no words!
my first block mined.
Very exciting... 5 nxt reward not bad!
[EDIT]
Two blocks... in few minutes, i have no words!
well, just hope you arent forging on the invalid forkedchain or you wont get to keep it
With the high risk of orphans and / or branching, what implications does this have to hazards of payments being double spent by us / to us when large volumes with block changes necessarily occurring during processing are in effect?
If u do as I advised - send with large deadline and then just broadcast - u r 100% safe.
yes, massive, working on it, online again in a few minutes.
22441 id 5750397643914585440 5792 % you see this?
why doesn't anyone mind, then, that DGEX.com is limiting your earning potential by not allowing you to place orders more than 30% lower off the 'current_price' ?
There was a lot of manipulation, some people bought a little NXT in much different prices than usual and were probably waiting for someone to fall to their traps.
Quote
or are you all just blindly buying at whatever price it comes?
you think its cheap? 5 days ago or so it was 0.00000330 and now all of a sudden its 0.0000679
you think its cheap? 5 days ago or so it was 0.00000330 and now all of a sudden its 0.0000679
Some rich people arrived and they were buying millions of Nxt, so the price got higher thanks to them.
Quote
Can you please explain to me, what was released by the NXT development team to justify this price jump?
No services, no automated exchange, no nothing.
Today was released new feature - Aliases + there were a some new articles in the press.No services, no automated exchange, no nothing.
Aliases is a rip off from emunie - they have it for months now.
the rich guys buying up is believable, yet still, its a very stupid way to be buying coins lol.
And as for the exchange limitations - it is not for the exchange owner to be deciding what margins are allowed and what not when it comes to placing buy orders.
What if I do serious calculations and can see that the price will drop to a certain amount in the coming days/weeks/months?
I can't put in a buy order and forget about it for a while. The price will drop and go up again - its normal. A single exchange imposing its own rules, which benfit only them is not acceptable. I don't see limits on sell orders. Implement them and I will shut up.
Now the owner is the only one who can remove the limit, let the price drop and catch all the cheap NXT.
If you guys think this is fair and how it is supposed to be - you will lose your money very fast.
Hell, I will make a coin of my own and open a manual exchange and do the same. Will be a millionaire in no time with 'traders' like you lot
I don't know how but it happened...
my first block mined.
Very exciting... 5 nxt reward not bad!
[EDIT]
Two blocks... in few minutes, i have no words!
my first block mined.
Very exciting... 5 nxt reward not bad!
[EDIT]
Two blocks... in few minutes, i have no words!
yes, massive, working on it, online again in a few minutes.
Jump to: