Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: Segfault on regenerating keys, rescanning, and repairing wallet on 32bit linux  (Read 607 times)

0 Members and 1 Guest are viewing this topic.

Offline maqifrnswa

  • Hero Member
  • *****
  • Posts: 661
    • View Profile

EDIT!:: See posts below, debugging figured things out - it's a 32bit problem

I'm trying wallet_regenerate_keys on an account in a wallet, but it keeps crashing. Any hints? Redacted error below:

Code: [Select]
>>> wallet_regenerate_keys XXX 10500
Backing up wallet...
Wallet automatically backed up to: XXX-before_key_regeneration.json
This may take a while...
Regenerating wallet child keys and importing into account: XXX
10 assert_exception: Assert Exception
*account_name == account_record->name: That key already belongs to a local account with a different name!
    {"account_record":{"index":X,"id":X,"name":"[b]NOT THE NAME I'M REGENERATING[/b]","public_data":null,"owner_key":"XXX","active_key_history":[["XXX"]],"registration_date":"XXX","last_update":"XXX","delegate_info":null,"meta_data":{"type":"public_account","data":""},"is_my_account":true,"approved":0,"is_favorite":true,"block_production_enabled":false,"last_used_gen_sequence":0,"private_data":null},"account_name":"[b]THE NAME I'M REGENERATING[/b]"}
    th_a  wallet.cpp:1667 import_private_key

    {"account_name":"[b]THE NAME I'M REGENERATING[/b]","create_account":false}
    th_a  wallet.cpp:1689 import_private_key
10 assert_exception: Assert Exception
*account_name == blockchain_account_record->name: That key already belongs to a registered account with a different name!
    {"blockchain_account_record":{"id":X,"name":"[b]ANOTHER DIFFERENT NAME[/b]","public_data":{"version":"0.8.1","slate_id":X},"owner_key":"XXX","active_key_history":[["XXX"]],"registration_date":"X","last_update":"X","delegate_info":{"votes_for":XXX,"pay_rate":X,"signing_key_history":[[XXX],"last_block_num_produced":XXX,"next_secret_hash":"XXX","pay_balance":XXX,"total_paid":XXX,"total_burned":X,"blocks_produced":XXX,"blocks_missed":XXX},"meta_data":{"type":"titan_account","data":""}},"account_name":"[b]THE NAME I'M REGENERATING[/b]"}
    th_a  wallet.cpp:1631 import_private_key

    {"account_name":"[b]THE NAME I'M REGENERATING[/b]","create_account":false}
    th_a  wallet.cpp:1689 import_private_key
10 assert_exception: Assert Exception
*account_name == account_record->name: That key already belongs to a local account with a different name!
    {"account_record":{"index":X,"id":XX,"name":"[b]YET ANOTHER DIFFERENT NAME[/b]","public_data":{"gravatarID":""},"owner_key":"XXX","active_key_history":[["XXXX"]],"registration_date":"X","last_update":"X","delegate_info":null,"meta_data":{"type":"titan_account","data":""},"is_my_account":true,"approved":0,"is_favorite":true,"block_production_enabled":false,"last_used_gen_sequence":X,"private_data":null},"account_name":"[b]THE NAME I'M REGENERATING[/b]"}
    th_a  wallet.cpp:1667 import_private_key

    {"account_name":"[b]THE NAME I'M REGENERATING[/b]","create_account":false}
    th_a  wallet.cpp:1689 import_private_key
Segmentation fault (core dumped)
« Last Edit: April 29, 2015, 07:31:05 PM by maqifrnswa »
maintains an Ubuntu PPA: https://launchpad.net/~showard314/+archive/ubuntu/bitshares [15% delegate] wallet_account_set_approval maqifrnswa true [50% delegate] wallet_account_set_approval delegate1.maqifrnswa true

Offline vikram

Re: wallet_regenerate_keys in wallet with multiple accounts
« Reply #1 on: April 22, 2015, 09:47:25 PM »
I'm trying wallet_regenerate_keys on an account in a wallet, but it keeps crashing. Any hints? Redacted error below:

Code: [Select]
>>> wallet_regenerate_keys XXX 10500
Backing up wallet...
Wallet automatically backed up to: XXX-before_key_regeneration.json
This may take a while...
Regenerating wallet child keys and importing into account: XXX
10 assert_exception: Assert Exception
*account_name == account_record->name: That key already belongs to a local account with a different name!
    {"account_record":{"index":X,"id":X,"name":"[b]NOT THE NAME I'M REGENERATING[/b]","public_data":null,"owner_key":"XXX","active_key_history":[["XXX"]],"registration_date":"XXX","last_update":"XXX","delegate_info":null,"meta_data":{"type":"public_account","data":""},"is_my_account":true,"approved":0,"is_favorite":true,"block_production_enabled":false,"last_used_gen_sequence":0,"private_data":null},"account_name":"[b]THE NAME I'M REGENERATING[/b]"}
    th_a  wallet.cpp:1667 import_private_key

    {"account_name":"[b]THE NAME I'M REGENERATING[/b]","create_account":false}
    th_a  wallet.cpp:1689 import_private_key
10 assert_exception: Assert Exception
*account_name == blockchain_account_record->name: That key already belongs to a registered account with a different name!
    {"blockchain_account_record":{"id":X,"name":"[b]ANOTHER DIFFERENT NAME[/b]","public_data":{"version":"0.8.1","slate_id":X},"owner_key":"XXX","active_key_history":[["XXX"]],"registration_date":"X","last_update":"X","delegate_info":{"votes_for":XXX,"pay_rate":X,"signing_key_history":[[XXX],"last_block_num_produced":XXX,"next_secret_hash":"XXX","pay_balance":XXX,"total_paid":XXX,"total_burned":X,"blocks_produced":XXX,"blocks_missed":XXX},"meta_data":{"type":"titan_account","data":""}},"account_name":"[b]THE NAME I'M REGENERATING[/b]"}
    th_a  wallet.cpp:1631 import_private_key

    {"account_name":"[b]THE NAME I'M REGENERATING[/b]","create_account":false}
    th_a  wallet.cpp:1689 import_private_key
10 assert_exception: Assert Exception
*account_name == account_record->name: That key already belongs to a local account with a different name!
    {"account_record":{"index":X,"id":XX,"name":"[b]YET ANOTHER DIFFERENT NAME[/b]","public_data":{"gravatarID":""},"owner_key":"XXX","active_key_history":[["XXXX"]],"registration_date":"X","last_update":"X","delegate_info":null,"meta_data":{"type":"titan_account","data":""},"is_my_account":true,"approved":0,"is_favorite":true,"block_production_enabled":false,"last_used_gen_sequence":X,"private_data":null},"account_name":"[b]THE NAME I'M REGENERATING[/b]"}
    th_a  wallet.cpp:1667 import_private_key

    {"account_name":"[b]THE NAME I'M REGENERATING[/b]","create_account":false}
    th_a  wallet.cpp:1689 import_private_key
Segmentation fault (core dumped)

Can you run in a debugger and get a stack trace of the crash?

Offline maqifrnswa

  • Hero Member
  • *****
  • Posts: 661
    • View Profile
Re: wallet_regenerate_keys in wallet with multiple accounts
« Reply #2 on: April 24, 2015, 08:03:02 PM »
All with version 0.9.0. wallet_repair_records, rescan, and wallet_regenerate_keys all segfaults

wallet_repair_records segfault:

Code: [Select]
passphrase:
OK
(wallet closed) >>> wallet_repair_records
[...]
Backing up wallet...
Wallet automatically backed up to: /home/X/.BitShares/wallets/.backups/default/default-20150424T185523-before_record_repair.json
Repairing wallet records. This may take a while...
Repairing key record     10003
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb03fdb40 (LWP 6398)]
__memset_sse2_rep () at ../sysdeps/i386/i686/multiarch/memset-sse2-rep.S:242
242 ../sysdeps/i386/i686/multiarch/memset-sse2-rep.S: No such file or directory.

(gdb) bt

#0  __memset_sse2_rep ()
    at ../sysdeps/i386/i686/multiarch/memset-sse2-rep.S:242
#1  0x0921edc6 in boost::coroutines::detail::standard_stack_allocator::allocate(boost::coroutines::stack_context&, unsigned int) ()
#2  0x0863bf12 in context (t=0x1aeadbdc, alloc=...,
    sf=0x863c5b0 <fc::thread_d::start_process_tasks(int)>, this=0x6ddad08)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/context.hpp:72
#3  fc::thread_d::start_next_fiber (this=0xb5800688, reschedule=false)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/thread_d.hpp:430
#4  0x08634de1 in fc::thread::wait_until(fc::shared_ptr<fc::promise_base>&&, fc::time_point const&) (this=0x1aeadbdc,
    p=<unknown type in /usr/lib/debug/.build-id/49/20015d4def319244f1a7b8682de1ab47b1a0c5.debug, CU 0x10b5375, DIE 0x1133177>, timeout=...)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/thread.cpp:406
#5  0x0863d41a in fc::promise_base::_wait_until (this=0x6ddaccc,
    timeout_us=...)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/future.cpp:67
#6  0x0863d668 in fc::promise_base::_wait (this=0x6ddaccc, timeout_us=...)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/future.cpp:54
#7  0x086dc815 in wait (timeout=..., this=<optimized out>)
    at /build/buildd/bitshares-0.9.0/libraries/fc/include/fc/thread/future.hpp:152
#8  fc::asio::tcp::connect<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> >, boost::asio::ip::basic_endpoint<boost::asio::ip::tcp> > (sock=..., ep=...)
    at /build/buildd/bitshares-0.9.0/libraries/fc/include/fc/asio.hpp:246
#9  0x086fd208 in fc::tcp_socket::connect_to (this=0x6dd5864,
    remote_endpoint=...)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/network/tcp_socket.cpp:150
#10 0x08af76b5 in bts::net::stcp_socket::connect_to (this=0x6dd5810,
    remote_endpoint=...)
    at /build/buildd/bitshares-0.9.0/libraries/net/stcp_socket.cpp:51
#11 0x08b141d3 in bts::net::detail::message_oriented_connection_impl::connect_to (this=0x6dd5808, remote_endpoint=...)
    at /build/buildd/bitshares-0.9.0/libraries/net/message_oriented_connection.cpp:106
#12 0x08b1438f in bts::net::message_oriented_connection::connect_to (
    this=<optimized out>, remote_endpoint=...)
    at /build/buildd/bitshares-0.9.0/libraries/net/message_oriented_connection.cpp:336
#13 0x08b0c5d9 in bts::net::peer_connection::connect_to (this=0x6dd5310,
    remote_endpoint=..., local_endpoint=...)
    at /build/buildd/bitshares-0.9.0/libraries/net/peer_connection.cpp:225
#14 0x08a87cd2 in bts::net::detail::node_impl::connect_to_task (
    this=0x21c362c0, new_peer=std::shared_ptr (count 3, weak 2) 0x6dd5310,
    remote_endpoint=...)
    at /build/buildd/bitshares-0.9.0/libraries/net/node.cpp:3952
#15 0x08a89010 in operator() (__closure=0x6dd5c4c)
    at /build/buildd/bitshares-0.9.0/libraries/net/node.cpp:4273
#16 fc::detail::void_functor_run<bts::net::detail::node_impl::initiate_connect_to(const peer_connection_ptr&)::<lambda()> >::run(void *, void *) (
    functor=0x6dd5c4c, prom=0x6dd5c48)
    at /build/buildd/bitshares-0.9.0/libraries/fc/include/fc/thread/task.hpp:83
#17 0x0863dd98 in fc::task_base::run_impl (this=0x6dd5c58)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/task.cpp:43
#18 0x0863e335 in fc::task_base::run (this=0x6dd5c58)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/task.cpp:32
#19 0x0863c23a in run_next_task (this=0xb5800688)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/thread_d.hpp:498
#20 fc::thread_d::process_tasks (this=<optimized out>)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/thread_d.hpp:547
#21 0x0863c5cd in fc::thread_d::start_process_tasks (my=-1249900920)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/thread_d.hpp:475
#22 0x0921c465 in make_fcontext ()

Also, I tried wallet_regenerate_keys, and it looks the same
Code: [Select]
Backing up wallet...
Wallet automatically backed up to: /home/X/.BitShares/wallets/.backups/default/default-20150424T193017-before_key_regeneration.json
This may take a while...
Regenerating wallet child keys and importing into account: X
Regenerating type 1 account child keys for account: X
Regenerating type 2 account owner child keys for account: X
wallet_name: default
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb03fdb40 (LWP 6682)]
__memset_sse2_rep () at ../sysdeps/i386/i686/multiarch/memset-sse2-rep.S:242
242 ../sysdeps/i386/i686/multiarch/memset-sse2-rep.S: No such file or directory.
(gdb) bt
#0  __memset_sse2_rep () at ../sysdeps/i386/i686/multiarch/memset-sse2-rep.S:242
#1  0x0921edc6 in boost::coroutines::detail::standard_stack_allocator::allocate(boost::coroutines::stack_context&, unsigned int) ()
#2  0x0863bf12 in context (t=0x21a2dc74, alloc=...,
    sf=0x863c5b0 <fc::thread_d::start_process_tasks(int)>, this=0x61c2b90)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/context.hpp:72
#3  fc::thread_d::start_next_fiber (this=0xb5800688, reschedule=false)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/thread_d.hpp:430
#4  0x08634de1 in fc::thread::wait_until(fc::shared_ptr<fc::promise_base>&&, fc::time_point const&) (
    this=0x21a2dc74,
    p=<unknown type in /usr/lib/debug/.build-id/49/20015d4def319244f1a7b8682de1ab47b1a0c5.debug, CU 0x10b5375, DIE 0x1133177>, timeout=...)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/thread.cpp:406
#5  0x0863d41a in fc::promise_base::_wait_until (this=0x368c554c, timeout_us=...)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/future.cpp:67
#6  0x0863d668 in fc::promise_base::_wait (this=0x368c554c, timeout_us=...)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/future.cpp:54
#7  0x091db9c4 in wait (timeout=..., this=<optimized out>)
    at /build/buildd/bitshares-0.9.0/libraries/fc/include/fc/thread/future.hpp:152
#8  fc::detail::rate_limiting_group_impl::process_pending_reads (this=0x21b46b48)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/network/rate_limiting.cpp:374
#9  0x091df08e in operator() (__closure=0xafa67b6c)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/network/rate_limiting.cpp:293
#10 fc::detail::void_functor_run<unsigned int fc::detail::rate_limiting_group_impl::readsome_impl<std::shared_ptr<char> >(boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> >&, std::shared_ptr<char> const&, unsigned int, unsigned int)::{lambda()#1}>::run(void*, fc::detail::void_functor_run<unsigned int fc::detail::rate_limiting_group_impl::readsome_impl<std::shared_ptr<char> >(boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> >&, std::shared_ptr<char> const&, unsigned int, unsigned int)::{lambda()#1}>) (functor=0xafa67b6c, prom=0xafa67b68)
    at /build/buildd/bitshares-0.9.0/libraries/fc/include/fc/thread/task.hpp:83
#11 0x0863dd98 in fc::task_base::run_impl (this=0xafa67b74)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/task.cpp:43
#12 0x0863e335 in fc::task_base::run (this=0xafa67b74)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/task.cpp:32
#13 0x0863c23a in run_next_task (this=0xb5800688)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/thread_d.hpp:498
#14 fc::thread_d::process_tasks (this=<optimized out>)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/thread_d.hpp:547
#15 0x0863c5cd in fc::thread_d::start_process_tasks (my=-1249900920)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/thread_d.hpp:475
#16 0x0921c465 in make_fcontext ()

maintains an Ubuntu PPA: https://launchpad.net/~showard314/+archive/ubuntu/bitshares [15% delegate] wallet_account_set_approval maqifrnswa true [50% delegate] wallet_account_set_approval delegate1.maqifrnswa true

Offline maqifrnswa

  • Hero Member
  • *****
  • Posts: 661
    • View Profile
Re: wallet_regenerate_keys in wallet with multiple accounts
« Reply #3 on: April 26, 2015, 12:35:30 AM »
Just clicking on the moonfund asset in the GUI (0.9.0) segfaults, similar bt

Code: [Select]
#0  __memset_sse2_rep ()
    at ../sysdeps/i386/i686/multiarch/memset-sse2-rep.S:242
#1  0x0924aa06 in boost::coroutines::detail::standard_stack_allocator::allocate(boost::coroutines::stack_context&, unsigned int) ()
#2  0x08d656c2 in context (t=0x87d3d1fc, alloc=...,
    sf=0x8d65d60 <fc::thread_d::start_process_tasks(int)>, this=0x79e06d8)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/context.hpp:72
#3  fc::thread_d::start_next_fiber (this=0xac903ad0, reschedule=false)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/thread_d.hpp:430
#4  0x08d5e721 in fc::thread::wait_until(fc::shared_ptr<fc::promise_base>&&, fc::time_point const&) (this=0x87d3d1fc,
    p=<unknown type in /usr/lib/debug/.build-id/65/7d18b654a50abea029d99a66126d3bde78a16f.debug, CU 0x70646c2, DIE 0x70e24c4>, timeout=...)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/thread.cpp:406
#5  0x08d66bca in fc::promise_base::_wait_until (this=0x79e068c,
    timeout_us=...)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/future.cpp:67
#6  0x08d66e18 in fc::promise_base::_wait (this=0x79e068c, timeout_us=...)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/future.cpp:54
#7  0x08e0c099 in wait (timeout=..., this=<optimized out>)
    at /build/buildd/bitshares-0.9.0/libraries/fc/include/fc/thread/future.hpp:152
#8  fc::asio::tcp::connect<boost::asio::basic_stream_socket<boost::asio::ip::tcp
, boost::asio::stream_socket_service<boost::asio::ip::tcp> >, boost::asio::ip::basic_endpoint<boost::asio::ip::tcp> > (sock=..., ep=...)
    at /build/buildd/bitshares-0.9.0/libraries/fc/include/fc/asio.hpp:246
#9  0x08e05748 in fc::tcp_socket::connect_to (this=0x79dced4,
    remote_endpoint=...)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/network/tcp_socket.cpp:150
#10 0x08ca2385 in bts::net::stcp_socket::connect_to (this=0x79dce80,
    remote_endpoint=...)
    at /build/buildd/bitshares-0.9.0/libraries/net/stcp_socket.cpp:51
#11 0x0919e6e3 in bts::net::detail::message_oriented_connection_impl::connect_to (this=0x79dce78, remote_endpoint=...)
    at /build/buildd/bitshares-0.9.0/libraries/net/message_oriented_connection.cpp:106
#12 0x0919e89f in bts::net::message_oriented_connection::connect_to (
    this=<optimized out>, remote_endpoint=...)
    at /build/buildd/bitshares-0.9.0/libraries/net/message_oriented_connection.cpp:336
#13 0x09199d79 in bts::net::peer_connection::connect_to (this=0x79dc980,
    remote_endpoint=..., local_endpoint=...)
    at /build/buildd/bitshares-0.9.0/libraries/net/peer_connection.cpp:225
#14 0x09119ce2 in bts::net::detail::node_impl::connect_to_task (
    this=0x855d9200, new_peer=std::shared_ptr (count 3, weak 2) 0x79dc980,
#15 0x0911b020 in operator() (__closure=0x79dd2bc)
    at /build/buildd/bitshares-0.9.0/libraries/net/node.cpp:4273
#16 fc::detail::void_functor_run<bts::net::detail::node_impl::initiate_connect_to(const peer_connection_ptr&)::<lambda()> >::run(void *, void *) (
    functor=0x79dd2bc, prom=0x79dd2b8)
    at /build/buildd/bitshares-0.9.0/libraries/fc/include/fc/thread/task.hpp:83
#17 0x08d67548 in fc::task_base::run_impl (this=0x79dd2c8)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/task.cpp:43
#18 0x08d67ae5 in fc::task_base::run (this=0x79dd2c8)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/task.cpp:32
#19 0x08d659ea in run_next_task (this=0xac903ad0)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/thread_d.hpp:498
#20 fc::thread_d::process_tasks (this=<optimized out>)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/thread_d.hpp:547
#21 0x08d65d7d in fc::thread_d::start_process_tasks (my=-1399833904)
    at /build/buildd/bitshares-0.9.0/libraries/fc/src/thread/thread_d.hpp:475
#22 0x092480a5 in make_fcontext ()
maintains an Ubuntu PPA: https://launchpad.net/~showard314/+archive/ubuntu/bitshares [15% delegate] wallet_account_set_approval maqifrnswa true [50% delegate] wallet_account_set_approval delegate1.maqifrnswa true

Offline vikram

Re: wallet_regenerate_keys in wallet with multiple accounts
« Reply #4 on: April 27, 2015, 05:26:16 PM »
Did you build this version yourself? Does anything different happen if you build in Release or Debug mode instead of the current mode? Is it possible for you to test if the same thing happens on another machine?

Offline maqifrnswa

  • Hero Member
  • *****
  • Posts: 661
    • View Profile
Re: wallet_regenerate_keys in wallet with multiple accounts
« Reply #5 on: April 27, 2015, 07:29:44 PM »
I built it myself. I tried none, Release, RelWithDebug, and Debug - they all crash. I've tried it on other machines and it doesn't crash (just one does). I'm trying to now to create a new wallet then importing my private keys and rescanning to see if something is corrupt there.

EDIT: It looks like the wallet is bad, a made a new wallet, reimported keys and rescanned - it seems to be fine now. The wallet is a somewhat complicated wallet that has been around since pre-release of bitsharesx.
« Last Edit: April 28, 2015, 01:59:39 AM by maqifrnswa »
maintains an Ubuntu PPA: https://launchpad.net/~showard314/+archive/ubuntu/bitshares [15% delegate] wallet_account_set_approval maqifrnswa true [50% delegate] wallet_account_set_approval delegate1.maqifrnswa true

Offline maqifrnswa

  • Hero Member
  • *****
  • Posts: 661
    • View Profile
Re: wallet_regenerate_keys in wallet with multiple accounts
« Reply #6 on: April 28, 2015, 03:48:13 AM »
Here's an update:

1) Created a new wallet
2) imported 4 private keys: three TITAN and one non-TITAN
3) imported a bitcoin wallet to one of the TITAN keys
4) rescan blockchain (worked fine)
5) Checking balance, the TITAN balances are good, but the non-TITAN account is not.
6) checking wallet_account_transaction history for the non-TITAN account: only the account registration shows up, no other transactions
7) repair wallet (worked fine)
8) regenerate 10500 keys for the non-TITAN account <-- SEGFAULTS
9) backtrace is the same as before

is something up with the non-TITAN account, perhaps?
I can try a wallet with just the non-TITAN account
« Last Edit: April 28, 2015, 03:50:18 AM by maqifrnswa »
maintains an Ubuntu PPA: https://launchpad.net/~showard314/+archive/ubuntu/bitshares [15% delegate] wallet_account_set_approval maqifrnswa true [50% delegate] wallet_account_set_approval delegate1.maqifrnswa true

Offline abit

Re: wallet_regenerate_keys in wallet with multiple accounts
« Reply #7 on: April 28, 2015, 09:08:03 AM »
Here's an update:

1) Created a new wallet
2) imported 4 private keys: three TITAN and one non-TITAN
3) imported a bitcoin wallet to one of the TITAN keys
4) rescan blockchain (worked fine)
5) Checking balance, the TITAN balances are good, but the non-TITAN account is not.
6) checking wallet_account_transaction history for the non-TITAN account: only the account registration shows up, no other transactions
7) repair wallet (worked fine)
8) regenerate 10500 keys for the non-TITAN account <-- SEGFAULTS
9) backtrace is the same as before

is something up with the non-TITAN account, perhaps?
I can try a wallet with just the non-TITAN account
I believe that it's no need to regenerate keys for non-TITAN account..
We'd better disable it.
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline maqifrnswa

  • Hero Member
  • *****
  • Posts: 661
    • View Profile
Re: wallet_regenerate_keys in wallet with multiple accounts
« Reply #8 on: April 28, 2015, 03:39:55 PM »
I believe that it's no need to regenerate keys for non-TITAN account..
We'd better disable it.

that's what I thought, but it works for some with non-TITAN:
https://bitsharestalk.org/index.php/topic,15911.msg0.html#new
(they're using the GUI, so I assume they created the account in the GUI which defaults to public_account)

I'm spinning up some DO servers and will try a bunch of combinations of importing accounts and rescanning, see if it is something weird with my configuration here. I don't know why I can't see any transactions if I rescan after importing a public_account.
maintains an Ubuntu PPA: https://launchpad.net/~showard314/+archive/ubuntu/bitshares [15% delegate] wallet_account_set_approval maqifrnswa true [50% delegate] wallet_account_set_approval delegate1.maqifrnswa true

Offline maqifrnswa

  • Hero Member
  • *****
  • Posts: 661
    • View Profile
Re: wallet_regenerate_keys in wallet with multiple accounts
« Reply #9 on: April 28, 2015, 07:32:24 PM »
1) Created a new DO machine
2) synced blockchain
3) imported non-TITAN account and rescan. Doesn't see any transactions
4) regenerated keys for the non-TITAN account and rescanned. It found all the transactions!
5) imported 3 TITAN accounts and 1 bitcoin wallet attached to the titan account and rescanned. Success!

Looks like something is screwed up on my machine. I'll back everything up, create a new .BitShares folder and wallet, and import everything to see if that fixes things.
maintains an Ubuntu PPA: https://launchpad.net/~showard314/+archive/ubuntu/bitshares [15% delegate] wallet_account_set_approval maqifrnswa true [50% delegate] wallet_account_set_approval delegate1.maqifrnswa true

Offline maqifrnswa

  • Hero Member
  • *****
  • Posts: 661
    • View Profile
I figured it out!

BitShares segfaults on 32bit machines on several operations in both the GUI and CLI.

I have tested it on i386 (32 bit) on several DO droplets with different linux distributions, and it is repeatable. 64-bit is stable throughout the operations, just 32 bit machines will crash.

CLI will segfault when you:
1) import a non-TITAN private key (EDIT: TITAN keys also will cause segfaults on 32 bit machines)
2) regen keys OR rescan OR repair wallet

GUI segfaults on several operations, hard to reproduce but will commonly crash when inverting UIA markets.
« Last Edit: April 30, 2015, 03:11:19 AM by maqifrnswa »
maintains an Ubuntu PPA: https://launchpad.net/~showard314/+archive/ubuntu/bitshares [15% delegate] wallet_account_set_approval maqifrnswa true [50% delegate] wallet_account_set_approval delegate1.maqifrnswa true

 

Google+