BitShares Forum

Main => Technical Support => Topic started by: onceuponatime on August 16, 2014, 06:13:55 pm

Title: Not connected
Post by: onceuponatime on August 16, 2014, 06:13:55 pm
My wallet is "Not connected" but it occasionally goes to "blocks are synced" for a moment and then back to "Not connected".

Do I need to addnodes? If so, what ones and how?
Title: Re: Not connected
Post by: onceuponatime on August 16, 2014, 06:18:45 pm
Now it is staying on "Blocks are synced".

Same thing happened yesterday morning when I started the wallet - toggled back and forth between "Blocks are synced" and "Not connected" for about 15 minutes and then was fine for the rest of the day.

Any ideas?
Title: Re: Not connected
Post by: onceuponatime on August 16, 2014, 06:47:00 pm
Stuck at "Not connected" again after 10 or so minutes of grace.
Title: Not connected
Post by: bitmeat on August 16, 2014, 06:52:07 pm
Man, I just reinstalled it's taking forever to download 1 month worth of data. What will this be like a year from now.

3 hours so far, still 21d worth of data left to download...
Title: Re: Not connected
Post by: onceuponatime on August 16, 2014, 06:59:44 pm
Man, I just reinstalled it's taking forever to download 1 month worth of data. What will this be like a year from now.

3 hours so far, still 21d worth of data left to download...

I sympathize, but that's a different issue. My wallet keeps going to "Not connected" even though it is up to date blockwise.

Can anyone answer the question of "if I need to and how to" addnodes? (And what ones)?
Title: Re: Not connected
Post by: bitmeat on August 16, 2014, 07:13:14 pm
Sorry, I forgot to mention... I just reinstalled... I also had to add nodes. The client I downloaded did not "just work"

207.12.89.119:48401
178.62.50.61:1776
106.185.26.162:1777
176.9.234.167:1776

network_add_node ip:port add
Title: Re: Not connected
Post by: onceuponatime on August 16, 2014, 07:32:18 pm
Sorry, I forgot to mention... I just reinstalled... I also had to add nodes. The client I downloaded did not "just work"

207.12.89.119:48401
178.62.50.61:1776
106.185.26.162:1777
176.9.234.167:1776

network_add_node ip:port add

Thanks a lot. I am still having trouble though. Would you please tell me exactly what to put in the Console for the first one:   207.12.89.119:4801
before I press Enter. I will then know how to do the same for the other ones.

>> network_add_node 207.12.89.119:48401 add

4 parse_error_exception: Parse Error
Can't parse a number with two decimal places
Title: Re: Not connected
Post by: onceuponatime on August 16, 2014, 08:39:59 pm
Sorry, I forgot to mention... I just reinstalled... I also had to add nodes. The client I downloaded did not "just work"

207.12.89.119:48401
178.62.50.61:1776
106.185.26.162:1777
176.9.234.167:1776

network_add_node ip:port add

Thanks a lot. I am still having trouble though. Would you please tell me exactly what to put in the Console for the first one:   207.12.89.119:4801
before I press Enter. I will then know how to do the same for the other ones.

>> network_add_node 207.12.89.119:48401 add

4 parse_error_exception: Parse Error
Can't parse a number with two decimal places

Anyone?
Title: Re: Not connected
Post by: xeroc on August 16, 2014, 08:43:51 pm
Sorry, I forgot to mention... I just reinstalled... I also had to add nodes. The client I downloaded did not "just work"

207.12.89.119:48401
178.62.50.61:1776
106.185.26.162:1777
176.9.234.167:1776

network_add_node ip:port add

Thanks a lot. I am still having trouble though. Would you please tell me exactly what to put in the Console for the first one:   207.12.89.119:4801
before I press Enter. I will then know how to do the same for the other ones.

>> network_add_node 207.12.89.119:48401 add

4 parse_error_exception: Parse Error
Can't parse a number with two decimal places

Anyone?

are we talking bitsharesx? try quoted:
  network_add_node "207.12.89.119:48401" add
Title: Re: Not connected
Post by: onceuponatime on August 16, 2014, 08:47:51 pm
Sorry, I forgot to mention... I just reinstalled... I also had to add nodes. The client I downloaded did not "just work"

207.12.89.119:48401
178.62.50.61:1776
106.185.26.162:1777
176.9.234.167:1776

network_add_node ip:port add

Thanks a lot. I am still having trouble though. Would you please tell me exactly what to put in the Console for the first one:   207.12.89.119:4801
before I press Enter. I will then know how to do the same for the other ones.

>> network_add_node 207.12.89.119:48401 add

4 parse_error_exception: Parse Error
Can't parse a number with two decimal places

Anyone?

are we talking bitsharesx? try quoted:
  network_add_node "207.12.89.119:48401" add

That was it! Thanks aa lot!
Title: Re: Not connected
Post by: xeroc on August 16, 2014, 08:51:12 pm
always welcome :)
Title: Re: Not connected
Post by: onceuponatime on August 16, 2014, 09:55:32 pm
So I have added the list of nodes: 

207.12.89.119:48401
178.62.50.61:1776
106.185.26.162:1777
176.9.234.167:1776

But my BitSharesX wallet is still constantly toggling between "Blocks are synced" and "Not connected" - with the majority of time being "Not connected".

It is very frustrating when I am trying to help the newcomers who need funds to register and can't.

Does anyone have an idea what is causing my wallet to be "Not connected" even after having added nodes?
Title: Re: Not connected
Post by: xeroc on August 16, 2014, 10:25:50 pm
Tried "getinfo" in the console? It gives you the seconds since the last block ..
Title: Re: Not connected
Post by: onceuponatime on August 17, 2014, 12:38:19 am
Tried "getinfo" in the console? It gives you the seconds since the last block ..

>> get_info

10 assert_exception: Assert Exception
part <= whole:
    {}
    bitshares  pretty.cpp:63 bts::cli::pretty_percent

    {}
    bitshares  common_api_client.cpp:2227 bts::rpc_stubs::common_api_client::get_info

    {"command":"get_info"}
    bitshares  cli.cpp:540 bts::cli::detail::cli_impl::execute_command
Title: Re: Not connected
Post by: bytemaster on August 17, 2014, 04:46:09 am
Log files have a clue.  Increase your log level to debug in config.json

Post files. 


Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
Title: Re: Not connected
Post by: pgbit on October 16, 2014, 05:44:59 pm
My bitshares X client isn't connecting, but KeyID is. Adding nodes, no action yet. I did just log into to Bitshares X and KeyID - both open. Any possible conflict?
Title: Re: Not connected
Post by: CLIFF on October 20, 2014, 07:47:57 am
Log files have a clue.  Increase your log level to debug in config.json

Post files. 


Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)

I have installed the wallet on a PC  and a virtual machine on Macbook.
The one on the vm is 0.4.20e 32bit version and the one on the pc is 0.4.20e 64bit version .They share one config.json.
the one on the pc can sync with the network and the one on the vm shows "Not Connected". And I have installed the KeyID on the same vm ,it can sync with the network well. So It confused me .
Title: Re: Not connected
Post by: CLIFF on October 22, 2014, 01:01:28 am
Maybe it is a database problem , i have fixed it .

The client on my pc can sync with the network. So i just copy the chain data from the pc to the vm .
When i restart the client on vm ,the wallet begins to sync with network from the first block .