Do you have Linux set up to honor the signal (usually some updates inittab and zipl.conf)? You have to direct the signal to call a script that will issue the shutdown command...
Scott On Wed, Jun 10, 2009 at 10:33 AM, Robert J McCarthy < bob.mccar...@custserv.com> wrote: > John, > When you shutdown your linux guest, do you use a "CP SIGNAL SHUTDOWN" > command to tell linux to shutdown, or do you manually shutdown linux. > Our manual shutdown appears to work, but when we try to automate it with > the "CP SIGNAL SHUTDOWN" from vm; linux appears to send a response to vm > saying it has completed shutdown; but appraently it really hasn't. > Thanks, Bob > > -----Original Message----- > From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On > Behalf Of Romanowski, John (OFT) > Sent: Wednesday, June 10, 2009 9:19 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: Clean Linux Guest Shutdown > > We start/stop oracle with an init.d script so oracle's start/stop is > part of Linux's boot and shutdown sequence. > > > -----Original Message----- > > From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] > > On Behalf Of Robert J McCarthy > > Sent: Wednesday, June 10, 2009 8:46 AM > > To: IBMVM@LISTSERV.UARK.EDU > > Subject: Re: Clean Linux Guest Shutdown > > > > The "CP SIGNAL SHUTDOWN" command has helped to clarify our problem. It > > > appear that the problem may be in the way linux shuts itself dowm. > > With the command, it appear that everthing works as designed from a vm > > > standpoint; however linux never seems to complete it's shutdown. > > Although a guest is given 30 minutes to complete it's shutdown, linux > > appear to send a shutdown complete message back to vm within 30 > > seconds. We have the "shutdown - h" in the inittab. in our systems, > > Oracle is in the process of shutting down when linux pulls the plug. > > How do any of you handle oracle/linux shutdown. > > Below > > is a listing of the linux log for one of the guests shutting down. Is > > it similar to what you see : > > Jun 7 01:44:59 zoracle2 syslog-ng[1780]: STATS: dropped 0 Jun 7 > > 02:02:28 zoracle2 shutdown[4266]: shutting down for system reboot Jun > > > 7 02:02:28 zoracle2 init: Switching to runlevel: 6 Jun 7 02:02:30 > > zoracle2 multipathd: mpvol1: stop event checker thread Jun 7 02:02:30 > > > zoracle2 multipathd: mpvol3: stop event checker thread Jun 7 02:02:30 > > > zoracle2 multipathd: mpvol4: stop event checker thread Jun 7 02:02:31 > > > zoracle2 multipathd: mpvol5: stop event checker thread Jun 7 02:02:31 > > > zoracle2 su: (to oracle) root on /dev/pts/8 Jun 7 02:02:31 zoracle2 > > multipathd: mpvol2: stop event checker thread Jun 7 02:02:31 zoracle2 > > > multipathd: mpvol6: stop event checker thread Jun 7 02:02:31 zoracle2 > > > multipathd: mpvol6: stop event checker thread Jun 7 02:02:37 zoracle2 > > > xinetd[2288]: Exiting... > > Jun 7 02:02:37 zoracle2 sshd[2302]: Received signal 15; terminating. > > Jun 7 02:02:38 zoracle2 su: (to oracle) root on /dev/pts/8 Jun 7 > > 02:02:46 zoracle2 kernel: Kernel logging (proc) stopped. > > Jun 7 02:02:46 zoracle2 kernel: Kernel log daemon terminating. > > Jun 7 02:02:48 zoracle2 syslog-ng[1780]: syslog-ng version 1.6.8 going > > > down Jun 7 05:56:37 zoracle2 syslog-ng[2311]: syslog-ng version 1.6.8 > > starting > > Thanks, Bob > > > This e-mail, including any attachments, may be confidential, privileged > or otherwise legally protected. It is intended only for the addressee. > If you received this e-mail in error or from someone who was not > authorized to send it to you, do not disseminate, copy or otherwise use > this e-mail or its attachments. Please notify the sender immediately by > reply e-mail and delete the e-mail from your system. >
