BitShares Forum
Main => Technical Support => Topic started by: Mochilles on November 02, 2014, 10:38:20 am
-
Hi guys,
I'm running the latest 0.4.23.1 64-bit windows wallet and have a Not Connected error.
It synced up to about 11 days ago (and says syncing for about ten seconds on load) but now has no connection.
I have tried:
- Reindexing the blockchain
- Increasing number of connections from the console
- Manually adding all the nodes recommended on the wiki from the console
- Leaving it running overnight for ten hours
At this point I'm out of ideas! Help!
-
Hi guys,
I'm running the latest 0.4.23.1 64-bit windows wallet and have a Not Connected error.
It synced up to about 11 days ago (and says syncing for about ten seconds on load) but now has no connection.
I have tried:
- Reindexing the blockchain
- Increasing number of connections from the console
- Manually adding all the nodes recommended on the wiki from the console
- Leaving it running overnight for ten hours
At this point I'm out of ideas! Help!
Hey and welcome to the community,
I noticed a bunch of people having the same issues currently. To me it seems like a bug in the network code.
- Do you also habe 0 connections state in console->"getinfo"
- can you remove the "peers_leveldb" folder in %APPDATA%\BitShares X" .. this will force the client to connect to the seed nodes!! (keep it running for 15 minutes or so)
-
Hi Xerooc, thanks for your reply.
I've tried your suggestion of removing the peers folder, but without success.
The console getinfo shows zero connections.
-
Apparently, the devs are already on it and it seems they have a potential fix for it ..
https://github.com/BitShares/bitshares/issues/836#issuecomment-58723018
sorry for the inconveniences
-
Thank you sir, I'll keep an eye on the github.
-
I noticed a similar problem in 0.4.23.1 64-bit with a wallet on one of my machines, but with a different wallet on a different machine, 0.4.23.1 64-bit seemed to be fine.
Then, when I copied the problematic Bitshares X folder in the 'roaming' folder (after making backups, of course) to the 'roaming' folder on the new machine, the problem seemed to be solved.
Perhaps this suggests that the problem is related in part to the hardware or the OS?
-
I'm getting the exact same type of error, wallet refuses to connect anymore, config below;
Client version
bitshares_toolkit_revision ab40d8dc51cd4e54c0e05a2e9770fca3f03d6565
bitshares_toolkit_revision_age 33 days ago
blockchain_description Decentralized Autonomous Exchange
blockchain_name BitShares X
boost_version 1.55
build win32 64-bit
client_version v0.4.20
compile_date compiled on Oct 2 2014 at 11:46:22
fc_revision c4e814d7ded6099dc4297aa843d4be7afa98b3ed
fc_revision_age 35 days ago
jenkins_build_number 92
openssl_version OpenSSL 1.0.1g 7 Apr 2014
I am trying to locate the config.json file so I can enable logging but am striking out on that front too. Any help for us noobs would be appreciated. P.S. I filed a help ticket to report the issue.
Many thanks,
Martin
-
I'm getting the exact same type of error, wallet refuses to connect anymore, config below;
Client version
bitshares_toolkit_revision ab40d8dc51cd4e54c0e05a2e9770fca3f03d6565
bitshares_toolkit_revision_age 33 days ago
blockchain_description Decentralized Autonomous Exchange
blockchain_name BitShares X
boost_version 1.55
build win32 64-bit
client_version v0.4.20
compile_date compiled on Oct 2 2014 at 11:46:22
fc_revision c4e814d7ded6099dc4297aa843d4be7afa98b3ed
fc_revision_age 35 days ago
jenkins_build_number 92
openssl_version OpenSSL 1.0.1g 7 Apr 2014
I am trying to locate the config.json file so I can enable logging but am striking out on that front too. Any help for us noobs would be appreciated. P.S. I filed a help ticket to report the issue.
Many thanks,
Martin
Scratch that! I just downloaded and installed 0.4.23.1 from dacsunlimited and it is connected and re-scanning the blockchain as I type :)
-
if you still want to find the config.json file it's located under %APPDATA%\BitShares X for Windows systems and somewhere in /Library/ or for Mac users
-
Same problem here. I'm using Windows 64. Ver 0.4.23.1
I have tried all the procedures under here: https://bitsharestalk.org/index.php?topic=7768.0
but my wallet still says NOT CONNECTED.
I even backed up the wallet and completely removed it from my drive (including "Roaming" folder).
Then I installed it again and imported the wallet.
Still the same problem.
-
go to console: type "getinfo" .. does it say 0 connections and block_head_num: 0
??
-
It responds with:
"blockchain_head_block_num": 0,
"blockchain_head_block_age": null,
"blockchain_head_block_timestamp": null,
"blockchain_average_delegate_participation": "0.00 %",
"blockchain_confirmation_requirement": 202,
"blockchain_delegate_pay_rate": "0.00000 BTSX",
"blockchain_share_supply": "1,999,999,999.81923 BTSX",
"blockchain_blocks_left_in_round": 101,
"blockchain_next_round_time": null,
"blockchain_next_round_timestamp": null,
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"client_data_dir": "C:/Users/Master of Disaster/AppData/Roaming/BitShares X",
"client_version": "v0.4.23.1",
"network_num_connections": 2,
"network_num_connections_max": 200,
"network_chain_downloader_running": false,
"network_chain_downloader_blocks_remaining": null,
"ntp_time": "2014-11-06T15:38:32",
"ntp_time_error": 1.0065390000000001,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "12 days in the future",
"wallet_unlocked_until_timestamp": "2014-11-18T05:23:32",
"wallet_last_scanned_block_timestamp": null,
"wallet_scan_progress": "0.00 %",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
-
"client_version": "v0.4.23.1",
"network_num_connections": 2,
That seems ok .. Just let it run a little longer .. no idea why it has a connection but has not yet loaded blocks ..
are you running a firewall of some kind?
-
Thanks for reply.
No, there is no firewall on any kind. Neither on my router nor in my Windows firewal settings (programs is allowed through firewall).
Yesterday, the wallet worked fine but today when I started it, it said there was an error last time I closed the program and it asked me for permission to re-scan again. I clicked "yes" and since then it's been showing "Not Connected".
Then I went through all the procedures mantioned above with no effect
(http://i156.photobucket.com/albums/t28/bladadupa/Error_zpsf98b01f4.jpg)
-
paging @vikram @toast @bytemaster
sorry dude ... never seen that happen .. you have connections but the wallet won't download ..
maybe you delete everything from the %APPDATA%\BitShares X folder EXCEPT(!!!!!) the "wallets" folder and try again ..
this is odd!
-
I already did like I explained above. It didn't help...
-
Wallet still Not Connected...
-
I have similar issue. Not connected.
Scott Howard's build run on Ubuntu 14.04.1 LTS.
-
I dont no whats up with this wallet it never wants to connect or it dosnt respond just locks up I tried everything uninstalled everything reinstalled it than it takes a year to download the blockchain again cause it stops responding and everytime i install the new patch I wont do nothing I had no problems with this wallet till this change the wallet does no good if ppl cant use it could someone please see if there is a way to get it fixed I no Im not the only one with problems
-
^ I am facing the same problem.Tried everything on win7 & win8 but it just won't sync.
-
have you tried typing the command "get_info" in the console to make sure it isn't syncing? I had the problem with my gui saying "not connected" for a long while. I then tried the magical formula of quitting the program and restarting it again a few times, and eventually, even though it said it wasn't connected, if I repeatedly typed in "get_info" i could see that it was syncing because the number of days it was behind was reducing. Eventually it just caught up and everything is fine now...
-
have you tried typing the command "get_info" in the console to make sure it isn't syncing? I had the problem with my gui saying "not connected" for a long while. I then tried the magical formula of quitting the program and restarting it again a few times, and eventually, even though it said it wasn't connected, if I repeatedly typed in "get_info" i could see that it was syncing because the number of days it was behind was reducing. Eventually it just caught up and everything is fine now...
just checked it the way u suggested it was downloading its just a little aggravating everything was fine till this patch thanks for the tip though i probably uninstalled and re-installed this wallet 50 times for no reason again thanks for the help
-
@mira
Thanks for for your help but get_info command keeps showing "wallet_scan_progress": "0.00 %" .Will leave it on for a while but am just tired now.Hope it will get fixed in the next release.
-
Scan progress is always 0 i had this problem I deleted by config file.. looks like outdated nodes in that file thay wont connect.. dont know if the client gives up trying in time because seems no syncing with older config file there must be some good nodes in there... latest bitcoin does a good job of handling this.
Anyways delete config file and ur good
-
@hotpotato: the output from the "get_info" command that you want to look at to see if it is syncing with the blockchain is "blockchain_head_block_age"
I also at some points have deleted everything in my .bitshares folder ((EXCEPT THE WALLETS FOLDER, DON'T DELETE THAT!)) to get it happily syncing again.
I know it's frustrating. They're still working out the bugs :-)
If it's burning you out I suggest turning on some good dancing music (at high volume), decompress, and try again later -- This is still early, early in the life of this software. You could think of it as being one of the first test drivers of the horseless carriage! I'm sure there were plenty of glitches before they got around to racing...
-
Scan progress is always 0 i had this problem I deleted by config file.. looks like outdated nodes in that file thay wont connect.. dont know if the client gives up trying in time because seems no syncing with older config file there must be some good nodes in there... latest bitcoin does a good job of handling this.
Anyways delete config file and ur good
Already tried with deleting the files but it still wont work.Thanks for your help though.
@hotpotato: the output from the "get_info" command that you want to look at to see if it is syncing with the blockchain is "blockchain_head_block_age"
I also at some points have deleted everything in my .bitshares folder ((EXCEPT THE WALLETS FOLDER, DON'T DELETE THAT!)) to get it happily syncing again.
I know it's frustrating. They're still working out the bugs :-)
If it's burning you out I suggest turning on some good dancing music (at high volume), decompress, and try again later -- This is still early, early in the life of this software. You could think of it as being one of the first test drivers of the horseless carriage! I'm sure there were plenty of glitches before they got around to racing...
Tried deleting everything(except wallets folder) but still get_info is giving me "blockchain_head_block_age": null,
Will take a break and try again later.As for music I have this chill track playing in the background now .Oh, not allowed to post external links. :o
We sure are still in the very early stages.Your horseless carriage analogy brought a smile to my face.Am sure the bts team will come up with a noob friendly, polished product soon.
-
I recently observed similar behaviour for some time - upgraded from 0.4.16, and found that wallet does not even start syncing.
Deleted everything except "wallets" folder, and after this entered exactly state being discussed here. Wallet was showing 12 connections:
>> getinfo
{
"blockchain_head_block_num": 0,
"blockchain_head_block_age": null,
"blockchain_head_block_timestamp": null,
"blockchain_average_delegate_participation": "0.00 %",
"blockchain_confirmation_requirement": 202,
"blockchain_share_supply": "2,499,002,518.57146 BTS",
"blockchain_blocks_left_in_round": 101,
"blockchain_next_round_time": null,
"blockchain_next_round_timestamp": null,
"blockchain_random_seed": "0000000000000000000000000000000000000000",
"client_data_dir": "C:/Users/yvg/AppData/Roaming/BitShares",
"client_version": "v0.4.24",
"network_num_connections": 12,
"network_num_connections_max": 200,
"network_chain_downloader_running": false,
"network_chain_downloader_blocks_remaining": null,
"ntp_time": "2014-11-30T09:54:55",
"ntp_time_error": 0.82485600000000003,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "12 days in the future",
"wallet_unlocked_until_timestamp": "2014-12-11T23:40:32",
"wallet_last_scanned_block_timestamp": null,
"wallet_scan_progress": "0.00 %",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
}
Somehow after [reasonably long] time [tens of minutes] wallet suddenly started syncing. Was it coincident or not, but it was right after I clicked "Overview" (I think it was coincident).
Another thing I currently observe (still syncing) is that "Successfully pushed sync block" count written to p2p.log does not match to one shown in GUI - getinfo shows more or less correct synchronization state, but block count shown in sync status popup in GUI lags really a lot.
CPU load is nearly 100%, and only process using it is BitShares.exe.
Currently I run client on an old Core 2 2.16 GHz machine with 4 Gb RAM (Win7 64-bit), so it can be that either client has some issues when running on slower/older hardware (especially because of some rare thread synchronization issues tend to show up on slow systems and resource starving conditions), or synchronization state visualization inconsistency.
At the moment of writing, "Last block synced" popup shows only about 56000 blocks (and stays in this state for half an hour or so), while getinfo shows 634000 blocks. Execution time of getinfo command is more than 10 seconds.