Re: RHEL 7 (systemd) reboot

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Bryce Pepper <BPepper(at)KCSouthern(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: RHEL 7 (systemd) reboot
Date: 2018-10-11 16:06:59
Message-ID: 9d666846-4e6e-bed5-0979-a8c00b515855@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 prior to reboot.

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

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bryce Pepper 2018-10-11 17:43:51 RE: RHEL 7 (systemd) reboot
Previous Message Jeff Janes 2018-10-11 15:36:06 Re: Advice on logging strategy