Here is the contents of the query and error: [root@kccontrolmt01 tmp]# cat ctm.Xf9pQkg2 update CMS_SYSPRM set CURRENT_STATE='STOPPING',DESIRED_STATE='Down' where DESIRED_STATE <> 'Ignored' ; psql: could not connect to server: Connection refused Is the server running on host "kccontrolmt01" (10.1.32.53) and accepting TCP/IP connections on port 5433? -----Original Message----- From: Adrian Klaver <adrian.klaver@xxxxxxxxxxx> Sent: Tuesday, October 09, 2018 7:39 PM To: Bryce Pepper <BPepper@xxxxxxxxxxxxxx>; pgsql-general@xxxxxxxxxxxxxxxxxxxx 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: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 patching which does a reboot. > > Looking in /var/log/messages and the stop scripts do not get invoked > on reboot, therefore I created a new shutdown service as described > here <https://unix.stackexchange.com/questions/211924/effect-of-reboot-signal-on-systemd-service-state>. > > It appears that PostGreSQL is receiving a signal from somewhere prior > to my script running. > > > The database must be available for the product to shut down in a > consistent state. > > I am open to suggestions. What is the below doing or coming from?: db_execute_sql failed while processing /data00/ctmlinux/ctm_server/tmp/upd_CMS_SYSPRM_29448. > > Thanks, > > Bryce > > *Bryce Pepper* > > Sr. Unix Applications Systems Engineer > > *The Kansas City Southern Railway Company * > > 114 West 11^th Street | Kansas City, MO 64105 > > Office: 816.983.1512 > > Email: bpepper@xxxxxxxxxxxxxx <mailto:bpepper@xxxxxxxxxxxxxx> > -- Adrian Klaver adrian.klaver@xxxxxxxxxxx