Re: RHEL 7 (systemd) reboot - Mailing list pgsql-general

From Adrian Klaver
Subject Re: RHEL 7 (systemd) reboot
Date
Msg-id 532b0c39-6b76-658f-fe45-852dd964d7ba@aklaver.com
Whole thread Raw
In response to RHEL 7 (systemd) reboot  (Bryce Pepper <BPepper@KCSouthern.com>)
Responses RE: RHEL 7 (systemd) reboot
RE: RHEL 7 (systemd) reboot
List pgsql-general
On 10/9/18 11:06 AM, Bryce Pepper wrote:
> I am running three instances (under different users) on a RHEL 7 server 
> to support a vendor product.
> 
> In the defined services, the start & stop scripts work fine when invoked 
> with systemctl {start|stop} whatever.service  but we have automated 
> monthly patching which does a reboot.
> 
> Looking in /var/log/messages and the stop scripts do not get invoked on 
> reboot, therefore I created a new shutdown service as described here 
> <https://unix.stackexchange.com/questions/211924/effect-of-reboot-signal-on-systemd-service-state>.
> 
> It appears that PostGreSQL is receiving a signal from somewhere prior to 
> my script running…
> 

> 
> The database must be available for the product to shut down in a 
> consistent state.
> 
> I am open to suggestions.

What is the below doing or coming from?:

db_execute_sql failed while processing 
/data00/ctmlinux/ctm_server/tmp/upd_CMS_SYSPRM_29448.

> 
> Thanks,
> 
> Bryce
> 
> *Bryce Pepper*
> 
> Sr. Unix Applications Systems Engineer
> 
> *The Kansas City Southern Railway Company *
> 
> 114 West 11^th Street  |  Kansas City,  MO 64105
> 
> Office:  816.983.1512
> 
> Email: bpepper@kcsouthern.com <mailto:bpepper@kcsouthern.com>
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com


pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Privilege mess?
Next
From: magodo
Date:
Subject: pg9.6: PITR paused just after failover, need manual resume