BitShares Forum
Main => General Discussion => Topic started by: bytemaster on August 30, 2014, 02:48:44 pm
-
DAC Sun Limited has updated their github repository with 0.4.10. It would be helpful if people could fetch and build and attempt to sync. Run a seed node and attempt to crash it.
Please file all issues in this thread.
-
Is this on the main blockchain or a testnet?
Anyway, building it now.
-
Is this on the main blockchain or a testnet?
Anyway, building it now.
Main chain.
-
harvey@needle:~/bitsharesx$ git checkout 0.4.10
error: pathspec '0.4.10' did not match any file(s) known to git.
-
ing
-
harvey@needle:~/bitsharesx$ git checkout 0.4.10
error: pathspec '0.4.10' did not match any file(s) known to git.
It'll be the only one. There's nothing to checkout.
"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_accumulated_fees": "0.00000 BTSX",
"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": "/home/riverhead/rivertest",
"client_version": "0.4.10",
"network_num_connections": 8,
"network_num_connections_max": 200,
"ntp_time": "2014-08-30T15:23:38",
"ntp_time_error": -0.038176000000000002,
"wallet_open": false,
"wallet_unlocked": null,
"wallet_unlocked_until": null,
"wallet_unlocked_until_timestamp": null,
"wallet_last_scanned_block_timestamp": null,
"wallet_scan_progress": null,
"wallet_block_production_enabled": null,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
-
trying
-
harvey@needle:~/bitsharesx$ git checkout 0.4.10
error: pathspec '0.4.10' did not match any file(s) known to git.
It'll be the only one. There's nothing to checkout.
"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_accumulated_fees": "0.00000 BTSX",
"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": "/home/riverhead/rivertest",
"client_version": "0.4.10",
"network_num_connections": 8,
"network_num_connections_max": 200,
"ntp_time": "2014-08-30T15:23:38",
"ntp_time_error": -0.038176000000000002,
"wallet_open": false,
"wallet_unlocked": null,
"wallet_unlocked_until": null,
"wallet_unlocked_until_timestamp": null,
"wallet_last_scanned_block_timestamp": null,
"wallet_scan_progress": null,
"wallet_block_production_enabled": null,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
Checkout master, it hasn't been tagged yet.
-
Can you tell me where we can dl it please ?
-
harvey@needle:~/bitsharesx$ git checkout 0.4.10
error: pathspec '0.4.10' did not match any file(s) known to git.
Just start in a new folder from scratch. I do this:
mkdir 0.4.10
git clone https://github.com/dacsunlimited/bitsharesx.git
cd bitsharesx
git checkout 0.4.10
git submodule init
git submodule update
cmake .
make
That way you can compile new version while old one is running - this should probably be a script somewhere in the GIT.
Plus if you need to revert to an old version you have it handy.
-
DAC Sun Limited has updated their github repository with 0.4.10. It would be helpful if people could fetch and build and attempt to sync. Run a seed node and attempt to crash it.
Please file all issues in this thread.
the main target is the crash for too many connections, right?
I even never crash with 0.4.8/0.4.9, with about 100 connections....
-
harvey@needle:~/bitsharesx$ git checkout 0.4.10
error: pathspec '0.4.10' did not match any file(s) known to git.
Just start in a new folder from scratch. I do this:
mkdir 0.4.10
git clone https://github.com/dacsunlimited/bitsharesx.git
cd bitsharesx
git checkout 0.4.10
git submodule init
git submodule update
cmake .
make
That way you can compile new version while old one is running - this should probably be a script somewhere in the GIT.
Plus if you need to revert to an old version you have it handy.
Thank you +5%
-
got to the very end of sync and then crashed
--- currently syncing at 287 blocks/sec, 35 seconds remaining
--- there are now 1 active connections to the p2p network
(wallet closed) >>> Segmentation fault (core dumped)
-
got to the very end of sync and then crashed
--- currently syncing at 287 blocks/sec, 35 seconds remaining
--- there are now 1 active connections to the p2p network
(wallet closed) >>> Segmentation fault (core dumped)
Try with blank wallet, see what happens...
-
got to the very end of sync and then crashed
--- currently syncing at 287 blocks/sec, 35 seconds remaining
--- there are now 1 active connections to the p2p network
(wallet closed) >>> Segmentation fault (core dumped)
Try with blank wallet, see what happens...
I did nothing to create a wallet, if that's what you mean. I just turned it on and let it sync.
I've relaunched. Its fully synced and running. 7 active connections.
-
ing
Crashed.
test (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x000000000066050b in fc::exception::to_detail_string (this=this@entry=0xeef9600, ll=..., ll@entry=...) at /tmp/bts/bts0.4.10/bitsharesx/libraries/fc/src/exception.cpp:144
144 ss << variant(my->_code).as_string() <<" " << my->_name << ": " <<my->_what<<"\n";
(gdb) bt
#0 0x000000000066050b in fc::exception::to_detail_string (this=this@entry=0xeef9600, ll=..., ll@entry=...) at /tmp/bts/bts0.4.10/bitsharesx/libraries/fc/src/exception.cpp:144
#1 0x00000000007c6fae in bts::net::detail::message_oriented_connection_impl::read_loop (this=<optimized out>)
at /tmp/bts/bts0.4.10/bitsharesx/libraries/net/message_oriented_connection.cpp:202
#2 0x00000000007c819c in operator() (__closure=<optimized out>) at /tmp/bts/bts0.4.10/bitsharesx/libraries/net/message_oriented_connection.cpp:128
#3 fc::detail::void_functor_run<bts::net::detail::message_oriented_connection_impl::connect_to(const fc::ip::endpoint&)::__lambda1>::run(void *, void *) (functor=<optimized out>,
prom=0xe6d03b0) at /tmp/bts/bts0.4.10/bitsharesx/libraries/fc/include/fc/thread/task.hpp:83
#4 0x0000000000672603 in fc::task_base::run_impl (this=this@entry=0xe6d03c0) at /tmp/bts/bts0.4.10/bitsharesx/libraries/fc/src/thread/task.cpp:43
#5 0x0000000000672cb5 in fc::task_base::run (this=this@entry=0xe6d03c0) at /tmp/bts/bts0.4.10/bitsharesx/libraries/fc/src/thread/task.cpp:32
#6 0x0000000000670d3b in run_next_task (this=0x1848690) at /tmp/bts/bts0.4.10/bitsharesx/libraries/fc/src/thread/thread_d.hpp:398
#7 fc::thread_d::process_tasks (this=this@entry=0x1848690) at /tmp/bts/bts0.4.10/bitsharesx/libraries/fc/src/thread/thread_d.hpp:422
#8 0x0000000000670fc6 in fc::thread_d::start_process_tasks (my=25462416) at /tmp/bts/bts0.4.10/bitsharesx/libraries/fc/src/thread/thread_d.hpp:378
#9 0x0000000000d58d7e in make_fcontext ()
#10 0x0000000001848690 in ?? ()
#11 0x00007fffb70a4810 in ?? ()
#12 0x0000000000000000 in ?? ()
-
got to the very end of sync and then crashed
--- currently syncing at 287 blocks/sec, 35 seconds remaining
--- there are now 1 active connections to the p2p network
(wallet closed) >>> Segmentation fault (core dumped)
Try with blank wallet, see what happens...
I did nothing to create a wallet, if that's what you mean. I just turned it on and let it sync.
But was your ~/.BitSharesX folder empty to begin with? i.e. did you have an old wallet or chain from before. MAKE A BACKUP OF THAT FOLDER. Then you can delete it and try fresh.
-
got to the very end of sync and then crashed
--- currently syncing at 287 blocks/sec, 35 seconds remaining
--- there are now 1 active connections to the p2p network
(wallet closed) >>> Segmentation fault (core dumped)
Try with blank wallet, see what happens...
I did nothing to create a wallet, if that's what you mean. I just turned it on and let it sync.
But was your ~/.BitSharesX folder empty to begin with? i.e. did you have an old wallet or chain from before. MAKE A BACKUP OF THAT FOLDER. Then you can delete it and try fresh.
Fresh server. Fresh install.
-
GUI crashed with 5d 22h to go in block history. New compile on a new VM.
My CLI test sync'd without issue. There is no wallet in that instance (haven't created one yet either). I'll wipe out the data directory and try again with a created wallet.
Update: Going to try the GUI again with no wallet.
-
33% and rising captain
[ 31%] Built target easylzma_static
Scanning dependencies of target fc
[ 32%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/uint128.cpp.o
[ 32%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/variant.cpp.o
[ 33%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/exception.cpp
-
for the past 10-15 mins the connection count was very stable at 7 connections. few if any new messages.
Just now its started going bananas again connecting and disconnecting rapidly 5-10 messages per second.
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 9 active connections to the p2p network
--- there are now 10 active connections to the p2p network
--- there are now 9 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 6 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 9 active connections to the p2p network
--- there are now 10 active connections to the p2p network
--- there are now 9 active connections to the p2p network
--- there are now 10 active connections to the p2p network
--- there are now 9 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 6 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 6 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 6 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 9 active connections to the p2p network
--- there are now 8 active connections to the p2p network
-
for the past 10-15 mins the connection count was very stable at 7 connections. few if any new messages.
Just now its started going bananas again connecting and disconnecting rapidly 5-10 messages per second.
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 9 active connections to the p2p network
--- there are now 10 active connections to the p2p network
--- there are now 9 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 6 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 9 active connections to the p2p network
--- there are now 10 active connections to the p2p network
--- there are now 9 active connections to the p2p network
--- there are now 10 active connections to the p2p network
--- there are now 9 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 6 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 6 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 6 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 9 active connections to the p2p network
--- there are now 8 active connections to the p2p network
Be brave.
Try this command:
network_set_advanced_node_parameters {"desired_number_of_connections":500, "maximum_number_of_connections":500}
8) 8)
-
built 0.4.10 on ubuntu 14.04 and synced from scratch (no wallet) without any problems.
-
Be brave.
Try this command:
network_set_advanced_node_parameters {"desired_number_of_connections":500, "maximum_number_of_connections":500}
8) 8)
Well, the connect/disconnect rate seems to be worse after that. Only made it to 20 connects briefly then crashed.
--- there are now 16 active connections to the p2p network
--- there are now 17 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 15 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 15 active connections to the p2p network
--- there are now 14 active connections to the p2p network
--- there are now 15 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 15 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 17 active connections to the p2p network
--- there are now 18 active connections to the p2p network
--- there are now 17 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 17 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 17 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 15 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 15 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 15 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 17 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 15 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 17 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 17 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 15 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 17 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 17 active connections to the p2p network
--- there are now 18 active connections to the p2p network
--- there are now 19 active connections to the p2p network
--- there are now 18 active connections to the p2p network
--- there are now 17 active connections to the p2p network
--- there are now 18 active connections to the p2p network
--- there are now 19 active connections to the p2p network
--- there are now 18 active connections to the p2p network
--- there are now 17 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 17 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 15 active connections to the p2p network
(wallet closed) >>> Segmentation fault (core dumped)
-
built 0.4.10 on ubuntu 14.04 and synced from scratch (no wallet) without any problems.
GUI or CLI?
-
Update: I have snyc'd the CLI with both a wallet and without now without issue. However the account was not registered so there were no transactions to scan.
How do you reset the Ubuntu environment?
I have done the following:
rm -rf .BitShares\ X
rm -rf /tmp/BitShares\ X
rm -rf /tmp/qt_*
What am I missing? When I launch the client I still get a "Crash detected" pop up that asks if I want to rest or continue.
-
built 0.4.10 on ubuntu 14.04 and synced from scratch (no wallet) without any problems.
GUI or CLI?
CLI
-
built 0.4.10 on ubuntu 14.04 and synced from scratch (no wallet) without any problems.
GUI or CLI?
CLI
I'm using GUI on ubuntu 14.04, update from old chain (re-index), w/o any problem
-
Correction:
mkdir 0.4.10
cd 0.4.10
git clone https://github.com/dacsunlimited/bitsharesx.git
cd bitsharesx
git checkout 0.4.10
git submodule init
git submodule update
cmake .
make
Forgot the cd 0.4.10
However it seems that tag is not yet available, when looking at the GitHub repo.
-
Has anything new been found by the developers? Just wondering if we're going to have a 0.4.11 or should I upgrade my delegate, seed, and chain nodes to 0.4.10?
If it's still too early to tell that's cool, just don't want to get caught on the wrong version :).
-
{
"bitshares_toolkit_revision": "1a1810e494b7216dbe504e4de536cd70f860376b",
"bitshares_toolkit_revision_age": "18 hours ago",
"fc_revision": "3222dc7c0be62b9ad0fdfd303c5c4f53b39063e6",
"fc_revision_age": "47 hours ago",
"compile_date": "compiled on Aug 31 2014 at 02:27:59"
}
--- there are now 13 active connections to the p2p network
--- there are now 14 active connections to the p2p network
--- there are now 13 active connections to the p2p network
--- there are now 14 active connections to the p2p network
--- there are now 13 active connections to the p2p network
Maintain 10+ connections, runs well
-
delegate id: help.chinese
17 connections
info
{
"blockchain_head_block_num": 357191,
"blockchain_head_block_age": "5 seconds old",
"blockchain_head_block_timestamp": "2014-08-30T18:46:20",
"blockchain_average_delegate_participation": "99.02 %",
"blockchain_confirmation_requirement": 1,
"blockchain_accumulated_fees": "291,141.94140 BTSX",
"blockchain_delegate_pay_rate": "2.40692 BTSX",
"blockchain_share_supply": "1,999,925,911.52970 BTSX",
"blockchain_blocks_left_in_round": 46,
"blockchain_next_round_time": "at least 8 minutes in the future",
"blockchain_next_round_timestamp": "2014-08-30T18:54:00",
"blockchain_random_seed": "1b024eeae18c9573cb263c6a7b067a74d7ffcd91",
"client_data_dir": "/home/daniel/.BitSharesX",
"client_version": "0.4.10",
"network_num_connections": 17,
"network_num_connections_max": 200,
"ntp_time": "2014-08-30T18:46:25",
"ntp_time_error": -0.003166,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "3 years 2 months in the future",
"wallet_unlocked_until_timestamp": "2017-10-31T04:25:26",
"wallet_last_scanned_block_timestamp": "2014-08-30T18:24:30",
"wallet_scan_progress": "? %",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
}
-
Sycned and scanned for transactions OK.
Most transactions show up, recipient is shown as "UNKNOWN" for BitUSD orders.
Missing BitUSD balance (shows zero). Also missing BTSX from an ask order.
Wallet was restored from JSON backup.
-
Sycned and scanned for transactions OK.
Most transactions show up, recipient is shown as "UNKNOWN" for BitUSD orders.
Missing BitUSD balance (shows zero). Also missing BTSX from an ask order.
Wallet was restored from JSON backup.
Have you issued a rescan?
-
Sycned and scanned for transactions OK.
Most transactions show up, recipient is shown as "UNKNOWN" for BitUSD orders.
Missing BitUSD balance (shows zero). Also missing BTSX from an ask order.
Wallet was restored from JSON backup.
Have you issued a rescan?
wallet_recover_accounts <accounts_to_recover> [maximum_number_of_attempts]
wallet_recover_transaction <transaction_id_prefix> [recipient_account]
-
Sycned and scanned for transactions OK.
Most transactions show up, recipient is shown as "UNKNOWN" for BitUSD orders.
Missing BitUSD balance (shows zero). Also missing BTSX from an ask order.
Wallet was restored from JSON backup.
Have you issued a rescan?
First thing I tried after fully syncing.
-
--- there are now 51 active connections to the p2p network
(wallet closed) >>>
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff6f5c5c8 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::string const&) ()
from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(gdb) bt
#0 0x00007ffff6f5c5c8 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::string const&) ()
from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1 0x000000000065f160 in exception_impl (
this=0x333f2780)
at /home/user/bitsharesx/libraries/fc/src/exception.cpp:28
#2 fc::exception::exception (this=0x35f660e0, c=...)
at /home/user/bitsharesx/libraries/fc/src/exception.cpp:98
#3 0x000000000074ff35 in bts::net::detail::node_impl::connect_to_task (this=0x236dcb0, new_peer=...,
remote_endpoint=...)
at /home/user/bitsharesx/libraries/net/node.cpp:3167
#4 0x0000000000750036 in operator() (
__closure=<optimized out>) -
09 at /home/user/bitsharesx/libraries/net/node.cpp:34---Type <return> to continue, or q <return> to quit---
#5 fc::detail::void_functor_run<bts::net::detail::node_impl::connect_to(const fc::ip::endpoint&)::__lambda19>::run(void *, void *) (functor=<optimized out>,
prom=0x2dd63b10)
at /home/user/bitsharesx/libraries/fc/include/fc/thread/task.hpp:83
#6 0x00000000006725a3 in fc::task_base::run_impl (
this=this@entry=0x2dd63b38)
at /home/user/bitsharesx/libraries/fc/src/thread/task.cpp:43
#7 0x0000000000672c55 in fc::task_base::run (
this=this@entry=0x2dd63b38)
at /home/user/bitsharesx/libraries/fc/src/thread/task.cpp:32
#8 0x0000000000670cdb in run_next_task (
this=0x1848690)
at /home/user/bitsharesx/libraries/fc/src/thread/-
#9 fc::thread_d::process_tasks (q <return> to quit---
this=this@entry=0x1848690)
at /home/user/bitsharesx/libraries/fc/src/thread/thread_d.hpp:422
#10 0x0000000000670f66 in fc::thread_d::start_process_tasks (my=25462416)
at /home/user/bitsharesx/libraries/fc/src/thread/thread_d.hpp:378
#11 0x0000000000d58d4e in make_fcontext ()
#12 0x0000000001848690 in ?? ()
#13 0x00007fffc586ec60 in ?? ()
#14 0x0000000000000000 in ?? ()
(gdb)
p2p log
https://www.dropbox.com/s/rpzoi37iqshget6/p2p.log.20140830T180000?dl=0
-
Sycned and scanned for transactions OK.
Most transactions show up, recipient is shown as "UNKNOWN" for BitUSD orders.
Missing BitUSD balance (shows zero). Also missing BTSX from an ask order.
Wallet was restored from JSON backup.
Have you issued a rescan?
wallet_recover_accounts <accounts_to_recover> [maximum_number_of_attempts]
wallet_recover_transaction <transaction_id_prefix> [recipient_account]
Ran those after the rescan, neither seemed to do anything (unless I am using them incorrectly).
I only have one registered account and placed 3 orders in the BitUSD market so what would be the correct values for accounts_to_recover and max attempts?
When I run wallet_recover_transaction on all the transactions that I can see, I get this output:
wallet_recover_transaction 289de77a ionx
10 assert_exception: Assert Exception
has_deposit:
{}
bitshares wallet.cpp:3018 recover_transaction
{}
bitshares wallet.cpp:3099 recover_transaction
{}
bitshares common_api_client.cpp:1667 wallet_recover_transaction
{"command":"wallet_recover_transaction"}
bitshares cli.cpp:481 execute_command
-
Sycned and scanned for transactions OK.
Most transactions show up, recipient is shown as "UNKNOWN" for BitUSD orders.
Missing BitUSD balance (shows zero). Also missing BTSX from an ask order.
Wallet was restored from JSON backup.
Have you issued a rescan?
wallet_recover_accounts <accounts_to_recover> [maximum_number_of_attempts]
wallet_recover_transaction <transaction_id_prefix> [recipient_account]
Ran those after the rescan, neither seemed to do anything (unless I am using them incorrectly).
I only have one registered account and placed 3 orders in the BitUSD market so what would be the correct values for accounts_to_recover and max attempts?
When I run wallet_recover_transaction on all the transactions that I can see, I get this output:
wallet_recover_transaction 289de77a ionx
10 assert_exception: Assert Exception
has_deposit:
{}
bitshares wallet.cpp:3018 recover_transaction
{}
bitshares wallet.cpp:3099 recover_transaction
{}
bitshares common_api_client.cpp:1667 wallet_recover_transaction
{"command":"wallet_recover_transaction"}
bitshares cli.cpp:481 execute_command
It looks like the recover transaction only works for transfers and not bids/asks. I am looking to add something to recover bids/asks.
-
Just got home. Do you still need someone to test this?
I've seen an announcement from DACSUNlimited stating they are going to release soon.
-
Just got home. Do you still need someone to test this?
I've seen an announcement from DACSUNlimited stating they are going to release soon.
Any testing prior to their release is good.
-
Just got home. Do you still need someone to test this?
I've seen an announcement from DACSUNlimited stating they are going to release soon.
Any testing prior to their release is good.
Thanks for the high efficiency. +5%
I updated the linux version, everything seems fine as always, but usually WIN version is more buggy. Do you consider testing WIN version in future before official release?
-
--- there are now 14 active connections to the p2p network
(wallet closed) >>> Segmentation fault (core dumped)
This is on my first attempt.
UPDATE:
This happened while synchronizating
28M Aug 31 00:12 default.log
After restart this was the console:
--- there are now 5 active connections to the p2p network
--- there are now 6 active connections to the p2p network
(wallet closed) >>> info
{
"blockchain_head_block_num": 253175,
"blockchain_head_block_age": "13 days old",
"blockchain_head_block_timestamp": "2014-08-18T07:44:50",
"blockchain_average_delegate_participation": "0.09 %",
"blockchain_confirmation_requirement": 2,
"blockchain_accumulated_fees": "128,843.25205 BTSX",
"blockchain_delegate_pay_rate": "1.06517 BTSX",
"blockchain_share_supply": "1,999,952,698.70823 BTSX",
"blockchain_blocks_left_in_round": 32,
"blockchain_next_round_time": "at least 5 minutes in the future",
"blockchain_next_round_timestamp": "2014-08-30T21:24:00",
"blockchain_random_seed": "8ec22d46a6e4647264f29983bafa529d391080e9",
"client_version": "0.4.10",
"network_num_connections": 6,
"network_num_connections_max": 200,
"ntp_time": "2014-08-30T21:18:49",
"ntp_time_error": -0.0021410000000000001,
"wallet_open": false,
"wallet_unlocked": null,
"wallet_unlocked_until": null,
"wallet_unlocked_until_timestamp": null,
"wallet_last_scanned_block_timestamp": null,
"wallet_scan_progress": null,
"wallet_block_production_enabled": null,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
}
It was synchronizing with about 1000 blocks/sec. And I increased desired_connections to 40 minute before the crash.
-
--- there are now 14 active connections to the p2p network
(wallet closed) >>> Segmentation fault (core dumped)
This is on my first attempt.
UPDATE:
This happened while synchronizating
28M Aug 31 00:12 default.log
After restart this was the console:
--- there are now 5 active connections to the p2p network
--- there are now 6 active connections to the p2p network
(wallet closed) >>> info
{
"blockchain_head_block_num": 253175,
"blockchain_head_block_age": "13 days old",
"blockchain_head_block_timestamp": "2014-08-18T07:44:50",
"blockchain_average_delegate_participation": "0.09 %",
"blockchain_confirmation_requirement": 2,
"blockchain_accumulated_fees": "128,843.25205 BTSX",
"blockchain_delegate_pay_rate": "1.06517 BTSX",
"blockchain_share_supply": "1,999,952,698.70823 BTSX",
"blockchain_blocks_left_in_round": 32,
"blockchain_next_round_time": "at least 5 minutes in the future",
"blockchain_next_round_timestamp": "2014-08-30T21:24:00",
"blockchain_random_seed": "8ec22d46a6e4647264f29983bafa529d391080e9",
"client_version": "0.4.10",
"network_num_connections": 6,
"network_num_connections_max": 200,
"ntp_time": "2014-08-30T21:18:49",
"ntp_time_error": -0.0021410000000000001,
"wallet_open": false,
"wallet_unlocked": null,
"wallet_unlocked_until": null,
"wallet_unlocked_until_timestamp": null,
"wallet_last_scanned_block_timestamp": null,
"wallet_scan_progress": null,
"wallet_block_production_enabled": null,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
}
Stack trace?
Make sure to pull the latest master we have fixed a few crash issues we discovered while testing.
-
default (unlocked) >>> about
{
"bitshares_toolkit_revision": "1a1810e494b7216dbe504e4de536cd70f860376b",
"bitshares_toolkit_revision_age": "21 hours ago",
"fc_revision": "3222dc7c0be62b9ad0fdfd303c5c4f53b39063e6",
"fc_revision_age": "50 hours ago",
"compile_date": "compiled on Aug 30 2014 at 20:06:36"
}
>>> get_info
{
"blockchain_head_block_num": 358126,
"blockchain_head_block_age": "5 seconds old",
"blockchain_head_block_timestamp": "2014-08-30T21:24:40",
"blockchain_average_delegate_participation": "97.12 %",
"blockchain_confirmation_requirement": 1,
"blockchain_accumulated_fees": "289,266.37678 BTSX",
"blockchain_delegate_pay_rate": "2.39142 BTSX",
"blockchain_share_supply": "1,999,925,610.19498 BTSX",
"blockchain_blocks_left_in_round": 20,
"blockchain_next_round_time": "at least 3 minutes in the future",
"blockchain_next_round_timestamp": "2014-08-30T21:28:00",
"blockchain_random_seed": "bbdbf0ca55a7bebfbd24da4bebce58f0c80c3f68",
"client_data_dir": "/root/.BitSharesX",
"client_version": "0.4.10",
"network_num_connections": 7,
"network_num_connections_max": 200,
"ntp_time": "2014-08-30T21:24:45",
"ntp_time_error": -0.019466000000000001,
"wallet_open": false,
"wallet_unlocked": null,
"wallet_unlocked_until": null,
"wallet_unlocked_until_timestamp": null,
"wallet_last_scanned_block_timestamp": null,
"wallet_scan_progress": null,
"wallet_block_production_enabled": null,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
--- there are now 15 active connections to the p2p network
default (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff6f5c5c8 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::string const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(gdb) bt
#0 0x00007ffff6f5c5c8 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::string const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1 0x000000000065f160 in exception_impl (this=0x16b97ca0) at /root/bitsharesx/libraries/fc/src/exception.cpp:28
#2 fc::exception::exception (this=0x3310abc0, c=...) at /root/bitsharesx/libraries/fc/src/exception.cpp:98
#3 0x000000000074ff35 in bts::net::detail::node_impl::connect_to_task (this=0x2343370, new_peer=..., remote_endpoint=...) at /root/bitsharesx/libraries/net/node.cpp:3167
#4 0x0000000000750036 in operator() (__closure=<optimized out>) at /root/bitsharesx/libraries/net/node.cpp:3409
#5 fc::detail::void_functor_run<bts::net::detail::node_impl::connect_to(const fc::ip::endpoint&)::__lambda19>::run(void *, void *) (functor=<optimized out>, prom=0x33931740) at /root/bitsharesx/libraries/fc/include/fc/thread/task.hpp:83
#6 0x00000000006725a3 in fc::task_base::run_impl (this=this@entry=0x33931768) at /root/bitsharesx/libraries/fc/src/thread/task.cpp:43
#7 0x0000000000672c55 in fc::task_base::run (this=this@entry=0x33931768) at /root/bitsharesx/libraries/fc/src/thread/task.cpp:32
#8 0x0000000000670cdb in run_next_task (this=0x1848690) at /root/bitsharesx/libraries/fc/src/thread/thread_d.hpp:398
#9 fc::thread_d::process_tasks (this=this@entry=0x1848690) at /root/bitsharesx/libraries/fc/src/thread/thread_d.hpp:422
#10 0x0000000000670f66 in fc::thread_d::start_process_tasks (my=25462416) at /root/bitsharesx/libraries/fc/src/thread/thread_d.hpp:378
#11 0x0000000000d58d4e in make_fcontext ()
#12 0x0000000001848690 in ?? ()
#13 0x00007fffcfb55c60 in ?? ()
#14 0x0000000000000000 in ?? ()
(gdb)
-
Stack trace?
Make sure to pull the latest master we have fixed a few crash issues we discovered while testing.
My version:
"bitshares_toolkit_revision": "1a1810e494b7216dbe504e4de536cd70f860376b",
"bitshares_toolkit_revision_age": "21 hours ago",
"fc_revision": "3222dc7c0be62b9ad0fdfd303c5c4f53b39063e6",
"fc_revision_age": "50 hours ago",
I'll try to reproduce it again and then I'll run it through gdb.
UPDATE: It crashed again.
-
Stack trace?
Make sure to pull the latest master we have fixed a few crash issues we discovered while testing.
My version:
"bitshares_toolkit_revision": "1a1810e494b7216dbe504e4de536cd70f860376b",
"bitshares_toolkit_revision_age": "21 hours ago",
"fc_revision": "3222dc7c0be62b9ad0fdfd303c5c4f53b39063e6",
"fc_revision_age": "50 hours ago",
I'll try to reproduce it again and then I'll run it through gdb.
Need to pull the latest code:
>> about
{
"bitshares_toolkit_revision": "2b3e00c5a2cbd29f628a8cc3e0a9889a05547775",
"bitshares_toolkit_revision_age": "24 minutes ago",
"fc_revision": "3222dc7c0be62b9ad0fdfd303c5c4f53b39063e6",
"fc_revision_age": "50 hours ago",
"compile_date": "compiled on Aug 30 2014 at 17:19:42"
}
-
OK
1a1810e494b7216dbe504e4de536cd70f860376b crashes 2 out of 2 attempts
2b3e00c5a2cbd29f628a8cc3e0a9889a05547775 crashes 0 out of 2 attempts
both are synchronizing with about 1000 blocks/sec and had desired_connections set to 40 (Although until full synchronization only 25 were established).
UPDATE: Actually 2b3e00c5a2cbd29f628a8cc3e0a9889a05547775 crashed. Running with gdb now.
(gdb) backtrace
Python Exception <class 'ImportError'> No module named 'gdb':
#0 0x00007ffff6f5c5c8 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::string const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1 0x000000000065f4e0 in exception_impl (this=0x1acf2140) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/exception.cpp:28
#2 fc::exception::exception (this=0x13995b50, c=...) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/exception.cpp:98
#3 0x0000000000750225 in bts::net::detail::node_impl::connect_to_task (this=0x1e2bbf0, new_peer=..., remote_endpoint=...) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/net/node.cpp:3167
#4 0x0000000000750326 in operator() (__closure=<optimized out>) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/net/node.cpp:3409
#5 fc::detail::void_functor_run<bts::net::detail::node_impl::connect_to(const fc::ip::endpoint&)::__lambda19>::run(void *, void *) (functor=<optimized out>, prom=0x1b971bb0)
at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/include/fc/thread/task.hpp:83
#6 0x0000000000672923 in fc::task_base::run_impl (this=this@entry=0x1b971bd8) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/task.cpp:43
#7 0x0000000000672fd5 in fc::task_base::run (this=this@entry=0x1b971bd8) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/task.cpp:32
#8 0x000000000067105b in run_next_task (this=0x184c690) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/thread_d.hpp:398
#9 fc::thread_d::process_tasks (this=this@entry=0x184c690) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/thread_d.hpp:422
#10 0x00000000006712e6 in fc::thread_d::start_process_tasks (my=25478800) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/thread_d.hpp:378
#11 0x0000000000d5c3fe in make_fcontext ()
#12 0x000000000184c690 in ?? ()
#13 0x00007fffcb5eec60 in ?? ()
#14 0x0000000000000000 in ?? ()
-
built 0.4.10 on ubuntu 14.04 and synced from scratch (no wallet) without any problems.
same here, stable for 6 hours now. Desired_connections: default
-
syncing with p2p network, our last block is 23 days old
--- currently syncing at 76 blocks/sec, 42 minutes remaining
So far no crash and everything easy.
-
The crash with 2b3e00c5a2cbd29f628a8cc3e0a9889a05547775 looks easy to reproduce - 2 out of 4 attempts crashed.
I only need to increase desired_connections.
-
OK
1a1810e494b7216dbe504e4de536cd70f860376b crashes 2 out of 2 attempts
2b3e00c5a2cbd29f628a8cc3e0a9889a05547775 crashes 0 out of 2 attempts
both are synchronizing with about 1000 blocks/sec and had desired_connections set to 40 (Although until full synchronization only 25 were established).
UPDATE: Actually 2b3e00c5a2cbd29f628a8cc3e0a9889a05547775 crashed. Running with gdb now.
(gdb) backtrace
Python Exception <class 'ImportError'> No module named 'gdb':
#0 0x00007ffff6f5c5c8 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::string const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1 0x000000000065f4e0 in exception_impl (this=0x1acf2140) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/exception.cpp:28
#2 fc::exception::exception (this=0x13995b50, c=...) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/exception.cpp:98
#3 0x0000000000750225 in bts::net::detail::node_impl::connect_to_task (this=0x1e2bbf0, new_peer=..., remote_endpoint=...) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/net/node.cpp:3167
#4 0x0000000000750326 in operator() (__closure=<optimized out>) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/net/node.cpp:3409
#5 fc::detail::void_functor_run<bts::net::detail::node_impl::connect_to(const fc::ip::endpoint&)::__lambda19>::run(void *, void *) (functor=<optimized out>, prom=0x1b971bb0)
at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/include/fc/thread/task.hpp:83
#6 0x0000000000672923 in fc::task_base::run_impl (this=this@entry=0x1b971bd8) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/task.cpp:43
#7 0x0000000000672fd5 in fc::task_base::run (this=this@entry=0x1b971bd8) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/task.cpp:32
#8 0x000000000067105b in run_next_task (this=0x184c690) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/thread_d.hpp:398
#9 fc::thread_d::process_tasks (this=this@entry=0x184c690) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/thread_d.hpp:422
#10 0x00000000006712e6 in fc::thread_d::start_process_tasks (my=25478800) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/thread_d.hpp:378
#11 0x0000000000d5c3fe in make_fcontext ()
#12 0x000000000184c690 in ?? ()
#13 0x00007fffcb5eec60 in ?? ()
#14 0x0000000000000000 in ?? ()
Dan & Eric are attempting to reporduce this, can you capture the P2P logs next time it crashes?
-
OK
1a1810e494b7216dbe504e4de536cd70f860376b crashes 2 out of 2 attempts
2b3e00c5a2cbd29f628a8cc3e0a9889a05547775 crashes 0 out of 2 attempts
both are synchronizing with about 1000 blocks/sec and had desired_connections set to 40 (Although until full synchronization only 25 were established).
UPDATE: Actually 2b3e00c5a2cbd29f628a8cc3e0a9889a05547775 crashed. Running with gdb now.
(gdb) backtrace
Python Exception <class 'ImportError'> No module named 'gdb':
#0 0x00007ffff6f5c5c8 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::string const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1 0x000000000065f4e0 in exception_impl (this=0x1acf2140) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/exception.cpp:28
#2 fc::exception::exception (this=0x13995b50, c=...) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/exception.cpp:98
#3 0x0000000000750225 in bts::net::detail::node_impl::connect_to_task (this=0x1e2bbf0, new_peer=..., remote_endpoint=...) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/net/node.cpp:3167
#4 0x0000000000750326 in operator() (__closure=<optimized out>) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/net/node.cpp:3409
#5 fc::detail::void_functor_run<bts::net::detail::node_impl::connect_to(const fc::ip::endpoint&)::__lambda19>::run(void *, void *) (functor=<optimized out>, prom=0x1b971bb0)
at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/include/fc/thread/task.hpp:83
#6 0x0000000000672923 in fc::task_base::run_impl (this=this@entry=0x1b971bd8) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/task.cpp:43
#7 0x0000000000672fd5 in fc::task_base::run (this=this@entry=0x1b971bd8) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/task.cpp:32
#8 0x000000000067105b in run_next_task (this=0x184c690) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/thread_d.hpp:398
#9 fc::thread_d::process_tasks (this=this@entry=0x184c690) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/thread_d.hpp:422
#10 0x00000000006712e6 in fc::thread_d::start_process_tasks (my=25478800) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/thread_d.hpp:378
#11 0x0000000000d5c3fe in make_fcontext ()
#12 0x000000000184c690 in ?? ()
#13 0x00007fffcb5eec60 in ?? ()
#14 0x0000000000000000 in ?? ()
Dan & Eric are attempting to reporduce this, can you capture the P2P logs next time it crashes?
I keep all data-dirs. Want them?
-
OK
1a1810e494b7216dbe504e4de536cd70f860376b crashes 2 out of 2 attempts
2b3e00c5a2cbd29f628a8cc3e0a9889a05547775 crashes 0 out of 2 attempts
both are synchronizing with about 1000 blocks/sec and had desired_connections set to 40 (Although until full synchronization only 25 were established).
UPDATE: Actually 2b3e00c5a2cbd29f628a8cc3e0a9889a05547775 crashed. Running with gdb now.
(gdb) backtrace
Python Exception <class 'ImportError'> No module named 'gdb':
#0 0x00007ffff6f5c5c8 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::string const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1 0x000000000065f4e0 in exception_impl (this=0x1acf2140) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/exception.cpp:28
#2 fc::exception::exception (this=0x13995b50, c=...) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/exception.cpp:98
#3 0x0000000000750225 in bts::net::detail::node_impl::connect_to_task (this=0x1e2bbf0, new_peer=..., remote_endpoint=...) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/net/node.cpp:3167
#4 0x0000000000750326 in operator() (__closure=<optimized out>) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/net/node.cpp:3409
#5 fc::detail::void_functor_run<bts::net::detail::node_impl::connect_to(const fc::ip::endpoint&)::__lambda19>::run(void *, void *) (functor=<optimized out>, prom=0x1b971bb0)
at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/include/fc/thread/task.hpp:83
#6 0x0000000000672923 in fc::task_base::run_impl (this=this@entry=0x1b971bd8) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/task.cpp:43
#7 0x0000000000672fd5 in fc::task_base::run (this=this@entry=0x1b971bd8) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/task.cpp:32
#8 0x000000000067105b in run_next_task (this=0x184c690) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/thread_d.hpp:398
#9 fc::thread_d::process_tasks (this=this@entry=0x184c690) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/thread_d.hpp:422
#10 0x00000000006712e6 in fc::thread_d::start_process_tasks (my=25478800) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/thread_d.hpp:378
#11 0x0000000000d5c3fe in make_fcontext ()
#12 0x000000000184c690 in ?? ()
#13 0x00007fffcb5eec60 in ?? ()
#14 0x0000000000000000 in ?? ()
Dan & Eric are attempting to reporduce this, can you capture the P2P logs next time it crashes?
I keep all data-dirs. Want them?
Post a link to where Eric can download the P2P logs for the crash.
-
The crash with 2b3e00c5a2cbd29f628a8cc3e0a9889a05547775 looks easy to reproduce - 2 out of 4 attempts crashed.
I only need to increase desired_connections.
What are you setting your desired connections to?
-
PM with link sent.
I set it to 40 (i think...)
UPDATE:
Exact commands:
(wallet closed) >>> network_get_advanced_node_parameters
{
"peer_connection_retry_timeout": 30,
"desired_number_of_connections": 8,
"maximum_number_of_connections": 200
}
(wallet closed) >>> network_set_advanced_node_parameters { "desired_number_of_connections": 40 }
OK
UPDATE2: No other commands were executed except "info"
-
Now it also crashed. I think segmentation fault. Sorry, where is the log file located again? I only used the bitshares_client.
-
PM with link sent.
I set it to 40 (i think...)
UPDATE:
Exact commands:
(wallet closed) >>> network_get_advanced_node_parameters
{
"peer_connection_retry_timeout": 30,
"desired_number_of_connections": 8,
"maximum_number_of_connections": 200
}
(wallet closed) >>> network_set_advanced_node_parameters { "desired_number_of_connections": 40 }
OK
UPDATE2: No other commands were executed except "info"
200 max connections could be quite high. Can you set both desired and max to 40 and make sure you still crash? Also, might be interesting to see how much memory is being used...
-
Got the same crash I think:
http://pastebin.com/CzT36yKK
Trying with maximum_number_of_connections set to 20.
-
PM with link sent.
I set it to 40 (i think...)
UPDATE:
Exact commands:
(wallet closed) >>> network_get_advanced_node_parameters
{
"peer_connection_retry_timeout": 30,
"desired_number_of_connections": 8,
"maximum_number_of_connections": 200
}
(wallet closed) >>> network_set_advanced_node_parameters { "desired_number_of_connections": 40 }
OK
UPDATE2: No other commands were executed except "info"
200 max connections could be quite high. Can you set both desired and max to 40 and make sure you still crash? Also, might be interesting to see how much memory is being used...
200 is default...
Running with 40/40 .
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
9097 emski 20 0 1571092 627476 124896 R 100.1 7.7 5:22.85 bitshares_clien
-
It didnt crash with 40/40 on first attempt but when it synchronized it lost a lot of connections:
--- there are now 22 active connections to the p2p network
--- there are now 23 active connections to the p2p network
--- there are now 22 active connections to the p2p network
--- there are now 23 active connections to the p2p network
--- there are now 22 active connections to the p2p network
--- there are now 23 active connections to the p2p network
--- there are now 22 active connections to the p2p network
--- there are now 23 active connections to the p2p network
--- there are now 22 active connections to the p2p network
--- there are now 23 active connections to the p2p network
--- there are now 22 active connections to the p2p network
--- there are now 23 active connections to the p2p network
--- there are now 22 active connections to the p2p network
--- syncing with p2p network, our last block is 36 hours old
--- currently syncing at 685 blocks/sec, 18 seconds remaining
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- syncing with p2p network, our last block is 28 hours old
--- currently syncing at 533 blocks/sec, 18 seconds remaining
--- there are now 6 active connections to the p2p network
--- syncing with p2p network, our last block is 11 hours old
--- currently syncing at 406 blocks/sec, 9 seconds remaining
--- there are now 7 active connections to the p2p network
--- there are now 6 active connections to the p2p network
-
2nd attempt
network_set_advanced_node_parameters { "maximum_number_of_connections": 40 }
network_set_advanced_node_parameters { "desired_number_of_connections": 40 }
--- there are now 26 active connections to the p2p network
--- there are now 27 active connections to the p2p network
--- there are now 26 active connections to the p2p network
(wallet closed) >>>
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff6f5c5c8 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::string const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(gdb) backtrace
#0 0x00007ffff6f5c5c8 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::string const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1 0x000000000065f4e0 in exception_impl (this=0x21742930) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/exception.cpp:28
#2 fc::exception::exception (this=0x1f5326f0, c=...) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/exception.cpp:98
#3 0x0000000000750225 in bts::net::detail::node_impl::connect_to_task (this=0x1e20f50, new_peer=..., remote_endpoint=...) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/net/node.cpp:3167
#4 0x0000000000750326 in operator() (__closure=<optimized out>) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/net/node.cpp:3409
#5 fc::detail::void_functor_run<bts::net::detail::node_impl::connect_to(const fc::ip::endpoint&)::__lambda19>::run(void *, void *) (functor=<optimized out>, prom=0x154ff890)
at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/include/fc/thread/task.hpp:83
#6 0x0000000000672923 in fc::task_base::run_impl (this=this@entry=0x154ff8b8) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/task.cpp:43
#7 0x0000000000672fd5 in fc::task_base::run (this=this@entry=0x154ff8b8) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/task.cpp:32
#8 0x000000000067105b in run_next_task (this=0x184c690) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/thread_d.hpp:398
#9 fc::thread_d::process_tasks (this=this@entry=0x184c690) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/thread_d.hpp:422
#10 0x00000000006712e6 in fc::thread_d::start_process_tasks (my=25478800) at /home/emski/bitsharesnodeTock/bitsharesx/libraries/fc/src/thread/thread_d.hpp:378
#11 0x0000000000d5c3fe in make_fcontext ()
#12 0x000000000184c690 in ?? ()
#13 0x00007fffc8d78c60 in ?? ()
#14 0x0000000000000000 in ?? ()
Need these p2p too ?
-
Its 2:00 (AM) here, so I'll be testing my pillow for the next 6-8 hours.
-
Looking good!
wallet_regenerate_keys got my balances back to where they should be.
This is reassuring and proves the keys for all transactions are deterministic as claimed (I'm using an old backup).
-
DAC Sun,
Suppose most of the delegates do not use the binary of the new version your provided but use git to pull the change,so please provide the following infor after you announce the new version, such that the delegates could confirm they have upgraded to the correct version.
btw,my delegates node have been upgrade to 0.4.10
crazybit (unlocked) >>> about
{
"bitshares_toolkit_revision": "1ed1a6b07153e3ce5916be46f859302a1b50a4b0",
"bitshares_toolkit_revision_age": "2 hours ago",
"fc_revision": "3222dc7c0be62b9ad0fdfd303c5c4f53b39063e6",
"fc_revision_age": "53 hours ago",
"compile_date": "compiled on Aug 31 2014 at 08:12:26"
}
-
My balance is showing 0.00 in version 0.4.10
-
My Windows Client is working fine :)
-
Just noticed that the transfer page is blank (white background, no fields/buttons).
And transfer from console gives this result:
10 assert_exception: Assert Exception
oacct.valid(): expecting an account to existing at this point
{}
bitshares wallet_db.cpp:381 store_key
{"real_amount_to_transfer":removed,"amount_to_transfer_symbol":"removed","paying_account_name":"removed","from_account_name":"removed","to_account_name":"removed","memo_message":"removed"}
bitshares wallet.cpp:3664 transfer_asset
{}
bitshares common_api_client.cpp:1027 wallet_transfer_from
{"command":"wallet_transfer_from"}
bitshares cli.cpp:481 execute_command
-
My 0.4.10 client doesn't sync. / osx 10.5.8
edit: restarted client, works now.
-
Windows and Linux GUI's working fine here.
-
(http://i.imgur.com/MKc7Dld.png)
Now wallet import works, however:
Did this wallet lose all of the 75K BTSX here? Is that 50K sent to UNKNOWN what went to margin call, or supposed to be returned?
-
0.4.10 exe still have a lot of UNKNOWNs with messed up balance, I'm start to think the programmers are incompetent
-
0.4.10 exe still have a lot of UNKNOWNs with messed up balance, I'm start to think the programmers are incompetent
Actually it's the cost of privacy - if you lose the transaction details, you can't recover them, but the balance should be safe.
So, backup your wallet often if you care about transaction details.
Also, if you don't like risk, wait until all the bugs are sorted out. You think Bitcoin was stable when it was $0.10?
-
0.4.10 exe still have a lot of UNKNOWNs with messed up balance, I'm start to think the programmers are incompetent
It's a complicated piece of software that's been out for a few weeks. The bugs are being worked out. We're not even on a 1.0 release yet.
I'm not sure about incompetent but they seem to be able to go days and days without sleep :o
-
I compiled a Windows version and while reindexing the blockchain it says this Assertion failed: _valid, file C:\bitshares\bitsharesx\libraries\fc\include\fc/optional.hpp 197
msvcr120d.dll!_NMSG_WRITE(int rterrnum) Line 226 C
msvcr120d.dll!abort() Line 62 C
msvcr120d.dll!_wassert(const wchar_t * expr, const wchar_t * filename, unsigned int lineno) Line 156 C
bitshares_client.exe!fc::optional<bts::blockchain::market_order>::operator->() Line 197 C++
bitshares_client.exe!bts::blockchain::detail::chain_database_impl::market_engine::execute(fc::signed_int quote_id, fc::signed_int base_id, const fc::time_point_sec & timestamp) Line 154 C++
bitshares_client.exe!bts::blockchain::detail::chain_database_impl::execute_markets(const fc::time_point_sec & timestamp, const std::shared_ptr<bts::blockchain::pending_chain_state> & pending_state) Line 786 C++
bitshares_client.exe!bts::blockchain::detail::chain_database_impl::extend_chain(const bts::blockchain::full_block & block_data) Line 847 C++
bitshares_client.exe!bts::blockchain::detail::chain_database_impl::switch_to_fork(const fc::ripemd160 & block_id) Line 532 C++
bitshares_client.exe!bts::blockchain::chain_database::push_block(const bts::blockchain::full_block & block_data) Line 1366 C++
bitshares_client.exe!bts::blockchain::chain_database::open(const fc::path & data_dir, fc::optional<fc::path> genesis_file, std::function<void __cdecl(unsigned int)> reindex_status_callback) Line 1070 C++
bitshares_client.exe!bts::client::client::open(const fc::path & data_dir, fc::optional<fc::path> genesis_file_path, std::function<void __cdecl(unsigned int)> reindex_status_callback) Line 1640 C++
bitshares_client.exe!bts::client::client::configure_from_command_line(int argc, char * * argv) Line 2412 C++
bitshares_client.exe!main(int argc, char * * argv) Line 32 C++
-
Did this wallet lose all of the 75K BTSX here? Is that 50K sent to UNKNOWN what went to margin call, or supposed to be returned?
Think you slipped a decimal on that 2.5k ;)
-
take a wild guess, I think the programmer did not commit enough or commited the wrong detail of the transactions and short positions to the blockchain, now they have no way to reconstruct the wallet with just a private key, we will have to manually print out transactions to get our balance right and our money back:( I'll send 3i my transactions, hopefully they will sent my missing balance back.
-
Maybe you can try in Release mode.
I compiled a Windows version and while reindexing the blockchain it says this Assertion failed: _valid, file C:\bitshares\bitsharesx\libraries\fc\include\fc/optional.hpp 197
msvcr120d.dll!_NMSG_WRITE(int rterrnum) Line 226 C
msvcr120d.dll!abort() Line 62 C
msvcr120d.dll!_wassert(const wchar_t * expr, const wchar_t * filename, unsigned int lineno) Line 156 C
bitshares_client.exe!fc::optional<bts::blockchain::market_order>::operator->() Line 197 C++
bitshares_client.exe!bts::blockchain::detail::chain_database_impl::market_engine::execute(fc::signed_int quote_id, fc::signed_int base_id, const fc::time_point_sec & timestamp) Line 154 C++
bitshares_client.exe!bts::blockchain::detail::chain_database_impl::execute_markets(const fc::time_point_sec & timestamp, const std::shared_ptr<bts::blockchain::pending_chain_state> & pending_state) Line 786 C++
bitshares_client.exe!bts::blockchain::detail::chain_database_impl::extend_chain(const bts::blockchain::full_block & block_data) Line 847 C++
bitshares_client.exe!bts::blockchain::detail::chain_database_impl::switch_to_fork(const fc::ripemd160 & block_id) Line 532 C++
bitshares_client.exe!bts::blockchain::chain_database::push_block(const bts::blockchain::full_block & block_data) Line 1366 C++
bitshares_client.exe!bts::blockchain::chain_database::open(const fc::path & data_dir, fc::optional<fc::path> genesis_file, std::function<void __cdecl(unsigned int)> reindex_status_callback) Line 1070 C++
bitshares_client.exe!bts::client::client::open(const fc::path & data_dir, fc::optional<fc::path> genesis_file_path, std::function<void __cdecl(unsigned int)> reindex_status_callback) Line 1640 C++
bitshares_client.exe!bts::client::client::configure_from_command_line(int argc, char * * argv) Line 2412 C++
bitshares_client.exe!main(int argc, char * * argv) Line 32 C++
-
For the devs:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `./BitSharesX'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f84cce730db in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::string const&) ()
from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(gdb) bt
#0 0x00007f84cce730db in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::string const&) ()
from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1 0x0000000000a74ac4 in operator()<std::basic_string<char>&> (
var=<error reading variable: Cannot access memory at address 0x7f8473e8>,
key="", this=0x7f8423afb200)
at /home/deleted/bitsharesx/libraries/fc/include/fc/variant_object.hpp:176
#2 fc::log_context::to_variant (this=this@entry=0x7f84740607e0)
at /home/deleted/bitsharesx/libraries/fc/src/log/log_message.cpp:167
#3 0x0000000000a759b3 in fc::to_variant (l=..., v=...)
at /home/deleted/bitsharesx/libraries/fc/src/log/log_message.cpp:94
#4 0x0000000000a75b99 in variant<fc::log_context> (val=...,
this=0x7f8423afb440)
at /home/deleted/bitsharesx/libraries/fc/include/fc/variant.hpp:421
#5 mutable_variant_object<fc::log_context&> (val=...,
key="(\353\342t\204\177\000\000\224!\242\000\000\000\000\000\340y\212t\204\177\000\000 xDt\204\177\000\000\210\263\204t\204\177\000\000 +\315t\204\177\000\000X\320Wt\204\177\000\000\004\000\000\000\000\000\000\000 xDt\204\177\000\000#\350\242\000\000\000\000\000Д\340t\204\177\000\000\300\264\257#\204\177", '\000' <repeats 18 times>, "\200\265\257#\204\177\000\000 xDt\204\177\000\000\200\265\257#\204\177\000\000 \000\000t\204\177\000\000\020\000\000\000\000\000\000\000\360\265\257#\204\177\000\000д\257#\204\177\000\000\070Ret\204\177\000\000\360\265\257#\204\177\000\000\000\000\000\000\000\000\000\000@ {t\204\177\000\000"...,
this=0x7f8423afb3f0)
---Type <return> to continue, or q <return> to quit---
at /home/deleted/bitsharesx/libraries/fc/include/fc/variant_object.hpp:197
#6 fc::log_message::to_variant (this=<optimized out>)
at /home/deleted/bitsharesx/libraries/fc/src/log/log_message.cpp:201
#7 0x0000000000a762b3 in fc::to_variant (m=..., v=...)
at /home/deleted/bitsharesx/libraries/fc/src/log/log_message.cpp:108
#8 0x0000000000a2b514 in variant<fc::log_message> (val=...,
this=0x7f8423afb4d0)
at /home/deleted/bitsharesx/libraries/fc/include/fc/variant.hpp:421
Python Exception <type 'exceptions.TypeError'> instance has no next() method:
#9 fc::to_variant<fc::log_message> (t=std::vector of length 1, capacity 1,
v=...) at /home/deleted/bitsharesx/libraries/fc/include/fc/variant.hpp:394
Python Exception <type 'exceptions.TypeError'> instance has no next() method:
#10 0x0000000000a27f2c in variant<std::vector<fc::log_message> > (
val=std::vector of length 1, capacity 1, this=0x7f8423afb5f0)
at /home/deleted/bitsharesx/libraries/fc/include/fc/variant.hpp:421
Python Exception <type 'exceptions.TypeError'> instance has no next() method:
#11 operator()<const std::vector<fc::log_message>&> (
var=std::vector of length 1, capacity 1,
key="\350lCt\204\177\000\000 \000\000t\204\177\000\000\032\000\000\000\000\000\000\000\237\266\257#\204\177\000\000\220\224Jt\204\177\000\000\030i\000T\204\177\000\000\000\000\000\000\000\000\000\000\260\361V̄\177", '\000' <repeats 18 times>, "X!\247\001\000\000\000\000 \000\000t\204\177\000\000 \271\257#\204\177\000\000\060\271\257#\204\177\000\000`\303Nt\204\177\000\000\033\257h\000\000\000\000\000x\t\000t\204\177\000\000\260\361V̄\177\000\000\237\266\257#\204\177\000\000\030", '\000' <repeats 23 times>, " \271\257#\204\177\000\000\060\271\257#\204\177\000\000\360\270\257#\204\177\000\000"..., this=0x7f8423afb580)
at /home/deleted/bitsharesx/libraries/fc/include/fc/variant_object.hpp:176
---Type <return> to continue, or q <return> to quit---
#12 fc::to_variant (e=..., v=...)
at /home/deleted/bitsharesx/libraries/fc/src/exception.cpp:114
#13 0x000000000068af1b in variant<fc::exception> (val=..., this=0x7f8423afb650)
at /home/deleted/bitsharesx/libraries/fc/include/fc/variant.hpp:421
#14 fc::mutable_variant_object::operator()<fc::exception const&> (
this=0x7f8423afb920, key="e", var=...)
at /home/deleted/bitsharesx/libraries/fc/include/fc/variant_object.hpp:176
#15 0x0000000000b9e56a in bts::net::peer_connection::destroy (
this=this@entry=0x7f8474e094d0)
at /home/deleted/bitsharesx/libraries/net/peer_connection.cpp:105
#16 0x0000000000b9f80b in bts::net::peer_connection::~peer_connection (
this=this@entry=0x7f8474e094d0, __in_chrg=<optimized out>)
at /home/deleted/bitsharesx/libraries/net/peer_connection.cpp:116
#17 0x0000000000ba5661 in ~peer_connection (this=0x7f8474e094d0,
__in_chrg=<optimized out>)
at /home/deleted/bitsharesx/libraries/net/peer_connection.cpp:117
#18 std::_Sp_counted_ptr<bts::net::peer_connection*, (__gnu_cxx::_Lock_policy)2>::_M_dispose (this=<optimized out>)
at /usr/include/c++/4.9/bits/shared_ptr_base.h:373
#19 0x0000000000b4b62a in _M_release (this=0x7f8474e28830)
at /usr/include/c++/4.9/bits/shared_ptr_base.h:149
#20 ~__shared_count (this=0x7f84748d73c8, __in_chrg=<optimized out>)
at /usr/include/c++/4.9/bits/shared_ptr_base.h:666
#21 ~__shared_ptr (this=0x7f84748d73c0, __in_chrg=<optimized out>)
---Type <return> to continue, or q <return> to quit---
at /usr/include/c++/4.9/bits/shared_ptr_base.h:914
#22 ~shared_ptr (this=0x7f84748d73c0, __in_chrg=<optimized out>)
at /usr/include/c++/4.9/bits/shared_ptr.h:93
#23 ~_List_node (this=0x7f84748d73b0, __in_chrg=<optimized out>)
at /usr/include/c++/4.9/bits/stl_list.h:106
#24 destroy<std::_List_node<std::shared_ptr<bts::net::peer_connection> > > (
this=<optimized out>, __p=0x7f84748d73b0)
at /usr/include/c++/4.9/ext/new_allocator.h:124
#25 std::_List_base<std::shared_ptr<bts::net::peer_connection>, std::allocator<std::shared_ptr<bts::net::peer_connection> > >::_M_clear (
this=this@entry=0x7f84744160d8) at /usr/include/c++/4.9/bits/list.tcc:75
#26 0x0000000000b063f8 in clear (this=0x7f84744160d8)
at /usr/include/c++/4.9/bits/stl_list.h:1304
#27 bts::net::detail::node_impl::delayed_peer_deletion_task (
this=0x7f8474415ca0) at /home/deleted/bitsharesx/libraries/net/node.cpp:1319
#28 0x0000000000b068dc in operator() (__closure=<optimized out>)
at /home/deleted/bitsharesx/libraries/net/node.cpp:1355
#29 fc::detail::void_functor_run<bts::net::detail::node_impl::schedule_peer_for_deletion(const peer_connection_ptr&)::<lambda()> >::run(void *, void *) (
functor=<optimized out>, prom=0x7f8474a74e70)
at /home/deleted/bitsharesx/libraries/fc/include/fc/thread/task.hpp:83
#30 0x0000000000a36675 in fc::task_base::run_impl (this=0x7f8474a74e80)
at /home/deleted/bitsharesx/libraries/fc/src/thread/task.cpp:43
#31 0x0000000000a35113 in run_next_task (this=<optimized out>)
---Type <return> to continue, or q <return> to quit---
at /home/deleted/bitsharesx/libraries/fc/src/thread/thread_d.hpp:398
#32 fc::thread_d::process_tasks (this=0x7f84740008c0)
at /home/deleted/bitsharesx/libraries/fc/src/thread/thread_d.hpp:422
#33 0x0000000000a35381 in fc::thread_d::start_process_tasks (
my=140206858569920)
at /home/deleted/bitsharesx/libraries/fc/src/thread/thread_d.hpp:378
#34 0x0000000000db20fe in make_fcontext ()
#35 0x00007f84740008c0 in ?? ()
#36 0x0000000000000000 in ?? ()
-
I think the balance fix will take at least two weeks, if ever.
-
I think the balance fix will take at least two weeks, if ever.
On what is this time estimate based? Hopefully it won't be that long. It's really the only serious glitch left.
-
I think the balance fix will take at least two weeks, if ever.
My balance is now showing as 0.00 -- I have a JSON backup. Am I ok? Did I just lose all of my investment?
-
I think the balance fix will take at least two weeks, if ever.
On what is this time estimate based? Hopefully it won't be that long. It's really the only serious glitch left.
because I think they messed up the blochchian somehow
-
I think the balance fix will take at least two weeks, if ever.
My balance is now showing as 0.00 -- I have a JSON backup. Am I ok? Did I just lose all of my investment?
your funds are safe because your private keys are safe and eventually all bugs will be worked out.
https://bitsharestalk.org/index.php?topic=7823.0
-
0.4.10 is no worse nor better than 0.4.9, waiting for 0.5.0 hehe
-
My balance is now showing as 0.00 -- I have a JSON backup. Am I ok? Did I just lose all of my investment?
Have you done wallet_backup_restore <.json file> <wallet_name> ?
-
Successfully installed 0.4.10 on win 7/32bit with single account registered today. (Already huge improvement over 0.4.9/a - this was never achieved on my system through the GUI on 0.4.9(a)).
Trying Ubuntu now (yes, 0.4.9/a the GUI mainly was crashing on it too, granted not so severely).
-
installment was a success no crashes at all on my end.
-
My balance is now showing as 0.00 -- I have a JSON backup. Am I ok? Did I just lose all of my investment?
Have you done wallet_backup_restore <.json file> <wallet_name> ?
Is that basically the same as File > Import Wallet ?
-
My balance is now showing as 0.00 -- I have a JSON backup. Am I ok? Did I just lose all of my investment?
Have you done wallet_backup_restore <.json file> <wallet_name> ?
Is that basically the same as File > Import Wallet ?
Yes I think so.
-
My balance is now showing as 0.00 -- I have a JSON backup. Am I ok? Did I just lose all of my investment?
Have you done wallet_backup_restore <.json file> <wallet_name> ?
Is that basically the same as File > Import Wallet ?
Yes I think so.
It's late and I'm being an idiot. I just realized the wallet is syncing to the blockchain. It's stuck on block 8387, so no wonder it's not displaying a balance. :o
-
When I run wallet_recover_transaction on all the transactions that I can see, I get this output:
wallet_recover_transaction 289de77a ionx
10 assert_exception: Assert Exception
has_deposit:
{}
bitshares wallet.cpp:3018 recover_transaction
{}
bitshares wallet.cpp:3099 recover_transaction
{}
bitshares common_api_client.cpp:1667 wallet_recover_transaction
{"command":"wallet_recover_transaction"}
bitshares cli.cpp:481 execute_command
It looks like the recover transaction only works for transfers and not bids/asks. I am looking to add something to recover bids/asks.
I'm suffering from the same problem. Is the issue https://github.com/BitShares/bitshares_toolkit/issues/725, https://github.com/BitShares/bitshares_toolkit/issues/712 or https://github.com/BitShares/bitshares_toolkit/issues/704 ?
-
My update:
I had already exported my wallet JSON file to a USB drive before upgrading to the 4.10 version. I downloaded and installed version 4.10 and ran the file. It got hung up on "reindexing.....Will take a few minutes". I went to task manager to get out of it and I waited about 1-2 minutes to restart it. I restarted version 4.10 and it worked fine and I was able to log in to my new 4.10 wallet. When the wallet started syncing, I initially got worried when I saw a zero balance in my wallet but the wallet was synching starting from about when it said "Last Block was synced 42d (days) ago". As of this post, it is now at "Last Block was synced 1d 15h 2m 10s ago" but I did experience a crash. I went to task manager and get out of it and I restarted the wallet. After I restarted the wallet, it resumed the syncing and it is almost finished.
I want to state the as the wallet was syncing, I was able to get my BTSX and BitUSD balances back to what they were before I upgraded my wallet and I did not have to import my JSON wallet at all. My conclusion to all of this is this: When the wallet begins to sync, it will show a zero balance but once it finishes syncing, then it should have your current balance.
I will repeat: The wallet did finish syncing and it shows my exact BTSX and BitUSD balances and it also shows all of the transactions that I made since I got started in Bitshares X. That is my report for the time being.
-
OSX 10.7.3
Running smooth with 30+ connections
-
I've updated to 0.4.10 .
None of the above-mentioned crashes exist.
Nice Work!
-
private key will lost when close the wallet , both happened with version 0.4.9 and 0.4.10
https://bitsharestalk.org/index.php?topic=7998.msg105817#msg105817
-
Linux Mint 17, 0.5GB RAM gives Segmentation faults.
My attempt was compiled just prior to the 0.4.10 being tagged but after this thread was a few pages deep, so I'm expecting it was the same code.
Initially from clean start, the qt-wallet fails. Wondering if the experience of normal user and delegate is different I tried looking to run the client only and then saw that stop; all that then seemed to allow the qt-wallet to open ok. After 10-15mins another Segmentation fault while downloading the blockchain.
$ ./BitSharesX &
.
.
Initializing genesis state from built-in genesis file
Successfully re-indexed 0 blocks in 0 seconds.
Initializing genesis state from built-in genesis file
[1]+ Segmentation fault ./BitSharesX
.
.
$ ./bitshares_client &
$ Loading blockchain from: /home/davidpbrown/.BitSharesX/chain
Loading config from: /home/davidpbrown/.BitSharesX/config.json
Initializing genesis state from built-in genesis file
$ Please be patient, this will take a few minutes...
Successfully re-indexed 0 blocks in 0 seconds.
Initializing genesis state from built-in genesis file
Not starting RPC server, use --server to enable the RPC interface
[1]+ Stopped ./bitshares_client
$ ./BitSharesX &
[2]- Exit 1 ./BitSharesX
$ ./BitSharesX &
[2]- Exit 1 ./BitSharesX
## The above two attempts and the second one more obviously, showed an alert suggesting that an instance of BitShares was running.
$ kill -9 8030
[1]+ Killed ./bitshares_client
$ ./BitSharesX &
## Success. Wallet creation ok and first few minutes of download of blockchain.
## but then a Segmentation fault roughly 10-15mins in.
-
All transactions are gone. My wallet no longer shows any transactions for any of my accounts.
wallet_account_transaction_history works fine..
(https://db.tt/LSTfFPEe)
-
Updated to 0.4.10 without any problems on OSX 10.8.5.
Did not lose balance or any transaction details. Easiest update for me so far. +5%
-
:( near finish sync syndrome (wallet crashed) both win and mac
-
Node Server: 188.226.195.137:60696 updated to 0.4.10 - running and stable
-
I'm not sure if this has been reported yet but there are two cosmetic issues that exist for quite some while now.
For one, the installer does not exit if you tick [ ] run client at the end. It waits for the bitshares process to finish.
Also this is the bitshares icon in my tray bar:
(http://i.snag.gy/gdfmI.jpg)
-
Just updated to 0.4.10 and the wallet synced up in less than 10 minutes....and all looked good until I checked out the transfer tab to be greeted with a blank screen under ..Transfer and Add Contacts....the navigation menu remains on the left which is all operational.
Anyone else with this issue...?....any fix...?.
-
:( near finish sync syndrome (wallet crashed) both win and mac
It SYNCED (win) !!! still not correct balance but better recovery :) great job!!! But what does this mean???
>> wallet_recover_transaction a1e8644f jwiz168
18 aes_exception: AES error
error during aes 256 cbc decrypt final
{"s":"error:0606506D:digital envelope routines:EVP_DecryptFinal_ex:wrong final block length"}
bitshares aes.cpp:263 fc::aes_decrypt
{}
bitshares wallet_records.cpp:52 bts::wallet::key_data::decrypt_private_key
{}
bitshares wallet.cpp:3126 bts::wallet::wallet::recover_transaction
{}
bitshares common_api_client.cpp:1667 bts::rpc_stubs::common_api_client::wallet_recover_transaction
{"command":"wallet_recover_transaction"}
bitshares cli.cpp:481 bts::cli::detail::cli_impl::execute_command
-
How long should 4.10 take to sync?
I am running OSX 10.9.4 I've been stuck at - last block sync 4 days 7 hours for the last 3 hours now. I am showing only between 3 and 6 network connections and intermittent loss of connection about every 30 sec. BitsharesX version 4.9 worked perfectly.
Thanks
-
My client is hung up on syncing the blockchain. I'm stuck on block 8387. Any solution to this problem?
-
ver 0.4.10
I created my 1st account last week - and today I created 2 further accounts in the same client, and registered those.
Made 2 transfers from the 1st account to both new accounts.
After several restarts of the client the balances of both new accounts still shows 0 BTSX.
The balance of 1st account correctly shows the balance after I transferred out of it.
I see this:
Transaction scanning progress is -100%
in the lower lefthand corner (in the green bar) Blocks are fully sync'ed
and:
Updating transaction history...
in the Recent Transactions
What could be wrong?
-
alright I have managed to register 2 accounts as delegates from my client - they now show as Standby.
The strange thing though is that the payrate for both accounts is not the number (between 1 and 100) I entered when registering?
Both numbers came up other than my entered number. And also I had to use both the console commands and the gui feature in order for it to succeed.
I used the commands from this:
https://github.com/BitShares/bitshares_toolkit/wiki/DPOS-Registering-Names-And-Delegates
and this:
http://wiki.bitshares.org/index.php/DPOS#How_to_become_a_delegate
which is somewhat confusing - because there is no clear instruction of the exact command to enter. Those 2 links shows slightly different command entries in order to register as a delegate.
Now I am in the unknown - waiting for eventual inclusion in the delegates list - or if I still need to input something in order to be an active delegate. I have no clue how to check if I am indeed active?
-
How long should 4.10 take to sync?
I am running OSX 10.9.4 I've been stuck at - last block sync 4 days 7 hours for the last 3 hours now. I am showing only between 3 and 6 network connections and intermittent loss of connection about every 30 sec. BitsharesX version 4.9 worked perfectly.
Thanks
Try this comand in console mode
network_add_node "188.226.195.137:60696" add
-
ver 0.4.10
I created my 1st account last week - and today I created 2 further accounts in the same client, and registered those.
Made 2 transfers from the 1st account to both new accounts.
After several restarts of the client the balances of both new accounts still shows 0 BTSX.
The balance of 1st account correctly shows the balance after I transferred out of it.
I see this:
Transaction scanning progress is -100%
in the lower lefthand corner (in the green bar) Blocks are fully sync'ed
and:
Updating transaction history...
in the Recent Transactions
What could be wrong?
Have you tried issues a rescan from the console screen? It seems like you have a full copy of the blockchain but it hasn't been successfully transaction scanned yet.
-
How long should 4.10 take to sync?
I am running OSX 10.9.4 I've been stuck at - last block sync 4 days 7 hours for the last 3 hours now. I am showing only between 3 and 6 network connections and intermittent loss of connection about every 30 sec. BitsharesX version 4.9 worked perfectly.
Thanks
Try this comand in console mode
network_add_node "188.226.195.137:60696" add
Thanks. What I did was to force quit out of the app, relaunch and choose the "Reset Database" option from the popup error message. So now it is re-syncing the entire database but seems to be working correctly...( 30min syncing and im about 1/2 way through).
-
How long should 4.10 take to sync?
I am running OSX 10.9.4 I've been stuck at - last block sync 4 days 7 hours for the last 3 hours now. I am showing only between 3 and 6 network connections and intermittent loss of connection about every 30 sec. BitsharesX version 4.9 worked perfectly.
Thanks
Try this comand in console mode
network_add_node "188.226.195.137:60696" add
Thanks. What I did was to force quit out of the app, relaunch and choose the "Reset Database" option from the popup error message. So now it is re-syncing the entire database but seems to be working correctly...( 30min syncing and im about 1/2 way through).
Bingo! This worked. For anyone using OSX, open activity monitor and force quit the bitsharesx app. You'll get the "reset database" prompt that way. Is there a console command for resetting the database?
-
Linux Mint 17, 0.5GB RAM gives Segmentation faults.
My attempt was compiled just prior to the 0.4.10 being tagged but after this thread was a few pages deep, so I'm expecting it was the same code.
Initially from clean start, the qt-wallet fails. Wondering if the experience of normal user and delegate is different I tried looking to run the client only and then saw that stop; all that then seemed to allow the qt-wallet to open ok. After 10-15mins another Segmentation fault while downloading the blockchain.
<snip />
It's working! :D
So, I thought I'd go back and try Chain Server again and after a few hours of grinding the hard drive it started scanning transactions and half hour later I'm fully synced all transactions look correct and block chain is staying up to date. The process of getting there was not nice.. in the sense of it demanding all resources but it got there.. so use Chain Server as per https://github.com/BitShares/bitshares_toolkit/wiki/Using-Chain-Servers#using-a-chain-server-to-sync-with-bitshares-x to fix Linux Mint and I expect also Ubuntu. Still a lot of glitches to fix but at least it's possible.
Glitches include reports in the terminal
QPainter::end: Painter ended with 2 saved states
which I saw in previous versions too.
and on receipt of asset notification, on moving the mouse to acknowledge and close that, I got a stream of
QApplication: Object event filter cannot be in a different thread.
8)
-
How long should 4.10 take to sync?
I am running OSX 10.9.4 I've been stuck at - last block sync 4 days 7 hours for the last 3 hours now. I am showing only between 3 and 6 network connections and intermittent loss of connection about every 30 sec. BitsharesX version 4.9 worked perfectly.
Thanks
Try this comand in console mode
network_add_node "188.226.195.137:60696" add
Thanks. What I did was to force quit out of the app, relaunch and choose the "Reset Database" option from the popup error message. So now it is re-syncing the entire database but seems to be working correctly...( 30min syncing and im about 1/2 way through).
Bingo! This worked. For anyone using OSX, open activity monitor and force quit the bitsharesx app. You'll get the "reset database" prompt that way. Is there a console command for resetting the database?
I noticed after the app is synced that the "from" TITAN (word/icon) address is missing. I was able to resent this instantly by importing my .JSON file backup.
-
don't waste our time releasing half baked quick fixs, just go and take a month time to fix all the bugs(GUI included) imaginable and throughly test in on testnet on all machines and OSs.
-
@Riverhead
yes I did try a rescan - but didn't look like it did much - a few sec and it was fully sync'ed
-
don't waste our time releasing half baked quick fixs, just go and take a month time to fix all the bugs(GUI included) imaginable and throughly test in on testnet on all machines and OSs.
You know, I used to think like that, but here is the thing - it is all open source if you REALLY disagree with how they do stuff, fork it and make your own. :)
-
don't waste our time releasing half baked quick fixs, just go and take a month time to fix all the bugs(GUI included) imaginable and throughly test in on testnet on all machines and OSs.
You know, I used to think like that, but here is the thing - it is all open source if you REALLY disagree with how they do stuff, fork it and make your own. :)
I don't have the time right now, I think the software designer of this project is the weak link here, should be replaced:(
-
don't waste our time releasing half baked quick fixs, just go and take a month time to fix all the bugs(GUI included) imaginable and throughly test in on testnet on all machines and OSs.
You know, I used to think like that, but here is the thing - it is all open source if you REALLY disagree with how they do stuff, fork it and make your own. :)
I don't have the time right now, I think the software designer of this project is the weak link here, should be replaced:(
Testing beta software isn't for everyone. Come back when we're on 1.x version and you should be happier. I don't think closing the public beta or asking for the head of Bytemaster is the quickest path to success. In fact just the opposite.
-
don't waste our time releasing half baked quick fixs, just go and take a month time to fix all the bugs(GUI included) imaginable and throughly test in on testnet on all machines and OSs.
You know, I used to think like that, but here is the thing - it is all open source if you REALLY disagree with how they do stuff, fork it and make your own. :)
I don't have the time right now, I think the software designer of this project is the weak link here, should be replaced:(
@yiminh your opinion is sufficiently expressed and heard - now take a month or two and come back after that. Or don't.
I for one, find the improvement from 0.4.9 to 0.4.10 amazing. To tell you the truth actually unbelievable. Did you guys actually switch to some new database? Or you did it in 0.4.9 and just fixed some first implementation screw-ups?
-
don't waste our time releasing half baked quick fixs, just go and take a month time to fix all the bugs(GUI included) imaginable and throughly test in on testnet on all machines and OSs.
that's what we're doing, we are the testing group... This is a community project, we are don't waste our time releasing half baked quick fixs, just go and take a month time to fix all the bugs(GUI included) imaginable and throughly test in on testnet on all machines and OSs.
You know, I used to think like that, but here is the thing - it is all open source if you REALLY disagree with how they do stuff, fork it and make your own. :)
I don't have the time right now, I think the software designer of this project is the weak link here, should be replaced:(
Testing beta software isn't for everyone. Come back when we're on 1.x version and you should be happier. I don't think closing the public beta or asking for the head of Bytemaster is the quickest path to success. In fact just the opposite.
strongly agree, thanks riverhead
-
don't waste our time releasing half baked quick fixs, just go and take a month time to fix all the bugs(GUI included) imaginable and throughly test in on testnet on all machines and OSs.
You know, I used to think like that, but here is the thing - it is all open source if you REALLY disagree with how they do stuff, fork it and make your own. :)
I don't have the time right now, I think the software designer of this project is the weak link here, should be replaced:(
Testing beta software isn't for everyone. Come back when we're on 1.x version and you should be happier. I don't think closing the public beta or asking for the head of Bytemaster is the quickest path to success. In fact just the opposite.
+5% Children in the future may be reading about Bytemaster and BitAssets one day in their history books imo :)
-
don't waste our time releasing half baked quick fixs, just go and take a month time to fix all the bugs(GUI included) imaginable and throughly test in on testnet on all machines and OSs.
You know, I used to think like that, but here is the thing - it is all open source if you REALLY disagree with how they do stuff, fork it and make your own. :)
I don't have the time right now, I think the software designer of this project is the weak link here, should be replaced:(
Testing beta software isn't for everyone. Come back when we're on 1.x version and you should be happier. I don't think closing the public beta or asking for the head of Bytemaster is the quickest path to success. In fact just the opposite.
I sure hope ByteMaster designed the details of this DAC, but he farmed out to some HongKong company, I think ByteMaster will never make the mistake of messing up transaction database design.
-
Updating transaction history...
Transaction scanning progress is -100%
those 2 messages are still present.
I tried to run the client on another computer but got same messages.
curious as to why those messages are 'hanging' there?
and for the time being my transfers to 2 other accounts are 'floating' somewhere out there on the blockchain i assume. and that was my whole stock of my BTSX
-
don't waste our time releasing half baked quick fixs, just go and take a month time to fix all the bugs(GUI included) imaginable and throughly test in on testnet on all machines and OSs.
I can build and run BitsharesX gui and client on Archlinux and Ubuntu without problems. So far - stable and secure.
-
Just had my first crash. Running on windows.
In 04.10 when exporting wallet and rewrote the file it crashed.
Then tried to make a new file, success
Just to check rewrote file and crash.
No big issue.
-
Just had my first crash. Running on windows.
In 04.10 when exporting wallet and rewrote the file it crashed.
Then tried to make a new file, success
Just to check rewrote file and crash.
No big issue.
Yes , same but in Ubuntu GUI. No big issue.
-
4.10 worked very nicely so far for me on windows 7. Synced quickly loaded wallet quickly, sees all accounts and market orders etc.
-
A behavior I noticed when using a chain server is that it says "Not connected" in the lower right, displays no other status message, but I can see my balance rising as it downloads/processes the chain. I can see why someone would think it's hung but it's actually working just fine.
-
Mine started to work but it eventually stopped syncing/connecting. Now it wont open at all.
-
Mine started to work but it eventually stopped syncing/connecting. Now it wont open at all.
Make sure it's not running in the background. I find sometimes it keeps the task going even though nothing shows and it needs to be killed.
-
Mine started to work but it eventually stopped syncing/connecting. Now it wont open at all.
Make sure it's not running in the background. I find sometimes it keeps the task going even though nothing shows and it needs to be killed.
Rebooted twice now. Can't connect to the network.
UPDATE: It randomly started connecting after bring open for a while. wierd
-
Mine started to work but it eventually stopped syncing/connecting. Now it wont open at all.
Make sure it's not running in the background. I find sometimes it keeps the task going even though nothing shows and it needs to be killed.
Rebooted twice now. Can't connect to the network.
UPDATE: It randomly started connecting after bring open for a while. wierd
Just saw your update (even though it quoted it...weird. Anyway, glad it's working :) .
That might be a GUI display issue. Mine also says Not connected but I can tell that it is because my balances are updating as it processes the chain.
Try updating config.json to include this after the Default Peers section:
"chain_servers": ["104.131.35.149:1775"],
-
My Mac OSX wallet isn't syncing at all. It shows not connected at the bottom right. It also shows an incorrect balance but all my transactions show in the recent transaction window. It's like the wallet got hung up on an old block.
-
My Mac OSX wallet isn't syncing at all. It shows not connected at the bottom right. It also shows an incorrect balance but all my transactions show in the recent transaction window. It's like the wallet got hung up on an old block.
Same problem here. After everything going smoothly for the first couple of days it crashed and is now stuck on block 320 when the client tries to resync.
On a separate issue, and this has more to do with aesthetics, the interface seems to be fuzzy. This was the same with 0.4.9 although everything was crisp on 0.4.7. I'm on Mac OSX 10.9.4.
-
When I clicked the "transfer" link on the top, the transfer page is not showing.
-
..update on this:
On the My accounts I still see this:
Updating transaction history...
and below to the left (in the green bar):
Transaction scanning progress is -100%
the summary shows the transactions.
on every account page the correct balance shows in the excel style format below the Filter box but the balance above, in the colored area of the actual account, shows 0
-
..update on this:
On the My accounts I still see this:
Updating transaction history...
and below to the left (in the green bar):
Transaction scanning progress is -100%
the summary shows the transactions.
on every account page the correct balance shows in the excel style format below the Filter box but the balance above, in the colored area of the actual account, shows 0
..please inform if this issue is being fixed - I have no funds in balance - so can't do anything - the transfers are showing below but since they are not actually in the balance above I am w/o funds..
..am I the only one with this issue?
-
FYI
I managed to install the 0.4.10 gui version for my windows 7 32 bit
only when I have let it sync BEFORE I imported my backup json file !!!
PS It would be great to see the progress of syncing before we create or import an account!
-
PS It would be great to see the progress of syncing before we create or import an account!
It looks like the direction they are going is that it stays at the opening splash screen until it's done some work. I think this is a great idea, letting the client get itself all figured out before allowing user interaction :) .
-
BitShares X has not synced the correct account balance, transaction history, or the fact that my account is registered for the past few versions. When attempting to rescan the blockchain, it crashes during the process. I'm on Lubuntu. This latest install was in a brand new folder as I renamed the old folder "BitShares X.old". I did notice that there was also a hidden .BitSharesX folder that could be holding some old config files or something. Should I try renaming that folder as well?
-
BitShares X has not synced the correct account balance, transaction history, or the fact that my account is registered for the past few versions. When attempting to rescan the blockchain, it crashes during the process. I'm on Lubuntu. This latest install was in a brand new folder as I renamed the old folder "BitShares X.old". I did notice that there was also a hidden .BitSharesX folder that could be holding some old config files or something. Should I try renaming that folder as well?
The .BitSharesX hidden folder is where all the data is stored including all your wallet backups. Yes, rename it, but BACK IT UP somewhere as well.
-
Overlapping is very confusing on the bid/ask wall. Not sure how to trade now. It looks like are a lot of sell orders that are lower than buy bids. Confusing !!!
-
is this "overlapping" bids and asks a feature or just a new bug?
if it is a new feature please remove it - it is a terrible solution.
if it is a bug please remove it - it is a terrible bug.
:o
-
BitShares X has not synced the correct account balance, transaction history, or the fact that my account is registered for the past few versions. When attempting to rescan the blockchain, it crashes during the process. I'm on Lubuntu. This latest install was in a brand new folder as I renamed the old folder "BitShares X.old". I did notice that there was also a hidden .BitSharesX folder that could be holding some old config files or something. Should I try renaming that folder as well?
The .BitSharesX hidden folder is where all the data is stored including all your wallet backups. Yes, rename it, but BACK IT UP somewhere as well.
Still crashing when trying to scan the blockchain. It seems that the problematic block is 321978.
-
I'm getting impatient now.
any news on fixing the transaction scanning progress error?
I am very worried if my funds are gone - or they can be recovered
further info:
I have found out that I can import a backup json from before I created the 2 new accounts and that removes the transaction scanning progress -100% in lower left corner and the message Updating transaction history.
And I can also see the transactions I did from the main account to those 2 new accounts but obviously the transaction shows unknown accounts.
My question now is:
Can I import/recover those 2 new accounts into that backup file and thereby get the balances to show correctly?
-
It'd be worth a private key dump on the two new accounts and importing the private keys (cut and paste, not a wallet file) into your wallet you sent the funds from. You may not get all the transaction details but you should "recover" your shares after a rescan.
Since you know the blocks your sends are in you don't have to scan the entire chain.
-
yes thx Riverhead - I'm actually doing it now - it just takes forever to scan the transactions - currently @ 54%..
I will be very curious to see if it works :P
-
FYI I'm pleased to say that I have now recovered the balance on one of the accounts and working on the next one :)
-
I updated the seed node to version 0.4.10, so far so good, no more segfaults. There are currently 50 connections.
-
A behavior I noticed when using a chain server is that it says "Not connected" in the lower right, displays no other status message, but I can see my balance rising as it downloads/processes the chain. I can see why someone would think it's hung but it's actually working just fine.
I have noticed that too but when I have recently purchased BTSX from Bter and withdrew the BTSX to my new Bitshares X wallet, it will correctly update my BTSX balance in my account to reflect that I made a BTSX withdrawal from Bter to deposit in my wallet despite it saying "Not Connected" on the bottom of my wallet. That part seems to be working and I have not had any issues with that.
-
A behavior I noticed when using a chain server is that it says "Not connected" in the lower right, displays no other status message, but I can see my balance rising as it downloads/processes the chain. I can see why someone would think it's hung but it's actually working just fine.
I have noticed that too but when I have recently purchased BTSX from Bter and withdrew the BTSX to my new Bitshares X wallet, it will correctly update my BTSX balance in my account to reflect that I made a BTSX withdrawal from Bter to deposit in my wallet despite it saying "Not Connected" on the bottom of my wallet. That part seems to be working and I have not had any issues with that.
That is a bug in the wallet ... you can check your real-syncin status with "getinfo" in the console
-
:( I'm back to square 1 with the Transaction scanning progress is -100% issue - a full rescan does not help..
-
:( I'm back to square 1 with the Transaction scanning progress is -100% issue - a full rescan does not help..
Not sure if you've tried this yet, but it's worth a shot.
"wallet_set_transaction_scanning true" in the console. After that, run "rescan".
-
We are now on 4.12.... I am locking this thread.