I want to add my server load normally, please see attachment, thanks.
On Mon, Oct 10, 2016 at 9:24 AM, Periko Support <pheriko.supp...@gmail.com> wrote: > I got some issues with my DB under ubuntu 14.x. > PSQL 9.3, odoo 7.x. > > This machine is under KVM with centos 6.x > > It has a Raid1 with ssd drives only for this vm. > > I detect some unexpected shutdows, see this lines: > > 2016-09-12 08:59:25 PDT ERROR: missing FROM-clause entry for table > "rp" at character 73 > 2016-09-12 08:59:25 PDT STATEMENT: select > pp.default_code,pc.product_code,pp.name_template,pc.product_name,rp.name > from product_product pp inner join product_customer_code pc on > pc.product_id=pp.id > 2016-09-12 08:59:26 PDT LOG: connection received: host=192.168.2.153 > port=59335 > 2016-09-12 08:59:26 PDT LOG: connection authorized: user=openerp > database=Mueblex > 2016-09-12 09:00:01 PDT LOG: connection received: host=::1 port=43536 > 2016-09-12 09:00:01 PDT LOG: connection authorized: user=openerp > database=template1 > 2016-09-12 09:00:01 PDT LOG: server process (PID 23958) was > terminated by signal 9: Killed > 2016-09-12 09:00:01 PDT DETAIL: Failed process was running: select > pp.default_code,pc.product_code,pp.name_template,pc.product_name,rp.name > from product_product pp inner join product_customer_code pc on > pc.product_id=pp.id > 2016-09-12 09:00:01 PDT LOG: terminating any other active server processes > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 09:00:01 PDT 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. > 2016-09-12 09:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 09:00:01 PDT LOG: archiver process (PID 989) exited with exit > code 1 > 2016-09-12 09:00:01 PDT LOG: all server processes terminated; > reinitializing > 2016-09-12 09:00:03 PDT LOG: database system was interrupted; last > known up at 2016-09-12 08:59:27 PDT > 2016-09-12 09:00:07 PDT LOG: database system was not properly shut > down; automatic recovery in progress > 2016-09-12 09:00:07 PDT LOG: redo starts at 29A/AF000028 > 2016-09-12 09:00:07 PDT LOG: record with zero length at 29A/BC001958 > 2016-09-12 09:00:07 PDT LOG: redo done at 29A/BC001928 > 2016-09-12 09:00:07 PDT LOG: last completed transaction was at log > time 2016-09-12 09:00:01.768271-07 > 2016-09-12 09:00:08 PDT LOG: MultiXact member wraparound protections > are now enabled > 2016-09-12 09:00:08 PDT LOG: database system is ready to accept > connections > 2016-09-12 09:00:08 PDT LOG: autovacuum launcher started > 2016-09-12 09:00:15 PDT LOG: connection received: host=127.0.0.1 > port=45508 > > Latter another one: > 2016-09-12 09:51:32 PDT ERROR: duplicate key value violates unique > constraint "upc_scan_plant_uniq" > 2016-09-12 09:51:32 PDT DETAIL: Key (name, plant_id)=(2016-09-12, 6) > already exists. > 2016-09-12 09:51:32 PDT STATEMENT: insert into "upc_scan" > (id,"plant_id","state","name",create_uid,create_date,write_uid,write_date) > values (1438,6,'draft','2016-09-12',87,(now() at time zone > 'UTC'),87,(now() at time zone 'UTC')) > 2016-09-12 09:51:40 PDT ERROR: duplicate key value violates unique > constraint "upc_scan_plant_uniq" > 2016-09-12 09:51:40 PDT DETAIL: Key (name, plant_id)=(2016-09-12, 6) > already exists. > 2016-09-12 09:51:40 PDT STATEMENT: insert into "upc_scan" > (id,"plant_id","state","name",create_uid,create_date,write_uid,write_date) > values (1439,6,'draft','2016-09-12',87,(now() at time zone > 'UTC'),87,(now() at time zone 'UTC')) > 2016-09-12 09:51:43 PDT ERROR: duplicate key value violates unique > constraint "upc_scan_plant_uniq" > 2016-09-12 09:51:43 PDT DETAIL: Key (name, plant_id)=(2016-09-12, 6) > already exists. > 2016-09-12 09:51:43 PDT STATEMENT: insert into "upc_scan" > (id,"plant_id","state","name",create_uid,create_date,write_uid,write_date) > values (1440,6,'draft','2016-09-12',87,(now() at time zone > 'UTC'),87,(now() at time zone 'UTC')) > 2016-09-12 10:00:01 PDT LOG: connection received: host=::1 port=43667 > 2016-09-12 10:00:01 PDT LOG: connection authorized: user=openerp > database=template1 > 2016-09-12 10:00:01 PDT LOG: server process (PID 30766) was > terminated by signal 9: Killed > 2016-09-12 10:00:01 PDT DETAIL: Failed process was running: select > pp.default_code,pc.product_code,pp.name_template,pc.product_name,rp.name > from product_product pp inner join product_customer_code pc on > pc.product_id=pp.id > 2016-09-12 10:00:01 PDT LOG: terminating any other active server processes > 2016-09-12 10:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 10:00:01 PDT 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. > 2016-09-12 10:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 10:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 10:00:01 PDT 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. > 2016-09-12 10:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 10:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 10:00:01 PDT 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. > 2016-09-12 10:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 10:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 10:00:01 PDT 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. > 2016-09-12 10:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 10:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 10:00:01 PDT 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. > 2016-09-12 10:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 10:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 10:00:01 PDT 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. > 2016-09-12 10:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 10:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 10:00:01 PDT 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. > 2016-09-12 10:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 10:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 10:00:01 PDT 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. > 2016-09-12 10:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 10:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 10:00:01 PDT 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. > 2016-09-12 10:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 10:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 10:00:01 PDT 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. > 2016-09-12 10:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 10:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 10:00:01 PDT 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. > 2016-09-12 10:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 10:00:01 PDT LOG: archiver process (PID 29336) exited with > exit code 1 > 2016-09-12 10:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 10:00:01 PDT 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. > 2016-09-12 10:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 10:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 10:00:01 PDT 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. > 2016-09-12 10:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 10:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 10:00:01 PDT 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. > 2016-09-12 10:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 10:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 10:00:01 PDT 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. > 2016-09-12 10:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 10:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 10:00:01 PDT 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. > 2016-09-12 10:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 10:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 10:00:01 PDT 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. > 2016-09-12 10:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 10:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 10:00:01 PDT 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. > 2016-09-12 10:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 10:00:01 PDT LOG: all server processes terminated; > reinitializing > 2016-09-12 10:00:02 PDT LOG: database system was interrupted; last > known up at 2016-09-12 09:58:45 PDT > 2016-09-12 10:00:06 PDT LOG: database system was not properly shut > down; automatic recovery in progress > 2016-09-12 10:00:06 PDT LOG: redo starts at 29C/DC000028 > 2016-09-12 10:00:06 PDT LOG: unexpected pageaddr 29B/ED01A000 in log > segment 000000010000029C000000F2, offset 106496 > 2016-09-12 10:00:06 PDT LOG: redo done at 29C/F2018D90 > 2016-09-12 10:00:06 PDT LOG: last completed transaction was at log > time 2016-09-12 10:00:00.558978-07 > 2016-09-12 10:00:07 PDT LOG: MultiXact member wraparound protections > are now enabled > 2016-09-12 10:00:07 PDT LOG: database system is ready to accept > connections > 2016-09-12 10:00:07 PDT LOG: autovacuum launcher started > 2016-09-12 10:00:11 PDT LOG: connection received: host=127.0.0.1 > port=45639 > > Other one: > > 2016-09-12 15:00:01 PDT LOG: server process (PID 22030) was > terminated by signal 9: Killed > 2016-09-12 15:00:01 PDT DETAIL: Failed process was running: SELECT > "name", "model", "description", "month" FROM "etiquetas_temp" > 2016-09-12 15:00:01 PDT LOG: terminating any other active server processes > 2016-09-12 15:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 15:00:01 PDT 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. > 2016-09-12 15:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 15:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 15:00:01 PDT 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. > 2016-09-12 15:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 15:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 15:00:01 PDT 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. > 2016-09-12 15:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 15:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 15:00:01 PDT 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. > 2016-09-12 15:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 15:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 15:00:01 PDT 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. > 2016-09-12 15:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 15:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 15:00:01 PDT 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. > 2016-09-12 15:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 15:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 15:00:01 PDT 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. > 2016-09-12 15:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 15:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 15:00:01 PDT 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. > 2016-09-12 15:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 15:00:01 PDT LOG: archiver process (PID 3254) exited with > exit code 1 > 2016-09-12 15:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 15:00:01 PDT 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. > 2016-09-12 15:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 15:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 15:00:01 PDT 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. > 2016-09-12 15:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 15:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 15:00:01 PDT 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. > 2016-09-12 15:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 15:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 15:00:01 PDT 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. > 2016-09-12 15:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 15:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 15:00:01 PDT 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. > 2016-09-12 15:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 15:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 15:00:01 PDT 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. > 2016-09-12 15:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 15:00:01 PDT WARNING: terminating connection because of > crash of another server process > 2016-09-12 15:00:01 PDT 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. > 2016-09-12 15:00:01 PDT HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2016-09-12 15:00:02 PDT LOG: all server processes terminated; > reinitializing > 2016-09-12 15:00:02 PDT LOG: database system was interrupted; last > known up at 2016-09-12 14:59:55 PDT > 2016-09-12 15:00:06 PDT LOG: database system was not properly shut > down; automatic recovery in progress > 2016-09-12 15:00:07 PDT LOG: redo starts at 2A8/69000028 > 2016-09-12 15:00:07 PDT LOG: record with zero length at 2A8/7201B4F8 > 2016-09-12 15:00:07 PDT LOG: redo done at 2A8/7201B4C8 > 2016-09-12 15:00:07 PDT LOG: last completed transaction was at log > time 2016-09-12 15:00:01.664762-07 > 2016-09-12 15:00:08 PDT LOG: MultiXact member wraparound protections > are now enabled > 2016-09-12 15:00:08 PDT LOG: database system is ready to accept > connections > 2016-09-12 15:00:08 PDT LOG: autovacuum launcher started > > What I can see is not because server load, maximum idle is 79% > > free > total used free shared buffers cached > Mem: 82493268 82027060 466208 3157228 136084 77526460 > -/+ buffers/cache: 4364516 78128752 > Swap: 1000444 9540 990904 > > Little use of swap, I will add more memory next week. > > In your experience this looks like HW issue? > > Thanks for your time!!! >
