A good idea for future reference is keep an IPL'able Linux kernel with
you on a flash drive (with instructions on how to load it, since most of
us rarely punch/IPL kernel's these days).  Worst case, if your
production Linux systems won't boot (for any reason) you can always
punch the kernel to the VM reader of the Linux guest and IPL it and use
that little system to diagnose/repair your production system.

-Mike 

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Peter E. Abresch Jr. - at Pepco
Sent: Tuesday, April 08, 2008 9:40 AM
To: [email protected]
Subject: Re: Linux Guest recovery at Sungard not going well

We have files,dns but one of the changes required by CAesm was the
following:

passwd: CA_esm compat
group:  CA_esm compat

I am going to do some testing today now that I more relaxed.

Peter





"Stricklin, Raymond J" <[EMAIL PROTECTED]> Sent by: Linux
on 390 Port <[email protected]>
04/07/2008 07:42 PM
Please respond to
Linux on 390 Port <[email protected]>


To
[email protected]
cc

Subject
Re: Linux Guest recovery at Sungard not going well






You know, I've seen this kind of thing result from having, for example,
dns (or nis) listed before files in nsswitch.conf, and then the dns
server becomes unavailable.

right:
                                 hosts:          files dns

wrong:

                                 hosts:          dns files

Note this effect can be duplicated (when the dns server becomes
unavailable) if you have fully-qualified domain names listed in certain
configuration files and only the short name (or no name at all!) in
/etc/hosts, even if nsswitch.conf is right.

ok
r.

> -----Original Message-----
> From: Ron Foster at Baldor-IS [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 07, 2008 3:11 PM
> To: [email protected]
> Subject: Re: Linux Guest recovery at Sungard not going well
>
> Peter,
>
> It bothers me that you brought up a SLES10 system that did not have an

> NFS mount and
> it still did not give you a logon prompt.   The idea of setting up a
> bogus  NFS server
> and forcing permission denied messages just to speed up processing 
> would not help in this situation.
>
> Do you have any idea how far it is getting before you hang?
> Is it permissible for you all to "cheat" and have someone IPL a system

> at your data center and compare messages?
>
> Is it permissible to download the installation media from Novell and 
> construct you a system to boot the starter system from?  We normally 
> use NFS, but the book says that you can boot the starter system from 
> smb and non-Microsoft FTP.
> (If you
> brought laptops with you, you might be able to share the install 
> media.
> I have not
> done it.)
>
> The idea about forcing Linux to not find all of it's files might be 
> useful.  If you could get a single user command prompt, it might be 
> helpful.  You would have to know which filesystem is on what minidisk 
> though.
>
> Hope this helps,
> Ron
>
>
>
> Peter E. Abresch Jr. - at Pepco wrote:
> > There is only one NFS background mount and yes, we waited for 45 
> > minutes but no timeout and no prompt. We do not have our
> installation
> > media up there but we do have some other Linux systems that
> we backup
> > but do not normally restore, but unfortunately they all
> have the NFS
> > background mount except for one. I might have to recover that one, 
> > link some DASD, setroot, and chkconfig nfs off, and hope that my 
> > problem really was NFS. I detached the osa from the vm
> guest and hoped
> > that will cause some early timeouts or failures? Nothing! I
> recovered
> > a SLES10 that does not use NFS and it IPLed fine except
> again, no prompt.
> >
> > As far as backing up, we shut all our Linux guests down, our z/VM 
> > system down, deactivate z/VM, flash the DASD, activate
> z/VM, IPL, and
> > start our guest. We then back up the flashed DASD from z/OS
> using FDR Full Volume.
> >
> > Is it something in z/VM?
> >
> > Peter
> >
> >
> >
> >
> >
> > Ron Foster at Baldor-IS <[EMAIL PROTECTED]> Sent by: Linux on 390 
> > Port <[email protected]>
> > 04/07/2008 04:37 PM
> > Please respond to
> > Linux on 390 Port <[email protected]>
> >
> >
> > To
> > [email protected]
> > cc
> >
> > Subject
> > Re: Linux Guest recovery at Sungard not going well
> >
> >
> >
> >
> >
> >
> > Peter,
> >
> > Did you bring a copy of your installation media?
> > Could you boot it and then look at your restored system?
> >
> > How many NFS mounts are there?  Are you saying you have waited 45 
> > minutes and not gotten a message indicating that one of your NFS 
> > mounts has been backgrounded or timed out?
> >
> > Have you tried setting up some system with the same IP
> address as your
> > NFS server, but not running NFS.
> > That way instead of timing out, you can get something like
> connection
> > request rejected.  (I forget the exact message).  In some
> cases, this
> > can hurry things along.
> >
> > By the way, how did you backup and restore?
> >
> > Ron
> >
> > Peter E. Abresch Jr. - at Pepco wrote:
> >
> >> We are at Sungard performing our yearly contingency test.
> Normally we
> >> restore our Linux DASD and IPL our Linux guest as a guest from 
> >> Sungard?s z/VM system. We then logon to our Linux guest from z/VM, 
> >> change the network configuration, reboot, and we are good to go.
> >> Usually we have to wait 10 minutes for NFS to timeout before 
> >> receiving the Linux LOGON
> >>
> > prompt
> >
> >> on the VM console. This has worked for us many times.
> >>
> >> However, this year, we never receive the LINUX logon prompt. Linux 
> >> IPLs fine, everything seems ok, however, we do not receive
> the Linux
> >> logon prompt. We wait as long as 45 minutes but never see
> the prompt.
> >> Without the prompt, we cannot logon and make any changes at all?
> >>
> >> The z/VM directory used at Sungard is the same that we
> have used in
> >> previous tests. Does anyone have any ideas or suggestions.
> >>
> >> Peter
> >> This Email message and any attachment may contain
> information that is
> >> proprietary, legally privileged, confidential and/or subject to
> >>
> > copyright
> >
> >> belonging to Pepco Holdings, Inc. or its affiliates ("PHI").  This 
> >> Email
> >>
> > is
> >
> >> intended solely for the use of the person(s) to which it
> is addressed.
> >>
> > If
> >
> >> you are not an intended recipient, or the employee or agent 
> >> responsible
> >>
> > for
> >
> >> delivery of this Email to the intended recipient(s), you are hereby
> >>
> > notified
> >
> >> that any dissemination, distribution or copying of this Email is
> >>
> > strictly
> >
> >> prohibited.  If you have received this message in error, please
> >>
> > immediately
> >
> >> notify the sender and permanently delete this Email and
> any copies.
> >> PHI policies expressly prohibit employees from making defamatory or
> >>
> > offensive
> >
> >> statements and infringing any copyright or any other legal right by
> >>
> > Email
> >
> >> communication.  PHI will not accept any liability in
> respect of such
> >> communications.
> >>
> >>
> ---------------------------------------------------------------------
> >> - 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 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
> >
> >
> > This Email message and any attachment may contain
> information that is
> > proprietary, legally privileged, confidential and/or subject to 
> > copyright belonging to Pepco Holdings, Inc. or its
> affiliates ("PHI").
> > This Email is intended solely for the use of the person(s)
> to which it
> > is addressed.  If you are not an intended recipient, or the
> employee
> > or agent responsible for delivery of this Email to the intended 
> > recipient(s), you are hereby notified that any dissemination, 
> > distribution or copying of this Email is strictly
> prohibited.  If you
> > have received this message in error, please immediately notify the 
> > sender and permanently delete this Email and any copies.
> PHI policies
> > expressly prohibit employees from making defamatory or offensive 
> > statements and infringing any copyright or any other legal right by 
> > Email communication.  PHI will not accept any liability in
> respect of such communications.
> >
> >
> ----------------------------------------------------------------------
> > 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 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 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


This Email message and any attachment may contain information that is
proprietary, legally privileged, confidential and/or subject to
copyright belonging to Pepco Holdings, Inc. or its affiliates ("PHI").
This Email is intended solely for the use of the person(s) to which it
is addressed.  If you are not an intended recipient, or the employee or
agent responsible for delivery of this Email to the intended
recipient(s), you are hereby notified that any dissemination,
distribution or copying of this Email is strictly prohibited.  If you
have received this message in error, please immediately notify the
sender and permanently delete this Email and any copies.  PHI policies
expressly prohibit employees from making defamatory or offensive
statements and infringing any copyright or any other legal right by
Email communication.  PHI will not accept any liability in respect of
such communications.

----------------------------------------------------------------------
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 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

Reply via email to