All users, please upgrade your client version to 0.4.5

[DACSunlimited]

0.4.6 is out, please upgrade to 0.4.6 instead.

[svk]

My delegate CLI crashed.  Missed three blocks.

What can I provide log file was to determine why?

From syslog

Code: [Select]

Aug 21 23:18:30 riverhead-del-server kernel: [110780.687870] bitshares_clien[6724]: segfault at 238 ip 000000000066cec6 sp 00007f58a4222a00 error 4 in bitshares_client[400000+1238000]


Same thing just happened to me, lost three blocks as well. Relaunched now with gdb, but hope it doesn't happen again cause I can't sit around monitoring it all day today!

I recommend setting your maximum connection count to 8 to reduce the likelihood of that happening.  Also if you compile from github DAC Sun Limited has a potential fix.

Thanks for the tip.

Still compiling but had another crash like 20 seconds before my next block production slot, so missed another one there. Had set the max connections to 125 and desired to 75 but guess that was still too high. Should have the latest version compiled by my next slot.

[bytemaster]

My delegate CLI crashed.  Missed three blocks.

What can I provide log file was to determine why?

From syslog

Code: [Select]

Aug 21 23:18:30 riverhead-del-server kernel: [110780.687870] bitshares_clien[6724]: segfault at 238 ip 000000000066cec6 sp 00007f58a4222a00 error 4 in bitshares_client[400000+1238000]


Same thing just happened to me, lost three blocks as well. Relaunched now with gdb, but hope it doesn't happen again cause I can't sit around monitoring it all day today!

I recommend setting your maximum connection count to 8 to reduce the likelihood of that happening.  Also if you compile from github DAC Sun Limited has a potential fix.

[svk]

My delegate CLI crashed.  Missed three blocks.

What can I provide log file was to determine why?

From syslog

Code: [Select]

Aug 21 23:18:30 riverhead-del-server kernel: [110780.687870] bitshares_clien[6724]: segfault at 238 ip 000000000066cec6 sp 00007f58a4222a00 error 4 in bitshares_client[400000+1238000]


Same thing just happened to me, lost three blocks as well. Relaunched now with gdb, but hope it doesn't happen again cause I can't sit around monitoring it all day today!

[DACSunlimited]

Hi, delegates who have experienced crash problem, can try to checkout the latest code from master branch of  https://github.com/dacsunlimited/bitsharesx

We merge some fix, hopefully, these crash issue have already been fixed.

[Riverhead]

You can email it to sales at syncad.com. There should be no private data in the logs. We're mostly interested in the p2p log.

Thanks. They have been posted as a bug on git hub: https://github.com/BitShares/bitshares_toolkit/issues/649

[dxtr]

Anyone else seeing this message? Is this bad? 

Code: [Select]

nobledelegate (unlocked) >>> get_info
6 key_not_found_exception: Key Not Found
unable to find key 0
    {"key":0}
    th_a  level_map.hpp:91 fetch
error fetching key 0
    {"key":0}
    th_a  level_map.hpp:101 fetch

    {"block_num":0}
    th_a  chain_database.cpp:1256 get_block_id

    {"block_num":0}
    th_a  chain_database.cpp:1241 get_block_header

    {}
    th_a  common_api_client.cpp:1859 get_info

    {"command":"get_info"}
    th_a  cli.cpp:471 execute_command
nobledelegate (unlocked) >>>


I have filed a bug report on this. https://github.com/BitShares/bitshares_toolkit/issues/669   

Probably harmless... let me know if you are able to sync

Turns out I am producing blocks. Which I assume means I'm in sync? Message doesn't go away though.


Sent from my iPhone using Tapatalk

Try this commands (I'm not sure if running this is healthy while producing blocks):

Code: [Select]

wallet_set_transaction_scanning true
wallet_rescan_blockchain

[dannotestein]

It's running in gdb now. Do I just wait for a crash?

The backtrace will be useful, but probably the most useful thing will be the logs around the time of the crash.

I have my logs directory tar.gz'd. Is there an email I can send them to? Also, is there anything in there I shouldn't be sending? I'm assuming by this point the logs are scrubbed of private data but want to be sure.

You can email it to sales at syncad.com. There should be no private data in the logs. We're mostly interested in the p2p log.

[bdnoble]

Anyone else seeing this message? Is this bad? 

Code: [Select]

nobledelegate (unlocked) >>> get_info
6 key_not_found_exception: Key Not Found
unable to find key 0
    {"key":0}
    th_a  level_map.hpp:91 fetch
error fetching key 0
    {"key":0}
    th_a  level_map.hpp:101 fetch

    {"block_num":0}
    th_a  chain_database.cpp:1256 get_block_id

    {"block_num":0}
    th_a  chain_database.cpp:1241 get_block_header

    {}
    th_a  common_api_client.cpp:1859 get_info

    {"command":"get_info"}
    th_a  cli.cpp:471 execute_command
nobledelegate (unlocked) >>>


I have filed a bug report on this. https://github.com/BitShares/bitshares_toolkit/issues/669   

Probably harmless... let me know if you are able to sync

Turns out I am producing blocks. Which I assume means I'm in sync? Message doesn't go away though.


Sent from my iPhone using Tapatalk

[bytemaster]

Anyone else seeing this message? Is this bad? 

Code: [Select]

nobledelegate (unlocked) >>> get_info
6 key_not_found_exception: Key Not Found
unable to find key 0
    {"key":0}
    th_a  level_map.hpp:91 fetch
error fetching key 0
    {"key":0}
    th_a  level_map.hpp:101 fetch

    {"block_num":0}
    th_a  chain_database.cpp:1256 get_block_id

    {"block_num":0}
    th_a  chain_database.cpp:1241 get_block_header

    {}
    th_a  common_api_client.cpp:1859 get_info

    {"command":"get_info"}
    th_a  cli.cpp:471 execute_command
nobledelegate (unlocked) >>>


I have filed a bug report on this. https://github.com/BitShares/bitshares_toolkit/issues/669   

Probably harmless... let me know if you are able to sync

[dxtr]

Yes, I was seeing this message too - it's probably related to what BM has said recently.
Don't worry - it will go away, once you sync just a little of blockchain.

[bdnoble]

Anyone else seeing this message? Is this bad? 

Code: [Select]

nobledelegate (unlocked) >>> get_info
6 key_not_found_exception: Key Not Found
unable to find key 0
    {"key":0}
    th_a  level_map.hpp:91 fetch
error fetching key 0
    {"key":0}
    th_a  level_map.hpp:101 fetch

    {"block_num":0}
    th_a  chain_database.cpp:1256 get_block_id

    {"block_num":0}
    th_a  chain_database.cpp:1241 get_block_header

    {}
    th_a  common_api_client.cpp:1859 get_info

    {"command":"get_info"}
    th_a  cli.cpp:471 execute_command
nobledelegate (unlocked) >>>


[GaltReport]

So far so good as far as crashes or missed blocks go.  No crashes or missed blocks.  I do see the disconnect messages though.  Actually, just one:

"I am disconnecting peer 78.46.32.25:1776 for reason: You offered us a block that we reject as invalid"

I continue to see large spikes in cpu and network traffic in and out during wee hours of the morning east coast time.  FYI for those who may have lower performance delegates.

[bytemaster]

*.charity and *.xeroc are up to date and seeing some disconnects from users because of invalid blocks (see above)

besides that .. stable for the last few hours! nice work!

I am also seeing disconnects from users because of invalid blocks, looking into it that is caused by a change I made in an attempt to prevent users from downloading forks...

It is actually happening quite a bit and is probably the reason people are having a hard time syncing. 

[xeroc]

*.charity and *.xeroc are up to date and seeing some disconnects from users because of invalid blocks (see above)

besides that .. stable for the last few hours! nice work!