CB Response: Errors such as - ERROR: index "pg_statistic_relid_att_inh_index" contains corrupted page at block 0 - being observed in console when starting the CB-pssql process
search cancel

CB Response: Errors such as - ERROR: index "pg_statistic_relid_att_inh_index" contains corrupted page at block 0 - being observed in console when starting the CB-pssql process

book

Article ID: 290153

calendar_today

Updated On:

Products

Carbon Black EDR (formerly Cb Response)

Issue/Introduction

Errors such as:

2019-02-04 09:21:03 GMT [job_runner_alliance_community_participation(8363) @ ::1(60000)] ERROR: index "pg_statistic_relid_att_inh_index" contains corrupted page at block 0 
2019-02-04 09:21:03 GMT [job_runner_alliance_community_participation(8363) @ ::1(60000)] HINT: Please REINDEX it. 
2019-02-04 09:21:03 GMT [job_runner_alliance_community_participation(8363) @ ::1(60000)] STATEMENT: SELECT t.oid, typarray 
FROM pg_type t JOIN pg_namespace ns 
ON typnamespace = ns.oid 
WHERE typname = 'hstore'; 

are being observed in the console when starting the CB-pssql process though the index names can vary.

This may be observed after a forced server shut down.

Environment

CB Response Server version 6.x

Cause

  • The forced server shut down has caused a corruption in the PostGres SQL database used by response. 
  • This can be a result of rebooting the server without taking down Response services gracefully.

Resolution

  1. A Db restore as detailed in the Cb Response Cluster Management Guide would be the only official solution available (see Related Content)
  2. A restore of the corrupt DB Index's could be attempted but would be carried out at the customer's own risk