is the witness thing running under win?

[tonyk]

A lot of activity is going on...but the withness_node still stuck.

[abit]

Looks like you run into a strange state. The active witness list and active committee member list are incorrect. But the block id of head block 2821722 is correct. (This should be able to be solved via --replay-blockchain).

(and I'm sorry that my assumptions of wrong version was incorrect but I kept insisting it)

In regards to the stuck issue, if you don't have another program running and listening on port 8090 or some other required ports, or for some reason the port isn't released cleanly, so current node is blocked from listening on the port / connecting to the network.. maybe p2p.log will help. Or a reboot.

[tonyk]

@tonky: could you please run the cli against your witness and execute "about" in the cli?

Code: [Select]

unlocked >>> about
about
{
  "client_version": "2.0.160128",
  "graphene_revision": "c1c37df31a5dab9beff5f169a00852b87b0d2039",
  "graphene_revision_age": "4 days ago",
  "fc_revision": "6495004302239ae0c775f05a0e78780c3b189502",
  "fc_revision_age": "16 weeks ago",
  "compile_date": "compiled on Jan 30 2016 at 15:34:20",
  "boost_version": "1.58",
  "openssl_version": "OpenSSL 1.0.1g 7 Apr 2014",
  "build": "win32 64-bit"
}
unlocked >>>

Code: [Select]

info
{'active_witnesses': ['1.6.1', '1.6.3', '1.6.4', '1.6.5', '1.6.6', '1.6.7', '1.6.8', '1.6.9', '1.6.10', '1.6.11', '1.6.12', '1.6.13', '1.6.14', '1.6.15', '1.6.16', '1.6.17', '1.6.18', '1.6.19', '1.6.20', '1.6.21', '1.6.22', '1.6.23', '1.6.24', '1.6.25', '1.6.26', '1.6.27', '1.6.28', '1.6.29', '1.6.32', '1.6.33', '1.6.34'], 'chain_id': '4018d7844c78f6a6c41c6a552b898022310fc5dec06da467ee7905a8dad512c8', 'head_block_id': '002b0e5a206413b5f17ee209705b51b3cb90fa4c', 'active_committee_members': ['1.5.0', '1.5.2', '1.5.4', '1.5.5', '1.5.6', '1.5.7', '1.5.8', '1.5.9', '1.5.10', '1.5.11', '1.5.1'], 'next_maintenance_time': '12 days ago', 'head_block_num': 2821722, 'head_block_age': '13 days old', 'participation': '100.00000000000000000'}


[xeroc]

@tonky: could you please run the cli against your witness and execute "about" in the cli?

[cube]

Stupid question maybe, but do you have enough disk space left?

193 G under win, 183 G under Linux

Update.... weird enough, stuck at exactly the same point under Ubuntu. [only difference it stuck a few blocks earlier 2821705..i.e 05 instead of 22

Granted I just ran it, then ran it with --replay-blockchain

At least this is the more supported OS so probably more people can help.

Well, you have not provided the netstats info for seed communication and the p2p log.  We cannot rule out a firewall or a network communication problem.

[abit]

Stupid question maybe, but do you have enough disk space left?

193 G under win, 183 G under Linux

Update.... weird enough, stuck at exactly the same point under Ubuntu. [only difference it stuck a few blocks earlier 2821705..i.e 05 instead of 22

Granted I just ran it, then ran it with --replay-blockchain

At least this is the more supported OS so probably more people can help.

Can I login to your Linux machine and take a look? Or windows? I suspect from the beginning that you're using a wrong version, and still think so. Might be stupid reasons.

[tonyk]

Stupid question maybe, but do you have enough disk space left?

193 G under win, 183 G under Linux

Update.... weird enough, stuck at exactly the same point under Ubuntu. [only difference it stuck a few blocks earlier 2821705..i.e 05 instead of 22

Granted I just ran it, then ran it with --replay-blockchain

At least this is the more supported OS so probably more people can help.

[xeroc]

Stupid question maybe, but do you have enough disk space left?

[tonyk]

[update]
sorry for being somewhat slow with this...

ran the cube's exe.

same result. stuck at the same point - [blochchain ID and block#]

given up more or less on getting this thing working

When you're posting there is another hard fork. No exe file has been released so far. Perhaps you can try to compile by yourself. This guide: https://github.com/neura-sx/neura-sx.github.io/blob/master/BUILD_WIN64.md

yeeh... but thanks.
As I posted moments ago I did listen to today's mumble's recording.
 So... I do  think my internet cannot handle the 'requirements'*  to run a witness node... 

*700 empty blocks... to say nothing if an asshole or two overloads the blockchain with a transaction or 2 every 10,000 blocks...

What is your Internet bandwidth?

I faced similar issue recently during the hard fork - ie blockchain download stuck.   But when I added a working seed node. It started downloading. So all is well.
The recent hard fork caused the binary to be invalid.  I will upload a new binary if the devs have not done so by then.

Edit: Latest Win tools binary is uploaded here - https://github.com/btscube/bitshares-2/releases/tag/20160129
Add a valid seed to the command line arguments eg -s 185.25.22.21:1776

CNX has released latest windows cli tools.
Cube: you didn't update the source/branch of your github repo to newest commit, it looks strange.

Still stuck at the same point as before. (not like Xeldal)
started with --replay-blockchain, btw.

[abit]

[update]
sorry for being somewhat slow with this...

ran the cube's exe.

same result. stuck at the same point - [blochchain ID and block#]

given up more or less on getting this thing working

When you're posting there is another hard fork. No exe file has been released so far. Perhaps you can try to compile by yourself. This guide: https://github.com/neura-sx/neura-sx.github.io/blob/master/BUILD_WIN64.md

yeeh... but thanks.
As I posted moments ago I did listen to today's mumble's recording.
 So... I do  think my internet cannot handle the 'requirements'*  to run a witness node... 

*700 empty blocks... to say nothing if an asshole or two overloads the blockchain with a transaction or 2 every 10,000 blocks...

What is your Internet bandwidth?

I faced similar issue recently during the hard fork - ie blockchain download stuck.   But when I added a working seed node. It started downloading. So all is well.
The recent hard fork caused the binary to be invalid.  I will upload a new binary if the devs have not done so by then.

Edit: Latest Win tools binary is uploaded here - https://github.com/btscube/bitshares-2/releases/tag/20160129
Add a valid seed to the command line arguments eg -s 185.25.22.21:1776

CNX has released latest windows cli tools.
Cube: you didn't update the source/branch of your github repo to newest commit, it looks strange.

[cube]

[update]
sorry for being somewhat slow with this...

ran the cube's exe.

same result. stuck at the same point - [blochchain ID and block#]

given up more or less on getting this thing working

When you're posting there is another hard fork. No exe file has been released so far. Perhaps you can try to compile by yourself. This guide: https://github.com/neura-sx/neura-sx.github.io/blob/master/BUILD_WIN64.md

yeeh... but thanks.
As I posted moments ago I did listen to today's mumble's recording.
 So... I do  think my internet cannot handle the 'requirements'*  to run a witness node... 

*700 empty blocks... to say nothing if an asshole or two overloads the blockchain with a transaction or 2 every 10,000 blocks...

What is your Internet bandwidth?

I faced similar issue recently during the hard fork - ie blockchain download stuck.   But when I added a working seed node. It started downloading. So all is well.
The recent hard fork caused the binary to be invalid.  I will upload a new binary if the devs have not done so by then.

Edit: Latest Win tools binary is uploaded here - https://github.com/btscube/bitshares-2/releases/tag/20160129
Add a valid seed to the command line arguments eg -s 185.25.22.21:1776

[tonyk]

[update]
sorry for being somewhat slow with this...

ran the cube's exe.

same result. stuck at the same point - [blochchain ID and block#]

given up more or less on getting this thing working

When you're posting there is another hard fork. No exe file has been released so far. Perhaps you can try to compile by yourself. This guide: https://github.com/neura-sx/neura-sx.github.io/blob/master/BUILD_WIN64.md

yeeh... but thanks.
As I posted moments ago I did listen to today's mumble's recording.
 So... I do  think my internet cannot handle the 'requirements'*  to run a witness node... 

*700 empty blocks... to say nothing if an asshole or two overloads the blockchain with a transaction or 2 every 10,000 blocks...

[abit]

[update]
sorry for being somewhat slow with this...

ran the cube's exe.

same result. stuck at the same point - [blochchain ID and block#]

given up more or less on getting this thing working

When you're posting there is another hard fork. No exe file has been released so far. Perhaps you can try to compile by yourself. This guide: https://github.com/neura-sx/neura-sx.github.io/blob/master/BUILD_WIN64.md

[tonyk]

[update]
sorry for being somewhat slow with this...

ran the cube's exe.

same result. stuck at the same point - [blochchain ID and block#]

given up more or less on getting this thing working

[abit]

  However you can try my compiled binary just to test it out. Remember to remove the blockchain and object folders.

https://github.com/btscube/bitshares-2/releases

Testing right now...

Did you change your repository in the last 2 mo. or so? I specifically checked, during this ordeal (last 2-3 days) to see if you have any compilation of your own and I did not see any.

[edit] ...and the same result...same chain ID as in the pic above...

Sorry Tony I didn't understand what you've said.

If you problem hasn't get solved yet, it might be a really stupid human error.

You reinstalled cli tools? the file date changed or still 1/4?
what's the path of the files (in the picture)?
what's your exact command for starting witness_node?

By the way I'm using cube's binary file and it works fine.