Just to inform, 0.7.6 runs smoothly on Android TV stick public node. For a while  Picuntu? Please share hardware and software information, I am VERY interested... I bricked a stick for this... Ubuntu 13.10 in Android, TV stick with RK3066 chip would you be nice enough to post a few pics, usually the chip name doesnt come on the package, I just want to know how it looks so when I go search for it I would know, thank you. Personally I run on http://www.tvstar.eu/smart-tv-stick-ii/ but it should run on any android tv stick. |
|
|
|
Just to inform, 0.7.6 runs smoothly on Android TV stick public node. For a while Picuntu? Please share hardware and software information, I am VERY interested... I bricked a stick for this... Ubuntu 13.10 in Android, TV stick with RK3066 chip |
|
|
|
Just to inform, 0.7.6 runs smoothly on Android TV stick public node. For a while |
|
|
|
Crimi666 While I'm not registered in nextcoing.org and read you had problems with www.peerexplorer.com and looking for person, who took 4100 NXT, maybe this will help you : http://nextcoins.ru/share/Look for "Александр Королев 13117504042955556224 3 NXT 28 января в 12:05" Maybe some russians could help you. Good luck |
|
|
|
|
One another (maybe) bug in 0.7.5:
Sometime I noticed, that some transactions disappear from the transaction list. Total account sum remains the same. After F5 they appear again.
|
|
|
|
Thanks for the quick reply.
I am using 0.7.5 which I d/loaded from nxtcrypto.org.
Would being on a fork mean my password logs me into the wrong account number? Remember, I can't find anything in the explorer either.
I am presently putting the client on my Windows machine to see if that helps.
Did you wait until complete blockchain loads? |
|
|
|
Back to problems with my public node. Today I see all blocks, which appears in blockchain and in recents blocks are not accepted in my public node with the error "DEBUG: Block XXXXXXXXXXXXXXXXXXXX not accepted. Previous block id doesn't match". What is going on? Do I need to shutdown my node? Public node http://217.17.88.5:7874/ It shows correct blockchain blocks, it is not on fork. |
|
|
|
Chuckone, in which list do you see your node and what version is showing near it?
Which lists? I cannot see myself in the NRS. But I run 0.7.5. What is your public node address? |
|
|
|
[2014-02-17 21:22:23.586] DEBUG: Failed to accept block 13734259069497850723 at
height 68803 received from node55.nxtbase.com, blacklisting
[2014-02-17 21:22:26.391] DEBUG: Failed to accept block 13734259069497850723 at
height 68803 received from miasik.no-ip.org, blacklisting
[2014-02-17 21:22:50.345] DEBUG: Failed to accept block 209947979157787352 at he
ight 68804 received from nxt.homer.ru, blacklisting
[2014-02-17 21:23:02.295] DEBUG: Failed to accept block 209947979157787352 at he
ight 68804 received from node10.nxtbase.com, blacklisting
a I don't understand why it keeps happening to your node, but again those two block ids are from the correct blockchain - at least on the nodes I run. I am still not sure, who determines what is the correct chain? i did a video interview with tai zen about how the network discovers the right chain. i cant make any promises but it may be helpful. http://www.youtube.com/watch?v=ZzKyXzZJJA8Okay, let me ask you some questions. I put these ones on the table some time ago in my analysis of 'Transparent Forging' and CfB haven't answered it, yet. So, maybe you can. You said: "The higher the stake involved in forging a block the 'better' the block." So, how should a node (not the network as every node decides on their own) decide when two blocks are forged: one from account A and one from account B. Now, there are several cases: 1) A comes first, TF says A is before B => A is on top of chain, B gets rejected when arriving (and vice versa) 2) B comes first, TF says A is before B => A didn't forge => B is on top of chain (and vice versa) 3) 2) happend; A arrived late; what happens? Will B get popped off? Chuckone, in which list do you see your node and what version is showing near it? |
|
|
|
|
Returning back to my public node errors, I see, that my public node is in known peers list, not in active peers. Also in this list my node has version ?(?)@? Maybe from here comes problems?
|
|
|
|
[2014-02-17 21:22:23.586] DEBUG: Failed to accept block 13734259069497850723 at
height 68803 received from node55.nxtbase.com, blacklisting
[2014-02-17 21:22:26.391] DEBUG: Failed to accept block 13734259069497850723 at
height 68803 received from miasik.no-ip.org, blacklisting
[2014-02-17 21:22:50.345] DEBUG: Failed to accept block 209947979157787352 at he
ight 68804 received from nxt.homer.ru, blacklisting
[2014-02-17 21:23:02.295] DEBUG: Failed to accept block 209947979157787352 at he
ight 68804 received from node10.nxtbase.com, blacklisting
I don't understand why it keeps happening to your node, but again those two block ids are from the correct blockchain - at least on the nodes I run. I am still not sure, who determines what is the correct chain? i did a video interview with tai zen about how the network discovers the right chain. i cant make any promises but it may be helpful. http://www.youtube.com/watch?v=ZzKyXzZJJA8Anon, I think I'm sure I am not on forked chain. Check http://217.17.88.5:7874/with base targets like those i would tend to agree. i do not think you are on a fork. OK. So what is the problem? In public node i see errors for not accepting 90% of good blocks, which are good in blockchain, private node and public node. |
|
|
|
[2014-02-17 21:22:23.586] DEBUG: Failed to accept block 13734259069497850723 at
height 68803 received from node55.nxtbase.com, blacklisting
[2014-02-17 21:22:26.391] DEBUG: Failed to accept block 13734259069497850723 at
height 68803 received from miasik.no-ip.org, blacklisting
[2014-02-17 21:22:50.345] DEBUG: Failed to accept block 209947979157787352 at he
ight 68804 received from nxt.homer.ru, blacklisting
[2014-02-17 21:23:02.295] DEBUG: Failed to accept block 209947979157787352 at he
ight 68804 received from node10.nxtbase.com, blacklisting
I don't understand why it keeps happening to your node, but again those two block ids are from the correct blockchain - at least on the nodes I run. I am still not sure, who determines what is the correct chain? i did a video interview with tai zen about how the network discovers the right chain. i cant make any promises but it may be helpful. http://www.youtube.com/watch?v=ZzKyXzZJJA8Anon, I think I'm sure I am not on forked chain. Check http://217.17.88.5:7874/ |
|
|
|
Jean-Luc Really strange behavior with my public node. I see "DEBUG: Block AAAAAAAAAAAAAAAAAAAA not accepted. Previous block id doesn't match", while block AAAAAAAAAAAAAAAAAAAA I see exists in public node recent blocks, private node recent blocks and in blockchain. How to understand these errors? EDIT: Public node for checking http://217.17.88.5:7874/ |
|
|
|
[2014-02-17 20:15:55.657] DEBUG: Failed to accept block 2507106602597677499 at h
eight 68774 received from node01.nxtcrypto.de, blacklisting
[2014-02-17 20:16:02.117] DEBUG: Failed to accept block 2507106602597677499 at h
eight 68774 received from node90.nxtbase.com, blacklisting
[2014-02-17 20:16:06.913] DEBUG: Failed to accept block 2507106602597677499 at h
eight 68774 received from node01.nxtcrypto.de, blacklisting
Block 2507106602597677499 is the correct block to be at that height: http://87.230.14.1/nxt/nxt.cgi?action=1000&blk=2507106602597677499If your node refuses to accept it, this means you are on a fork. Your base target is probably very high too, another indication of being on the wrong fork. If it doesn't recover by itself, you will need to delete the nxt_db folder and redownload the blockchain. Okay, strange. I started 0.7.5 fresh. So no files from a previous installation, downloaded the blockchain from scratch. Also sending and receiving money goes without a problem (I even forged a block yesterday evening). I will try to redownload the blockchain. Thanks for answering! Yes, that's strange. I also get mass of these errors on my public node, but I think I'm sure I am not on the fork, comparing public node blocks info with private nodeblocks and blockchain. |
|
|
|
I keep getting 100's of these messages (NRS 0.7.5)
[2014-02-17 11:58:47.291] DEBUG: Failed to accept block 5019498541751544021 at h
eight 68491 received from vps5.nxtcrypto.org, blacklisting
[2014-02-17 11:58:48.350] DEBUG: Failed to accept block 5019498541751544021 at h
eight 68491 received from vps5.nxtcrypto.org, blacklisting
[2014-02-17 11:58:51.529] DEBUG: Failed to accept block 5019498541751544021 at h
eight 68491 received from vps1.nxtcrypto.org, blacklisting
[2014-02-17 11:58:52.579] DEBUG: Failed to accept block 5019498541751544021 at h
eight 68491 received from vps5.nxtcrypto.org, blacklisting
[2014-02-17 11:58:54.779] DEBUG: Failed to accept block 5019498541751544021 at h
eight 68491 received from vps5.nxtcrypto.org, blacklisting
[2014-02-17 11:58:56.980] DEBUG: Failed to accept block 5019498541751544021 at h
eight 68491 received from vps5.nxtcrypto.org, blacklisting
[2014-02-17 11:58:58.318] DEBUG: Failed to accept block 5019498541751544021 at h
eight 68491 received from vps1.nxtcrypto.org, blacklisting
[2014-02-17 11:58:59.369] DEBUG: Failed to accept block 5019498541751544021 at h
eight 68491 received from vps5.nxtcrypto.org, blacklisting
What's causing this? Can this be ignored?
My public node acts the same. |
|
|
|
|
What is going on in bter? Price to da moon.
|
|
|
|
What does this mean?
[2014-02-14 10:39:40.346] DEBUG: Will pop block 5073332198957728923 at height 66148
[2014-02-14 10:39:40.347] DEBUG: Will pop block 8348856438008341233 at height 66147
[2014-02-14 10:39:40.348] DEBUG: Reversal of alias assignment not supported
[2014-02-14 10:39:40.348] DEBUG: Popping off last block not possible, will do a rescan
[2014-02-14 10:39:40.349] Re-scanning blockchain...
[2014-02-14 10:39:54.734] ...Done
[2014-02-14 10:39:54.737] DEBUG: Generate block failed: Previous block id doesn't match
I'm getting the same errors both on public and home nodes. |
|
|
|
How about: nemini confide (ne BCNext quidem)
"Trust no one" (not even BCNext)
- may be " magis quam moneta" - "more than coin" +1 A world with the money can not be perfect->Mundus non potest esse perfectior aere |
|
|
|
Do we need this command everytime we start NRS, or forging is started automatically with the start of NRS? |
|
|
|
|
Show Posts
