Got a crash and it cost me a whole 1/2 day of mining. Was running then died while I was sleeping.
Exception in thread "Thread-8" java.nio.channels.NotYetConnectedException
at sun.nio.ch.AsynchronousSocketChannelImpl.read(AsynchronousSocketChannelImpl.java:240)
at sun.nio.ch.AsynchronousSocketChannelImpl.read(AsynchronousSocketChannelImpl.java:296)
at java.nio.channels.AsynchronousSocketChannel.read(AsynchronousSocketChannel.java:407)
at Nxt$Peer$1.completed(Unknown Source)
at Nxt$Peer$1.completed(Unknown Source)
at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
at sun.nio.ch.UnixAsynchronousSocketChannelImpl.finishConnect(UnixAsynchronousSocketChannelImpl.java:278)
at sun.nio.ch.UnixAsynchronousSocketChannelImpl.finish(UnixAsynchronousSocketChannelImpl.java:198)
at sun.nio.ch.UnixAsynchronousSocketChannelImpl.onEvent(UnixAsynchronousSocketChannelImpl.java:213)
at sun.nio.ch.KQueuePort$EventHandlerTask.run(KQueuePort.java:301)
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
[2013-11-30 11:17:03.435] Saving blocks...
[2013-11-30 11:17:03.540] ...Done
[2013-11-30 11:17:48.170] Saving blocks...
[2013-11-30 11:17:48.269] ...Done
[2013-11-30 11:18:14.077] Saving blocks...
[2013-11-30 11:18:14.182] ...Done
[2013-11-30 11:18:28.207] Saving blocks...
[2013-11-30 11:18:28.321] ...Done
Exception in thread "Thread-15" java.nio.channels.NotYetConnectedException
at sun.nio.ch.AsynchronousSocketChannelImpl.read(AsynchronousSocketChannelImpl.java:240)
at sun.nio.ch.AsynchronousSocketChannelImpl.read(AsynchronousSocketChannelImpl.java:296)
at java.nio.channels.AsynchronousSocketChannel.read(AsynchronousSocketChannel.java:407)
at Nxt$Peer$1.completed(Unknown Source)
at Nxt$Peer$1.completed(Unknown Source)
at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
at sun.nio.ch.UnixAsynchronousSocketChannelImpl.finishConnect(UnixAsynchronousSocketChannelImpl.java:278)
at sun.nio.ch.UnixAsynchronousSocketChannelImpl.finish(UnixAsynchronousSocketChannelImpl.java:198)
at sun.nio.ch.UnixAsynchronousSocketChannelImpl.onEvent(UnixAsynchronousSocketChannelImpl.java:213)
at sun.nio.ch.KQueuePort$EventHandlerTask.run(KQueuePort.java:301)
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
[2013-11-30 11:19:21.174] 10: java.nio.channels.NotYetConnectedException
[2013-11-30 11:19:21.174] Nxt stopped.
Topic: NXT :: descendant of Bitcoin - Updated Information - page 2512. (Read 2761650 times)
I cannot connect to Nxt now... Are the servers down..?
Make sure that your time is synced (try syncing it over the Internet)
I cannot connect to Nxt now... Are the servers down..?
The network is fine atm
eid
I cannot connect to Nxt now... Are the servers down..?
BCNext gave me a new version that is supposed to fix problem related to direct buffers issue. It's a fix for peer connections only, if it works he will do the same for bots (API). I hope this will solve ur problem and no workaround will be necessary. I'm testing/profiling it now.
I had the list of codes somewhere, give me 5 mins.
I had the list of codes somewhere, give me 5 mins.
Come from beyond, I just wanted to say thank you, you are doing a great job! Without you Nxt would be a dead horse, so I would like to say thanks and donate 10k Nxt to you
Please post your Nxt account so I can send them to you
The list of API error codes - https://bitcointalksearch.org/topic/m.3778035
great, thanks cfb.
Come-From-Behind.... you my friend are a fucking legend!
(I thought I had done the time sync earlier today, but when i checked the log... it said FAILED to update...)
I seen the little Snowflake in the time column and thought... ohh cool I am exact same time with them.
Now i realize not.
Should be always numbers!
(I thought I had done the time sync earlier today, but when i checked the log... it said FAILED to update...)
I seen the little Snowflake in the time column and thought... ohh cool I am exact same time with them.
Now i realize not.
Should be always numbers!
The list of API error codes - https://bitcointalksearch.org/topic/m.3778035
We need more bootstrapping peers, the old ones went offline. Anyone wants to become a well-known peer with blue balloon next to its address?
Sure - if you help me out!What do we need to do?
Owners of nodes that r accessible from the Internet should just PM me with their static IPs/domains.
-> 87.230.14.1
question to the java pros here.
with the latest version the nulllpointerexeptions are gone which is fine.
but still having many ReadPendingException, ClosedChannelException, IOException
and stuff like this, which leads into many freezes when using the api intense.
already tested different socket libs (libcurl, native socket and even via piped wget commandline)
and different java versions (openjdk/sun) to access the api with no difference.
starting the client with bigger heap size doesn't work either.
instead adding more features to the blockchain explorer i am busy coding
workarounds for this which bothers me a little.
(the last days i wished bcnext would have coded the client in plain ansi c instead java)
the client is running on a lean debian server, so this shouldn't be the reason
but a final check could be to change the os, perhaps the *java-diva* ;-) needs
something different. any further ideas i could look into?
edit: an api-errorcode listing would be nice to.
BCNext gave me a new version that is supposed to fix problem related to direct buffers issue. It's a fix for peer connections only, if it works he will do the same for bots (API). I hope this will solve ur problem and no workaround will be necessary. I'm testing/profiling it now.
I had the list of codes somewhere, give me 5 mins.
I had problems with the Blocks and such not updating when I went to the new Client version.
Tried it a couple of times etc. without any luck.
Deleted the peers list... now I have only 3 peers.
88.198.210.245 88.198.210.245 0 B 34 B -
146.185.168.142 146.185.168.142 0 B 18 B -
162.243.145.83 162.243.145.83 0 B 50 B -
But seems it does not connect to them.
I opened up port 7874, but still nothing. Looks like i am sending, but not receiving anything.
And no other Peers are showing up (previously there were 15 accepted, 30 blacklisted)
Tried it a couple of times etc. without any luck.
Deleted the peers list... now I have only 3 peers.
88.198.210.245 88.198.210.245 0 B 34 B -
146.185.168.142 146.185.168.142 0 B 18 B -
162.243.145.83 162.243.145.83 0 B 50 B -
But seems it does not connect to them.
I opened up port 7874, but still nothing. Looks like i am sending, but not receiving anything.
And no other Peers are showing up (previously there were 15 accepted, 30 blacklisted)
Time/timezone issue.
I had problems with the Blocks and such not updating when I went to the new Client version.
Tried it a couple of times etc. without any luck.
Deleted the peers list... now I have only 3 peers.
88.198.210.245 88.198.210.245 0 B 34 B -
146.185.168.142 146.185.168.142 0 B 18 B -
162.243.145.83 162.243.145.83 0 B 50 B -
But seems it does not connect to them.
I opened up port 7874, but still nothing. Looks like i am sending, but not receiving anything.
And no other Peers are showing up (previously there were 15 accepted, 30 blacklisted)
Tried it a couple of times etc. without any luck.
Deleted the peers list... now I have only 3 peers.
88.198.210.245 88.198.210.245 0 B 34 B -
146.185.168.142 146.185.168.142 0 B 18 B -
162.243.145.83 162.243.145.83 0 B 50 B -
But seems it does not connect to them.
I opened up port 7874, but still nothing. Looks like i am sending, but not receiving anything.
And no other Peers are showing up (previously there were 15 accepted, 30 blacklisted)
We need more bootstrapping peers, the old ones went offline. Anyone wants to become a well-known peer with blue balloon next to its address?
Sure - if you help me out!What do we need to do?
Owners of nodes that r accessible from the Internet should just PM me with their static IPs/domains.
-> 87.230.14.1
question to the java pros here.
with the latest version the nulllpointerexeptions are gone which is fine.
but still having many ReadPendingException, ClosedChannelException, IOException
and stuff like this, which leads into many freezes when using the api intense.
already tested different socket libs (libcurl, native socket and even via piped wget commandline)
and different java versions (openjdk/sun) to access the api with no difference.
starting the client with bigger heap size doesn't work either.
instead adding more features to the blockchain explorer i am busy coding
workarounds for this which bothers me a little.
(the last days i wished bcnext would have coded the client in plain ansi c instead java)
the client is running on a lean debian server, so this shouldn't be the reason
but a final check could be to change the os, perhaps the *java-diva* ;-) needs
something different. any further ideas i could look into?
edit: an api-errorcode listing would be nice to.
Do clients automatically do reverse DNS lookup before broadcast? I noticed that on other clients it doesn't show "nxt.c4c.io" on announced address.
I don't know. Let's wait when source code of peer connection revealed. This will happen soon.
We need more bootstrapping peers, the old ones went offline. Anyone wants to become a well-known peer with blue balloon next to its address?
Yes, nxt.c4c.io
Thx.
BTW, post ur IPs here, so I don't need to resend them to BCNext.
Do clients automatically do reverse DNS lookup before broadcast? I noticed that on other clients it doesn't show "nxt.c4c.io" on announced address.
We need more bootstrapping peers, the old ones went offline. Anyone wants to become a well-known peer with blue balloon next to its address?
Yes, nxt.c4c.io
Thx.
BTW, post ur IPs here, so I don't need to resend them to BCNext.
We need more bootstrapping peers, the old ones went offline. Anyone wants to become a well-known peer with blue balloon next to its address?
Yes, nxt.c4c.io
We need more bootstrapping peers, the old ones went offline. Anyone wants to become a well-known peer with blue balloon next to its address?
Sure - if you help me out!What do we need to do?
Owners of nodes that r accessible from the Internet should just PM me with their static IPs/domains.
We need more bootstrapping peers, the old ones went offline. Anyone wants to become a well-known peer with blue balloon next to its address?
Sure - if you help me out!What do we need to do?
We need more bootstrapping peers, the old ones went offline. Anyone wants to become a well-known peer with blue balloon next to its address?
Can you not make this part of the client? I'm thinking long-term here..
Well, in long-term blacklisting should be used. It's just a list of peers that were offline when u tried to connect to them. In a week u may decide to unblacklist them and try to connect again. I see nothing wrong with this approach.
It just seems like unnecessary maintenance that could be automated. Why not traverse through the blacklist every 30 minutes or so and see if you can connect to them?
Most users aren't going to want to maintain the blacklist, and they shouldn't need to.
Maybe u r right. BCNext has his own ideas and usually they look strange. At the moment this issue is not in the high-priority list.
Jump to: