BitShares Forum
Main => Technical Support => Topic started by: sudo on October 10, 2015, 01:33:35 pm
-
just three days left for upgrade
not every user can handle the consolo backup action.
0.9.3c GUI backup json can't be read by bts2.0 import
-
@fav, please bring it back to the General Discussion.
It's very important for the devs to notice this thread and address it asap.
It's not something that can wait. The longer we delay the bigger mess and confusion is created. Why are we doing it to ourselves?
The current situation is inconsistent with the official announcements (https://bitsharestalk.org/index.php/topic,18752.msg241359.html#msg241359) and BM's mumble talk.
-
@fav, please bring it back to the General Discussion.
It's very important for the devs to notice this thread and address it asap.
It's not something that can wait. The longer we delay the bigger mess and confusion is created. Why are we doing it to ourselves?
The current situation is inconsistent with the official announcements (https://bitsharestalk.org/index.php/topic,18752.msg241359.html#msg241359) and BM's mumble talk.
+5%
-
@fav, please bring it back to the General Discussion.
It's very important for the devs to notice this thread and address it asap.
It's not something that can wait. The longer we delay the bigger mess and confusion is created. Why are we doing it to ourselves?
The current situation is inconsistent with the official announcements (https://bitsharestalk.org/index.php/topic,18752.msg241359.html#msg241359) and BM's mumble talk.
+5%
devs are aware, there are tons of thread regarding this issue.
ask xeroc in the migration thread https://bitsharestalk.org/index.php/topic,18714.0.html for help, if you can't figure out how to copy paste a line or got some issues with finding the file
-
@fav, please bring it back to the General Discussion.
It's very important for the devs to notice this thread and address it asap.
It's not something that can wait. The longer we delay the bigger mess and confusion is created. Why are we doing it to ourselves?
The current situation is inconsistent with the official announcements (https://bitsharestalk.org/index.php/topic,18752.msg241359.html#msg241359) and BM's mumble talk.
+5%
devs are aware, there are tons of thread regarding this issue.
ask xeroc in the migration thread https://bitsharestalk.org/index.php/topic,18714.0.html for help, if you can't figure out how to copy paste a line or got some issues with finding the file
@fav, myself I'm not having any issues.
I'm just worried our reputation is at risk if we neglect problems like this and hide them from the most visible place which happens to be the General Discussion.
But if you say you are sure the devs are aware and still don't see fixing it as a priority - I rest my case.
I just haven't seen a single comment from the devs but instead I have seen plenty of legitimate complaints from disappointed users.
-
@fav, please bring it back to the General Discussion.
It's very important for the devs to notice this thread and address it asap.
It's not something that can wait. The longer we delay the bigger mess and confusion is created. Why are we doing it to ourselves?
The current situation is inconsistent with the official announcements (https://bitsharestalk.org/index.php/topic,18752.msg241359.html#msg241359) and BM's mumble talk.
+5%
devs are aware, there are tons of thread regarding this issue.
ask xeroc in the migration thread https://bitsharestalk.org/index.php/topic,18714.0.html for help, if you can't figure out how to copy paste a line or got some issues with finding the file
@fav, myself I'm not having any issues.
I'm just worried our reputation is at risk if we neglect problems like this and hide them from the most visible place which happens to be the General Discussion.
But if you say you are sure the devs are aware and still don't see fixing it as a priority - I rest my case.
I just haven't seen a single comment from the devs but instead I have seen plenty of legitimate complaints from disappointed users.
@bytemaster
-
@fav
As I'm reading more and more user feedback like this (https://bitsharestalk.org/index.php/topic,18714.msg243189.html#msg243189), would you point me to the place on the forum which makes you think the devs are well aware of the problem.
-
https://github.com/bitshares/bitshares/issues/1558
-
https://github.com/bitshares/bitshares/issues/1558
It only shows that the problem has been reported.
It does not mean the devs are aware of the problem itself nor the scale of PR damage this is causing us.
Please help me to communicate it to them.
-
I've letting the client sync for a while, however, it doesn't, the time since Last Block was Synced just keeps increasing instead of decreasing. Tried it yesterday and today but keeps happening. Maybe I just should let it be for a while? Or should I try something on the console?
-
I've letting the client sync for a while, however, it doesn't, the time since Last Block was Synced just keeps increasing instead of decreasing. Tried it yesterday and today but keeps happening. Maybe I just should let it be for a while? Or should I try something on the console?
If you are on Windows I can share what helped in my case:
- make sure there is only one BitShares.exe process running (sometimes as a result of relaunching after a crash there two or more such processes running and they interfere with each other)
- make sure there is enough space on your hard drive (the blockchain currently needs around 6 GB of space on the OS drive, i.e. the C: drive)
- try to restart the GUI as it might be the case the blockchain is already synced but only the GUI is stuck
-
I've letting the client sync for a while, however, it doesn't, the time since Last Block was Synced just keeps increasing instead of decreasing. Tried it yesterday and today but keeps happening. Maybe I just should let it be for a while? Or should I try something on the console?
If you are on Windows I can share what helped in my case:
- make sure there is only one BitShares.exe process running (sometimes as a result of relaunching after a crash there two or more such processes running and they interfere with each other)
- make sure there is enough space on your hard drive (the blockchain currently needs around 6 GB of space on the OS drive, i.e. the C: drive)
- try to restart the GUI as it might be the case the blockchain is already synced but only the GUI is stuck
I only have 1 process running
There's enough space in my hard drive
I tried to restart it yesterday and today but this keeps happening
I type "info" on the console and I get
"blockchain_head_block_age": "58 hours old",
"blockchain_head_block_timestamp": "2015-10-09T03:05:10",
Makes sense since it's increasing and is now last synced since 2 days ago, however I also get
"wallet_scan_progress": "100.00 %",
How is it 100% scanned if it's missing the last 2 days? Or is it about the last time it scanned my transactions when it was synced 2 days ago? Or is it about this
"wallet_last_scanned_block_timestamp": "2015-10-07T17:51:30" saying at that time it was 100% scanned?
-
I've letting the client sync for a while, however, it doesn't, the time since Last Block was Synced just keeps increasing instead of decreasing. Tried it yesterday and today but keeps happening. Maybe I just should let it be for a while? Or should I try something on the console?
If you are on Windows I can share what helped in my case:
- make sure there is only one BitShares.exe process running (sometimes as a result of relaunching after a crash there two or more such processes running and they interfere with each other)
- make sure there is enough space on your hard drive (the blockchain currently needs around 6 GB of space on the OS drive, i.e. the C: drive)
- try to restart the GUI as it might be the case the blockchain is already synced but only the GUI is stuck
This & : wired connection works flawless, with wireless I never achieved a full sync "from zero"
-
How is it 100% scanned if it's missing the last 2 days? Or is it about the last time it scanned my transactions when it was synced 2 days ago?
I think there is no contradiction in being "100% scanned" and not fully synced.
I guess "100% scanned" only means that whatever part of the blockchain you've managed to sync, this part has been scanned. i.e. all transactions involving any of your accounts are reflected in the GUI.
And I guess the increasing time since the last sync means that the blockchain is growing with each new block but your wallet is stuck and for some reason is unable to sync the last two days that remain.
The ultimate solution (assuming you're on Windows) is to quit the GUI, make sure there is no BitShares.exe running, and delete this folder:
C:\Users\[your user name]\AppData\Roaming\BitShares\chainBut be aware that this will reset the whole blockchain and will force the sync process to start from scratch which may take several hours depending on your internet connection and the speed of your machine.
Whatever you do, you are safe as long as you do not lose this folder:
C:\Users\[your user name]\AppData\Roaming\BitShares\wallets
EDIT: and one more thing - if your only purpose is to export your wallet (aiming for 2.0 import) I think you do not need to be synced to able to do it. Just follow the instructions available here:
http://docs.bitshares.eu/migration/howto-exporting-wallet.html
-
Thanks jakub +5%
I just wanted to sync because I've read somewhere you should send all your balance to yourself. Really simple and easy to follow guide from xeroc, thanks!
Edit: just tried the export command and apparently I can't find the file in the BitShares folder. Aftet the command I got the "OK" so everything should be fine but I can't find it.
-
Thanks jakub +5%
I just wanted to sync because I've read somewhere you should send all your balance to yourself. Really simple and easy to follow guide from xeroc, thanks!
Edit: just tried the export command and apparently I can't find the file in the BitShares folder. Aftet the command I got the "OK" so everything should be fine but I can't find it.
https://bitsharestalk.org/index.php/topic,18714.msg243152.html#msg243152
-
Thanks jakub +5%
I just wanted to sync because I've read somewhere you should send all your balance to yourself. Really simple and easy to follow guide from xeroc, thanks!
Edit: just tried the export command and apparently I can't find the file in the BitShares folder. Aftet the command I got the "OK" so everything should be fine but I can't find it.
I couldn't find the file either until I started using the full path as I described it here:
https://bitsharestalk.org/index.php/topic,18714.msg243224.html#msg243224
And regarding the requirement to fully sync before export - it's not so simple as I initially thought. Please read xeroc's explanation here:
https://bitsharestalk.org/index.php/topic,18714.msg243319.html#msg243319
-
this is a really big problem, though I know you tech guys will not think so.
-
Thanks jakub +5%
I just wanted to sync because I've read somewhere you should send all your balance to yourself. Really simple and easy to follow guide from xeroc, thanks!
Edit: just tried the export command and apparently I can't find the file in the BitShares folder. Aftet the command I got the "OK" so everything should be fine but I can't find it.
I couldn't find the file either until I started using the full path as I described it here:
https://bitsharestalk.org/index.php/topic,18714.msg243224.html#msg243224
And regarding the requirement to fully sync before export - it's not so simple as I initially thought. Please read xeroc's explanation here:
https://bitsharestalk.org/index.php/topic,18714.msg243319.html#msg243319
I did it with the full path and I can confirm the file was created. However I didn't run the client as admin beforehand, is that a problem?
-
I did it with the full path and I can confirm the file was created. However I didn't run the client as admin beforehand, is that a problem?
I don't think it matters as long as the file was created. If admin rights were needed the file couldn't have been created.
-
I have tried for 8 hours to open and create new wallet (windows) - 400+ days of blockchain sync - and it will not succeed.
I think I have closed and opened wallet 15 times - always made sure no bitshares process was running before a new restart.
It always get stuck after trying to sync just a few days - is this really supposed to happen on the day of official release?
-
It always get stuck after trying to sync just a few days - is this really supposed to happen on the day of official release?
no, you just decided to sync up 400 days. or did you address yourself with this question?
don't touch your client, it'll move on eventually
or
wait until I or someone else uploaded the full chain
-
not sure what you mean with 'I decided..'?
I am a new user and downloaded the wallet from the official page to try it - I don't have any old wallets
and after waiting for hours for further chain download I have given up - it's stuck completely - or do you expect me to leave it waiting for days?
-
not sure what you mean with 'I decided..'?
I am a new user and downloaded the wallet from the official page to try it - I don't have any old wallets
and after waiting for hours for further chain download I have given up - it's stuck completely - or do you expect me to leave it waiting for days?
if you don't have any funds in your wallet, since you're new, don't sync up. it's the old client and will be replaced with 2.0 later today
-
oh - shouldn't that info be available on the download page?
I didn't see any that is..