On 10/11/18 10:43 AM, Bryce Pepper wrote:
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
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
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
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
On 10/11/18 6:33 AM, Bryce Pepper wrote:
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/progra
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
On 10/10/18 7:37 AM, Bryce Pepper wrote:
Sorry, I wasn't clear in the prior posts.
The stop script is running during reboot. The problem is the database is not
reachable when the stop script runs. The ctmdist server shut down is as
follows:
Stop control-m application
Stop control-m co
/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
neral@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 phishing attempt,
please report via PhishAlarm.
On 10/9/18 11:
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
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 pa
12 matches
Mail list logo
