Hi, I somehow missed your email, sorry :-(
On Sun, Aug 11, 2019 at 2:45 PM Sameer Sardar <[email protected]> wrote: > Hi Martin, > Thanks for your reply. > I'm aware that there is some connectivity issue between PostgreSQL and > engine. > > I've checked pg_logs but couldn't find the root cause of the problem. > Please look into it and suggest what to do. > > [root@manager pg_log]# tail -100 postgresql-Sun.log > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > LOG: database system is ready to accept connections > LOG: autovacuum launcher started > PANIC: corrupted item pointer: offset = 1664, size = 16 > Looks like you have corrupted PostgreSQL data, please check if you disk is not failing. Regarding the recovery, I'm not PostgreSQL expert, but you will most probably need to restore your database from backup. But please check on PostgreSQL mailing list, they might be able to help you LOG: server process (PID 19115) was terminated by signal 6: Aborted > LOG: terminating any other active server processes > WARNING: terminating connection because of crash of another server process > DETAIL: The postmaster has commanded this server process to roll back the > current transaction and exit, because another server process exited > abnormally and possibly corrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and > repeat your command. > WARNING: terminating connection because of crash of another server process > DETAIL: The postmaster has commanded this server process to roll back the > current transaction and exit, because another server process exited > abnormally and possibly corrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and > repeat your command. > WARNING: terminating connection because of crash of another server process > DETAIL: The postmaster has commanded this server process to roll back the > current transaction and exit, because another server process exited > abnormally and possibly corrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and > repeat your command. > WARNING: terminating connection because of crash of another server process > DETAIL: The postmaster has commanded this server process to roll back the > current transaction and exit, because another server process exited > abnormally and possibly corrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and > repeat your command. > WARNING: terminating connection because of crash of another server process > DETAIL: The postmaster has commanded this server process to roll back the > current transaction and exit, because another server process exited > abnormally and possibly corrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and > repeat your command. > WARNING: terminating connection because of crash of another server process > DETAIL: The postmaster has commanded this server process to roll back the > current transaction and exit, because another server process exited > abnormally and possibly corrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and > repeat your command. > WARNING: terminating connection because of crash of another server process > DETAIL: The postmaster has commanded this server process to roll back the > current transaction and exit, because another server process exited > abnormally and possibly corrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and > repeat your command. > WARNING: terminating connection because of crash of another server process > DETAIL: The postmaster has commanded this server process to roll back the > current transaction and exit, because another server process exited > abnormally and possibly corrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and > repeat your command. > WARNING: terminating connection because of crash of another server process > DETAIL: The postmaster has commanded this server process to roll back the > current transaction and exit, because another server process exited > abnormally and possibly corrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and > repeat your command. > WARNING: terminating connection because of crash of another server process > DETAIL: The postmaster has commanded this server process to roll back the > current transaction and exit, because another server process exited > abnormally and possibly corrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and > repeat your command. > WARNING: terminating connection because of crash of another server process > DETAIL: The postmaster has commanded this server process to roll back the > current transaction and exit, because another server process exited > abnormally and possibly corrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and > repeat your command. > WARNING: terminating connection because of crash of another server process > DETAIL: The postmaster has commanded this server process to roll back the > current transaction and exit, because another server process exited > abnormally and possibly corrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and > repeat your command. > WARNING: terminating connection because of crash of another server process > DETAIL: The postmaster has commanded this server process to roll back the > current transaction and exit, because another server process exited > abnormally and possibly corrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and > repeat your command. > LOG: all server processes terminated; reinitializing > LOG: database system was interrupted; last known up at 2019-08-11 > 09:35:45 UTC > LOG: database system was not properly shut down; automatic recovery in > progress > LOG: redo starts at 247/ED612898 > LOG: record with zero length at 247/EDF74C18 > LOG: redo done at 247/EDF74BE0 > LOG: last completed transaction was at log time 2019-08-11 > 09:37:51.409331+00 > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > FATAL: the database system is in recovery mode > LOG: database system is ready to accept connections > LOG: autovacuum launcher started > > > Thanks & Regards, > Sameer Sardar > _______________________________________________ > Devel mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/[email protected]/message/VHBLTRREK2EKY2OS6F77T2RVWKAHFR6L/ > -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.
_______________________________________________ Devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/4IYFKTNXVJIM3JIOWA2ROONVNIEPC5EY/
