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

From Adrian Klaver
Subject Re: RHEL 7 (systemd) reboot
Date
Msg-id 9d666846-4e6e-bed5-0979-a8c00b515855@aklaver.com
Whole thread Raw
In response to RE: RHEL 7 (systemd) reboot  (Bryce Pepper <BPepper@KCSouthern.com>)
Responses RE: RHEL 7 (systemd) reboot  (Bryce Pepper <BPepper@KCSouthern.com>)
List pgsql-general
On 10/11/18 7:53 AM, Bryce Pepper wrote:
> Adrian,
> 
> I tried changing the Before to After but the postgresql instance was still shutdown too early.

In an earlier post you had:

cat ControlM_Shutdown.service
[Unit]
Description=Run mycommand at shutdown
Requires=network.target CTM_Postgre.service

Did you add CTM_Postgre.service to After= ?

My suspicion being that CTM_Postgre.service is running before you get to 
ControlM_Shutdown.service. Unless of course CTM_Postgre.service does not 
exist anymore.

Then there is this:

Oct 11 09:20:00 kccontrolmt01 stop_ctmdist_server.sh[10316]: setenv: Too 
many arguments.
Oct 11 09:20:00 kccontrolmt01 stop_ctmdist_server.sh[10316]: Stopping 
CONTROL-M application
Oct 11 09:20:00 kccontrolmt01 stop_ctmdist_server.sh[10316]: SQL Server 
is not running.
Oct 11 09:20:00 kccontrolmt01 stop_ctmlinux_server.sh[10318]: setenv: 
Too many arguments.
Oct 11 09:20:00 kccontrolmt01 stop_ctmlinux_server.sh[10318]: Stopping 
CONTROL-M application
Oct 11 09:20:00 kccontrolmt01 stop_ctmlinux_server.sh[10318]: SQL Server 
is not running.

which to me looks like the script is running twice

> 
> I appreciate all of the help but think I'm going to ask the patching group to ensure they stop the control-m services
priorto reboot.
 

Yeah, there seems to be hidden dependencies happening.
> 
> Bryce
> 



-- 
Adrian Klaver
adrian.klaver@aklaver.com


pgsql-general by date:

Previous
From: Jeff Janes
Date:
Subject: Re: Advice on logging strategy
Next
From: Bryce Pepper
Date:
Subject: RE: RHEL 7 (systemd) reboot