I disabled and removed the CTM_Postgre.service as it didn't help (and I didn't
want too many moving parts left out there).
I did find a post
https://superuser.com/questions/1016827/how-do-i-run-a-script-before-everything-else-on-shutdown-with-systemd
that I think is getting me closer.
I tried
Adrian,
I tried changing the Before to After but the postgresql instance was still
shutdown too early.
I appreciate all of the help but think I'm going to ask the patching group to
ensure they stop the control-m services prior to reboot.
Bryce
Oct 11 09:19:57 kccontrolmt01 su[9816]: pam_uni
Adrian,
Thanks for being willing to dig into this.
You are correct there are other scripts being called from mine (delivered by
BMC with their software). In order to stay in support and work with their
updates I use the vendor supplied scripts/programs.
The Control-M product is installed
/ctm_server/scripts/shutdb
fi
fi
exit 0
-Original Message-
From: Adrian Klaver
Sent: Wednesday, October 10, 2018 8:25 AM
To: Bryce Pepper ; pgsql-general@lists.postgresql.org
Subject: Re: RHEL 7 (systemd) reboot
This email originated from outside the company. Please use caution when open
erver running on host "kccontrolmt01" (10.1.32.53) and accepting
TCP/IP connections on port 5433?
-Original Message-
From: Adrian Klaver
Sent: Tuesday, October 09, 2018 7:39 PM
To: Bryce Pepper ; pgsql-general@lists.postgresql.org
Subject: Re: RHEL 7 (systemd) reboot
-
From: Adrian Klaver
Sent: Tuesday, October 09, 2018 7:39 PM
To: Bryce Pepper ; pgsql-general@lists.postgresql.org
Subject: Re: RHEL 7 (systemd) reboot
This email originated from outside the company. Please use caution when opening
attachments or clicking on links. If you suspect this to be a
that the
Configuration Agent might start the CONTROL-M/Server
The database must be available for the product to shut down in a consistent
state.
I am open to suggestions.
Thanks,
Bryce
Bryce Pepper
Sr. Unix Applications Systems Engineer
The Kansas City Southern Railway Company
114 West
