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 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.
Seems to me the first priority is finding what is shutting down Postgres.
Does the system log show anything?
If not, find the shutdown time in the Postgres log and correlate that
with the system log.
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.
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
