[RESOLVED] 0.4.21 not connected and other issues

Started by tonyk, October 23, 2014, 09:36:29 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Methodise

All better now. I was being silly..  :-\
BTS: methodise

Methodise

Quote from: bitmeat on October 28, 2014, 07:51:31 AM
Quote from: tonyk on October 26, 2014, 07:04:39 AM
Quote from: bitmeat on October 26, 2014, 07:00:23 AM
It's a feature, not a bug! It prevents people from dumping on an exchange... LOL

I have never called anybody an idiot...But it is as good case as it  gets...

Y so serious, tonyk? Couldn't see the humor in this?

Some good, dark humour. But I believe one has to be British to laugh so heartily at their own misfortune? I'm not trying to dump, on the contrary. This situation is becoming so ugly, it must be a buy op. But being unable to sync sure makes a compelling case for dumping out of frustration.

I suppose I should get off my arse, present a delegate, and start seeding. But then, how would I sync the fucking things?

BTS: methodise

bitmeat

Quote from: tonyk on October 26, 2014, 07:04:39 AM
Quote from: bitmeat on October 26, 2014, 07:00:23 AM
It's a feature, not a bug! It prevents people from dumping on an exchange... LOL

I have never called anybody an idiot...But it is as good case as it  gets...

Y so serious, tonyk? Couldn't see the humor in this?

Eylrid

I'm having a similar problem. I got up to block #679840 and now it won't connect. I'm using v0.4.22 on Windows Vista 32 bit.

I tried posting the results of get_info but the forum told me "I'm sorry but you can't post external links." I'm not sure what it thought was an external link.

tonyk

#17
Quote from: bitmeat on October 26, 2014, 07:00:23 AM
It's a feature, not a bug! It prevents people from dumping on an exchange... LOL

I have never called anybody an idiot...But it is as good case as it  gets...
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

bitmeat

It's a feature, not a bug! It prevents people from dumping on an exchange... LOL

tonyk

BTW,
if somebody is experiencing the same problem, and really needs a quick and dirty hack... PM or something.

I do not want to post it here, cause I am pretty certain it is not how it is supposed to be resolved.
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

lil_jay890

Quote from: tonyk on October 24, 2014, 03:43:39 AM
Quote from: lil_jay890 on October 24, 2014, 03:39:26 AM
Do I have to download the 4.22 Wallet or will my 4.20 wallet update automatically?  I have windows 7 64 bit

You have to download it. Try to not kill you current database though so you do not have to go through the pain I am going through (i.e. in win install it over the previous version)

How do I not "kill" the current database?  Sorry I'm not very familiar with crypto wallets

joele

#13
0.4.22 ; Win7 32bit. Same issue. Any solution?

default.log all like this

20141024T132206.021522 bitshares:rebroadcast_pending rebroadcast_pending_ ] rebroadcasting 0         client.cpp:1117
20141024T132219.021979 bitshares:rebroadcast_pending rebroadcast_pending_ ] rebroadcasting 0         client.cpp:1117

Tuck Fheman

#12
FWIW 4.22 32 bit worked for me, but I'm not sure if it was switching to the 32bit version or the fact that I deleted the wallet folder and imported my wallet this time ... and honestly I don't care because I've spent 5 hours trying to sync.  :-\

Note : I'm running it in compatibility mode (WinXP/SP3) and as administrator.

joele


tonyk


Yep.. 0.4.22 works the way it is expected to ... the same way 0.4.21 works (with those unavailable for me improvements).


-So the question is can I turn 

"network_chain_downloader_running": false,

to true and if 'yes' how?

-If not - what are my alternatives - wait for official fix/ get the database from a trusted party/ something else....???? 
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

tonyk

Quote from: lil_jay890 on October 24, 2014, 03:39:26 AM
Do I have to download the 4.22 Wallet or will my 4.20 wallet update automatically?  I have windows 7 64 bit

You have to download it. Try to not kill you current database though so you do not have to go through the pain I am going through (i.e. in win install it over the previous version)
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

lil_jay890

Do I have to download the 4.22 Wallet or will my 4.20 wallet update automatically?  I have windows 7 64 bit

clayop

Quote from: tonyk on October 24, 2014, 03:25:03 AM
Quote from: Tuck Fheman on October 24, 2014, 03:18:32 AM
same here. no connection w/4.21 on Win7/64. tried using compatibility mode, still no go. client hangs trying to exit. will try 32bit version.

Edit : found binaries for 4.22, trying that instead.

Where did you find them? I do not see any binaries for 0.4.22 here https://github.com/dacsunlimited/bitsharesx/releases
plus the 4.22  just fixes the 2 issues explained , IFAIKT...

http://bitshares-x.info/
Bitshares Korea - [url="http://www.bitshares.kr"]http://www.bitshares.kr[/url]
Vote for me and see Korean Bitshares community grows
delegate-clayop

tonyk

Quote from: Tuck Fheman on October 24, 2014, 03:18:32 AM
same here. no connection w/4.21 on Win7/64. tried using compatibility mode, still no go. client hangs trying to exit. will try 32bit version.

Edit : found binaries for 4.22, trying that instead.

Where did you find them? I do not see any binaries for 0.4.22 here https://github.com/dacsunlimited/bitsharesx/releases
plus the 4.22  just fixes the 2 issues explained , IFAIKT...
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

Tuck Fheman

same here. no connection w/4.21 on Win7/64. tried using compatibility mode, still no go. client hangs trying to exit. will try 32bit version.

Edit : found binaries for 4.22, trying that instead.

tonyk


Is there any particular reason I should keep my wallet opened any longer? It's been opened for several hours now and I keep being stuck at the same block.
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

tonyk

OK it got stuck at block 175194 with between 6 and 8 connections.


>> get_info

{
  "blockchain_head_block_num": 175194,
  "blockchain_head_block_age": "76 days old",
  "blockchain_head_block_timestamp": "2014-08-09T03:00:20",
  "blockchain_average_delegate_participation": "0.02 %",
  "blockchain_confirmation_requirement": 2,
  "blockchain_delegate_pay_rate": "0.87119 BTSX",
  "blockchain_share_supply": "1,999,964,748.13929 BTSX",
  "blockchain_blocks_left_in_round": 41,
  "blockchain_next_round_time": "at least 7 minutes in the future",
  "blockchain_next_round_timestamp": "2014-10-23T22:35:50",
  "blockchain_random_seed": "2df26cc69c1a6d0d5512b7c39acaedc4122ddfc3",
  "client_data_dir": "C:/Users/Toni/AppData/Roaming/BitShares X",
  "client_version": "v0.4.21",
  "network_num_connections": 6,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2014-10-23T22:29:09",
  "ntp_time_error": 3.0093510000000001,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "12 days in the future",
  "wallet_unlocked_until_timestamp": "2014-11-04T12:09:50",
  "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
}


Can I just restore the old chain info/database? Which directories should I put back? 'chain' only?
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

tonyk

update
After what seems forever it started downloading the blockchain...will update in probably 3h...
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

tonyk

#1
0.4.21 on win 7 / 32 bit

'Not connected' while 8 connection

>> get_info

{
  "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/Toni/AppData/Roaming/BitShares X",
  "client_version": "v0.4.21",
  "network_num_connections": 8,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "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-04T11:14:26",
  "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
}



After
>> wallet_rescan_blockchain

OK

>> get_info

{
  "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/Toni/AppData/Roaming/BitShares X",
  "client_version": "v0.4.21",
  "network_num_connections": 5,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2014-10-23T21:33:06",
  "ntp_time_error": 2.6468579999999999,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "12 days in the future",
  "wallet_unlocked_until_timestamp": "2014-11-04T11:14:26",
  "wallet_last_scanned_block_timestamp": null,
  "wallet_scan_progress": "100.00 %",
  "wallet_block_production_enabled": false,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}


My accounts still show 0
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.