[Resolved] Wallet Won't Connect

[marbles]

Looks like I fixed my issue.

Windows Vista

Open Windows Task Manager > Use it to force close BS application and process > Restart wallet > Accept database reset > Sit around and watch while 104 days of blocks get synced

[marbles]

I've had that same problem since installing 0.4.23.1 (32bit Windows). A minute after starting the wallet it will just go to "Not connected".

So far none of the addnodes have done anything. Reinstall didn't help either.

[Eylrid]

This is a major problem that is rendering my wallet completely useless and it still isn't resolved. Is there no one around here who can give real help?

[mint chocolate chip]

I'm having the same problem on the Mac with 04.21 (which was working then stopped) and 04.22 (downloaded after I gave up on v21, reopened several times, not syncing at all). Is this likely to be a wallet issue or my system? (warning: I am not IT technical)

you need the 0.4.22 (and soon the 0.4.23) to stay connected!!!

let the client run some 30 minutes or so .. it used to find the network by then

I have v0.4.20 and cannot connect.
Do you just have to download the newer version of the wallet from bitshare-x.info and install that over the existing wallet?

just reinstall! existing wallet will be upgraded (reindexed)

That was easy. Thanks.

[Eylrid]

I looked in the logs. I found a lot of "error fetching key 679837", "Exception thrown while canceling message_oriented_connection's read_loop" and "Peer IP is disconnecting us because: I rejected your connection request (hello message) so I'm disconnecting"

I would post a larger sample of my logs, but when I try the forum says "Sorry, you are not allowed to post external links."

[Eylrid]

There seems to be a deadlock of some kind in the network code .. can you let it run for an hour or so ..
I remember people reporting that after a while they synced up again ..

Alternatively you can try to connect to the seednodes manually:
    "178.62.50.61:1776",
    "178.62.50.61:1777",
    "178.62.50.61:1778",
    "80.240.133.79:1776",
    "80.240.133.79:1777",
    "5.101.106.138:1777",
    "5.101.106.138:1778",
    "128.199.137.122:1776",
    "128.199.137.122:1777",
    "95.85.33.16:8764",
    "180.153.142.120:1777",
    "84.238.140.192:42577",
    "5.101.106.138:1776",
    "61.129.33.213:1776",
    "80.240.133.79:1778",
    "89.187.144.203:8764",
    "104.131.35.149:1776",
    "178.62.50.61:1779",
    "178.62.157.161:1776",
    "188.226.195.137:60696",
    "auseednode.minebitshares.com:1776",
    "euseednode.minebitshares.com:1776"

in the console type:

network_add_node <IP>

I tried both of those. They didn't work.

[starspirit]

I'm having the same problem on the Mac with 04.21 (which was working then stopped) and 04.22 (downloaded after I gave up on v21, reopened several times, not syncing at all). Is this likely to be a wallet issue or my system? (warning: I am not IT technical)

you need the 0.4.22 (and soon the 0.4.23) to stay connected!!!

let the client run some 30 minutes or so .. it used to find the network by then

This worked, thanks. I was too impatient!

[xeroc]

I'm having the same problem on the Mac with 04.21 (which was working then stopped) and 04.22 (downloaded after I gave up on v21, reopened several times, not syncing at all). Is this likely to be a wallet issue or my system? (warning: I am not IT technical)

you need the 0.4.22 (and soon the 0.4.23) to stay connected!!!

let the client run some 30 minutes or so .. it used to find the network by then

I have v0.4.20 and cannot connect.
Do you just have to download the newer version of the wallet from bitshare-x.info and install that over the existing wallet?

just reinstall! existing wallet will be upgraded (reindexed)

[mint chocolate chip]

I'm having the same problem on the Mac with 04.21 (which was working then stopped) and 04.22 (downloaded after I gave up on v21, reopened several times, not syncing at all). Is this likely to be a wallet issue or my system? (warning: I am not IT technical)

you need the 0.4.22 (and soon the 0.4.23) to stay connected!!!

let the client run some 30 minutes or so .. it used to find the network by then

I have v0.4.20 and cannot connect.
Do you just have to download the newer version of the wallet from bitshare-x.info and install that over the existing wallet?

[xeroc]

I'm having the same problem on the Mac with 04.21 (which was working then stopped) and 04.22 (downloaded after I gave up on v21, reopened several times, not syncing at all). Is this likely to be a wallet issue or my system? (warning: I am not IT technical)

you need the 0.4.22 (and soon the 0.4.23) to stay connected!!!

let the client run some 30 minutes or so .. it used to find the network by then

[starspirit]

I'm having the same problem on the Mac with 04.21 (which was working then stopped) and 04.22 (downloaded after I gave up on v21, reopened several times, not syncing at all). Is this likely to be a wallet issue or my system? (warning: I am not IT technical)

[xeroc]

There seems to be a deadlock of some kind in the network code .. can you let it run for an hour or so ..
I remember people reporting that after a while they synced up again ..

Alternatively you can try to connect to the seednodes manually:
    "178.62.50.61:1776",
    "178.62.50.61:1777",
    "178.62.50.61:1778",
    "80.240.133.79:1776",
    "80.240.133.79:1777",
    "5.101.106.138:1777",
    "5.101.106.138:1778",
    "128.199.137.122:1776",
    "128.199.137.122:1777",
    "95.85.33.16:8764",
    "180.153.142.120:1777",
    "84.238.140.192:42577",
    "5.101.106.138:1776",
    "61.129.33.213:1776",
    "80.240.133.79:1778",
    "89.187.144.203:8764",
    "104.131.35.149:1776",
    "178.62.50.61:1779",
    "178.62.157.161:1776",
    "188.226.195.137:60696",
    "auseednode.minebitshares.com:1776",
    "euseednode.minebitshares.com:1776"

in the console type:

network_add_node <IP>

[Eylrid]

Version: 0.4.22
OS: Windows Vista 32 bit

My wallet synced up to block 679840 and now won't connect. I have tried closing the program and opening it again. At first it says that it has 8 connections, but doesn't get any new blocks. After a couple of minutes it switches to "Not connected".

Also, it oddly seems to be actually losing blocks. First it said that the latest block was 679840. After a shut down and reopen it said that the latest block was 679839. Another shut down and reopen and it now says that the latest block is 679838. 

I've tried deleting the peers_leveldb folder as suggested in this comment: index.php?topic=10185.msg133395#msg133395 That didn't seem to have any effect.

Edit: This has been resolved.

I got help with this on github. Here's what was happening: A memory leak was causing the wallet to use increasing amounts of RAM. When the RAM use became too much for my computer Bitshares crashed, corrupting the database. The corrupt database kept the wallet from connecting or accessing the blocks it already had.

Version 0.4.24 fixed the memory leak. Deleting the blockchain database and resyncing fixed the corrupt database.