recovering from an unresponsive hostd after a datastore/storage goes PDL

Hostd crashes with the below: Hostd.log 2018-12-17T22:37:50.138Z info hostd[9130B80] [Originator@6876 sub=Hostsvc] Storage data synchronization policy set to invalidate_change 2018-12-17T22:37:50.140Z info hostd[9130B80] [Originator@6876 sub=Libs] lib/ssl: OpenSSL using FIPS_drbg for RAND 2018-12-17T22:37:50.140Z info hostd[9130B80] [Originator@6876 sub=Libs] lib/ssl: protocol list tls1.2 2018-12-17T22:37:50.140Z info hostd[9130B80] [Originator@6876 sub=Libs] lib/ssl: protocol list tls1.2 (openssl flags 0x17000000) 2018-12-17T22:37:50.140Z info hostd[9130B80] [Originator@6876 sub=Libs] […]

Read More

PostgreSQL: could not open file “/var/lib/pgsql/data/pg_clog/0726”: No such file or directory

when selecting a specific date from a table, at times due to database corruption Postgres might report the file was not found. hsphere=# select * from TABLE; ERROR:  could not access status of transaction 1918986094 DETAIL:  could not open file “/var/lib/pgsql/data/pg_clog/0726”: No such file or directory   In Such instances, we will need to re-create […]

Read More