BitShares Forum

Main => General Discussion => Topic started by: emski on September 28, 2014, 05:14:40 pm

Title: 0.4.18 Issues
Post by: emski on September 28, 2014, 05:14:40 pm
0.4.18 "froze". The process was still running but there was no output and apparently the client wasn't signing blocks.

Code: [Select]
debug_list_errors_brief
[[
    "20140921T073236.695498",
    "block is older than our undo history allows us to process"
  ],[
    "20140921T073239.606532",
    "block is older than our undo history allows us to process"
  ],[
    "20140921T074040.440579",
    "block is older than our undo history allows us to process"
  ],[
    "20140921T075005.683440",
    "block is older than our undo history allows us to process"
  ],[
    "20140921T075110.221327",
    "block is older than our undo history allows us to process"
  ],[
    "20140921T075110.732240",
    "block is older than our undo history allows us to process"
  ],[
    "20140921T204747.803572",
    "block is older than our undo history allows us to process"
  ],[
    "20140925T053612.521647",
    "block is older than our undo history allows us to process"
  ],[
    "20140925T054027.605496",
    "block is older than our undo history allows us to process"
  ],[
    "20140928T150744.609798",
    "block is older than our undo history allows us to process"
  ],[
    "20140928T150745.356679",
    "block is older than our undo history allows us to process"
  ],[
    "20140928T151129.256737",
    "block is older than our undo history allows us to process"
  ],[
    "20140928T153826.816657",
    "block is older than our undo history allows us to process"
  ],[
    "20140928T153826.985026",
    "block is older than our undo history allows us to process"
  ],[
    "20140928T170955.557677",
    "block is older than our undo history allows us to process"
  ]
]


I haven't done anything differently during this update and I haven't seen this before.

As the process was still running the watchdog script was unable to determine if there is something wrong with it. Perhaps I'll have to run another client and make the watchdog check if each delegate is signing blocks properly.


Title: Re: 0.4.18 Issues
Post by: tonyk on September 30, 2014, 05:06:29 pm
More rarely but the same issue as 0.4.17 in 0.4.18

Code: [Select]
>> get_info

{
  "blockchain_head_block_num": 621865,
  "blockchain_head_block_age": "32 minutes old",
  "blockchain_head_block_timestamp": "2014-09-30T16:31:50",
  "blockchain_average_delegate_participation": "34.71 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_delegate_pay_rate": "2.57903 BTSX",
  "blockchain_share_supply": "1,999,981,705.46931 BTSX",
  "blockchain_blocks_left_in_round": 93,
  "blockchain_next_round_time": "at least 15 minutes in the future",
  "blockchain_next_round_timestamp": "2014-09-30T17:19:00",
  "blockchain_random_seed": "19a2d7b82fe07b96f31fbef97022e72032983aa9",
  "client_data_dir": "C:/Users/Toni/AppData/Roaming/BITSHA~1",
  "client_version": "v0.4.18-RC1",
  "network_num_connections": 14,
  "network_num_connections_max": 200,
  "ntp_time": "2014-09-30T17:03:39",
  "ntp_time_error": 3.2023950000000001,

win 7/32 bit
after running the client for about 2h, I believe.
Title: Re: 0.4.18 Issues
Post by: Method-X on September 30, 2014, 06:15:23 pm
Code: [Select]
>> debug_list_errors_brief

[[
    "20140905T201735.976152",
    "expired transaction"
  ],[
    "20140905T201736.015769",
    "expired transaction"
  ],[
    "20140905T201854.181940",
    "expired transaction"
  ],[
    "20140905T201945.991089",
    "expired transaction"
  ],[
    "20140905T201946.030876",
    "expired transaction"
  ],[
    "20140905T202104.007327",
    "expired transaction"
  ],[
    "20140905T202156.007488",
    "expired transaction"
  ],[
    "20140905T202156.046381",
    "expired transaction"
  ],[
    "20140905T202314.381295",
    "expired transaction"
  ],[
    "20140905T202406.298287",
    "expired transaction"
  ],[
    "20140905T202406.335773",
    "expired transaction"
  ],[
    "20140905T202524.327326",
    "expired transaction"
  ],[
    "20140905T202616.041507",
    "expired transaction"
  ],[
    "20140905T202616.082193",
    "expired transaction"
  ],[
    "20140905T202734.157556",
    "expired transaction"
  ],[
    "20140905T202826.051528",
    "expired transaction"
  ],[
    "20140905T202826.090029",
    "expired transaction"
  ],[
    "20140905T202944.222476",
    "expired transaction"
  ],[
    "20140905T203036.136694",
    "expired transaction"
  ],[
    "20140905T203036.175703",
    "expired transaction"
  ]
]
Title: Re: 0.4.18 Issues
Post by: theoretical on September 30, 2014, 11:17:12 pm

BitUSD : BTSX market is showing "Assert Exception" in a big red box at the top.  How can I get more information?
Title: Re: 0.4.18 Issues
Post by: xeroc on October 01, 2014, 06:52:15 am

BitUSD : BTSX market is showing "Assert Exception" in a big red box at the top.  How can I get more information?

blockchain_market_status USD BTSX