i sent funds to myself. found the transaction in block 1462 but I did not receive the funds in my account. my wallet showed the transaction previously. i cleared the pending transactions and that transaction disappeared but the funds were not in my account. what does this mean?

If you have any enabled delegate accounts, try using the 'wallet_delegate_enable_transaction_scanning true' command and then rescan that block. Let us know if this does not fix the problem.

1) Press for the simulation/testing phase. 2) Gameify the simulation/testing phase. 3) Exploits found go ASAP 1 again.

Maybe my intellect is just too limited, but I don't see any other way to figure this stuff out than by being experimental. It is like when you sit inside too long and you go outside and become astonished at how detailed everything is.

Quote from: bytemaster on July 01, 2014, 01:58:52 pm

Quote from: alt on July 01, 2014, 01:24:24 pm

So many blocks are missed by my account...

Very curious...   we will get some enhanced diagnostics on when you produce blocks (or didn't produce blocks) and try to find out what is going on here.

from default.log, I see delegate_loop never call after  time  20140701T052959.
this is why I missed all block.

Code: [Select]

20140701T052801.000417       th_a        delegate_loop ] Starting delegate loop at time: 20140701T052801                        client.cpp:627
20140701T052801.000513       th_a        delegate_loop ] Producing block at time: 20140701T061600                       client.cpp:630
20140701T052801.000566       th_a        delegate_loop ] Rescheduling delegate loop for time: 20140701T053000                   client.cpp:671
20140701T052959.000467       th_a        delegate_loop ] Starting delegate loop at time: 20140701T052959                        client.cpp:627
20140701T052959.000592       th_a        delegate_loop ] Producing block at time: 20140701T061600                       client.cpp:630
20140701T052959.000647       th_a        delegate_loop ] Rescheduling delegate loop for time: 20140701T053000                   client.cpp:671
20140701T053001.820272       th_a       handle_message ] CLIENT: just received block 0dc06149e6ffa59c9ce9d7545f66e9f134d88ce4                   client.cpp:884
20140701T053001.820488       th_a         on_new_block ] Received a new block from the p2p network, current head block is 2287, new block is {"previous":"294eb907b484ab
f5a97050ace2dd2341b411ba32","block_num":2288,"fee_rate":1000,"delegate_pay_rate":944695,"timestamp":"20140701T053000","transaction_digest":"c8cf12fe3180ed901a58a0697a52
2f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"fa5d0d638414feea623b92b19b54cb6b37ae244f","previous_secret":"de3023f9cec81e87207ae298f3c07053dd1e1e24","delega
te_signature":"1f6a741172f533a9dfe139195657585c475c843990b3ee59b4d876f85c8c2bee66dc379a53dd34483b74e2c78486b0745a6ceb3cc2d13480117ca26c8726c77f89","user_transactions":[
]}, current head block is 2287                  client.cpp:794
20140701T053001.820977       th_a      store_and_index ]            we already know about its previous: 294eb907b484abf5a97050ace2dd2341b411ba32                       
chain_database.cpp:399
20140701T053001.824635       th_a   apply_transactions ] Applying transactions from block: 2288                 chain_database.cpp:493
20140701T053001.883146       th_a         on_new_block ] After push_block, current head block is 2288                   client.cpp:810
20140701T053424.244715       th_a       handle_message ] CLIENT: just received transaction 9b23ba837f9d6379be5dc9b4d19b2094f209977f                     client.cpp:892


I think I fixed the probem: https://github.com/BitShares/bitshares_toolkit/commit/a58370d6c7d3e2991c8544c4910ad466c9acd4f5

Let us know if it happens again.

client crashed while opening wallet


(wallet closed) >>> connect: Operation now in progress
open momkey

Program received signal SIGSEGV, Segmentation fault.
_int_malloc (av=0x7ffff697e760 <main_arena>, bytes=39) at malloc.c:3302
3302    malloc.c: No such file or directory.
(gdb)

People seem to be getting segfaults once in a while, but it seems to be fixed upon wiping the data directory. Make sure you are on the latest code otherwise you could give that a shot: https://bitsharestalk.org/index.php?topic=5303.msg71563#msg71563

Ghmm, I'm constatntly getting segfault with latest git master

Can you make an issue on GitHub about it?

Code: [Select]

liondani (unlocked) >>> blockchain_get_delegate_block_stats liondani
[[
    912,{
      "missed": false,
      "latency": 1
    }
  ],[
    977,{
      "missed": false,
      "latency": 1
    }
  ],[
    1044,{
      "missed": false,
      "latency": 1
    }
  ],[
    1112,{
      "missed": false,
      "latency": 1
    }
  ],[
    1163,{
      "missed": true,
      "latency": null
    }
  ],[
    1165,{
      "missed": true,
      "latency": null
    }
  ],[
    1223,{
      "missed": true,
      "latency": null
    }
  ]
]


what means:  "latency": null     

You are running an old version of the code.

Code: [Select]

"block_production_enabled": true,

Code: [Select]

  "wallet_open": true,
  "wallet_unlocked_until": "20170827T033301",


Code: [Select]

wallet (unlocked) >>> blockchain_list_delegates 54 55
ID   NAME                          APPROVAL            BLOCKS PRODUCED BLOCKS MISSED   
---------------------------------------------------------
390  dele-puppy                    0.0002794781 %      0               1               
wallet (unlocked) >>>

delegate loop is not listed in default.log at all.

Can you give the full output of 'get_info'?

Quote from: wackou on June 26, 2014, 09:16:20 am

Quote from: vlight on June 26, 2014, 09:09:48 am

Code: [Select]

322  light                         0.0000000000 %      0               0Still 0% approval 

voted for you, you should be in the active delegates list next block

Thanks, i'm in the Top 

Also, my wallet keeps spamming these more and more:

Code: [Select]

active delegates: 1
active delegates: 1
active delegates: 1
active delegates: 1
active delegates: 1
active delegates: 1
active delegates: 1
active delegates: 1
active delegates: 1
active delegates: 1
active delegates: 1
active delegates: 1

Make sure you are running the latest code.