OTRS is temporarily unavailable

[liketheother]

Good day!
Starting work as a programmer, leadership gave the task write data to the base in OTRS, since then, now i am administrator of the system. Unfortunately I do not have deep knowledge in the analysis of logs.
Situation:
OTRS 4 stands at CentOS with Postgre database over the past two months, OTRS twice refused to work until I did not reboot a server.
I found the following entry in the log (the last time you did not work OTRS)
------------------------------------------------------------------
[Wed Nov 11 10:53:21 2015] otrs.Scheduler.pl: DBD::Pg::st DESTROY failed: FATAL: terminating connection due to administrator command
[Wed Nov 11 10:53:21 2015] otrs.Scheduler.pl: SSL connection has been closed unexpectedly at /opt/otrs/Kernel/System/DB.pm line 629.
[Wed Nov 11 10:53:21 2015] otrs.Scheduler.pl: DBD::Pg::st execute failed: no connection to the server at /opt/otrs/Kernel/System/DB.pm line 629.
ERROR: OTRS-otrs.Scheduler-73 Perl: 5.18.2 OS: linux Time: Wed Nov 11 10:53:22 2015

Message: no connection to the server, SQL: '
SELECT process_name, process_id, process_host, process_create, process_change
FROM process_id
WHERE process_name = ? LIMIT 1'

Traceback (14911):
Module: Kernel::System::PID::PIDGet Line: 163
Module: main::_Start Line: 421
Module: /opt/otrs/bin/otrs.Scheduler.pl Line: 156

ERROR: OTRS-otrs.Scheduler-73 Perl: 5.18.2 OS: linux Time: Wed Nov 11 10:53:22 2015

Message: Process could not be found in the process table!
Scheduler is stopping...!


Traceback (14911):
Module: main::_AutoStop Line: 653
Module: main::_Start Line: 425
Module: /opt/otrs/bin/otrs.Scheduler.pl Line: 156
------------------------------------------------------------------


help good people where I should dig and what to see?

[EXG133]

http://www.postgresql.org/message-id/56 ... .pgh.pa.us

> PGSQL ERROR: FATAL: terminating connection due to administrator command

This means that something sent the server process a SIGTERM signal.

So something is shutting down your database. Possible culprit could be the Linux out of memory killer but check your logs to make sure.