Author Topic: "Not Connected"  (Read 3555 times)

0 Members and 1 Guest are viewing this topic.

Offline Bitshark

  • Full Member
  • ***
  • Posts: 75
    • View Profile
the "not connected" message might be misleading .. you can always check "for certain" when you go to the console type either "getinfo" or "blockchain_is_synced" ..

no idea why the wallet is crashing.. you do have the most recent version installed? Do you send the crash reports? Any special message that appears, besides "it crashes"?

Client just miraculously synced up. cool. dont know why it worked this time.

Offline mint chocolate chip

not misleading, I tried sending btsx and it has said pending next to the transaction ever since, though the date the transaction expires has  passed by several days, it still says pending because the client never synced up to that date.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
the "not connected" message might be misleading .. you can always check "for certain" when you go to the console type either "getinfo" or "blockchain_is_synced" ..

no idea why the wallet is crashing.. you do have the most recent version installed? Do you send the crash reports? Any special message that appears, besides "it crashes"?

Offline Bitshark

  • Full Member
  • ***
  • Posts: 75
    • View Profile
Crashed again trying to sync

Offline mint chocolate chip

xeroc, help me too please. I downloaded the client a week ago, it took a bunch of hours to finish syncing. The next day it was working fine. Then I got the Not Connected message and I have tried shutting down and turning the client back on several times over the past week but always get the not connected message. I tried adding all the nodes listed in the wiki with no luck. Yesterday, after putting 'info' into the console, I  saw a few minutes later that it was again syncing but that only lasted a few minutes before returning to the 'not connected' message. What do I need to do?

Offline Bitshark

  • Full Member
  • ***
  • Posts: 75
    • View Profile
May it be that you have "plenty" of account names?

From this perspective, it seems the client is syncing with the network as there are plenty of connections .. is the "blockchain_head_block_num" increasing?

Not alot of account names only 2. I've had issues with the client in the past and as a result have a bunch of installs on my system. Some 32 some 86 .. How do I just wipe everything and start fresh.

1) make a backup (in-app)
2) go to "%APPDATA%\BitShares X\"
3) wipe everything .. except "wallets"
4) rename "wallets" into something different (just to be on the safe side)
5) start over from square 1 (read: start the client) :)

Did as you said. Was reloading the blockchain than it crashed. Resetting the database again now. It either crashes or diverts to "not connected"

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
May it be that you have "plenty" of account names?

From this perspective, it seems the client is syncing with the network as there are plenty of connections .. is the "blockchain_head_block_num" increasing?

Not alot of account names only 2. I've had issues with the client in the past and as a result have a bunch of installs on my system. Some 32 some 86 .. How do I just wipe everything and start fresh.

1) make a backup (in-app)
2) go to "%APPDATA%\BitShares X\"
3) wipe everything .. except "wallets"
4) rename "wallets" into something different (just to be on the safe side)
5) start over from square 1 (read: start the client) :)

Offline Bitshark

  • Full Member
  • ***
  • Posts: 75
    • View Profile
May it be that you have "plenty" of account names?

From this perspective, it seems the client is syncing with the network as there are plenty of connections .. is the "blockchain_head_block_num" increasing?

Not alot of account names only 2. I've had issues with the client in the past and as a result have a bunch of installs on my system. Some 32 some 86 .. How do I just wipe everything and start fresh.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
May it be that you have "plenty" of account names?

From this perspective, it seems the client is syncing with the network as there are plenty of connections .. is the "blockchain_head_block_num" increasing?

Offline Bitshark

  • Full Member
  • ***
  • Posts: 75
    • View Profile
See if the wallet scan progress goes up.

Sent from my SM-G900T using Tapatalk

wallet scan progress is currently a "?"

Offline Riverhead

See if the wallet scan progress goes up.

Sent from my SM-G900T using Tapatalk


Offline Bitshark

  • Full Member
  • ***
  • Posts: 75
    • View Profile
It'll stay that way while it does stuff in the background. Let it sit.

Sent from my SM-G900T using Tapatalk

Does this usually take hours?

No. Go to the console screen and type "info" and see if it has any blocks or if it's stuck on one. You can also check your process manager and see if BitSharesX is actually doing anything.

On my older laptop, a Core2Duo, it can take hours because the indexing is super slow.

{
  "blockchain_head_block_num": 626781,
  "blockchain_head_block_age": "26 days old",
  "blockchain_head_block_timestamp": "2014-10-01T06:12:00",
  "blockchain_average_delegate_participation": "0.05 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_delegate_pay_rate": "2.47849 BTSX",
  "blockchain_share_supply": "1,999,979,848.34948 BTSX",
  "blockchain_blocks_left_in_round": 25,
  "blockchain_next_round_time": "at least 4 minutes in the future",
  "blockchain_next_round_timestamp": "2014-10-27T03:48:50",
  "blockchain_random_seed": "da2535d190299cda021a06846afc7d3340303c01",
  "client_data_dir":
  "client_version": "v0.4.22",
  "network_num_connections": 12,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2014-10-27T03:44:44",
  "ntp_time_error": -0.51117900000000005,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "12 days in the future",
  "wallet_unlocked_until_timestamp": "2014-11-07T17:28:52",
  "wallet_last_scanned_block_timestamp": "2014-07-20T00:07:00",
  "wallet_scan_progress": "1.17 %",
  "wallet_block_production_enabled": false,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}

It tries to sync at 26 days than prompts to "not connected"

Offline Riverhead

It'll stay that way while it does stuff in the background. Let it sit.

Sent from my SM-G900T using Tapatalk

Does this usually take hours?

No. Go to the console screen and type "info" and see if it has any blocks or if it's stuck on one. You can also check your process manager and see if BitSharesX is actually doing anything.

On my older laptop, a Core2Duo, it can take hours because the indexing is super slow.

Offline Bitshark

  • Full Member
  • ***
  • Posts: 75
    • View Profile
It'll stay that way while it does stuff in the background. Let it sit.

Sent from my SM-G900T using Tapatalk

Does this usually take hours?

Offline tonyk

  • Hero Member
  • *****
  • Posts: 3308
    • View Profile
It'll stay that way while it does stuff in the background. Let it sit.

Sent from my SM-G900T using Tapatalk

Yeeh if you are on win and you have to download the whole blockchain it just will not do so...  :)

https://bitsharestalk.org/index.php?topic=10473.0
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.