Author Topic: Wallet Not Connected despite trying all the tricks  (Read 8395 times)

0 Members and 1 Guest are viewing this topic.

Offline BitCoin Operated Boy

  • Newbie
  • *
  • Posts: 13
    • View Profile
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

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
go to console: type "getinfo" .. does it say 0 connections and block_head_num: 0
??

Offline BitCoin Operated Boy

  • Newbie
  • *
  • Posts: 13
    • View Profile
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.
« Last Edit: November 06, 2014, 02:50:40 pm by BitCoin Operated Boy »

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
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

Offline Martin81Vette

  • Newbie
  • *
  • Posts: 3
    • View Profile
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 :)

Offline Martin81Vette

  • Newbie
  • *
  • Posts: 3
    • View Profile
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

Offline pendragon3

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?

Offline Mochilles

  • Newbie
  • *
  • Posts: 4
    • View Profile
Thank you sir, I'll keep an eye on the github.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
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

Offline Mochilles

  • Newbie
  • *
  • Posts: 4
    • View Profile
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.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
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)

Offline Mochilles

  • Newbie
  • *
  • Posts: 4
    • View Profile
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!