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.

Messages - abit

Pages: 1 ... 270 271 272 273 274 275 276 [277] 278 279 280 281 282 283 284 ... 309

4141

Technical Support / Re: Block sync stuck at 2074788 on Mac wallet

« on: March 30, 2015, 03:14:02 pm »

//Update: sorry for the wrong information I've ever posted. Corrected below.

Yes you are on a fork. Reindex doesn't work in this case.
You need to remove the chain folder and resync.
Try replace your checkpoints.json with the one in this post https://bitsharestalk.org/index.php?topic=15218.msg196858#msg196858 , then resync.

4142

中文 (Chinese) / 0.8钱包问题小结

« on: March 30, 2015, 03:47:14 am »

0.8钱包问题小结

1. 事情经过
1) 由于0.8.1钱包发布比较仓促，很多受托人在分叉块 2113000 之前来不及升级到最新版，导致分叉链比较长；
2) 由于0.8.1升级时没有强制re-index，就是说钱包不会重新检查本地chain的每个块是否符合规则，所以升级前如果已经跑到分叉链，就会卡住；
3) 按照现在的分叉链切换算法，当钱包在分叉链上跑了超过360个块之后，不能自动切回主链，就算手工re-index也不行，只能删除 chain 目录重新下载；
4) 使用 0.8.0 版本的普通用户（非受托人），很可能跑到分叉链上，删除 chain 目录重新同步仍然可能跑到分叉链上；
5) 现在版本的钱包，收到其他节点的块时，如果发现与自己的出块规则不匹配，会把整个块的内容记入 log 日志，同时还会记录到 exceptions 目录，导致占用硬盘空间大

2. 问题分析和解决
1) 无法同步到最新块
1- 确定钱包是不是最新版本(v0.8.1)，由于官方没有发布 Mac 版本的可执行文件下载，建议 Mac 用户自己编译升级，或者等发布，或者按下面步骤~~碰运气~~
（编辑更新：不想升级或者没办法升级到0.8.1的同学，可以下载这个帖子里面的checkpoints.json
https://bitsharestalk.org/index.php?topic=15218.msg196858#msg196858
替换掉自己钱包数据目录的同名文件，然后删除chain目录重新下载就不会再跑岔了。）
2- 如果块链数据已经损坏，或者是在 2113000 块之后，也就是北京时间3月24号晚上20:35之后升级到最新版本的，需要删除 chain 目录重新同步
3- 如果显示没有网络连接，可以尝试删除 peers.leveldb 目录重新同步
4- 其他方案：下载云盘区块数据替换、使用 chain_server 、手工添加节点等

2) 数据目录占用硬盘空间太大
1- 退出钱包，删除 logs 目录和 exceptions 目录，重新启动钱包
2- 对于需要长时间保持钱包开启的用户，比如受托人
a- 针对 logs目录：将数据目录中 config.json 里的 logging 部分的 "enabled": true 全部改为 false ，重启钱包
b- 针对 exceptions 目录：修改 libraries/client/client.cpp ，删除 665,850,867,1234-1237 行代码，即 _exception_db.store() 相关代码，重新编译

4143

General Discussion / Re: BitShares 0.8.0 Feedback

« on: March 30, 2015, 03:43:28 am »

Quote from: Bitty on March 28, 2015, 05:55:35 am

Blockchain stuck at block 2074788.
Mac client.
Upgraded to 0.8.

What can I do?

Users who're using 0.8.0 may run into the wrong fork, then have to delete the chain folder and re-sync from scratch (and may run into the wrong fork again). So it's recommended to release a 0.8.1 binary for MacOS.
It's also recommended that all users upgrade to version 0.8.1
@vikram

4144

General Discussion / Re: there is no apple version of V0.8.1

« on: March 30, 2015, 03:41:33 am »

Quote from: xeroc ¯\_(ツ)_/¯ on March 27, 2015, 04:44:04 pm

Quote from: kokojie on March 27, 2015, 04:33:34 pm
0.8.1 is delegate only I believe
*confirmed*
and it contains only marginal changes over 0.8.1 .. nothing you would see in the GUI .. also nothing that has any effect anylonger

Mac users who're using 0.8.0 may run into the wrong fork, then have to delete the chain folder and re-sync from scratch (and may run into the wrong fork again). So it's recommended to release a 0.8.1 binary for MacOS.

4145

Technical Support / Re: Disk space?

« on: March 29, 2015, 12:35:20 pm »

I also noticed that size of logs and exceptions folder increasing fast with v0.8.0.
Perhaps need to tweak config.json to avoid disk space issue.

//Edit:
Looks like it's possible to disable logging. Dont know if it's recomended though.
Dont know if it's possible to truncate exceptions folder while the client is running.
@developers please advise.
@delegates please keep an eye on your server's disk space usage.

4146

中文 (Chinese) / Re: BTS国内注册的水龙，菜鸟弄的。

« on: March 23, 2015, 02:07:44 am »

Quote from: heyD on March 22, 2015, 10:26:58 am

不用注册？难道作者不知道星在飘这个人，他可以写个脚本疯狂注册账号，直到把水龙头资金耗光。

从我的 iPhone 发送，使用 Tapatalk

对的，建议加个验证码之类

4147

中文 (Chinese) / Re: BTS国内注册的水龙，菜鸟弄的。

« on: March 23, 2015, 02:05:40 am »

Quote from: BTSdac on March 22, 2015, 07:38:53 am

BTS国内注册的水龙，菜鸟弄的。
小伙伴们说国外的水龙访问困难，弄了个简陋的国内注册水龙头
http://121.42.33.218:3000/ 国内BTS注册的水龙头，不用验证自由注册

对于non-titan账号，这个功能在重钱包试过没问题，在web钱包试的时候发现一点问题。

大家知道，账号有 owner_key和active_key ，最新版的钱包创建账号时owner_key和active_key是不同的，因为这样更安全。但是这样也导致出现一些复杂情况。

在钱包的keys界面显示的是active_key，当把这个key填到楼主的水龙头里注册的时候，水龙头会把这个key同时当做owner_key和active_key来注册账号，也就是说楼主的水龙头注册出来的账号的owner_key和active_key是一样的，与自行从最新版钱包注册账户的结果不同。

最新版本的重钱包，会同时检测钱包里账户的active_key和owner_key是否注册，如果发现其中一个被注册，就会自动将钱包中的账号显示为“已注册”，并且更新钱包里记录的账号的owner_key和active_key，与块链上的注册名同步。

最新版的web钱包，观察下来只会检测owner_key是否注册，而不会检测active_key，所以按推荐流程注册成功后钱包状态不会更新。如果在控制台执行 “wallet_get_account 账户名” 取到owner_key填到水龙头，则账户注册成功后钱包状态会更新。

优化思路：
1. 水龙头方面：参考官方水龙头，将owner_key和active_key同时作为注册要素（API方面是否支持还不清楚）
2. web钱包方面：参照重钱包，检测active_key是否已被注册

4148

General Discussion / Re: why no Order history&K chart ? in BDR.AAPL : BitCNY market

« on: March 23, 2015, 12:37:13 am »

Afaik there is a feature/bug in current implemention of market history recording, which causes that volume of non-bts pairs trading wont be recorded to the database, as a result prices wont be recorded as well.
I will look into this issue.
Is it ok to record the volume of asset whose ID is smaller? The volumes of bts pairs are recorded this way, however it looks odd for other assets. Will the Gui be able to handle the flipping markets in this case?
@svk @valzav

4149

General Discussion / Re: Reworking the wallet trading interface

« on: March 21, 2015, 03:04:03 am »

Quote from: svk on March 20, 2015, 05:35:44 pm

Thanks for all the feedback everyone! I've kept working on this yesterday and today, and now have a workable version combining what I had with some of your ideas. I hope you'll recognize it Arhag

All orders are now grouped together, shorts with sells and buys with covers (covers not yet implemented). Shorts are color-coded blue, buys green, sells red.

Clicking on "Account orders history" replaces the blockchain orders with your personal orders.

Volume, high, low and change are for the current day.

Clicking on the "Margin calls" or "Shorts" button makes the respective tables visible one level below the current tables. Inverting the market switches the buttons correctly.

Clicking on the "Cover" tab replaces the orders history table with the open margin orders table, I had to put it there due to space issues.

For the courageous you can check it out by pulling the branch from github as always.

I think it could be better if the 'order books' field and 'new orders' field are closer, so people don't need to move eyes/mouse across the screen, it's useful especially when you implemented the 'click and fill order form' feature (another click needed for submit) in the future.

4150

General Discussion / Re: Alternative GUI for BitShares

« on: March 21, 2015, 02:29:28 am »

Good job

4151

General Discussion / Re: BitShares 0.7.0 Feedback

« on: March 21, 2015, 02:14:56 am »

Quote from: DataSecurityNode on March 20, 2015, 12:54:10 pm

I do notice however though during startup that the disk access for whatever reason is extremely high. Why so much disk access? Is there some kind of complete reindexing taking place at startup?

The client loads the full chain database's data and indexes from disk into memory or into some kind of cache at startup.

4152

Muse/SoundDAC / Re: Micro update

« on: March 21, 2015, 01:01:45 am »

Quote from: toast on March 20, 2015, 09:53:05 pm

We were waiting for 0.7.0 because of the network bug. Now that it's out there's no reason to delay. I'll maybe do more test distributions on devshares and then do the real thing before March 25th.

Just a note: the 0.7.0 out there is not real 0.7.0, it's just a unfinished patch.

4153