RE: RHEL 7 (systemd) reboot

From: Bryce Pepper <BPepper(at)KCSouthern(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(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 17:43:51
Message-ID: f3d88aa476d94195874ef050f0e73379@WNEXMBFEP03.KCSCP.CORP
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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 RequiresMountsFor=/data00 which starts the script much sooner but unfortunately the postgresql instance is unreachable by the time the script gets there.

These are two unique datacenter shutdowns: ctmdist & ctmlinux

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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2018-10-11 17:53:17 Re: how to identify the timeline of specified recovery_target_time when do multiple PITR
Previous Message Adrian Klaver 2018-10-11 16:06:59 Re: RHEL 7 (systemd) reboot