Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - anychto

#1
Quote from: yoyowd on August 22, 2017, 09:05:04 PM
Quote from: anychto on August 22, 2017, 03:33:54 PM
2928481ms th_a       application.cpp:573           handle_block         ] Got block: #129615 0001fa4feda3bf61184ddf510bb0d64a9f80c1d0 time: 2017-08-22T14:48:48 latency: 481 ms from: 209413652/j
eff  irreversible: 129591 (-24)
2931557ms th_a       application.cpp:573           handle_block         ] Got block: #129616 0001fa50fb4583ab5d0cf8647c6987aeb3fef269 time: 2017-08-22T14:48:51 latency: 557 ms from: 209416038/d
umdumgal  irreversible: 129592 (-24)
2934867ms th_a       application.cpp:573           handle_block         ] Got block: #129617 0001fa513108ef8b2c064e1f84ce25337629b9c2 time: 2017-08-22T14:48:54 latency: 867 ms from: 25997/init1
  irreversible: 129593 (-24)
2940790ms th_a       application.cpp:573           handle_block         ] Got block: #129619 0001fa53be2136895b2e421d0dc19feb28105cc7 time: 2017-08-22T14:49:00 latency: 790 ms from: 209414065/a
bit  irreversible: 129594 (-25)
2940791ms th_a       fork_database.cpp:66          push_block           ] Pushing block to fork database that failed to link: 0001fa53be2136895b2e421d0dc19feb28105cc7, 129619
2940791ms th_a       fork_database.cpp:67          push_block           ] Head: 129617, 0001fa513108ef8b2c064e1f84ce25337629b9c2
2940822ms th_a       application.cpp:602           handle_block         ] Error when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
    {}
    th_a  fork_database.cpp:87 _push_block

    {"new_block":{"previous":"0001fa52390a055afa6e89e0b93b51b3ab6f798e","timestamp":"2017-08-22T14:49:00","witness":209414065,"transaction_merkle_root":"0000000000000000000000000000000000000000
","witness_signature":"204e6e4147cff8a1274daf0c8cdf47341414b43fd34caa676ca764d307a2bc0778171f5491ada4fa11763c555161763fbe6101758ba454645177d7173c8af837cf","transactions":[]}}
    th_a  db_block.cpp:208 _push_block
2941125ms th_a       application.cpp:573           handle_block         ] Got block: #129618 0001fa52390a055afa6e89e0b93b51b3ab6f798e time: 2017-08-22T14:48:57 latency: 4125 ms from: 209411264/blockman  irreversible: 129594 (-24)
2943562ms th_a       application.cpp:573           handle_block         ] Got block: #129620 0001fa54694a498ab7c794dee652bdb53c15cc79 time: 2017-08-22T14:49:03 latency: 562 ms from: 209411732/kimziv  irreversible: 129594 (-26)
2946861ms th_a       application.cpp:573           handle_block         ] Got block: #129621 0001fa554363f2cd4b0cb2a0acf46a990eabc2b3 time: 2017-08-22T14:49:06 latency: 861 ms from: 25997/init1  irreversible: 129594 (-27)
2949548ms th_a       application.cpp:573           handle_block         ] Got block: #129622 0001fa563164714e90ec4d02915bf5ce32c0f3bb time: 2017-08-22T14:49:09 latency: 548 ms from: 209416038/dumdumgal  irreversible: 129594 (-28)
Killed


之前是正常接收和出块的消息。然后后面不知为何出错......启动命令里已经加上--replay了。
另外进程被kill之后似乎见证人没有自动下线......?因此错过了十几个block generation了......
偶尔出现 unlinkable block 属于正常情况,特别是你的节点或者他人节点网络不稳定的时候,以及重新从头开始同步的时候。
出于网络整体安全方面考虑,被动触发离线需要等比较长一段时间,现在测试网里这个参数是3小时。具体参数可以用get_global_properties命令看。

另外,kill是你主动发起的?如果不是,可能原因是内存不足。

既然是正常情况看来不用担心了......kill我不确定是自己screen误操作还是系统自动终止了。0.75G的内存配置似乎有点小了。跑节点后期占用内存会越来越大么。

对了,有什么办法可以把node运行的输出打印到文件里方便之后查看并寻找问题么。
#2
2928481ms th_a       application.cpp:573           handle_block         ] Got block: #129615 0001fa4feda3bf61184ddf510bb0d64a9f80c1d0 time: 2017-08-22T14:48:48 latency: 481 ms from: 209413652/j
eff  irreversible: 129591 (-24)
2931557ms th_a       application.cpp:573           handle_block         ] Got block: #129616 0001fa50fb4583ab5d0cf8647c6987aeb3fef269 time: 2017-08-22T14:48:51 latency: 557 ms from: 209416038/d
umdumgal  irreversible: 129592 (-24)
2934867ms th_a       application.cpp:573           handle_block         ] Got block: #129617 0001fa513108ef8b2c064e1f84ce25337629b9c2 time: 2017-08-22T14:48:54 latency: 867 ms from: 25997/init1
  irreversible: 129593 (-24)
2940790ms th_a       application.cpp:573           handle_block         ] Got block: #129619 0001fa53be2136895b2e421d0dc19feb28105cc7 time: 2017-08-22T14:49:00 latency: 790 ms from: 209414065/a
bit  irreversible: 129594 (-25)
2940791ms th_a       fork_database.cpp:66          push_block           ] Pushing block to fork database that failed to link: 0001fa53be2136895b2e421d0dc19feb28105cc7, 129619
2940791ms th_a       fork_database.cpp:67          push_block           ] Head: 129617, 0001fa513108ef8b2c064e1f84ce25337629b9c2
2940822ms th_a       application.cpp:602           handle_block         ] Error when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
    {}
    th_a  fork_database.cpp:87 _push_block

    {"new_block":{"previous":"0001fa52390a055afa6e89e0b93b51b3ab6f798e","timestamp":"2017-08-22T14:49:00","witness":209414065,"transaction_merkle_root":"0000000000000000000000000000000000000000
","witness_signature":"204e6e4147cff8a1274daf0c8cdf47341414b43fd34caa676ca764d307a2bc0778171f5491ada4fa11763c555161763fbe6101758ba454645177d7173c8af837cf","transactions":[]}}
    th_a  db_block.cpp:208 _push_block
2941125ms th_a       application.cpp:573           handle_block         ] Got block: #129618 0001fa52390a055afa6e89e0b93b51b3ab6f798e time: 2017-08-22T14:48:57 latency: 4125 ms from: 209411264/blockman  irreversible: 129594 (-24)
2943562ms th_a       application.cpp:573           handle_block         ] Got block: #129620 0001fa54694a498ab7c794dee652bdb53c15cc79 time: 2017-08-22T14:49:03 latency: 562 ms from: 209411732/kimziv  irreversible: 129594 (-26)
2946861ms th_a       application.cpp:573           handle_block         ] Got block: #129621 0001fa554363f2cd4b0cb2a0acf46a990eabc2b3 time: 2017-08-22T14:49:06 latency: 861 ms from: 25997/init1  irreversible: 129594 (-27)
2949548ms th_a       application.cpp:573           handle_block         ] Got block: #129622 0001fa563164714e90ec4d02915bf5ce32c0f3bb time: 2017-08-22T14:49:09 latency: 548 ms from: 209416038/dumdumgal  irreversible: 129594 (-28)
Killed


之前是正常接收和出块的消息。然后后面不知为何出错......启动命令里已经加上--replay了。
另外进程被kill之后似乎见证人没有自动下线......?因此错过了十几个block generation了......
#3
Quote from: yoyowd on August 21, 2017, 09:40:43 PM
Quote from: anychto on August 21, 2017, 07:26:25 PM
1149000ms th_a       witness.cpp:195               block_production_loo ] Not producing block for 209420985 because I don't have the private key for YYW82qoU3N6dwoRHRM4y3QhGF3XQrrrcSUCnmDJJZondR7GSfaPfY
1150000ms th_a       witness.cpp:195               block_production_loo ] Not producing block for 209420985 because I don't have the private key for YYW82qoU3N6dwoRHRM4y3QhGF3XQrrrcSUCnmDJJZondR7GSfaPfY
1151000ms th_a       witness.cpp:195               block_production_loo ] Not producing block for 209420985 because I don't have the private key for YYW82qoU3N6dwoRHRM4y3QhGF3XQrrrcSUCnmDJJZondR7GSfaPfY

试了几次都出现丢块,回头看记录的时候发现错误提示是这个。
不过在运行的时候已经把privkey也追加到运行参数里面了,可能是什么原因导致出块失败了呢。
有几次启动程序都会出现 Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production),似乎需要反复启动几次程序才能接收其他人的出块。

运行的指令是这个(私钥用privkey代替了):
./yoyow_node --rpc-endpoint -w 209420985 -private-key '["YYW82qoU3N6dwoRHRM4y3QhGF3XQrrrcSUCnmDJJZondR7GSfaPfY","privkey"]'
你上面的错误提示有两种,一个是 because I don't have the private key ,那么是参数设错了,命令里私钥参数是 --private-key 最前面是两个横杠,不是一个

另一种错 production is disabled until we receive a recent block 有可能是系统时间不同步;如果时间已经同步了,那就要等一会,可以到 client 里面用 info 或者 get_dynamic_global_properties 命令看同步状态, head_block_num , head_block_age 和 time 这几个值,是否是最新。

如果 node 里出现 unlinkable 的问题,目前的临时解决方案是启动命令里加一个 --replay 参数
./yoyow_node --rpc-endpoint -w 209420985 --private-key '["YYW82qoU3N6dwoRHRM4y3QhGF3XQrrrcSUCnmDJJZondR7GSfaPfY","privkey"]' --replay

谢谢~出块成功了,unlinkable也没出现了。
#4
1149000ms th_a       witness.cpp:195               block_production_loo ] Not producing block for 209420985 because I don't have the private key for YYW82qoU3N6dwoRHRM4y3QhGF3XQrrrcSUCnmDJJZondR7GSfaPfY
1150000ms th_a       witness.cpp:195               block_production_loo ] Not producing block for 209420985 because I don't have the private key for YYW82qoU3N6dwoRHRM4y3QhGF3XQrrrcSUCnmDJJZondR7GSfaPfY
1151000ms th_a       witness.cpp:195               block_production_loo ] Not producing block for 209420985 because I don't have the private key for YYW82qoU3N6dwoRHRM4y3QhGF3XQrrrcSUCnmDJJZondR7GSfaPfY

试了几次都出现丢块,回头看记录的时候发现错误提示是这个。
不过在运行的时候已经把privkey也追加到运行参数里面了,可能是什么原因导致出块失败了呢。
有几次启动程序都会出现 Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production),似乎需要反复启动几次程序才能接收其他人的出块。

运行的指令是这个(私钥用privkey代替了):
./yoyow_node --rpc-endpoint -w 209420985 -private-key '["YYW82qoU3N6dwoRHRM4y3QhGF3XQrrrcSUCnmDJJZondR7GSfaPfY","privkey"]'
#5
YOYOW / Re: YOYOW测试网报名帖
August 21, 2017, 01:47:08 PM
报名测试。
用户名:alice
公钥:YYW5i6pAEHvddtRQ9BuqZhFy7m5QghGwXMSyT9dNN76T8QL2Y95Z6
#6
YOYOW / Re: YOYOW测试网报名帖
August 17, 2017, 03:31:53 PM
报名参加测试。
#7
There're 3 styles and those styles are quite elegant.
But it'd be better if there're some more or if one can easily customize his own style/syntax.
#8
Since yesterday I found that I could do nothing ... I have balances on several assets, but found out to be impossible to make any exchange. For example I tried to buy some BTS with BTC and my balance indicated was around 0.089. I placed my order and received an error code like this:
itr -> get_balance() >= -delta: Insufficient Balance: xxx's balance of 0.00000120 OPEN.BTC is less than required 0.00000121 OPEN.BTC
I have changed the API server, using Chrome browser instead of the desktop app but it failed always.