BitShares Forum
Main => Technical Support => Topic started by: kmtan on October 21, 2014, 01:21:52 pm
-
Hi, i getting trouble to get my btsx client to get connected on my macbook air which just update with osx yosemite
i had add network node as following:
207.12.89.119:48401
178.62.50.61:1776
106.185.26.162:1777
176.9.234.167:1776
but it is still cannot connect to the network. thus i had to get help from community for this problem as i unable to search the answer from the net. This issue take me several days already.
is that issue if i had add 2 founder account to the btsx client?
here below is the getinfo :
>> 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_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": "/Users/kmtan/Library/Application Support/BitShares X",
"client_version": "v0.4.20",
"network_num_connections": 0,
"network_num_connections_max": 200,
"ntp_time": null,
"ntp_time_error": null,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "12 days in the future",
"wallet_unlocked_until_timestamp": "2014-11-02T02:27:23",
"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
}
-
I guess you are the first to use BTSX with Yosemite .. and from what I can see here is that it seems to be a connectivity issue that should be published at the bugtracker directly
.. unless you have a firewall running that is just blocking the connections .. do you?
would you please fill your bug at:
https://github.com/BitShares/bitshares_toolkit/issues
-
I guess you are the first to use BTSX with Yosemite .. and from what I can see here is that it seems to be a connectivity issue that should be published at the bugtracker directly
.. unless you have a firewall running that is just blocking the connections .. do you?
would you please fill your bug at:
https://github.com/BitShares/bitshares_toolkit/issues
hi xeroc, i am using company network, may be you are right, it is a firewall filtering some website, but i am not sure..will check on this friday when get home. once i had verify at home will fill on the github.
-
hi xeroc, i am using company network, may be you are right, it is a firewall filtering some website, but i am not sure..will check on this friday when get home. once i had verify at home will fill on the github.
Could be a reason .. please let us know if everything works out @home :-D
-
HI Xeroc, i am able to connected to the network @ home with just 2 network connection.
here below is the getinfo for your review, pls advise me if any
{
"blockchain_head_block_num": 124269,
"blockchain_head_block_age": "84 days old",
"blockchain_head_block_timestamp": "2014-08-03T03:02:00",
"blockchain_average_delegate_participation": "0.01 %",
"blockchain_confirmation_requirement": 1,
"blockchain_delegate_pay_rate": "1.17502 BTSX",
"blockchain_share_supply": "1,999,972,509.57258 BTSX",
"blockchain_blocks_left_in_round": 62,
"blockchain_next_round_time": "at least 10 minutes in the future",
"blockchain_next_round_timestamp": "2014-10-25T15:21:10",
"blockchain_random_seed": "bd47a0b3b5d53c3d465579539831448bd5017465",
"client_data_dir": "/Users/kmtan/Library/Application Support/BitShares X",
"client_version": "v0.4.20",
"network_num_connections": 2,
"network_num_connections_max": 200,
"ntp_time": null,
"ntp_time_error": null,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "12 days in the future",
"wallet_unlocked_until_timestamp": "2014-11-06T04:23:05",
"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
}
-
HI Xeroc, i am able to connected to the network @ home with just 2 network connection.
here below is the getinfo for your review, pls advise me if any
{
"blockchain_head_block_num": 124269,
"blockchain_head_block_age": "84 days old",
"blockchain_head_block_timestamp": "2014-08-03T03:02:00",
"blockchain_average_delegate_participation": "0.01 %",
"blockchain_confirmation_requirement": 1,
"blockchain_delegate_pay_rate": "1.17502 BTSX",
"blockchain_share_supply": "1,999,972,509.57258 BTSX",
"blockchain_blocks_left_in_round": 62,
"blockchain_next_round_time": "at least 10 minutes in the future",
"blockchain_next_round_timestamp": "2014-10-25T15:21:10",
"blockchain_random_seed": "bd47a0b3b5d53c3d465579539831448bd5017465",
"client_data_dir": "/Users/kmtan/Library/Application Support/BitShares X",
"client_version": "v0.4.20",
"network_num_connections": 2,
"network_num_connections_max": 200,
"ntp_time": null,
"ntp_time_error": null,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "12 days in the future",
"wallet_unlocked_until_timestamp": "2014-11-06T04:23:05",
"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
}
Looks good to me .. connection counter should increase after some time ..
with the command
network_get_advanced_node_parameters
you can see how many connections the client perferes to open up .. should be around 8 or so ..
Further, please consider upgrading to 0.4.22 and soon to be released 0.4.23 as there have been some blockchain upgrades and you would end up stuck at a block with your current version ..
-
I had fixed the problem before https://bitsharestalk.org/index.php?topic=7020.15
when i upgrade to 0.4.23.1, it shows again.
the client shows "not connected", but i use network_get_connection_count in the console ,it shows 12 connection.
>> network_get_connection_count
12
btw:how to reindex the database in the console ?
-
I had fixed the problem before https://bitsharestalk.org/index.php?topic=7020.15
when i upgrade to 0.4.23.1, it shows again.
the client shows "not connected", but i use network_get_connection_count in the console ,it shows 12 connection.
btw:how to reindex the database in the console ?
it's a known glitch in the user interface .. sorry about that ..
a reindex will appear automatically when you start the client after an upgrade .. no need to run the reindex per hand.
however you can (at least in the linux version) .. pass some parameters when launching the binary .. IIRC the reindex can be initiated with "--rebuild-indec"
-
I've had difficulty trying to sync, it's said "Catching Up processed 881233 of 930393" for several days now, and my account still appears as unregistered. It may be that the recent upgrade of IOS has cause a problem (rocking OS X Yosemite, 10.10)
[I've posted my key and have been sent a share and registered]
What would be the best course of action to get caught up?
-
Same problem with my Windows wallet. "Not Connected"
https://bitsharestalk.org/index.php?topic=10895.0
-
I've had difficulty trying to sync, it's said "Catching Up processed 881233 of 930393" for several days now
I'm having this same issue now, and also stuck at 881233.
Did you resolve this issue in the end?
-
Is your client up-to-date? 0.4.27.2
-
With an up to date client I've been able to sync, but my situation is a bit strange.
After importing my old wallet to the new client, the client changed the address by 1 letter, which I didn't realise before withdrawing funds to my old address, which it seems is not not accessible any more due to the fork, so it seems I may have lost the funds.
I have more details on this thread: https://bitsharestalk.org/index.php?topic=13170.0
If you're able to help it'd be much appreciated!
-
With an up to date client I've been able to sync, but my situation is a bit strange.
After importing my old wallet to the new client, the client changed the address by 1 letter, which I didn't realise before withdrawing funds to my old address, which it seems is not not accessible any more due to the fork, so it seems I may have lost the funds.
I have more details on this thread: https://bitsharestalk.org/index.php?topic=13170.0
If you're able to help it'd be much appreciated!
That's ok ... we used to have the prefix "BTSX" ... when the name of the client was BitShares-X ... but after the merger we now only have BitShares and thus the prefix is BTS.
Though you can still use everything as usual .. either you use the "*_depricated" commands in the CLI or you just remove the "X" after BTS ..
Addresses still have a checksum .. so if you mess with your addresses to much the client will complain
-
Though you can still use everything as usual .. either you use the "*_depricated" commands in the CLI or you just remove the "X" after BTS ..
Thanks. Do you have any link to the 'deprecated' commands, as I searched the documentation & couldn't find them.
My issue is that a transaction was sent to the old address with the X in the prefix, and wonder how to get the balance of this transaction into the new address without the X. Is this what the deprecated commands can do, by getting my client to accept transactions to the previous address?