Сбои после аварийного завершения

[dedy]

Вчера повис сервер с заббиксом, был отправлен в ребут. После ребута вижу в логах постгреса
2020-10-28 10:01:33.926 EET [1329] LOG: all server processes terminated; reinitializing
2020-10-28 10:01:34.039 EET [20583] FATAL: the database system is in recovery mode
2020-10-28 10:01:34.040 EET [20584] FATAL: the database system is in recovery mode
2020-10-28 10:01:34.068 EET [20585] FATAL: the database system is in recovery mode
2020-10-28 10:01:34.070 EET [20582] LOG: database system was interrupted; last known up at 2020-10-28 10:01:06 EET
2020-10-28 10:01:34.087 EET [20586] FATAL: the database system is in recovery mode
2020-10-28 10:01:34.164 EET [20587] FATAL: the database system is in recovery mode
2020-10-28 10:01:34.173 EET [20588] FATAL: the database system is in recovery mode
2020-10-28 10:01:34.301 EET [20589] FATAL: the database system is in recovery mode
2020-10-28 10:01:34.332 EET [20590] FATAL: the database system is in recovery mode
2020-10-28 10:01:34.355 EET [20591] FATAL: the database system is in recovery mode
2020-10-28 10:01:34.370 EET [20582] LOG: database system was not properly shut down; automatic recovery in progress
2020-10-28 10:01:34.394 EET [20582] LOG: redo starts at E1C/AF4C4968
2020-10-28 10:01:34.495 EET [20592] FATAL: the database system is in recovery mode
2020-10-28 10:01:34.565 EET [20593] FATAL: the database system is in recovery mode
2020-10-28 10:01:34.663 EET [20594] FATAL: the database system is in recovery mode
2020-10-28 10:01:34.669 EET [20582] LOG: invalid record length at E1C/AFEBCB78: wanted 24, got 0
2020-10-28 10:01:34.669 EET [20582] LOG: redo done at E1C/AFEBCB50
2020-10-28 10:01:34.678 EET [20582] LOG: last completed transaction was at log time 2020-10-28 10:01:33.215996+02
2020-10-28 10:01:34.686 EET [20596] FATAL: the database system is in recovery mode
2020-10-28 10:01:35.102 EET [20597] FATAL: the database system is in recovery mode
2020-10-28 10:01:35.355 EET [1329] LOG: database system is ready to accept connections
2020-10-28 10:01:35.443 EET [20603] LOG: TimescaleDB background worker launcher connected to shared catalogs
2020-10-28 10:01:43.585 EET [20636] WARNING: there is no transaction in progress
2020-10-28 10:01:43.609 EET [20637] WARNING: there is no transaction in progress
2020-10-28 10:01:44.058 EET [20640] WARNING: there is no transaction in progress
2020-10-28 10:01:44.066 EET [20639] WARNING: there is no transaction in progress
2020-10-28 10:02:36.661 EET [20640] LOG: unexpected EOF on client connection with an open transaction
2020-10-28 10:02:37.153 EET [20637] LOG: unexpected EOF on client connection with an open transaction
2020-10-28 10:02:37.171 EET [20636] LOG: unexpected EOF on client connection with an open transaction


Служба заббикс сервера периодически рестартуется сам, в логах периодами
13500:20201028:090837.199 syncing history data... 23.568670%
13500:20201028:090846.333 slow query: 8.278260 sec, "update trends_uint set num=60,value_min=14800584704,value_avg=14800584704 ,value_max=14800584704 where itemid=31720 and clock=1603868400;
update trends_uint set num=59,value_min=1603868440,value_avg=1603870184,v alue_max=1603871980 where itemid=31840 and clock=1603868400;
update trends_uint set num=61,value_min=1,value_avg=1,value_max=1 where itemid=32860 and clock=1603868400;
update trends_uint set num=61,value_min=854847488,value_avg=854847488,val ue_max=854847488 where itemid=32980 and clock=1603868400

Чем тут можно помочь ?

Поможет ли обновление на новую версию 5.2, в теории оно ж обновит саму базу ?

[Hamardaban]

Обновление только усугубит ситуацию!
Нужно отключать от базы всех и ремонтировать ее (см в интернет по запросу «FATAL: the database system is in recovery mode»)
Если есть свежая копия - возможно проще с нее восстановить базу.
См в логи постгреса для выяснения в чем проблема.