BitShares Forum
Main => General Discussion => Topic started by: evolvo on August 28, 2014, 07:31:25 am
-
Not connecting....RPC Server Error: In method 'blockchain_list_assets': Assert Exception (10)
-
same here
-
can confirm that it's being a son-of-a-bitch.
-
same here, tried everything, still not working!
-
Is it just not syncing? I can increase my seed node connections.
-
I just uninstalled and reinstalled and now the error code is gone and at least my wallet is loading correctly with the correct balance...but I'm not getting any connections
-
try
network_add_node "95.85.33.16:8764"
That seed node isn't full yet
***edit*** Also just increased connection count on 104.131.238.223:1776
-
I added it...still not working.
-
RPC Server Error: In method 'blockchain_list_assets': Assert Exception (10)
- same for me too.
Edit: it does say "Updating transaction history." lower down so best wait a while...
-
probably/obvious to much "traffic" right now... I bet in acouple of hours it will be fine ;)
-
RPC Server Error: In method 'get_config' is the error I'm getting now
If this amount of volume is too much that doesn't bode well for the future does it? I doubt that's the problem....we just need to get these wallets debugged.
-
The same here, Windows 7
The first time i launched 4.9 I got
RPC Server Error: In method 'blockchain_list_assets': Assert Exception (10)
and "Not connected"
After a restart the error is gone but the syn process got stuck on block 321978.
-
This release well and truly borked.. DB rescan crashed, DB reset crashed, sync from genesis again, but took hours.. now got no connection and get recent blocks.
Lots of problems.
-
yup...try again please....we gotta stop dropping the ball on these wallet releases...
-
stop 0.4.9 before you ruin everything! redowloaded the blockchain twice, stuck till 1 day left, then no connection.
-
BM ?
-
Its 4AM EST
-
all wallet with version 4.9 is not connected!!
why?
solution?
-
try
network_add_node "95.85.33.16:8764"
That seed node isn't full yet
***edit*** Also just increased connection count on 104.131.238.223:1776
worked for me
-
try
network_add_node "95.85.33.16:8764"
That seed node isn't full yet
***edit*** Also just increased connection count on 104.131.238.223:1776
worked for me
Here's some more.
network_add_node "107.170.211.129:1700"
network_add_node "80.240.133.79:1776"
network_add_node "188.226.195.137:60696"
network_add_node "76.74.170.79:54200"
network_add_node "176.9.234.166:1700"
network_add_node "180.153.142.120:1777"
network_add_node "162.243.220.142:1777"
network_add_node "84.238.140.192:42577"
network_add_node "5.101.106.138:1778"
network_add_node "69.164.192.144:1700"
-
still just getting this: RPC Server Error: In method 'get_config' and "Not Connected"
-
Adding nodes worked for me this time. I guess I was too late for the one posted earlier.
-
Its 4AM EST
somebody throw him a bucket of ice water?
(http://www.macleans.ca/wp-content/uploads/2014/08/ICEBUCKET-tile.jpg)
-
Adding nodes worked for me this time. I guess I was too late for the one posted earlier.
Yeah. The seed nodes fill up fast.
-
Adding nodes worked for me this time. I guess I was too late for the one posted earlier.
Yeah. The seed nodes fill up fast.
Mine still has slots though... It must be something else.
-
Adding nodes worked for me this time. I guess I was too late for the one posted earlier.
Yeah. The seed nodes fill up fast.
my client stopped syncing again
-
I added all of these nodes....still not connecting.
-
Adding nodes worked for me this time. I guess I was too late for the one posted earlier.
Yeah. The seed nodes fill up fast.
Mine still has slots though... It must be something else.
Yeah. I have been having a harder time getting connected and syncing since 4.8 I've been having to run my delegate on my laptop, to prevent crashes or disconnections from making me miss blocks.
-
I am running three nodes with over 250 connections in total .. but all of the nodes reached their 'max_connection' ..
-
I am running three nodes with over 250 connections in total .. but all of the nodes reached their 'max_connection' ..
My seed nodes fill up within minutes. Its a good thing they crash every once in a while to give new people a change to connect. The connections issues I have is with my delegate with inbound connections turned off. I get maybe 1 or 2 connections but never get more, and then I lose those and don't reconnect.
-
I am running three nodes with over 250 connections in total .. but all of the nodes reached their 'max_connection' ..
It doesn't seem to be an issue with seed node slots.
Mine has 150 connections out of 400.
Just the client cannot sync on some blocks. Fresh resync doesn't work. You need to sync 4.8 and then reindex data-dir.
-
It's an issue with the wallet...bugs galore
-
After reinstalling it for the 11th time...it looks like its actually syncing now....let's see if it continues
-
Mine is broken again too.
After giving it a seed node it started re-syncing. Number of connections quickly went up to 8 and stayed there. When it hit about 2 days to go it suddenly went back to "Not connected".
-
We need 0.4.9-a
-
My connection also died with about 1 and a half days left to sync.....groan
-
Since this is a fork with some protections against the client connecting to an old fork we probably need to wait for the seed nodes to update as well.
-
Try to add this node if you have problem:
network_add_node "188.138.107.159:1776" add
-
added it....and....surprise....still doesn't work
-
added it....and....surprise....still doesn't work
it would be a surprise if it worked :P
-
I added a chain server and have been having good luck with that.
https://github.com/BitShares/bitshares_toolkit/wiki/Using-Chain-Servers
I am in the processes of setting up a dedicated chain server. Will post the IP address shortly.
-
it would be pretty fantastic if I could access my funds....i feel like every wallet update is playing russian roulette
-
added it....and....surprise....still doesn't work
it would be a surprise if it worked :P
just kidding...
with the linux cli version 0.4.9 I have any problems so far...
-
Confirming here.
Just downloaded and launched 0.4.9 - still having same crash issues. It throws an "RPC server error" just before crashing.
-
Wow. Just woke up to this.
-
My delegate that blocks incoming connections has been rock solid. Hasn't missed a block since starting it at about 3AM EDT.
-
My delegate that blocks incoming connections has been rock solid. Hasn't missed a block since starting it at about 3AM EDT.
Its all ok even without blocking inoming connections. You just need to sync with earlier version.
-
Wow. Just woke up to this.
Enjoy!
-
My delegate that blocks incoming connections has been rock solid. Hasn't missed a block since starting it at about 3AM EDT.
Its all ok even without blocking inoming connections. You just need to sync with earlier version.
Will that have you on the correct fork?
-
Fork hasn't happened yet
-
My delegate that blocks incoming connections has been rock solid. Hasn't missed a block since starting it at about 3AM EDT.
How do you do the block incoming connections thing again?
-
My delegate that blocks incoming connections has been rock solid. Hasn't missed a block since starting it at about 3AM EDT.
How do you do the block incoming connections thing again?
--accept-incoming-connections 0
-
Fork hasn't happened yet
Thanks :)
-
So we will not get connections until the fork happens?
The install went fine but it says no connections, I want to make sure this is because of the fork.
RPC Server Error: In method 'blockchain_list_assets': Assert Exception (10)
-
My 0.4.9 delegates seem to be working fine. Windows wallet has low/no connections but seems to connect from time to time. I noticed this with some of my delegates as well. Initially had 1 or 2 connections but after awhile they increased. I will keep at it on the windows side and see if it eventually syncs up.
-
I am attempting to gain my bearings on what is going on now that I am in the office.
1) Looks like my 0.4.8 OS X GUI still has 8 connections and 97% delegate participation! Good work guys.
2) My 0.4.9 command line client (OSX) fully synced from last night, attempting a fresh sync (so far so good, 8 connections from scratch)
3) About to test out 0.4.9 OS X GUI to see where we get....
Update: fully connected from a fresh start with 7 connections. Now for the GUI.
-
So we will not get connections until the fork happens?
The install went fine but it says no connections, I want to make sure this is because of the fork.
RPC Server Error: In method 'blockchain_list_assets': Assert Exception (10)
Same here on windows for me.
Mac crashes though.
-
My 0.4.9 delegates seem to be working fine. Windows wallet has low/no connections but seems to connect from time to time. I noticed this with some of my delegates as well. Initially had 1 or 2 connections but after awhile they increased. I will keep at it on the windows side and see if it eventually syncs up.
Same. My seed node sync'd really fast (about 30 minutes on a clean install) but my Windows GUI is taking its sweet time.
-
Mac GUI successfully upgraded my 0.4.8 database and now has 8 network connections.
What the hell is going on with everyone else's computer...
-
Mac GUI successfully upgraded my 0.4.8 database and now has 8 network connections.
What the hell is going on with everyone else's computer...
I experienced issues starting 0.4.9 with fresh data-dir. Upgrading from 0.4.8 had no issues.
-
Mac GUI successfully upgraded my 0.4.8 database and now has 8 network connections.
What the hell is going on with everyone else's computer...
(http://s2.quickmeme.com/img/f7/f726aa660e3fd2121f19e72f277736aed236a00b450a0321b0d9c7bf24fd5c61.jpg)
-
Mac crashes though.
It would really help if you could provide a strack trace from the crash reporter:
On the OSX Terminal:
defaults write com.apple.CrashReporter DialogType Developer
-
I have delegates working without problem blocking incoming connections.
Instead an other node than can accept connections after a while crash (when there are many connections ~100) and I have now enabled the automatic restart procedure.
-
The same here, Windows 7
The first time i launched 4.9 I got
RPC Server Error: In method 'blockchain_list_assets': Assert Exception (10)
and "Not connected"
After a restart the error is gone but the syn process got stuck on block 321978.
Same here, stuck on block 321978 then No connection.
-
Mac GUI successfully upgraded my 0.4.8 database and now has 8 network connections.
What the hell is going on with everyone else's computer...
I experienced issues starting 0.4.9 with fresh data-dir. Upgrading from 0.4.8 had no issues.
I synced from scratch this morning om 0.4.9 without any issues, was surprisingly fast too.
Ubuntu 14, peaked around 800 blocks per second, tok me less than 10 minutes to sync the whole chain.
-
The same here, Windows 7
The first time i launched 4.9 I got
RPC Server Error: In method 'blockchain_list_assets': Assert Exception (10)
and "Not connected"
After a restart the error is gone but the syn process got stuck on block 321978.
Same here, stuck on block 321978 then No connection.
Same here.
-
The same here, Windows 7
The first time i launched 4.9 I got
RPC Server Error: In method 'blockchain_list_assets': Assert Exception (10)
and "Not connected"
After a restart the error is gone but the syn process got stuck on block 321978.
Yup me too same thing.
Same here, stuck on block 321978 then No connection.
-
did a fresh install of 4.8.0, synced, but all of my transactions messed up:(
-
Same here, stuck on block 321978 then No connection.
Can you use "debug_list_errors" to see what the issue is?
-
did a fresh install of 4.8.0, synced, but all of my transactions messed up:(
The wallet automatically made a backup of the prior wallet state. 4.9 doesn't have this issue.
-
Mac crashes though.
It would really help if you could provide a strack trace from the crash reporter:
On the OSX Terminal:
defaults write com.apple.CrashReporter DialogType Developer
OK - I'll attempt to do this when I get home from work.
-
Upgrading from 0.4.8 had no problems at all (linux cli - delegate). Creating a new VPS (linux) will only work if I had " --accept-incoming-connections=0 " Currently only 4 connections.
-
Same here, stuck on block 321978 then No connection.
Can you use "debug_list_errors" to see what the issue is?
>> debug_list_errors
20140828T140220.837466 (28 seconds ago )
10 assert_exception: Assert Exception
hash_of_previous_secret == delegate_record->delegate_info->next_secret_hash:
{"previous_secret":"f34ed43768d340b4e0ab92a6ec2face8c9d826fa","hash_of_previous_secret":"046b7e76330d459f2fbf107e01dbfb1b6e5f1c5a","delegate_record":{"id":2156,"name":"delegate-baozi","public_data":null,"owner_key":"BTSX8QpSmZ9HRUyZyq5zNUiWZX6cCkAY3nwDmS7KBFib1WrZ3m5Uh5","active_key_history":[["20140720T004040","BTSX8QpSmZ9HRUyZyq5zNUiWZX6cCkAY3nwDmS7KBFib1WrZ3m5Uh5"]],"registration_date":"20140720T004040","last_update":"20140720T004040","delegate_info":{"votes_for":22830235072068,"blocks_produced":3032,"blocks_missed":36,"pay_rate":100,"pay_balance":159484848,"next_secret_hash":"4567c7d5877ac73f9150fc89020eebffa16c0230","last_block_num_produced":321979},"meta_data":null}}
bitshares chain_database.cpp:689 bts::blockchain::detail::chain_database_impl::update_delegate_production_info
{"block":{"previous":"237b2b29c6717f382230c2a133a6ff7ea71ba6a4","block_num":321979,"timestamp":"20140826T141700","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"4567c7d5877ac73f9150fc89020eebffa16c0230","previous_secret":"f34ed43768d340b4e0ab92a6ec2face8c9d826fa","delegate_signature":"1f10fcbd21d8b1617502010d98a781e1c95d8926f8febe64cd90c27224b9ca2fa0e1a5ae3dba3a3d397ed12e42c48c3b702141a3e6272a2da6effc55895ddb998a","user_transactions":[{"expiration":"20140826T161653","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"BTSXLeoXC7sVMH8R7NFXVDquctfUzCA3t192b","amount":1091000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"BTSXAcZ9kAbm4Vo8sjAtmEqcbLezm5pkaEzbP","amount":281158999,"claim_input_data":""}},{"type":"ask_op_type","data":{"amount":282239999,"ask_index":{"order_price":{"ratio":"0.004464285714285714","quote_asset_id":22,"base_asset_id":0},"owner":"BTSXH6CrzKWKD5gSpkDrVPzqKjexXKAS7yHm"}}}],"signatures":["20d3f616a32e34cbfc3ab9962ba24d3e16947b8fdc62f2980bfda4ad15deccfdd0e9af47575d303a9b98d0468d9bcdb22a8c7d5336a6cb7778fd624eed1eb00b71","1fb5d9771c90ab766756e6d340eed3e60b68673afb6978c21f3ad700839404f96b7e70918654538417c1c47ee28fd7231d8b224c601690f47fbbc2efd462f1392e","202c7a9a01ded25747c6971d2947bfa857546195c9f6b99bf4893eff429ef7a4b87992ccbe8cea6511aca46a234e5a445b0dabaecfb8ab84e90ff56e2b26e5d193"]}]}}
bitshares chain_database.cpp:878 bts::blockchain::detail::chain_database_impl::extend_chain
{"block_data":{"previous":"237b2b29c6717f382230c2a133a6ff7ea71ba6a4","block_num":321979,"timestamp":"20140826T141700","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"4567c7d5877ac73f9150fc89020eebffa16c0230","previous_secret":"f34ed43768d340b4e0ab92a6ec2face8c9d826fa","delegate_signature":"1f10fcbd21d8b1617502010d98a781e1c95d8926f8febe64cd90c27224b9ca2fa0e1a5ae3dba3a3d397ed12e42c48c3b702141a3e6272a2da6effc55895ddb998a","user_transactions":[{"expiration":"20140826T161653","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"BTSXLeoXC7sVMH8R7NFXVDquctfUzCA3t192b","amount":1091000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"BTSXAcZ9kAbm4Vo8sjAtmEqcbLezm5pkaEzbP","amount":281158999,"claim_input_data":""}},{"type":"ask_op_type","data":{"amount":282239999,"ask_index":{"order_price":{"ratio":"0.004464285714285714","quote_asset_id":22,"base_asset_id":0},"owner":"BTSXH6CrzKWKD5gSpkDrVPzqKjexXKAS7yHm"}}}],"signatures":["20d3f616a32e34cbfc3ab9962ba24d3e16947b8fdc62f2980bfda4ad15deccfdd0e9af47575d303a9b98d0468d9bcdb22a8c7d5336a6cb7778fd624eed1eb00b71","1fb5d9771c90ab766756e6d340eed3e60b68673afb6978c21f3ad700839404f96b7e70918654538417c1c47ee28fd7231d8b224c601690f47fbbc2efd462f1392e","202c7a9a01ded25747c6971d2947bfa857546195c9f6b99bf4893eff429ef7a4b87992ccbe8cea6511aca46a234e5a445b0dabaecfb8ab84e90ff56e2b26e5d193"]}]}}
bitshares chain_database.cpp:1374 bts::blockchain::chain_database::push_block
Error pushing block 321979 - c4079669db15ce1e843c2c792501412ad30de888
{"block_id":"c4079669db15ce1e843c2c792501412ad30de888","block_number":321979,"block":{"previous":"237b2b29c6717f382230c2a133a6ff7ea71ba6a4","block_num":321979,"timestamp":"20140826T141700","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"4567c7d5877ac73f9150fc89020eebffa16c0230","previous_secret":"f34ed43768d340b4e0ab92a6ec2face8c9d826fa","delegate_signature":"1f10fcbd21d8b1617502010d98a781e1c95d8926f8febe64cd90c27224b9ca2fa0e1a5ae3dba3a3d397ed12e42c48c3b702141a3e6272a2da6effc55895ddb998a","user_transactions":[{"expiration":"20140826T161653","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"BTSXLeoXC7sVMH8R7NFXVDquctfUzCA3t192b","amount":1091000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"BTSXAcZ9kAbm4Vo8sjAtmEqcbLezm5pkaEzbP","amount":281158999,"claim_input_data":""}},{"type":"ask_op_type","data":{"amount":282239999,"ask_index":{"order_price":{"ratio":"0.004464285714285714","quote_asset_id":22,"base_asset_id":0},"owner":"BTSXH6CrzKWKD5gSpkDrVPzqKjexXKAS7yHm"}}}],"signatures":["20d3f616a32e34cbfc3ab9962ba24d3e16947b8fdc62f2980bfda4ad15deccfdd0e9af47575d303a9b98d0468d9bcdb22a8c7d5336a6cb7778fd624eed1eb00b71","1fb5d9771c90ab766756e6d340eed3e60b68673afb6978c21f3ad700839404f96b7e70918654538417c1c47ee28fd7231d8b224c601690f47fbbc2efd462f1392e","202c7a9a01ded25747c6971d2947bfa857546195c9f6b99bf4893eff429ef7a4b87992ccbe8cea6511aca46a234e5a445b0dabaecfb8ab84e90ff56e2b26e5d193"]}]}}
bitshares client.cpp:1136 bts::client::detail::client_impl::on_new_block
20140828T140220.841466 (28 seconds ago )
0 exception: unspecified
I am disconnecting peer 84.238.140.192:42577 for reason: You offered us a block that we reject as invalid
{}
bitshares client.cpp:1525 bts::client::detail::client_impl::error_encountered
20140828T140220.844466 (28 seconds ago )
0 exception: unspecified
I am disconnecting peer 80.240.133.79:1776 for reason: You offered us a block that we reject as invalid
{}
bitshares client.cpp:1525 bts::client::detail::client_impl::error_encountered
-
you should have a professional QA tester with different types of computers(PCs, Macs, Unixs) and different OS versions, doing nothing but test a new version on every machines, OSs...
-
The same here, Windows 7
The first time i launched 4.9 I got
RPC Server Error: In method 'blockchain_list_assets': Assert Exception (10)
and "Not connected"
After a restart the error is gone but the syn process got stuck on block 321978.
Same here, stuck on block 321978 then No connection.
Exact problem here for windows. BM - any error or bug report I can get to assist?
-
>> debug_list_errors
20140828T125739.813169 (2 hours ago )
0 exception: unspecified
Peer 114.215.129.110:1776 is disconnecting us because of an error: You offered us a block that we reject as invalid, exception: {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"chain_database.cpp","line":1309,"method":"push_block","hostname":"","thread_name":"th_a","timestamp":"20140828T125745.177734"},"format":"block_data.block_num > (get_head_block_num() - BTS_BLOCKCHAIN_MAX_UNDO_HISTORY): ","data":{"BTS_BLOCKCHAIN_MAX_UNDO_HISTORY":404}},{"context":{"level":"warn","file":"chain_database.cpp","line":1360,"method":"push_block","hostname":"","thread_name":"th_a","timestamp":"20140828T125745.177804"},"format":"","data":{"block_data":{"previous":"0000000000000000000000000000000000000000","block_num":1,"timestamp":"20140719T031850","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"38c370dbf65ab46b5a403dd3d44729bceeb282cb","previous_secret":"9c9dc7b87c243311961ac3e8000b5827841372b4","delegate_signature":"20248c112ed3b1c56696cae6e0b8ff55a0403eb0287b445813a99262e141f7cd56e7004948cf962bd76a9649fe749d14a6b88b5a700e11e1b068042d0972f45396","user_transactions":[]}}},{"context":{"level":"warn","file":"client.cpp","line":1090,"method":"on_new_block","hostname":"","thread_name":"th_a","timestamp":"20140828T125745.177887"},"format":"Error pushing block ${block_number} - ${block_id}","data":{"block_id":"8abcfb93c52f999e3ef5288c4f837f4f15af5521","block_number":1,"block":{"previous":"0000000000000000000000000000000000000000","block_num":1,"timestamp":"20140719T031850","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"38c370dbf65ab46b5a403dd3d44729bceeb282cb","previous_secret":"9c9dc7b87c243311961ac3e8000b5827841372b4","delegate_signature":"20248c112ed3b1c56696cae6e0b8ff55a0403eb0287b445813a99262e141f7cd56e7004948cf962bd76a9649fe749d14a6b88b5a700e11e1b068042d0972f45396","user_transactions":[]}}}]}
-
>> debug_list_errors
20140828T125739.813169 (2 hours ago )
0 exception: unspecified
Peer 114.215.129.110:1776 is disconnecting us because of an error: You offered us a block that we reject as invalid, exception: {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"chain_database.cpp","line":1309,"method":"push_block","hostname":"","thread_name":"th_a","timestamp":"20140828T125745.177734"},"format":"block_data.block_num > (get_head_block_num() - BTS_BLOCKCHAIN_MAX_UNDO_HISTORY): ","data":{"BTS_BLOCKCHAIN_MAX_UNDO_HISTORY":404}},{"context":{"level":"warn","file":"chain_database.cpp","line":1360,"method":"push_block","hostname":"","thread_name":"th_a","timestamp":"20140828T125745.177804"},"format":"","data":{"block_data":{"previous":"0000000000000000000000000000000000000000","block_num":1,"timestamp":"20140719T031850","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"38c370dbf65ab46b5a403dd3d44729bceeb282cb","previous_secret":"9c9dc7b87c243311961ac3e8000b5827841372b4","delegate_signature":"20248c112ed3b1c56696cae6e0b8ff55a0403eb0287b445813a99262e141f7cd56e7004948cf962bd76a9649fe749d14a6b88b5a700e11e1b068042d0972f45396","user_transactions":[]}}},{"context":{"level":"warn","file":"client.cpp","line":1090,"method":"on_new_block","hostname":"","thread_name":"th_a","timestamp":"20140828T125745.177887"},"format":"Error pushing block ${block_number} - ${block_id}","data":{"block_id":"8abcfb93c52f999e3ef5288c4f837f4f15af5521","block_number":1,"block":{"previous":"0000000000000000000000000000000000000000","block_num":1,"timestamp":"20140719T031850","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"38c370dbf65ab46b5a403dd3d44729bceeb282cb","previous_secret":"9c9dc7b87c243311961ac3e8000b5827841372b4","delegate_signature":"20248c112ed3b1c56696cae6e0b8ff55a0403eb0287b445813a99262e141f7cd56e7004948cf962bd76a9649fe749d14a6b88b5a700e11e1b068042d0972f45396","user_transactions":[]}}}]}
Looks like you connected to a peer running an old version of the code. Error was on their side, not yours.
-
The same here, Windows 7
The first time i launched 4.9 I got
RPC Server Error: In method 'blockchain_list_assets': Assert Exception (10)
and "Not connected"
After a restart the error is gone but the syn process got stuck on block 321978.
Same here, stuck on block 321978 then No connection.
Exact problem here for windows. BM - any error or bug report I can get to assist?
We have an issue where debug builds evaluate differently that release builds... I can reproduce this reliably in debug build... I get stuck on a block around that number... it looks like you retried it 3 times :)
-
>> debug_list_errors
20140828T125739.813169 (2 hours ago )
0 exception: unspecified
Peer 114.215.129.110:1776 is disconnecting us because of an error: You offered us a block that we reject as invalid, exception: {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"chain_database.cpp","line":1309,"method":"push_block","hostname":"","thread_name":"th_a","timestamp":"20140828T125745.177734"},"format":"block_data.block_num > (get_head_block_num() - BTS_BLOCKCHAIN_MAX_UNDO_HISTORY): ","data":{"BTS_BLOCKCHAIN_MAX_UNDO_HISTORY":404}},{"context":{"level":"warn","file":"chain_database.cpp","line":1360,"method":"push_block","hostname":"","thread_name":"th_a","timestamp":"20140828T125745.177804"},"format":"","data":{"block_data":{"previous":"0000000000000000000000000000000000000000","block_num":1,"timestamp":"20140719T031850","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"38c370dbf65ab46b5a403dd3d44729bceeb282cb","previous_secret":"9c9dc7b87c243311961ac3e8000b5827841372b4","delegate_signature":"20248c112ed3b1c56696cae6e0b8ff55a0403eb0287b445813a99262e141f7cd56e7004948cf962bd76a9649fe749d14a6b88b5a700e11e1b068042d0972f45396","user_transactions":[]}}},{"context":{"level":"warn","file":"client.cpp","line":1090,"method":"on_new_block","hostname":"","thread_name":"th_a","timestamp":"20140828T125745.177887"},"format":"Error pushing block ${block_number} - ${block_id}","data":{"block_id":"8abcfb93c52f999e3ef5288c4f837f4f15af5521","block_number":1,"block":{"previous":"0000000000000000000000000000000000000000","block_num":1,"timestamp":"20140719T031850","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"38c370dbf65ab46b5a403dd3d44729bceeb282cb","previous_secret":"9c9dc7b87c243311961ac3e8000b5827841372b4","delegate_signature":"20248c112ed3b1c56696cae6e0b8ff55a0403eb0287b445813a99262e141f7cd56e7004948cf962bd76a9649fe749d14a6b88b5a700e11e1b068042d0972f45396","user_transactions":[]}}}]}
Looks like you connected to a peer running an old version of the code. Error was on their side, not yours.
I have the exact same error and it is trying to connect to the same peer.
-
Reposting, debug error stuck on block 321978.
>> debug_list_errors
20140828T140220.837466 (28 seconds ago )
10 assert_exception: Assert Exception
hash_of_previous_secret == delegate_record->delegate_info->next_secret_hash:
{"previous_secret":"f34ed43768d340b4e0ab92a6ec2face8c9d826fa","hash_of_previous_secret":"046b7e76330d459f2fbf107e01dbfb1b6e5f1c5a","delegate_record":{"id":2156,"name":"delegate-baozi","public_data":null,"owner_key":"BTSX8QpSmZ9HRUyZyq5zNUiWZX6cCkAY3nwDmS7KBFib1WrZ3m5Uh5","active_key_history":[["20140720T004040","BTSX8QpSmZ9HRUyZyq5zNUiWZX6cCkAY3nwDmS7KBFib1WrZ3m5Uh5"]],"registration_date":"20140720T004040","last_update":"20140720T004040","delegate_info":{"votes_for":22830235072068,"blocks_produced":3032,"blocks_missed":36,"pay_rate":100,"pay_balance":159484848,"next_secret_hash":"4567c7d5877ac73f9150fc89020eebffa16c0230","last_block_num_produced":321979},"meta_data":null}}
bitshares chain_database.cpp:689 bts::blockchain::detail::chain_database_impl::update_delegate_production_info
{"block":{"previous":"237b2b29c6717f382230c2a133a6ff7ea71ba6a4","block_num":321979,"timestamp":"20140826T141700","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"4567c7d5877ac73f9150fc89020eebffa16c0230","previous_secret":"f34ed43768d340b4e0ab92a6ec2face8c9d826fa","delegate_signature":"1f10fcbd21d8b1617502010d98a781e1c95d8926f8febe64cd90c27224b9ca2fa0e1a5ae3dba3a3d397ed12e42c48c3b702141a3e6272a2da6effc55895ddb998a","user_transactions":[{"expiration":"20140826T161653","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"BTSXLeoXC7sVMH8R7NFXVDquctfUzCA3t192b","amount":1091000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"BTSXAcZ9kAbm4Vo8sjAtmEqcbLezm5pkaEzbP","amount":281158999,"claim_input_data":""}},{"type":"ask_op_type","data":{"amount":282239999,"ask_index":{"order_price":{"ratio":"0.004464285714285714","quote_asset_id":22,"base_asset_id":0},"owner":"BTSXH6CrzKWKD5gSpkDrVPzqKjexXKAS7yHm"}}}],"signatures":["20d3f616a32e34cbfc3ab9962ba24d3e16947b8fdc62f2980bfda4ad15deccfdd0e9af47575d303a9b98d0468d9bcdb22a8c7d5336a6cb7778fd624eed1eb00b71","1fb5d9771c90ab766756e6d340eed3e60b68673afb6978c21f3ad700839404f96b7e70918654538417c1c47ee28fd7231d8b224c601690f47fbbc2efd462f1392e","202c7a9a01ded25747c6971d2947bfa857546195c9f6b99bf4893eff429ef7a4b87992ccbe8cea6511aca46a234e5a445b0dabaecfb8ab84e90ff56e2b26e5d193"]}]}}
bitshares chain_database.cpp:878 bts::blockchain::detail::chain_database_impl::extend_chain
{"block_data":{"previous":"237b2b29c6717f382230c2a133a6ff7ea71ba6a4","block_num":321979,"timestamp":"20140826T141700","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"4567c7d5877ac73f9150fc89020eebffa16c0230","previous_secret":"f34ed43768d340b4e0ab92a6ec2face8c9d826fa","delegate_signature":"1f10fcbd21d8b1617502010d98a781e1c95d8926f8febe64cd90c27224b9ca2fa0e1a5ae3dba3a3d397ed12e42c48c3b702141a3e6272a2da6effc55895ddb998a","user_transactions":[{"expiration":"20140826T161653","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"BTSXLeoXC7sVMH8R7NFXVDquctfUzCA3t192b","amount":1091000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"BTSXAcZ9kAbm4Vo8sjAtmEqcbLezm5pkaEzbP","amount":281158999,"claim_input_data":""}},{"type":"ask_op_type","data":{"amount":282239999,"ask_index":{"order_price":{"ratio":"0.004464285714285714","quote_asset_id":22,"base_asset_id":0},"owner":"BTSXH6CrzKWKD5gSpkDrVPzqKjexXKAS7yHm"}}}],"signatures":["20d3f616a32e34cbfc3ab9962ba24d3e16947b8fdc62f2980bfda4ad15deccfdd0e9af47575d303a9b98d0468d9bcdb22a8c7d5336a6cb7778fd624eed1eb00b71","1fb5d9771c90ab766756e6d340eed3e60b68673afb6978c21f3ad700839404f96b7e70918654538417c1c47ee28fd7231d8b224c601690f47fbbc2efd462f1392e","202c7a9a01ded25747c6971d2947bfa857546195c9f6b99bf4893eff429ef7a4b87992ccbe8cea6511aca46a234e5a445b0dabaecfb8ab84e90ff56e2b26e5d193"]}]}}
bitshares chain_database.cpp:1374 bts::blockchain::chain_database::push_block
Error pushing block 321979 - c4079669db15ce1e843c2c792501412ad30de888
{"block_id":"c4079669db15ce1e843c2c792501412ad30de888","block_number":321979,"block":{"previous":"237b2b29c6717f382230c2a133a6ff7ea71ba6a4","block_num":321979,"timestamp":"20140826T141700","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"4567c7d5877ac73f9150fc89020eebffa16c0230","previous_secret":"f34ed43768d340b4e0ab92a6ec2face8c9d826fa","delegate_signature":"1f10fcbd21d8b1617502010d98a781e1c95d8926f8febe64cd90c27224b9ca2fa0e1a5ae3dba3a3d397ed12e42c48c3b702141a3e6272a2da6effc55895ddb998a","user_transactions":[{"expiration":"20140826T161653","delegate_slate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"BTSXLeoXC7sVMH8R7NFXVDquctfUzCA3t192b","amount":1091000,"claim_input_data":""}},{"type":"withdraw_op_type","data":{"balance_id":"BTSXAcZ9kAbm4Vo8sjAtmEqcbLezm5pkaEzbP","amount":281158999,"claim_input_data":""}},{"type":"ask_op_type","data":{"amount":282239999,"ask_index":{"order_price":{"ratio":"0.004464285714285714","quote_asset_id":22,"base_asset_id":0},"owner":"BTSXH6CrzKWKD5gSpkDrVPzqKjexXKAS7yHm"}}}],"signatures":["20d3f616a32e34cbfc3ab9962ba24d3e16947b8fdc62f2980bfda4ad15deccfdd0e9af47575d303a9b98d0468d9bcdb22a8c7d5336a6cb7778fd624eed1eb00b71","1fb5d9771c90ab766756e6d340eed3e60b68673afb6978c21f3ad700839404f96b7e70918654538417c1c47ee28fd7231d8b224c601690f47fbbc2efd462f1392e","202c7a9a01ded25747c6971d2947bfa857546195c9f6b99bf4893eff429ef7a4b87992ccbe8cea6511aca46a234e5a445b0dabaecfb8ab84e90ff56e2b26e5d193"]}]}}
bitshares client.cpp:1136 bts::client::detail::client_impl::on_new_block
20140828T140220.841466 (28 seconds ago )
0 exception: unspecified
I am disconnecting peer 84.238.140.192:42577 for reason: You offered us a block that we reject as invalid
{}
bitshares client.cpp:1525 bts::client::detail::client_impl::error_encountered
20140828T140220.844466 (28 seconds ago )
0 exception: unspecified
I am disconnecting peer 80.240.133.79:1776 for reason: You offered us a block that we reject as invalid
{}
bitshares client.cpp:1525 bts::client::detail::client_impl::error_encountered
-
I deleted everything in my AppData roaming folder except wallet and I have 5 connections and rising. The only down side, re downloading the entire block chain. We will see if I get stuck were others are getting stuck.
Bright side is, it's connected.
*this is windows 7 0.4.9.exe
**Never mind. Disconnected. Won't connect now. Stuck 24 days behind.
-
we maybe should stop trading before this bug is fixed
-
we maybe should stop trading before this bug is fixed
As one of the people with crash issues, I wouldn't want anyone else to stop trading. Keep on keeping on my friends and I'll be with you there soon. We're still super early, there's bound to be bugs here and there; it's the nature of being an early adopter and a sub 1.0 participant in the network.
-
we maybe should stop trading before this bug is fixed
As one of the people with crash issues, I wouldn't want anyone else to stop trading. Keep on keeping on my friends and I'll be with you there soon. We're still super early, there's bound to be bugs here and there; it's the nature of being an early adopter and a sub 1.0 participant in the network.
+5% edge as in cutting :)
-
client 0.4.9, installed over 0.4.8-a
win 7 (32bit)
Stuck at block 321973
network_get_connection_count 0
debug_list_errors errors are from 6+ days ago. (Can post pm if of any help.)
-
https://bitsharestalk.org/index.php?topic=7824.0
-
we maybe should stop trading before this bug is fixed
I doubt the recent sell off is due to bug issues but even so I'm looking at it as a shorting opportunity in the future ;D
-
we maybe should stop trading before this bug is fixed
I doubt the recent sell off is due to bug issues but even so I'm looking at it as a shorting opportunity in the future ;D
I doubt it's bug related as well but frankly I don't care. Cheap BTSX is good BTSX :)
-
we maybe should stop trading before this bug is fixed
I doubt the recent sell off is due to bug issues but even so I'm looking at it as a shorting opportunity in the future ;D
Well you need a functional wallet in order to short ... Hopefully a fix will be release soon.
-
Installed 0.4.9a, still crashing. Why does the crash report say app version 0.4.1...?
<?xml version="1.0" encoding="UTF-8" ?>
<CrashRpt version="1402">
<CrashGUID>d4948a18-d9f4-4cd1-afa1-02d8c415e851</CrashGUID>
<AppName>BitSharesX</AppName>
<AppVersion>0.4.1</AppVersion>
<ImageName>C:\Program Files (x86)\BitSharesX\bin\BitSharesX.exe</ImageName>
<OperatingSystem>Windows 7 Professional Build 7601</OperatingSystem>
<OSIs64Bit>1</OSIs64Bit>
<GeoLocation>en-us</GeoLocation>
<SystemTimeUTC>2014-08-28T18:13:57Z</SystemTimeUTC>
<ExceptionAddress>0x1378c64</ExceptionAddress>
<ExceptionModule>C:\Program Files (x86)\BitSharesX\bin\BitSharesX.exe</ExceptionModule>
<ExceptionModuleBase>0x12b0000</ExceptionModuleBase>
<ExceptionModuleVersion>0.0.0.0</ExceptionModuleVersion>
<ExceptionType>0</ExceptionType>
<ExceptionCode>-1073741819</ExceptionCode>
<GUIResourceCount>100</GUIResourceCount>
<OpenHandleCount>1841</OpenHandleCount>
<MemoryUsageKbytes>153500</MemoryUsageKbytes>
<ScreenshotInfo>
<VirtualScreen left="0" top="0" width="3840" height="1080" />
<Monitors>
<Monitor left="0" top="0" width="1920" height="1080" file="screenshot0.jpg" />
<Monitor left="1920" top="0" width="1920" height="1080" file="screenshot1.jpg" />
</Monitors>
<Windows>
<Window left="31" top="132" width="1040" height="753" title="BitShares X" />
</Windows>
</ScreenshotInfo>
<CustomProps />
<FileList>
<FileItem name="crashdump.dmp" description="Crash Minidump" />
<FileItem name="crashrpt.xml" description="Crash Description XML" />
<FileItem name="p2p.log" description="P2P Log File" />
<FileItem name="qt_temp.Hp3448" description="Log File" />
<FileItem name="screenshot0.jpg" description="Desktop Screenshot" />
<FileItem name="screenshot1.jpg" description="Desktop Screenshot" />
</FileList>
</CrashRpt>
-
Installed 0.4.9a, still crashing. Why does the crash report say app version 0.4.1...?
<?xml version="1.0" encoding="UTF-8" ?>
<CrashRpt version="1402">
<CrashGUID>d4948a18-d9f4-4cd1-afa1-02d8c415e851</CrashGUID>
<AppName>BitSharesX</AppName>
<AppVersion>0.4.1</AppVersion>
<ImageName>C:\Program Files (x86)\BitSharesX\bin\BitSharesX.exe</ImageName>
<OperatingSystem>Windows 7 Professional Build 7601</OperatingSystem>
<OSIs64Bit>1</OSIs64Bit>
<GeoLocation>en-us</GeoLocation>
<SystemTimeUTC>2014-08-28T18:13:57Z</SystemTimeUTC>
<ExceptionAddress>0x1378c64</ExceptionAddress>
<ExceptionModule>C:\Program Files (x86)\BitSharesX\bin\BitSharesX.exe</ExceptionModule>
<ExceptionModuleBase>0x12b0000</ExceptionModuleBase>
<ExceptionModuleVersion>0.0.0.0</ExceptionModuleVersion>
<ExceptionType>0</ExceptionType>
<ExceptionCode>-1073741819</ExceptionCode>
<GUIResourceCount>100</GUIResourceCount>
<OpenHandleCount>1841</OpenHandleCount>
<MemoryUsageKbytes>153500</MemoryUsageKbytes>
<ScreenshotInfo>
<VirtualScreen left="0" top="0" width="3840" height="1080" />
<Monitors>
<Monitor left="0" top="0" width="1920" height="1080" file="screenshot0.jpg" />
<Monitor left="1920" top="0" width="1920" height="1080" file="screenshot1.jpg" />
</Monitors>
<Windows>
<Window left="31" top="132" width="1040" height="753" title="BitShares X" />
</Windows>
</ScreenshotInfo>
<CustomProps />
<FileList>
<FileItem name="crashdump.dmp" description="Crash Minidump" />
<FileItem name="crashrpt.xml" description="Crash Description XML" />
<FileItem name="p2p.log" description="P2P Log File" />
<FileItem name="qt_temp.Hp3448" description="Log File" />
<FileItem name="screenshot0.jpg" description="Desktop Screenshot" />
<FileItem name="screenshot1.jpg" description="Desktop Screenshot" />
</FileList>
</CrashRpt>
I would assume the version is not updated in the build process and thus requires manual intervention which hasn't been done... meaning .. it doesn't really matter. You're getting the right code. ;)
-
I had initial crash as well. Removed all files except wallet and am now on the slow synch path....fingers crossed.
-
I had initial crash as well. Removed all files except wallet and am now on the slow synch path....fingers crossed.
ich auch.
-
I would assume the version is not updated in the build process and thus requires manual intervention which hasn't been done... meaning .. it doesn't really matter. You're getting the right code. ;)
Cool, thanks gamey
-
Still getting "Not Connected" with 0.4.9-a
-
Still getting "Not Connected" with 0.4.9-a
So am I.
0.4.9-a on Windows 7 does not connect.
-
Still getting "Not Connected" with 0.4.9-a
So am I.
0.4.9-a on Windows 7 does not connect.
I got that too but if you let is "sit" it seems to start synching...slowly...
-
Still getting "Not Connected" with 0.4.9-a
So am I.
0.4.9-a on Windows 7 does not connect.
I waited a few minutes and then my client connected. Currently have 8 network connections, although the sync does appear to be taking longer than usual...
-
For me 4.9-a did not connect at all(waited 15mins or so). I had to delete my default wallet directory and now its got 1 connection that comes in and out. very slow.
https://bitsharestalk.org/index.php?topic=7768.msg102881#msg102881
-
Still getting "Not Connected" with 0.4.9-a
So am I.
0.4.9-a on Windows 7 does not connect.
I got that too but if you let is "sit" it seems to start synching...slowly...
Now it got the connection but gets stuck on block 321976.
Is there anything I should do to make it go further?
-
I added this and got more connections:
network_set_advanced_node_parameters { "peer_connection_retry_timeout": 30, "desired_number_of_connections": 50, "maximum_number_of_connections": 200 }
Not sure if it helped or placebo effect. :)
but it also started crashing after that.... :'(
-
Still getting "Not Connected" with 0.4.9-a
So am I.
0.4.9-a on Windows 7 does not connect.
I got that too but if you let is "sit" it seems to start synching...slowly...
Now it got the connection but gets stuck on block 321976.
Is there anything I should do to make it go further?
I could not connect either with 0.4.9-a. I removed all files except wallet, and sync again and it works now I have 8 connections.
-
0.4.9a synced for me, but balance i s not right, and had unknown address.
>> debug_list_errors
20140828T183455.036580 (39 minutes ago )
0 exception: unspecified
Peer 114.215.129.110:1777 is disconnecting us because of an error: You offered us a block that we reject as invalid, exception: {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"chain_database.cpp","line":1309,"method":"push_block","hostname":"","thread_name":"th_a","timestamp":"20140828T183500.494240"},"format":"block_data.block_num > (get_head_block_num() - BTS_BLOCKCHAIN_MAX_UNDO_HISTORY): ","data":{"BTS_BLOCKCHAIN_MAX_UNDO_HISTORY":404}},{"context":{"level":"warn","file":"chain_database.cpp","line":1360,"method":"push_block","hostname":"","thread_name":"th_a","timestamp":"20140828T183500.494307"},"format":"","data":{"block_data":{"previous":"0000000000000000000000000000000000000000","block_num":1,"timestamp":"20140719T031850","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"38c370dbf65ab46b5a403dd3d44729bceeb282cb","previous_secret":"9c9dc7b87c243311961ac3e8000b5827841372b4","delegate_signature":"20248c112ed3b1c56696cae6e0b8ff55a0403eb0287b445813a99262e141f7cd56e7004948cf962bd76a9649fe749d14a6b88b5a700e11e1b068042d0972f45396","user_transactions":[]}}},{"context":{"level":"warn","file":"client.cpp","line":1090,"method":"on_new_block","hostname":"","thread_name":"th_a","timestamp":"20140828T183500.494364"},"format":"Error pushing block ${block_number} - ${block_id}","data":{"block_id":"8abcfb93c52f999e3ef5288c4f837f4f15af5521","block_number":1,"block":{"previous":"0000000000000000000000000000000000000000","block_num":1,"timestamp":"20140719T031850","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"38c370dbf65ab46b5a403dd3d44729bceeb282cb","previous_secret":"9c9dc7b87c243311961ac3e8000b5827841372b4","delegate_signature":"20248c112ed3b1c56696cae6e0b8ff55a0403eb0287b445813a99262e141f7cd56e7004948cf962bd76a9649fe749d14a6b88b5a700e11e1b068042d0972f45396","user_transactions":[]}}}]}
-
Crashed again for me right around 320000 block mark. And I can't open the client.
-
Just got mine fully in sync. Had to quit and restart about 3 times though.
-
It's very annoying. They update it everyday but none of them is stable.
-
Just got mine fully in sync. Had to quit and restart about 3 times though.
Did you reset the database 3 separate times? or just close out the client and restart it 3 times? (via "continue normally")
-
Crashed again for me right around 320000 block mark. And I can't open the client.
.0.4.9-a crashed after opened. On personal computer and VPS.
-
Crashed again for me right around 320000 block mark. And I can't open the client.
.0.4.9-a crashed after opened. On personal computer and VPS.
If you ever get stuck, you may need to re-sync.
-
Just got mine fully in sync. Had to quit and restart about 3 times though.
Did you reset the database 3 separate times? or just close out the client and restart it 3 times? (via "continue normally")
I just had to choose reset one time. Even after that, I only got past so many blocks then would show "No Connections". I would then quit and restart it to continue. Eventually it did finish. Although now I am seeing strange GUI problems, specifically in the market the entire left side of the application going blank.
-
I still am unable to connect on version 4.9 on Windows
-
I still am unable to connect on version 4.9 on Windows
Did you try this https://bitsharestalk.org/index.php?topic=7768.0 (https://bitsharestalk.org/index.php?topic=7768.0)
note when I went into my wallet folder I had 2 default folders one was called: default-backup-2014-08-20T180708
I had to delete them both to get it to work
-
I still am unable to connect on version 4.9 on Windows
Did you try this https://bitsharestalk.org/index.php?topic=7768.0 (https://bitsharestalk.org/index.php?topic=7768.0)
note when I went into my wallet folder I had 2 default folders one was called: default-backup-2014-08-20T180708
I had to delete them both to get it to work
THIS WORKED FOR ME!!!
I was able to open the client (as if you were launching for the first time) and import a backup. However, I'm now in the process of reconciling my balances which are about 50% of what they should be... ???
I have a sneaking feeling it has to do with how I was running the same wallet off 2 seperate machines. BM has since suggested not to do that; in the mean time, time to play sherlock holmes and find my monies...
Thanks to everyone who's been posting solutions and workarounds! +5%
-
I couldn't sync with 0.4.9-a on Windows 7- it was getting stuck on block 321976.
I removed all files except the wallet, let it rebuild the whole thing from scratch (it took a while), did a rescan (wallet_rescan_blockchain) and now everything is fine, no crashes so far.
-
I couldn't sync with 0.4.9-a on Windows 7- it was getting stuck on block 321976.
I removed all files except the wallet, let it rebuild the whole thing from scratch (it took a while), did a rescan (wallet_rescan_blockchain) and now everything is fine, no crashes so far.
This worked for me as well. I was unable to make any connections.
I removed all files from appdata/roaming/bitsharesx except for the wallet folder. reinstalled. imported backup wallet. Now its fully synced running smooth.
-
I still am unable to connect on version 4.9 on Windows
Did you try this https://bitsharestalk.org/index.php?topic=7768.0 (https://bitsharestalk.org/index.php?topic=7768.0)
note when I went into my wallet folder I had 2 default folders one was called: default-backup-2014-08-20T180708
I had to delete them both to get it to work
I did this and it finally synced up...thank you for the troubleshooting!
-
Finally got 0.4.9a synced and working. It was slow but it worked. Best not to touch it whilst it's syncing!!
I'm now able to use it as intended.
-
after redownload the chain, none of my shorts showed up in the open order column, the blockchain saved my shorts did it not?
-
Finally got 0.4.9a synced and working. It was slow but it worked. Best not to touch it whilst it's syncing!!
I'm now able to use it as intended.
How? When I let mine run, it crashes and asks me to send a report. I can't even get to any of my funds at this moment. Doesn't matter where I try, it just fails on VPS or at home.
-
Finally got 0.4.9a synced and working. It was slow but it worked. Best not to touch it whilst it's syncing!!
I'm now able to use it as intended.
How? When I let mine run, it crashes and asks me to send a report. I can't even get to any of my funds at this moment. Doesn't matter where I try, it just fails on VPS or at home.
What seems to have helped in most cases is this:
remove all files except the wallet, let it sync and rebuild the whole database blockchain from scratch (it takes a while) and when the sync is finished do a rescan (wallet_rescan_blockchain)
-
Mac crashes though.
It would really help if you could provide a stack trace from the crash reporter:
On the OSX Terminal:
defaults write com.apple.CrashReporter DialogType Developer
Still having issues with mac (crashed again while re-syncing block chain). Can someone walk me step by step what I need to access a stack trace? (i.e. I'm not a dev, like not even kind of close)
-
Finally got 0.4.9a synced and working. It was slow but it worked. Best not to touch it whilst it's syncing!!
I'm now able to use it as intended.
How? When I let mine run, it crashes and asks me to send a report. I can't even get to any of my funds at this moment. Doesn't matter where I try, it just fails on VPS or at home.
What seems to have helped in most cases is this:
remove all files except the wallet, let it sync and rebuild the whole database blockchain from scratch (it takes a while) and when the sync is finished do a rescan (wallet_rescan_blockchain)
Tried that, still a bunch of UNKNOWNs:( I covered one of my large short order in servral smaller chunks prior to 0.4.8, which was not allowed anymore, will that be the problem?
-
Tried that multiple times. I'll get a 8 connections and get about half the blockchain, then it stops and I get no connections.
-
Going to try a new VPS and not import wallet or key until it syncs.
-
Mac crashes though.
It would really help if you could provide a strack trace from the crash reporter:
On the OSX Terminal:
defaults write com.apple.CrashReporter DialogType Developer
BM - let me know if this is what you're looking for
Process: BitSharesX [48656]
Path: /Applications/BitSharesX 0.4.9.app/Contents/MacOS/BitSharesX
Identifier: org.bitshares.btsx
Version: .. (..)
Code Type: X86-64 (Native)
Parent Process: launchd [371]
Responsible: BitSharesX [48656]
User ID: 501
Date/Time: 2014-08-28 19:45:19.195 -0400
OS Version: Mac OS X 10.9.3 (13D65)
Report Version: 11
Anonymous UUID: AF344F7C-B3F6-3789-440C-0799A13448F7
Sleep/Wake UUID: 41812ABC-D275-457D-810C-E646104676E9
Crashed Thread: 5
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0xfffffffffffffd40
Here's what's going on for me:
I've been able to get stable versions of the client running on both a windows machine and a mac machine without importing a wallet backup. If I upload my latest manual backup (which is from 8.26) and rescan the block chain, my balance are over 50% less than what they should be.
This is where it gets interesting, my last transaction was yesterday (8.27) at 4:46:28 PM EDT I did not get the chance to do a manual backup at this point. The reason I know this is when I retain the "default" folder in its current location and launch via "reset database". I can see all my transaction up to the point in which the client began crashing for me while the blockchain is syncing. I was even able to pull screenshots of everything to see all the transactions that were made. I'm able to get all the blocks synced and up to date (only by removing the default folder and letting the blockchain catch up); once I re-insert the "default" folder and rescan the transactions, the wallet crashes.
Now, I understand this isn't what you're supposed to do and I didn't realize until after I mentioned it and BM said not too... I was running the same wallet on multiple machines and doing market trades with multiple accounts within the wallet. I think this may have something to do with what's going on.
My questions is: what information do I need in order to "unwind" all those transactions and get it back to where I believe it to be correct. I also may have had some open orders, but I'm not certain.
TLDR; Balances way off with manual backup; client crashes with [as close to] "correct balance" [as I can tell] with 'default' backup.
-
0.4.8 - b on the margin of return amount, I can't find it on the 0.4.9
-
Sorry, if there is separate thread for 0.4.9.b.
0.4.9. was just not syncing on win 7.
0.4.9-b is crashing like crazy.(first version that does it on my system). Not just crashing but obviously not closing all the processes, as I could not restart without a re-boot.
Sent all the reports I can bare to withstand. Hope they help.
-
General Question: If my balances have yet to be corrected, should I refrain from making any transactions to further complicate things in my wallet?
-
General Question: If my balances have yet to be corrected, should I refrain from making any transactions to further complicate things in my wallet?
Any transactions you make will be relative to the balances already known and will not affect balances that are unknown. With 0.4.10 you should be able to recover all balances belonging to you.
-
General Question: If my balances have yet to be corrected, should I refrain from making any transactions to further complicate things in my wallet?
Any transactions you make will be relative to the balances already known and will not affect balances that are unknown. With 0.4.10 you should be able to recover all balances belonging to you.
Great! Downloading 0.4.10 now and will confirm.
-
Mac crashes though.
It would really help if you could provide a stack trace from the crash reporter:
On the OSX Terminal:
defaults write com.apple.CrashReporter DialogType Developer
Still having issues with mac (crashed again while re-syncing block chain). Can someone walk me step by step what I need to access a stack trace? (i.e. I'm not a dev, like not even kind of close)
Check this thread reply #113, hopefully this solution will work for you:
https://bitsharestalk.org/index.php?topic=7999.msg106009#msg106009
-
All issues have been resolved with my vault from 0.4.10
Great work to the dev team!