Re: Clean Linux Guest Shutdown
I believe that I may have found something that could be causing my quick shutdowns. I issued the following commands with results : Q SHUTDOWN System shutdown time: 30 seconds Q SIGNAL SHUTDOWN System default shutdown signal timeout: 1200 seconds Even though I enter the following command : CP SIGNAL SHUTDOWN ZORACLE2 WITHIN 1800 could vm be using the system shutdown time of 30 seconds when it receives a response from a guest. This might explain why all all guests appear to shutdown within 30 seconds. If I increase that value to say 1800 with a CP SET SHUTDOWNTIME 1800, might this correct my problem ? Thanks,Bob -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Marcy Cortes Sent: Wednesday, June 10, 2009 4:31 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Please post the console messages from post syslog going down. Marcy - Original Message - From: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To: IBMVM@LISTSERV.UARK.EDU IBMVM@LISTSERV.UARK.EDU Sent: Wed Jun 10 14:15:06 2009 Subject: Re: [IBMVM] Clean Linux Guest Shutdown David, The reboot was 3 hours later when the guest was manually brought up after the corrupted filesystem was fixed. The last message received at shutdown was : Jun 7 02:02:48 zoracle2 syslog-ng[1780]: syslog-ng version 1.6.8 going down We did not have vmpoff=LOGOFF in the parm lines. The linux guests were in a vm DSC status. We were not logged into any of them. I did notice however that the guests were all logged off of vm once the vm termination message was received. Thanks,Bob -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of David Boyes Sent: Wednesday, June 10, 2009 2:17 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown It appears that linux sends the termination response to vm before it has really completed it's (linux)shutdown. In linux's inittab we have shutdown -h coded. But your example shows a automatic reboot and the system trying to come back up. Something else is wrong... do you specify vmpoff=LOGOFF in your parm lines? You want the virtual machine to log off when it's done.
Re: Clean Linux Guest Shutdown
According the HELP CPSET SHUTDOWNTIME (on 5.4): 1. This command takes effect only when the WITHIN interval or BY hh:mm:ss options of the SHUTDOWN command are used. If these options are not specified on the command, the SHUTDOWNTIME and SIGNAL SHUTDOWN times are added together and that is the time allowed for the shutdown, if necessary. So unless you're using WITHIN or BY when you do a z/VM shutdown - you should be waiting 1230 seconds if necessary. Also, note - this is only applicable to a z/VM shutdown -- if you SIGNAL SHUTDOWN a guest manually -- SHUTDOWNTIME isn't involved. Scott On Thu, Jun 11, 2009 at 7:58 AM, Robert J McCarthy bob.mccar...@custserv.com wrote: I believe that I may have found something that could be causing my quick shutdowns. I issued the following commands with results : Q SHUTDOWN System shutdown time: 30 seconds Q SIGNAL SHUTDOWN System default shutdown signal timeout: 1200 seconds Even though I enter the following command : CP SIGNAL SHUTDOWN ZORACLE2 WITHIN 1800 could vm be using the system shutdown time of 30 seconds when it receives a response from a guest. This might explain why all all guests appear to shutdown within 30 seconds. If I increase that value to say 1800 with a CP SET SHUTDOWNTIME 1800, might this correct my problem ? Thanks,Bob -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Marcy Cortes Sent: Wednesday, June 10, 2009 4:31 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Please post the console messages from post syslog going down. Marcy - Original Message - From: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To: IBMVM@LISTSERV.UARK.EDU IBMVM@LISTSERV.UARK.EDU Sent: Wed Jun 10 14:15:06 2009 Subject: Re: [IBMVM] Clean Linux Guest Shutdown David, The reboot was 3 hours later when the guest was manually brought up after the corrupted filesystem was fixed. The last message received at shutdown was : Jun 7 02:02:48 zoracle2 syslog-ng[1780]: syslog-ng version 1.6.8 going down We did not have vmpoff=LOGOFF in the parm lines. The linux guests were in a vm DSC status. We were not logged into any of them. I did notice however that the guests were all logged off of vm once the vm termination message was received. Thanks,Bob -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of David Boyes Sent: Wednesday, June 10, 2009 2:17 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown It appears that linux sends the termination response to vm before it has really completed it's (linux)shutdown. In linux's inittab we have shutdown -h coded. But your example shows a automatic reboot and the system trying to come back up. Something else is wrong... do you specify vmpoff=LOGOFF in your parm lines? You want the virtual machine to log off when it's done.
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 t he 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 shutdo wn 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 wh en linux pulls the plug. How do any of you handle oracle/linux shutdown. Bel ow 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
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.
Re: Clean Linux Guest Shutdown
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.
Re: Clean Linux Guest Shutdown
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.
Re: Clean Linux Guest Shutdown
I CP FORCE guest WITHIN nn Like CP SIGNAL SHUTDOWN that triggers the linux's inittab CTRLALTDEL entry. What do you mean when you say linux appears to send a response to VM saying it has completed shutdown; but apparently it really hasn't ? Is that sent response just a message on the guest's console or a linux script doing VMCP MESSAGE userid blah blah blah? -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 12:34 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown 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. 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.
Re: Clean Linux Guest Shutdown
John, I am sorry I wasn't clear. VM and linux are communicating : When I enter the CP SIGNAL SHUTDOWN command from MAINT linux begins shutting down. A short time later vm receives the termination from linux and writes the following message to the vm MAINT log : HCPSIG2113I User ZORACLE2 has reported successful termination From a vm standpoint everything appears to be working as designed. It appears that linux sends the termination response to vm before it has really completed it's (linux)shutdown. In linux's inittab we have shutdown -h coded. 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 12:57 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown I CP FORCE guest WITHIN nn Like CP SIGNAL SHUTDOWN that triggers the linux's inittab CTRLALTDEL entry. What do you mean when you say linux appears to send a response to VM saying it has completed shutdown; but apparently it really hasn't ? Is that sent response just a message on the guest's console or a linux script doing VMCP MESSAGE userid blah blah blah? -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 12:34 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown 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. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected
Re: Clean Linux Guest Shutdown
On Wednesday, 06/10/2009 at 02:01 EDT, Robert J McCarthy bob.mccar...@custserv.com wrote: John, I am sorry I wasn't clear. VM and linux are communicating : When I enter the CP SIGNAL SHUTDOWN command from MAINT linux begins shutting down. A short time later vm receives the termination from linux and writes the following message to the vm MAINT log : HCPSIG2113I User ZORACLE2 has reported successful termination From a vm standpoint everything appears to be working as designed. It appears that linux sends the termination response to vm before it has really completed it's (linux)shutdown. In linux's inittab we have shutdown -h coded. The HCPSIG2113I indicates that the guest is no longer running. Linux *has* completed shutdown and loaded a special WAIT PSW. If you want applications to terminate cleanly, then Linux shutdown scripts need to wait for the application to end. Alan Altmark z/VM Development IBM Endicott
Re: Clean Linux Guest Shutdown
It appears that linux sends the termination response to vm before it has really completed it's (linux)shutdown. In linux's inittab we have shutdown -h coded. But your example shows a automatic reboot and the system trying to come back up. Something else is wrong... do you specify vmpoff=LOGOFF in your parm lines? You want the virtual machine to log off when it's done.
Re: Clean Linux Guest Shutdown
We have the shutdown - h in the inittab. Hmm. But you are still getting the shutting down for reboot message, which seems odd to me. I think there's something funny in your init scripts for starting/stopping Oracle -- there should be something there that makes the shutdown process synchronous with actual exit of the program. Could you paste those into a message and let us have a look? in our systems, Oracle is in the process of shutting down wh en linux pulls the plug. How do any of you handle oracle/linux shutdown. That's one of the reasons why we wrote SYSVINIT. It goes through the sequence of virtual machines and waits for each one to exit and log off, then issues the CP SHUTDOWN. That way we know the fragile stuff is already packed away before CP goes away. It's free, give it a try. http://www.sinenomine.net/products/vm/s5i
Re: Clean Linux Guest Shutdown
David, The reboot was 3 hours later when the guest was manually brought up after the corrupted filesystem was fixed. The last message received at shutdown was : Jun 7 02:02:48 zoracle2 syslog-ng[1780]: syslog-ng version 1.6.8 going down We did not have vmpoff=LOGOFF in the parm lines. The linux guests were in a vm DSC status. We were not logged into any of them. I did notice however that the guests were all logged off of vm once the vm termination message was received. Thanks,Bob -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of David Boyes Sent: Wednesday, June 10, 2009 2:17 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown It appears that linux sends the termination response to vm before it has really completed it's (linux)shutdown. In linux's inittab we have shutdown -h coded. But your example shows a automatic reboot and the system trying to come back up. Something else is wrong... do you specify vmpoff=LOGOFF in your parm lines? You want the virtual machine to log off when it's done.
Re: Clean Linux Guest Shutdown
Bob,
I think it's as the others said, Linux is shutting down the way you told it to
do but not the way you intend it to do:
Here's how we shutdown a disconnected sles 10 oracle server gracefully here,
hope the example helps you:
/etc/inittab has a record to run 'shutdown -h now' in response to the SIGNAL
SHUTDOWN or FORCE WITHIN
ca::ctrlaltdel:/sbin/shutdown -h -t 4 now
our zipl.conf doesn't have any vmpoff/halt-whatevers in it.
CP Q SIGNALS shows the oracle guest enabled for the SHUTDOWN signal
Signalled Timeout
UseridSignalSignal Status By Remaining
DZ2DF138 SHUTDOWN Enabled - -
init script dbora (see listing below) with proper comment headers is in
/etc/init.d/dbora
I ran command 'chkconfig dbora on' so the start/kill symlinks to dbora are
built in /etc/init.d/rc.3/
'chkconfig -l dbora' reports dbora is on in run level 3
dz2df138 is running disconnected; From VM did CP SIGNAL SHUTDOWN dz2df138
On dz2df138 oracle shutdown cleanly and then linux finished shutting down, and
VM then logged off dz2df138.
This is our /etc/init.d/dbora script:
-
#!/bin/sh
# OFT John R 3/20/2007 An init script to start/stop oracle 10gR2 database(s)
# and the Oracle listener by running Oracle's scripts based on this script's
# input parameter of start or stop.
# The Oracle scripts are run as userid oracle.
#
#This incorporates some code from Oracle's dbora script shown in their doc. We
use
# 'su' not 'rsh' that Oracle used.
### BEGIN INIT INFO
# Provides: dbora
# Required-Start: $local_fs $network $syslog
# Should-Start: $local_fs $network $syslog nscd sshd
# Default-Start: 3
# Short-Description: Starts/stops oracle db and listener.
# Description: dbora is OFT's script to start/stop oracle database and its
listener;
#also starts/stops oracle dbconsole.
### END INIT INFO
case $1 in
'start')
echo ... ORACLE listener, database(s) and dbconsole starting ...
su - oracle -c sh -c \dbstart \$ORACLE_HOME \
echo emctl start dbconsole...
su - oracle -c sh -c \emctl start dbconsole \#can be in parallel
;;
'stop')
echo ... ORACLE dbconsole, database(s) and listener stopping ...
su - oracle -c sh -c \emctl stop dbconsole \
echo dbshut...
su - oracle -c sh -c \dbshut \$ORACLE_HOME \
;;
*)
echo usage: $0 {start | stop}
exit
;;
esac
#
-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 1:59 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Clean Linux Guest Shutdown
John,
I am sorry I wasn't clear. VM and linux are communicating :
When I enter the CP SIGNAL SHUTDOWN command from MAINT linux begins
shutting down. A short time later vm receives the termination from
linux
and writes the following message to the vm MAINT log :
HCPSIG2113I User ZORACLE2 has reported successful termination
From a vm standpoint everything appears to be working as designed. It
appears that linux sends the termination response to vm before it has
really completed it's (linux)shutdown. In linux's inittab we have
shutdown -h coded.
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 12:57 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Clean Linux Guest Shutdown
I CP FORCE guest WITHIN nn
Like CP SIGNAL SHUTDOWN that triggers the linux's inittab CTRLALTDEL
entry.
What do you mean when you say linux appears to send a response to VM
saying it has completed shutdown; but apparently it really hasn't ?
Is that sent response just a message on the guest's console or a linux
script doing VMCP MESSAGE userid blah blah blah?
-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 12:34 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Clean Linux Guest Shutdown
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
Re: Clean Linux Guest Shutdown
On 6/10/2009 at 3:15 PM, Robert J McCarthy bob.mccar...@custserv.com wrote: -snip- We did not have vmpoff=LOGOFF in the parm lines. The linux guests were in a vm DSC status. We were not logged into any of them. I did notice however that the guests were all logged off of vm once the vm termination message was received. Let's dig a little deeper here. 0. vmpoff is totally unrelated to the problem you're experiencing. As others have noted, Linux loads a specific PSW when it's done processing the shutdown signal. z/VM doesn't care if the guest is then logged off or not. (See previous list discussions on why you might want to do it anyway.) 1. How are your Oracle instances started and stopped? A script? Written by whom? 2. Have you spooled your guest's console so that you can see what happens when the shutdown signal is received? 3. Have you tried spooling your guest's console _and_ turning on script tracing for whatever does shut down Oracle? (set -x for /bin/sh and /bin/bash) Mark Post
Re: Clean Linux Guest Shutdown
( resent to correct my /etc/init.d/rc.3/ to /etc/init.d/rc3.d/)
Bob,
I think it's as the others said, Linux is shutting down the way you told it to
do but not the way you intend it to do:
Here's how we shutdown a disconnected sles 10 oracle server gracefully here,
hope the example helps you:
/etc/inittab has a record to run 'shutdown -h now' in response to the SIGNAL
SHUTDOWN or FORCE WITHIN
ca::ctrlaltdel:/sbin/shutdown -h -t 4 now
our zipl.conf doesn't have any vmpoff/halt-whatevers in it.
CP Q SIGNALS shows the oracle guest enabled for the SHUTDOWN signal
Signalled Timeout
UseridSignalSignal Status By Remaining
DZ2DF138 SHUTDOWN Enabled - -
init script dbora (see listing below) with proper comment headers is in
/etc/init.d/dbora
I ran command 'chkconfig dbora on' so the start/kill symlinks to dbora are
built in /etc/init.d/rc3.d/
'chkconfig -l dbora' reports dbora is on in run level 3
dz2df138 is running disconnected; From VM did CP SIGNAL SHUTDOWN dz2df138
On dz2df138 oracle shutdown cleanly and then linux finished shutting down, and
VM then logged off dz2df138.
This is our /etc/init.d/dbora script:
-
#!/bin/sh
# OFT John R 3/20/2007 An init script to start/stop oracle 10gR2 database(s)
# and the Oracle listener by running Oracle's scripts based on this script's
# input parameter of start or stop.
# The Oracle scripts are run as userid oracle.
#
#This incorporates some code from Oracle's dbora script shown in their doc. We
use
# 'su' not 'rsh' that Oracle used.
### BEGIN INIT INFO
# Provides: dbora
# Required-Start: $local_fs $network $syslog
# Should-Start: $local_fs $network $syslog nscd sshd
# Default-Start: 3
# Short-Description: Starts/stops oracle db and listener.
# Description: dbora is OFT's script to start/stop oracle database and its
listener;
#also starts/stops oracle dbconsole.
### END INIT INFO
case $1 in
'start')
echo ... ORACLE listener, database(s) and dbconsole starting ...
su - oracle -c sh -c \dbstart \$ORACLE_HOME \
echo emctl start dbconsole...
su - oracle -c sh -c \emctl start dbconsole \#can be in parallel
;;
'stop')
echo ... ORACLE dbconsole, database(s) and listener stopping ...
su - oracle -c sh -c \emctl stop dbconsole \
echo dbshut...
su - oracle -c sh -c \dbshut \$ORACLE_HOME \
;;
*)
echo usage: $0 {start | stop}
exit
;;
esac
#
-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 1:59 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Clean Linux Guest Shutdown
John,
I am sorry I wasn't clear. VM and linux are communicating :
When I enter the CP SIGNAL SHUTDOWN command from MAINT linux begins
shutting down. A short time later vm receives the termination from
linux
and writes the following message to the vm MAINT log :
HCPSIG2113I User ZORACLE2 has reported successful termination
From a vm standpoint everything appears to be working as designed. It
appears that linux sends the termination response to vm before it has
really completed it's (linux)shutdown. In linux's inittab we have
shutdown -h coded.
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 12:57 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Clean Linux Guest Shutdown
I CP FORCE guest WITHIN nn
Like CP SIGNAL SHUTDOWN that triggers the linux's inittab CTRLALTDEL
entry.
What do you mean when you say linux appears to send a response to VM
saying it has completed shutdown; but apparently it really hasn't ?
Is that sent response just a message on the guest's console or a linux
script doing VMCP MESSAGE userid blah blah blah?
-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 12:34 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Clean Linux Guest Shutdown
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
Re: Clean Linux Guest Shutdown
Please post the console messages from post syslog going down. Marcy - Original Message - From: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To: IBMVM@LISTSERV.UARK.EDU IBMVM@LISTSERV.UARK.EDU Sent: Wed Jun 10 14:15:06 2009 Subject: Re: [IBMVM] Clean Linux Guest Shutdown David, The reboot was 3 hours later when the guest was manually brought up after the corrupted filesystem was fixed. The last message received at shutdown was : Jun 7 02:02:48 zoracle2 syslog-ng[1780]: syslog-ng version 1.6.8 going down We did not have vmpoff=LOGOFF in the parm lines. The linux guests were in a vm DSC status. We were not logged into any of them. I did notice however that the guests were all logged off of vm once the vm termination message was received. Thanks,Bob -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of David Boyes Sent: Wednesday, June 10, 2009 2:17 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown It appears that linux sends the termination response to vm before it has really completed it's (linux)shutdown. In linux's inittab we have shutdown -h coded. But your example shows a automatic reboot and the system trying to come back up. Something else is wrong... do you specify vmpoff=LOGOFF in your parm lines? You want the virtual machine to log off when it's done.
Re: Clean Linux Guest Shutdown
John,
We checked the linux scripts on several guests with what you sent us
and our scripts are very similar. We went through the process with one
test linux /oracle guest and reviewed the log. This guest came down
cleanly without any issues. Oracle shutdown down normally, all within
about 30 seconds. The problem that occurred on Sunday was that we
shutdown approximately 35 linux guests of which about 20 have Oracle
databases. We did stagger the shutdowns to some degree to alleviate
system contention for resources. The test database was also a small
database. Some of the production databases are about 2-3tb each, and
would probably take longer than 30 seconds to shutdown depending on what
they were doing at the time. It seems as though all of the guests
shutdown within 30 seconds and the scripts on some have not completed
processing yet. We are going to continue to research this and see where
we might have made a mistake. I am also going to look at the SYSVINIT
product, since it appears that it could be very helpful in an orderly
shutdown/startup of the guests from a vm standpoint. The input from the
list respondants has been very informative. We are kind of new to this
environment; but it is growing very fast at our site.
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 3:38 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Clean Linux Guest Shutdown
( resent to correct my /etc/init.d/rc.3/ to /etc/init.d/rc3.d/) Bob, I
think it's as the others said, Linux is shutting down the way you told
it to do but not the way you intend it to do:
Here's how we shutdown a disconnected sles 10 oracle server gracefully
here, hope the example helps you:
/etc/inittab has a record to run 'shutdown -h now' in response to the
SIGNAL SHUTDOWN or FORCE WITHIN ca::ctrlaltdel:/sbin/shutdown -h -t 4
now
our zipl.conf doesn't have any vmpoff/halt-whatevers in it.
CP Q SIGNALS shows the oracle guest enabled for the SHUTDOWN signal
Signalled Timeout
UseridSignalSignal Status By Remaining
DZ2DF138 SHUTDOWN Enabled - -
init script dbora (see listing below) with proper comment headers is in
/etc/init.d/dbora
I ran command 'chkconfig dbora on' so the start/kill symlinks to dbora
are built in /etc/init.d/rc3.d/ 'chkconfig -l dbora' reports dbora is
on in run level 3
dz2df138 is running disconnected; From VM did CP SIGNAL SHUTDOWN
dz2df138
On dz2df138 oracle shutdown cleanly and then linux finished shutting
down, and VM then logged off dz2df138.
This is our /etc/init.d/dbora script:
-
#!/bin/sh
# OFT John R 3/20/2007 An init script to start/stop oracle 10gR2
database(s) # and the Oracle listener by running Oracle's scripts
based on this script's # input parameter of start or stop.
# The Oracle scripts are run as userid oracle.
#
#This incorporates some code from Oracle's dbora script shown in their
doc. We use # 'su' not 'rsh' that Oracle used.
### BEGIN INIT INFO
# Provides: dbora
# Required-Start: $local_fs $network $syslog # Should-Start: $local_fs
$network $syslog nscd sshd # Default-Start: 3 # Short-Description:
Starts/stops oracle db and listener.
# Description: dbora is OFT's script to start/stop oracle database and
its listener;
#also starts/stops oracle dbconsole.
### END INIT INFO
case $1 in
'start')
echo ... ORACLE listener, database(s) and dbconsole starting
...
su - oracle -c sh -c \dbstart \$ORACLE_HOME \
echo emctl start dbconsole...
su - oracle -c sh -c \emctl start dbconsole \#can be in
parallel
;;
'stop')
echo ... ORACLE dbconsole, database(s) and listener stopping
...
su - oracle -c sh -c \emctl stop dbconsole \
echo dbshut...
su - oracle -c sh -c \dbshut \$ORACLE_HOME \
;;
*)
echo usage: $0 {start | stop}
exit
;;
esac
#
-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 1:59 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Clean Linux Guest Shutdown
John,
I am sorry I wasn't clear. VM and linux are communicating :
When I enter the CP SIGNAL SHUTDOWN command from MAINT linux begins
shutting down. A short time later vm receives the termination from
linux and writes the following message to the vm MAINT log :
HCPSIG2113I User ZORACLE2 has reported successful termination From a
vm standpoint everything appears to be working as designed. It appears
that linux sends the termination response to vm before it has really
completed it's (linux)shutdown. In linux's inittab we have shutdown
-h coded.
Thanks, Bob
Re: Clean Linux Guest Shutdown
When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. Are you using IMMEDIATE operand of SHUTDOWN command? IMMEDIATE doesn't mean now, it means without sending any signals. Ivica Brodaric
Re: Clean Linux Guest Shutdown
Thank all of you for your input. I have tested the CP SIGNAL SHUTDOWN guest WITHIN xx and it does exactly what I want. I am writing an exec to shutdown each guest individually and in phases. I think that I have run into a problem in the past due to the fact that twenty minutes is in sufficent. I currently have about 35 linux guests on this lpar. Two are very large Oracle databases (20tb and 40tb). I intend to stagger the shutdown over perhaps a 45min-1 hour timeframe. I will be testing this out this weekend, since I am upgrading the lpar from 5.3 to 5.4. Thanks, Bob -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Martin, Terry R. (CMS/CTR) (CTR) Sent: Wednesday, June 03, 2009 8:12 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown I have also written a shutdown exec to cleanly shutdown all of my z/Linux guests and log them off once they are logged off a send a message to the console stating this. This works well and I have not had any problems. The one thing I would mention is that we have some large Oracle guests with large (5TB) data bases. To ensure that the Oracle shutdown script has time to complete cleanly I make sure that my time out value is very large at least 30 minutes. Now it normally does not take nearly that long but if you add in the possibility of paging as Rob mentioned you could be pushing the envelope and if the Oracle shutdown scripts do not complete cleanly you run the very real risk of corrupting ASM and believe me that is no fun. I have been there! So if you are running these types of workloads make sure you give the shutdown process plenty of time to complete cleanly. Thank You, Terry Martin Lockheed Martin - Information Technology z/OS z/VM Systems - Performance and Tuning Cell - 443 632-4191 Work - 410 786-0386 terry.mar...@cms.hhs.gov -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 5:54 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown That makes sense ... if it doesn't just seem longer (remember, pacing takes time, too - it is just spent waiting idly instead of waiting for the work to be done) and paging during SHUTDOWN is something you really have to worry about. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Rob van der Heij Sent: Wednesday, June 03, 2009 2:21 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown On Wed, Jun 3, 2009 at 8:00 PM, Schuh, Richard rsc...@visa.com wrote: Why not CP SIGNAL SHUTDOWN ALL instead of the table. From the peanut - uh performance gallery... If you have a lot of Linux servers, the orderly shutdown may actually take quite some paging resources to complete. When the shutdown is making them all do this at once, it may take much longer than when you pace it a bit. Seen with those who set LDUBUFF wrong. Rob -- Rob van der Heij Velocity Software http://www.velocitysoftware.com/
Re: Clean Linux Guest Shutdown
Ivica, I had CP SET SIGNAL SHUTDOWN 1200 specified in my autolog1 exec. I believe that my problem was that I the initial setting was CP SET SIGNAL SHUTDOWN 60 and this is what was picked up at the time of shutdown. The writing of the CP SIGNAL exec will be much cleaner and give me much more control, before I actually shutdown vm Thanks, Bob From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Ivica Brodaric Sent: Thursday, June 04, 2009 7:45 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. Are you using IMMEDIATE operand of SHUTDOWN command? IMMEDIATE doesn't mean now, it means without sending any signals. Ivica Brodaric
Re: Clean Linux Guest Shutdown
Sounds good Bob! Thank You, Terry Martin Lockheed Martin - Information Technology z/OS z/VM Systems - Performance and Tuning Cell - 443 632-4191 Work - 410 786-0386 terry.mar...@cms.hhs.gov -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Robert J McCarthy Sent: Thursday, June 04, 2009 7:56 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Thank all of you for your input. I have tested the CP SIGNAL SHUTDOWN guest WITHIN xx and it does exactly what I want. I am writing an exec to shutdown each guest individually and in phases. I think that I have run into a problem in the past due to the fact that twenty minutes is in sufficent. I currently have about 35 linux guests on this lpar. Two are very large Oracle databases (20tb and 40tb). I intend to stagger the shutdown over perhaps a 45min-1 hour timeframe. I will be testing this out this weekend, since I am upgrading the lpar from 5.3 to 5.4. Thanks, Bob -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Martin, Terry R. (CMS/CTR) (CTR) Sent: Wednesday, June 03, 2009 8:12 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown I have also written a shutdown exec to cleanly shutdown all of my z/Linux guests and log them off once they are logged off a send a message to the console stating this. This works well and I have not had any problems. The one thing I would mention is that we have some large Oracle guests with large (5TB) data bases. To ensure that the Oracle shutdown script has time to complete cleanly I make sure that my time out value is very large at least 30 minutes. Now it normally does not take nearly that long but if you add in the possibility of paging as Rob mentioned you could be pushing the envelope and if the Oracle shutdown scripts do not complete cleanly you run the very real risk of corrupting ASM and believe me that is no fun. I have been there! So if you are running these types of workloads make sure you give the shutdown process plenty of time to complete cleanly. Thank You, Terry Martin Lockheed Martin - Information Technology z/OS z/VM Systems - Performance and Tuning Cell - 443 632-4191 Work - 410 786-0386 terry.mar...@cms.hhs.gov -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 5:54 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown That makes sense ... if it doesn't just seem longer (remember, pacing takes time, too - it is just spent waiting idly instead of waiting for the work to be done) and paging during SHUTDOWN is something you really have to worry about. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Rob van der Heij Sent: Wednesday, June 03, 2009 2:21 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown On Wed, Jun 3, 2009 at 8:00 PM, Schuh, Richard rsc...@visa.com wrote: Why not CP SIGNAL SHUTDOWN ALL instead of the table. From the peanut - uh performance gallery... If you have a lot of Linux servers, the orderly shutdown may actually take quite some paging resources to complete. When the shutdown is making them all do this at once, it may take much longer than when you pace it a bit. Seen with those who set LDUBUFF wrong. Rob -- Rob van der Heij Velocity Software http://www.velocitysoftware.com/
Re: Clean Linux Guest Shutdown
On Jun 3, 2009, at 12:43 PM, Robert J McCarthy wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown - r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob Our SYSVINIT drop-in-replacement for a list-of-machines-in-autolog would do the trick. It may be overkill. Adam
Re: Clean Linux Guest Shutdown
Why not CP SIGNAL SHUTDOWN ALL instead of the table. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Wednesday, June 03, 2009 10:55 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown I have an exec I run that runs through a table and sends the command to each linux. 'CP SIGNAL SHUTDOWN ' linux ' WITHIN 60' On Wed, Jun 3, 2009 at 1:49 PM, Adam Thornton athorn...@sinenomine.netmailto:athorn...@sinenomine.net wrote: On Jun 3, 2009, at 12:43 PM, Robert J McCarthy wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob Our SYSVINIT drop-in-replacement for a list-of-machines-in-autolog would do the trick. It may be overkill. Adam -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
Re: Clean Linux Guest Shutdown
Because I also use my exec to shutdown individual Linux guests for various reasons also. On Wed, Jun 3, 2009 at 2:00 PM, Schuh, Richard rsc...@visa.com wrote: Why not CP SIGNAL SHUTDOWN ALL instead of the table. Regards, Richard Schuh -- *From:* The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] *On Behalf Of *Mark Pace *Sent:* Wednesday, June 03, 2009 10:55 AM *To:* IBMVM@LISTSERV.UARK.EDU *Subject:* Re: Clean Linux Guest Shutdown I have an exec I run that runs through a table and sends the command to each linux. 'CP SIGNAL SHUTDOWN ' linux ' WITHIN 60' On Wed, Jun 3, 2009 at 1:49 PM, Adam Thornton athorn...@sinenomine.netwrote: On Jun 3, 2009, at 12:43 PM, Robert J McCarthy wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob Our SYSVINIT drop-in-replacement for a list-of-machines-in-autolog would do the trick. It may be overkill. Adam -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317 -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
Re: Clean Linux Guest Shutdown
Richard and Mark, Am I right in assuming that CP SIGNAL will only shutdown the guests and not vm, particularily if I use the table ? I could safely test this routine on one guest without impacting other guests. Thank you, Bob From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Why not CP SIGNAL SHUTDOWN ALL instead of the table. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Wednesday, June 03, 2009 10:55 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown I have an exec I run that runs through a table and sends the command to each linux. 'CP SIGNAL SHUTDOWN ' linux ' WITHIN 60' On Wed, Jun 3, 2009 at 1:49 PM, Adam Thornton athorn...@sinenomine.net wrote: On Jun 3, 2009, at 12:43 PM, Robert J McCarthy wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob Our SYSVINIT drop-in-replacement for a list-of-machines-in-autolog would do the trick. It may be overkill. Adam -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
Re: Clean Linux Guest Shutdown
Mike, Per the linux doc for SLES10 it states that the following change be made : In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h Is there something else from a linux standpoint that needs to be done ? Thank you, Bob -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mike Walter Sent: Wednesday, June 03, 2009 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Have you updated each Linux guest so that they are registered to receive and respond to the SIGNAL SHUTDOWN service? Check your Linux distribution for the proper means to register for the SIGNAL SHUTDOWN service, and how to respond appropriately. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Robert J McCarthy bob.mccar...@custserv.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 06/03/2009 12:43 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Clean Linux Guest Shutdown I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: Clean Linux Guest Shutdown
Have you updated each Linux guest so that they are registered to receive and respond to the SIGNAL SHUTDOWN service? Check your Linux distribution for the proper means to register for the SIGNAL SHUTDOWN service, and how to respond appropriately. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Robert J McCarthy bob.mccar...@custserv.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 06/03/2009 12:43 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Clean Linux Guest Shutdown I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: Clean Linux Guest Shutdown
You could use the CP SIGNAL SHUTDOWN command before you actually did the SHUTDOWN. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Adam Thornton Sent: Wednesday, June 03, 2009 10:50 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown On Jun 3, 2009, at 12:43 PM, Robert J McCarthy wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob Our SYSVINIT drop-in-replacement for a list-of-machines-in-autolog would do the trick. It may be overkill. Adam
Re: Clean Linux Guest Shutdown
Issue Q SIGNALS, Q SHUTDOWN, Q SIGNAL SHUTDOWNTIME from your VM system and post those here. What does your /etc/zipl.conf look like? Post that too. IIRC, there wasn't anything needed on SLES 10. I for sure didn't change anything in /etc/inittab on SLES 10. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Robert J McCarthy Sent: Wednesday, June 03, 2009 11:11 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Clean Linux Guest Shutdown Mike, Per the linux doc for SLES10 it states that the following change be made : In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h Is there something else from a linux standpoint that needs to be done ? Thank you, Bob -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mike Walter Sent: Wednesday, June 03, 2009 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Have you updated each Linux guest so that they are registered to receive and respond to the SIGNAL SHUTDOWN service? Check your Linux distribution for the proper means to register for the SIGNAL SHUTDOWN service, and how to respond appropriately. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Robert J McCarthy bob.mccar...@custserv.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 06/03/2009 12:43 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Clean Linux Guest Shutdown I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: Clean Linux Guest Shutdown
On 6/3/2009 at 1:43 PM, Robert J McCarthy bob.mccar...@custserv.com wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h This is entirely unnecessary. If you leave the switch as -r it will still work. This makes it possible to have a common /etc/inittab for all architectures and still get the desired results. Mark Post
Re: Clean Linux Guest Shutdown
That assumption is correct, even if you use the ALL parameter. That causes the signal to be sent to all guests that have registered to receive it, but not to those who haven't registered. The actual shutdown is via the SHUTDOWN command which is separate from the SIGNAL command. The command, itself, does not shut the guests down, it tells them to do their own orderly shutdown. That is presumably why they registered to receive the signal. You could test on a single guest without any problems for the others or for the system. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Robert J McCarthy Sent: Wednesday, June 03, 2009 11:05 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Richard and Mark, Am I right in assuming that CP SIGNAL will only shutdown the guests and not vm, particularily if I use the table ? I could safely test this routine on one guest without impacting other guests. Thank you, Bob From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Why not CP SIGNAL SHUTDOWN ALL instead of the table. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Wednesday, June 03, 2009 10:55 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown I have an exec I run that runs through a table and sends the command to each linux. 'CP SIGNAL SHUTDOWN ' linux ' WITHIN 60' On Wed, Jun 3, 2009 at 1:49 PM, Adam Thornton athorn...@sinenomine.netmailto:athorn...@sinenomine.net wrote: On Jun 3, 2009, at 12:43 PM, Robert J McCarthy wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob Our SYSVINIT drop-in-replacement for a list-of-machines-in-autolog would do the trick. It may be overkill. Adam -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
Re: Clean Linux Guest Shutdown
Marcy, Attached are the responses that you requested : q SIGNALS Signalled Timeout UseridSignalSignal Status By Remaining DFNORVAR SHUTDOWN Enabled - - ZORACLE1 SHUTDOWN Enabled - - DFNREPSHUTDOWN Enabled - - NSBDX02 SHUTDOWN Enabled - - NSBDX01 SHUTDOWN Enabled - - TDCPWK01 SHUTDOWN Enabled - - TDCPM01 SHUTDOWN Enabled - - TQRTOR01 SHUTDOWN Enabled - - NDRTWB01 SHUTDOWN Enabled - - IFNETLSHUTDOWN Enabled - - IFNILOG SHUTDOWN Enabled - - IFNINFO SHUTDOWN Enabled - - IFNORSTG SHUTDOWN Enabled - - IFNORSTO SHUTDOWN Enabled - - NPSTOR01 SHUTDOWN Enabled - - TFNPOR01 SHUTDOWN Enabled - - ZORACLE3 SHUTDOWN Enabled - - DFNILOG SHUTDOWN Enabled - - DFNINFO SHUTDOWN Enabled - - ZORACLE5 SHUTDOWN Enabled - - ZORACLE7 SHUTDOWN Enabled - - ZORACLE6 SHUTDOWN Enabled - - ZORACLE4 SHUTDOWN Enabled - - ZORACLE8 SHUTDOWN Enabled - - ZORACLE2 SHUTDOWN Enabled - - DFNWEBSHUTDOWN Enabled - - DFNETLSHUTDOWN Enabled - - DFNORWAR SHUTDOWN Enabled - - DFNORRUL SHUTDOWN Enabled - - DFNORSTG SHUTDOWN Enabled - - ZORACLEA SHUTDOWN Enabled - - ZORACLE9 SHUTDOWN Enabled - - Ready; T=0.01/0.01 14:21:34 Q shutdown System shutdown time: 30 seconds Ready; T=0.01/0.01 14:22:33 q signal shutdowntime System default shutdown signal timeout: 1200 seconds Ready; T=0.01/0.01 14:23:09 The contents of one of the zipl files is as follows: dfnorvar:~ # cat /etc/zipl.conf # Modified by YaST2. Last modification on Tue Mar 10 14:01:45 UTC 2009 [defaultboot] defaultmenu = menu :menu default = 1 prompt = 1 target = /boot/zipl timeout = 10 1 = ipl 2 = Failsafe ###Don't change this comment - YaST2 identifier: Original name: ipl### [ipl] image = /boot/image target = /boot/zipl ramdisk = /boot/initrd,0x100 parameters = root=/dev/dasda1 TERM=dumb ###Don't change this comment - YaST2 identifier: Original name: failsafe### [Failsafe] image = /boot/image-2.6.16.60-0.21-default target = /boot/zipl ramdisk = /boot/initrd-2.6.16.60-0.21-default,0x100 parameters = root=/dev/dasda1 TERM=dumb 3 dfnorvar:~ # Thank you, Bob -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Marcy Cortes Sent: Wednesday, June 03, 2009 2:16 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Issue Q SIGNALS, Q SHUTDOWN, Q SIGNAL SHUTDOWNTIME from your VM system and post those here. What does your /etc/zipl.conf look like? Post that too. IIRC, there wasn't anything needed on SLES 10. I for sure didn't change anything in /etc/inittab on SLES 10. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Robert J McCarthy Sent: Wednesday, June 03, 2009 11:11 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Clean Linux Guest Shutdown Mike, Per the linux doc for SLES10 it states that the following change be made : In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h Is there something else from a linux standpoint that needs to be done ? Thank you, Bob -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mike Walter Sent: Wednesday, June 03, 2009 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Have
Re: Clean Linux Guest Shutdown
In /etc/zipl.conf, change parameters = root=/dev/dasda1 TERM=dumb To parameters = root=/dev/dasda1 TERM=dumb vmpoff=LOGOFF vmhalt=LOGOFF Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.
Re: Clean Linux Guest Shutdown
On 6/3/2009 at 2:52 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: In /etc/zipl.conf, change parameters = root=/dev/dasda1 TERM=dumb To parameters = root=/dev/dasda1 TERM=dumb vmpoff=LOGOFF vmhalt=LOGOFF This is also unnecessary. It just causes the guest to log itself off, which z/VM doesn't really care about one way or the other. Mark Post
Re: Clean Linux Guest Shutdown
On 6/3/2009 at 2:44 PM, Robert J McCarthy bob.mccar...@custserv.com wrote: -snip- Q shutdown System shutdown time: 30 seconds Ready; T=0.01/0.01 14:22:33 q signal shutdowntime System default shutdown signal timeout: 1200 seconds This raises a question for me. Is the 30 second System shutdown time added to the 1200 second System default shutdown signal timeout to get the amount of time z/VM will wait before doing the shutdown? (I seem to remember reading that somewhere.) In any case, I really just think it's a case of your guests need more than that amount of time to all shut down cleanly. If it's only a few here and there, and they're different each time, I would say you've got things set up correctly, you're just not waiting long enough. Mark Post
Re: Clean Linux Guest Shutdown
Hmm. OK. Bob, you are getting 1-2 minutes and not the 1200? Everything else you have set up looks just like what we have set up and we are getting our whole 1200. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Post Sent: Wednesday, June 03, 2009 12:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Clean Linux Guest Shutdown On 6/3/2009 at 2:52 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: In /etc/zipl.conf, change parameters = root=/dev/dasda1 TERM=dumb To parameters = root=/dev/dasda1 TERM=dumb vmpoff=LOGOFF vmhalt=LOGOFF This is also unnecessary. It just causes the guest to log itself off, which z/VM doesn't really care about one way or the other. Mark Post
Re: Clean Linux Guest Shutdown
Be aware CP SIGNAL ALL tells all the non-linux guests like the Shared File System servers VMSERVS,U,R to shutdown. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 2:35 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown That assumption is correct, even if you use the ALL parameter. That causes the signal to be sent to all guests that have registered to receive it, but not to those who haven't registered. The actual shutdown is via the SHUTDOWN command which is separate from the SIGNAL command. The command, itself, does not shut the guests down, it tells them to do their own orderly shutdown. That is presumably why they registered to receive the signal. You could test on a single guest without any problems for the others or for the system. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Robert J McCarthy Sent: Wednesday, June 03, 2009 11:05 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Richard and Mark, Am I right in assuming that CP SIGNAL will only shutdown the guests and not vm, particularily if I use the table ? I could safely test this routine on one guest without impacting other guests. Thank you, Bob From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Why not CP SIGNAL SHUTDOWN ALL instead of the table. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Wednesday, June 03, 2009 10:55 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown I have an exec I run that runs through a table and sends the command to each linux. 'CP SIGNAL SHUTDOWN ' linux ' WITHIN 60' On Wed, Jun 3, 2009 at 1:49 PM, Adam Thornton athorn...@sinenomine.netmailto:athorn...@sinenomine.net wrote: On Jun 3, 2009, at 12:43 PM, Robert J McCarthy wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob Our SYSVINIT drop-in-replacement for a list-of-machines-in-autolog would do the trick. It may be overkill. Adam -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317 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.
Re: Clean Linux Guest Shutdown
True -- VM doesn't care whether a guest logs off in response to a SIGNAL SHUTDOWN. But VM sysprogs may care. It becomes clear when searching the VM console log that the Linux actually did actually complete graceful shutdown. Staying disconnected doesn't prove anything. (But I think that I'll add a CP QUERY SIGNALS to the end of our SHUTDOWN EXEC). If you're looking at the VM console log to determine if guests are getting shutdown within the allotted time, that saves time searching Linux syslogs to get the same information. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Mark Post mp...@novell.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 06/03/2009 01:59 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Clean Linux Guest Shutdown On 6/3/2009 at 2:52 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: In /etc/zipl.conf, change parameters = root=/dev/dasda1 TERM=dumb To parameters = root=/dev/dasda1 TERM=dumb vmpoff=LOGOFF vmhalt=LOGOFF This is also unnecessary. It just causes the guest to log itself off, which z/VM doesn't really care about one way or the other. Mark Post The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: Clean Linux Guest Shutdown
That might not be a bad thing when you are getting ready to shut the system down. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Romanowski, John (OFT) Sent: Wednesday, June 03, 2009 12:22 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Be aware CP SIGNAL ALL tells all the non-linux guests like the Shared File System servers VMSERVS,U,R to shutdown. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 2:35 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown That assumption is correct, even if you use the ALL parameter. That causes the signal to be sent to all guests that have registered to receive it, but not to those who haven't registered. The actual shutdown is via the SHUTDOWN command which is separate from the SIGNAL command. The command, itself, does not shut the guests down, it tells them to do their own orderly shutdown. That is presumably why they registered to receive the signal. You could test on a single guest without any problems for the others or for the system. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Robert J McCarthy Sent: Wednesday, June 03, 2009 11:05 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Richard and Mark, Am I right in assuming that CP SIGNAL will only shutdown the guests and not vm, particularily if I use the table ? I could safely test this routine on one guest without impacting other guests. Thank you, Bob From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Why not CP SIGNAL SHUTDOWN ALL instead of the table. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Wednesday, June 03, 2009 10:55 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown I have an exec I run that runs through a table and sends the command to each linux. 'CP SIGNAL SHUTDOWN ' linux ' WITHIN 60' On Wed, Jun 3, 2009 at 1:49 PM, Adam Thornton athorn...@sinenomine.netmailto:athorn...@sinenomine.net wrote: On Jun 3, 2009, at 12:43 PM, Robert J McCarthy wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob Our SYSVINIT drop-in-replacement for a list-of-machines-in-autolog would do the trick. It may be overkill. Adam -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317 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.
Re: Clean Linux Guest Shutdown
Mark Post wrote: On 6/3/2009 at 2:52 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: In /etc/zipl.conf, change parameters = root=/dev/dasda1 TERM=dumb To parameters = root=/dev/dasda1 TERM=dumb vmpoff=LOGOFF vmhalt=LOGOFF This is also unnecessary. It just causes the guest to log itself off, which z/VM doesn't really care about one way or the other. Mark Post It may be unnecessary, but I like to see them go away when they are finished shutting down. I also prefer my desktop to actually turn off instead of displaying a message saying you can power off now but maybe I am . :) -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us
Re: Clean Linux Guest Shutdown
I'm with you Stephen, I like to see them logoff also. Then I'm really sure they are down. On Wed, Jun 3, 2009 at 4:18 PM, Stephen Frazier ste...@doc.state.ok.uswrote: It may be unnecessary, but I like to see them go away when they are finished shutting down. I also prefer my desktop to actually turn off instead of displaying a message saying you can power off now but maybe I am . :) -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
Re: Clean Linux Guest Shutdown
Dude, you need to run Linux on your desktop ;-) Scott It may be unnecessary, but I like to see them go away when they are finished shutting down. I also prefer my desktop to actually turn off instead of displaying a message saying you can power off now but maybe I am . :) -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us
Re: Clean Linux Guest Shutdown
On 6/3/2009 at 4:18 PM, Stephen Frazier ste...@doc.state.ok.us wrote: -snip- It may be unnecessary, but I like to see them go away when they are finished shutting down. I also prefer my desktop to actually turn off instead of displaying a message saying you can power off now but maybe I am . :) All of which has nothing to do with trying to figure out the OP's problem. I didn't say the parms were useless or undesirable, but they are completely unrelated to what he's experiencing. Mark Post
Re: Clean Linux Guest Shutdown
On Wed, Jun 3, 2009 at 8:00 PM, Schuh, Richard rsc...@visa.com wrote: Why not CP SIGNAL SHUTDOWN ALL instead of the table. From the peanut - uh performance gallery... If you have a lot of Linux servers, the orderly shutdown may actually take quite some paging resources to complete. When the shutdown is making them all do this at once, it may take much longer than when you pace it a bit. Seen with those who set LDUBUFF wrong. Rob -- Rob van der Heij Velocity Software http://www.velocitysoftware.com/
Re: Clean Linux Guest Shutdown
That makes sense ... if it doesn't just seem longer (remember, pacing takes time, too - it is just spent waiting idly instead of waiting for the work to be done) and paging during SHUTDOWN is something you really have to worry about. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Rob van der Heij Sent: Wednesday, June 03, 2009 2:21 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown On Wed, Jun 3, 2009 at 8:00 PM, Schuh, Richard rsc...@visa.com wrote: Why not CP SIGNAL SHUTDOWN ALL instead of the table. From the peanut - uh performance gallery... If you have a lot of Linux servers, the orderly shutdown may actually take quite some paging resources to complete. When the shutdown is making them all do this at once, it may take much longer than when you pace it a bit. Seen with those who set LDUBUFF wrong. Rob -- Rob van der Heij Velocity Software http://www.velocitysoftware.com/
Re: Clean Linux Guest Shutdown
That might not be a bad thing when you are getting ready to shut the system down. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Romanowski, John (OFT) Sent: Wednesday, June 03, 2009 12:22 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Be aware CP SIGNAL ALL tells all the non-linux guests like the Shared File System servers VMSERVS,U,R to shutdown. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 2:35 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown That assumption is correct, even if you use the ALL parameter. That causes the signal to be sent to all guests that have registered to receive it, but not to those who haven't registered. The actual shutdown is via the SHUTDOWN command which is separate from the SIGNAL command. The command, itself, does not shut the guests down, it tells them to do their own orderly shutdown. That is presumably why they registered to receive the signal. You could test on a single guest without any problems for the others or for the system. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Robert J McCarthy Sent: Wednesday, June 03, 2009 11:05 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Richard and Mark, Am I right in assuming that CP SIGNAL will only shutdown the guests and not vm, particularily if I use the table ? I could safely test this routine on one guest without impacting other guests. Thank you, Bob From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Why not CP SIGNAL SHUTDOWN ALL instead of the table. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Wednesday, June 03, 2009 10:55 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown I have an exec I run that runs through a table and sends the command to each linux. 'CP SIGNAL SHUTDOWN ' linux ' WITHIN 60' On Wed, Jun 3, 2009 at 1:49 PM, Adam Thornton athorn...@sinenomine.netmailto:athorn...@sinenomine.net wrote: On Jun 3, 2009, at 12:43 PM, Robert J McCarthy wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob Our SYSVINIT drop-in-replacement for a list-of-machines-in-autolog would do the trick. It may be overkill. Adam -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317 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.
Re: Clean Linux Guest Shutdown
I have also written a shutdown exec to cleanly shutdown all of my z/Linux guests and log them off once they are logged off a send a message to the console stating this. This works well and I have not had any problems. The one thing I would mention is that we have some large Oracle guests with large (5TB) data bases. To ensure that the Oracle shutdown script has time to complete cleanly I make sure that my time out value is very large at least 30 minutes. Now it normally does not take nearly that long but if you add in the possibility of paging as Rob mentioned you could be pushing the envelope and if the Oracle shutdown scripts do not complete cleanly you run the very real risk of corrupting ASM and believe me that is no fun. I have been there! So if you are running these types of workloads make sure you give the shutdown process plenty of time to complete cleanly. Thank You, Terry Martin Lockheed Martin - Information Technology z/OS z/VM Systems - Performance and Tuning Cell - 443 632-4191 Work - 410 786-0386 terry.mar...@cms.hhs.gov -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 5:54 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown That makes sense ... if it doesn't just seem longer (remember, pacing takes time, too - it is just spent waiting idly instead of waiting for the work to be done) and paging during SHUTDOWN is something you really have to worry about. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Rob van der Heij Sent: Wednesday, June 03, 2009 2:21 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown On Wed, Jun 3, 2009 at 8:00 PM, Schuh, Richard rsc...@visa.com wrote: Why not CP SIGNAL SHUTDOWN ALL instead of the table. From the peanut - uh performance gallery... If you have a lot of Linux servers, the orderly shutdown may actually take quite some paging resources to complete. When the shutdown is making them all do this at once, it may take much longer than when you pace it a bit. Seen with those who set LDUBUFF wrong. Rob -- Rob van der Heij Velocity Software http://www.velocitysoftware.com/
