Marcy,
It was my testing that was flawed. I was able to reproduce the problem on a
SLES 11 SP3 system (when logged onto the console). I went back to my SLES 12
system and issued 'signal shutdown ...' from another guest (without being
logged onto the console) and the SLES 12 guest machine was logged off when
linux terminated.
The only thing that I modified in SLES 12 for this to work was to issue command
chshut poff vmcmd LOGOFF
Thank you! I've been working on this 'non-issue' off and on for a few weeks
now.
Harley
-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Marcy
Cortes
Sent: Monday, January 05, 2015 12:49 PM
To: [email protected]
Subject: Re: Having trouble getting SLES 12 to logoff the z/VM guest when it
shuts down
And from Usage note 2 in "HELP CP SIGNAL"
2. When the signal times out or the user machine indicates that it has
terminated operation, whichever occurs first, the virtual machine is
logged off if it has been disconnected.
-----Original Message-----
From: Cortes, Marcy D.
Sent: Monday, January 05, 2015 10:47 AM
To: [email protected]
Subject: RE: [LINUX-390] Having trouble getting SLES 12 to logoff the z/VM
guest when it shuts down
That's behavior consistent with sles 11 too.
If you are logged into the virtual machine, you don't get logged off.
You do if you are disconnected.
Marcy
-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Linker
Harley - hlinke
Sent: Monday, January 05, 2015 8:26 AM
To: [email protected]
Subject: Re: [LINUX-390] Having trouble getting SLES 12 to logoff the z/VM
guest when it shuts down
Peter,
Thanks for the tip but that didn't work. I was logged into PuTTY to make the
change you recommended. I logged into my guest machine on z/VM and connected
to the console for lnxadmin. From my guest machine I issued 'signal shutdown
lnxadmin winthin 300'. The PuTTY session immediately disconnected and there
were no messages issued to the lnxadmin console. From the guest where I issued
'signal shutdown...' I displayed the logged on guests and lnxadmin was still
logged on. I tried the 'signal shutdown...' a few times and no messages were
written to the lnxadmin console - linux just stopped.
I booted Linux again, logged on with PuTTY, and issued 'reboot'. Linux shut
down and the last message written to the lnxadmin console was the disabled wait
PSW.
Harley
-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Peter
Webb, Toronto Transit Commission
Sent: Monday, January 05, 2015 10:00 AM
To: [email protected]
Subject: Re: Having trouble getting SLES 12 to logoff the z/VM guest when it
shuts down
Hi Harley,
I think what you want to do is the following:
cd /lib/systemd/system
ln -f -s shutdown.target ctrl-alt-del.target
This changes the symlink ctrl-alt-del.target from reboot.target to
shutdown.target, at least on Fedora 15. I am assuming that SLES 12 is similar.
Peter
-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Linker
Harley - hlinke
Sent: December 19, 2014 12:20 PM
To: [email protected]
Subject: Having trouble getting SLES 12 to logoff the z/VM guest when it shuts
down
Hi,
I am having trouble configuring SLES 12 to logoff the z/VM guest when it shuts
down (in some situations). In SLES 11 I updated the parameters in
/etc/zipl.conf and specified 'vmpoff=LOGOFF' and also modified the ctrl-alt-del
line in /etc/inittab from ca::ctrlaltdel:/sbin/shutdown -r -t 4 now
to
ca::ctrlaltdel:/sbin/shutdown -h -t 4 now
The z/VM guest is automatically logged off with the above if the 'shutdown
-h..' command is issued from Linux or if 'signal shutdown guest-name within
...' from an authorized z/VM guest. By automatically logged off I mean that
the z/VM login screen is displayed if you are connected to the guests console.
With SLES 12 /etc/inittab no longer exists - because systemd is now used where
systemv was used in prior releases. I modified the zipl parameters, which were
incorporated into the grub2 parameters, and specified 'vmpoff=LOGOFF'. Issuing
Linux's 'shutdown -h...' command causes the guest to log off from z/VM.
If I issue the 'signal shutdown..' command Linux shuts down but the guest is
not logged off - the last line on the console is the disabled wait PSW
HCPGIR450W CP entered; disabled wait PSW 00020001 80000000 00000000 00000FFF I
need for the guest to log off when a 'signal shutdown' is issued. My
production system only uses mainframe dasd (mirrored) and we shutdown all
production servers (via a REXX EXEC) just after midnight on Friday night to get
a clean backup of the dasd. After the servers come down, Operations runs a
batch job on z/OS to break the mirrors and when this job completes (after a few
minutes) they reply to a prompt issued by the REXX exec which then boots all
of the servers. The mirror for each volume is reconnected when the FDR backup
on z/OS completes for that volume. If the guest does not log off, the
'xautolog guest-name' command fails xautolog lnxadmin HCPLGA054E Already logged
on LDEV L0005
A Novell technician pointed me at an IBM manual, "Device Drivers, Features, and
Commands on SUSE Linux Enterprise Server 12", which mentions a relatively new
command called chshut. It aappears that it was introduced with one of the SLES
11 Service Packs. I've issued the following chshut commands but a 'signal
shutdown' still does not cause the guest to log off:
chshut halt vmcmd LOGOFF
chshut poff VMCMD LOGOFF
After issuing the commands I display the settings with 'lsshut'. It shows
Trigger Action
========================
Halt vmcmd ("LOGOFF")
Power off vmcmd ("LOGOFF")
Reboot reipl
Restart kdump,stop
Panic kdump,stop
When I reboot the server the Action for the 'Halt' setting once again is set to
'stop'.
I have also tried to modify how systemd handles the 'signal shutdown' and this
change also does not log the guest off. Maybe I'm not doing something
correctly? These are the commands that I've issued (which I found via Google
searches).
cd /usr/lib/systemd/system
rm ctrl-alt-del.target
ln -s poweroff.target ctrl-alt-del.target rm halt.target ln -s halt.target
ctrl-alt-del.target systemctl daemon-reload
I've read about systemd and found that a better way may be to copy files to
/etc/systemd/system and make my changes there (so that they aren't 'lost'
if/when maintenance is applied to systemd). I will do that once I get the
shutdown to work properly.
My SLES 12 server has had maintenance applied up to around 10:00 AM on 12/17.
It is running on a z/VM 6.3 non-SSI system.
Any ideas?
Harley Linker
HARLEY LINKER JR.
Sr. Systems Programmer (z/Linux, z/OS, z/VM)
[Acxiom_IT_color]
Acxiom Corporation
EML [email protected]<mailto:[email protected]>
TEL +1 630.944.5111
3333 Finley Road, 8th Floor - NW, Downers Grove, IL, 60515, USA
www.acxiomit.com<http://www.acxiomit.com/>
[Friend Us on Facebook]<http://www.facebook.com/acxiomcorp> [Link Us on
LinkedIn] <http://www.linkedin.com/groupRegistration?gid=2901735> [Follow Us
on Twitter] <http://twitter.com/acxiom>
***************************************************************************
The information contained in this communication is confidential, is intended
only for the use of the recipient named above, and may be legally privileged.
If the reader of this message is not the intended recipient, you are hereby
notified that any dissemination, distribution or copying of this communication
is strictly prohibited.
If you have received this communication in error, please resend this
communication to the sender and delete the original message or any copy of it
from your computer system.
Thank You.
****************************************************************************
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit http://wiki.linuxvm.org/
The information transmitted is intended only for the person or entity to which
it is addressed and may contain confidential and/or privileged material. Any
review retransmission dissemination or other use of or taking any action in
reliance upon this information by persons or entities other than the intended
recipient or delegate is strictly prohibited. If you received this in error
please contact the sender and delete the material from any computer. The
integrity and security of this message cannot be guaranteed on the Internet.
The sender accepts no liability for the content of this e-mail or for the
consequences of any actions taken on the basis of information provided. The
recipient should check this e-mail and any attachments for the presence of
viruses. The sender accepts no liability for any damage caused by any virus
transmitted by this e-mail. This disclaimer is property of the TTC and must
not be altered or circumvented in any manner.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit http://wiki.linuxvm.org/
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit http://wiki.linuxvm.org/
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit http://wiki.linuxvm.org/
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
