Transferring a console session with z/VM Version 6.2
z/VM Transferring a console session We can take over a session, such as the operator?s console by logon userid here. Can we transfer a session such as the operator?s console to another device? Another words, give it back without intervention from the remote side? 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 lists...@vm.marist.edu 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/
Re: Another SLES11 SMT mirroring repository question
To install these updates from SLES11-SP2-Core, I found out that I can do the following: YaST online updates, repository tab, right click in list in the right panel and choose: All in this list Install when a newer version is available. This will install all the remaining SP2 package updates. Is this the correct process? I am use to seeing all patches and updates available from Online Updates or does everyone simple use zypper up? This seems to more of a procedural issue on my end. Comments and user experiences are always welcome. Thanks. 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 lists...@vm.marist.edu 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/
Re: Another SLES11 SMT mirroring repository question
| SLES11-SP2-Core | yast2-registration | 2.17.35.3-0.4.2.1 | 2.17.35.3-0.5.87 | noarch v | SLES11-SP2-Core | yast2-registration-branding-SLE | 2.17.35.3-0.4.2.1 | 2.17.35.3-0.5.87 | noarch v | SLES11-SP2-Core | yast2-repair| 2.17.7-1.48| 2.17.11-0.5.109| noarch v | SLES11-SP2-Core | yast2-restore | 2.17.4-0.1.79| 2.17.6-0.7.3 | noarch v | SLES11-SP2-Core | yast2-runlevel | 2.17.7-0.2.41| 2.17.9-0.7.3 | noarch v | SLES11-SP2-Core | yast2-s390 | 2.17.16-0.2.46 | 2.17.28-0.5.163| s390x v | SLES11-SP2-Core | yast2-samba-client | 2.17.18-0.5.5| 2.17.21-0.5.186| noarch v | SLES11-SP2-Core | yast2-samba-server | 2.17.11-0.2.72 | 2.17.13-0.7.5 | noarch v | SLES11-SP2-Core | yast2-schema| 2.17.4-1.52| 2.17.5-0.5.42 | s390x v | SLES11-SP2-Core | yast2-security | 2.17.14-0.2.38 | 2.17.15-0.5.214| noarch v | SLES11-SP2-Core | yast2-theme-SLE | 2.17.19-0.2.17 | 2.17.27-0.18.9 | noarch v | SLES11-SP2-Core | yast2-trans-en_US | 2.17.26-0.2.5| 2.17.32-0.5.1 | noarch v | SLES11-SP2-Core | yast2-transfer | 2.16.2-0.1.126 | 2.16.3-0.5.133 | s390x v | SLES11-SP2-Core | yast2-update| 2.17.20-0.2.52 | 2.17.23-0.5.40 | s390x v | SLES11-SP2-Core | yast2-users | 2.17.43.1-0.3.1 | 2.17.51-0.5.166| s390x v | SLES11-SP2-Core | zip | 2.32-75.21| 3.0-4.7.1 | s390x From: Marcy Cortes marcy.d.cor...@wellsfargo.com To: LINUX-390@vm.marist.edu, Date: 09/07/2012 04:10 PM Subject:Re: Another SLES11 SMT mirroring repository question Sent by:Linux on 390 Port LINUX-390@vm.marist.edu Also , what do zypper lr and zypper lu have to say? Marcy -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy Cortes Sent: Friday, September 07, 2012 12:44 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Another SLES11 SMT mirroring repository question I also have SLES11-SP2-Extension-Store SLES11-Extras What do you show for zypper products Marcy -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Peter E. Abresch Jr. - at Pepco Sent: Friday, September 07, 2012 8:12 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Another SLES11 SMT mirroring repository question We upgraded to SLES11-SP2 from our local SMT server repositories. We are mirroring the following locally: | Yes | 5 | nu | SLES11-SP1-Pool | sle-11-s390x | SLES11-SP1-Pool for sle-11-s390x | Yes | No | | Yes | 6 | nu | SLES11-SP1-Updates| sle-11-s390x | SLES11-SP1-Updates for sle-11-s390x| Yes | No | | Yes | 7 | nu | SLES11-SP2-Core | sle-11-s390x | SLES11-SP2-Core for sle-11-s390x | Yes | No | | Yes | 8 | nu | SLES11-SP2-Updates| sle-11-s390x | SLES11-SP2-Updates for sle-11-s390x| Yes | No | '-++--+---+--++-+-' However, when we run sam --spreport it shows that many packages might still be out of date? When we enter YaST2 Online Updates, we see no updates to these packages. This leads me to think that maybe I am not mirroring within SMT all the repositories that I should. Can someone confirm which repositories we should mirror to keep SLES11 up to date? Thanks as always. Peter Supportability Analysis Module 0.8.4 *** Report by 'sam --spreport' *** Installed versions: suse-sam-data0.8.4-0.5.2 satsolver-tools 0.17.5-0.5.2 suse-sam 0.8.4-0.7.1 perl-satsolver 0.44.5-0.5.8 *** Installed products: 2 (known vendors: 2) System architecture: s390x Baseproduct: SUSE_SLES.prod sle-smt.prod: summary: Subscription Management Tool for SUSE Linux Enterprise 11 SP2 name version: sle-smt 11.2 SP, release: 2 (none) arch: s390x repository: obs://build.suse.de/SUSE:SLE-11-SP2:GA:Products:Test/standard repository:obs://build.suse.de/SUSE:SLE-11-SP2:GA/standard repository:obs://build.suse.de/SUSE:SLE-11-SP1:Update/snapshot-SP2 repository:obs://build.suse.de/SUSE:SLE-11-SP1:GA/standard repository:obs://build.suse.de/SUSE:SLE-11:Update/snapshot-SP2 repository:obs://build.suse.de/SUSE:SLE-11:GA/standard SUSE_SLES.prod: summary: SUSE Linux Enterprise Server 11 SP2 name version: SUSE_SLES 11.2 SP, release: 2 (none) arch: s390x repository:obs://build.suse.de/SUSE:SLE-11-SP2:Update/standard repository
Another SLES11 SMT mirroring repository question
We upgraded to SLES11-SP2 from our local SMT server repositories. We are mirroring the following locally: .-. | Mirror? | ID | Type | Name | Target | Description | Can be Mirrored | Staging | +-++--+---+--++-+-+ | Yes | 1 | nu | SLE11-SMT-SP2-Pool| sle-11-s390x | SLE11-SMT-SP2-Pool for sle-11-s390x| Yes | No | | Yes | 2 | nu | SLE11-SMT-SP2-Updates | sle-11-s390x | SLE11-SMT-SP2-Updates for sle-11-s390x | Yes | No | | Yes | 3 | nu | SLE11-SP1-SMT-Pool| sle-11-s390x | SLE11-SP1-SMT-Pool for sle-11-s390x| Yes | No | | Yes | 4 | nu | SLE11-SP1-SMT-Updates | sle-11-s390x | SLE11-SP1-SMT-Updates for sle-11-s390x | Yes | No | | Yes | 5 | nu | SLES11-SP1-Pool | sle-11-s390x | SLES11-SP1-Pool for sle-11-s390x | Yes | No | | Yes | 6 | nu | SLES11-SP1-Updates| sle-11-s390x | SLES11-SP1-Updates for sle-11-s390x| Yes | No | | Yes | 7 | nu | SLES11-SP2-Core | sle-11-s390x | SLES11-SP2-Core for sle-11-s390x | Yes | No | | Yes | 8 | nu | SLES11-SP2-Updates| sle-11-s390x | SLES11-SP2-Updates for sle-11-s390x| Yes | No | '-++--+---+--++-+-' However, when we run sam --spreport it shows that many packages might still be out of date? When we enter YaST2 Online Updates, we see no updates to these packages. This leads me to think that maybe I am not mirroring within SMT all the repositories that I should. Can someone confirm which repositories we should mirror to keep SLES11 up to date? Thanks as always. Peter Supportability Analysis Module 0.8.4 *** Report by 'sam --spreport' *** Installed versions: suse-sam-data0.8.4-0.5.2 satsolver-tools 0.17.5-0.5.2 suse-sam 0.8.4-0.7.1 perl-satsolver 0.44.5-0.5.8 *** Installed products: 2 (known vendors: 2) System architecture: s390x Baseproduct: SUSE_SLES.prod sle-smt.prod: summary: Subscription Management Tool for SUSE Linux Enterprise 11 SP2 name version: sle-smt 11.2 SP, release: 2 (none) arch: s390x repository: obs://build.suse.de/SUSE:SLE-11-SP2:GA:Products:Test/standard repository:obs://build.suse.de/SUSE:SLE-11-SP2:GA/standard repository:obs://build.suse.de/SUSE:SLE-11-SP1:Update/snapshot-SP2 repository:obs://build.suse.de/SUSE:SLE-11-SP1:GA/standard repository:obs://build.suse.de/SUSE:SLE-11:Update/snapshot-SP2 repository:obs://build.suse.de/SUSE:SLE-11:GA/standard SUSE_SLES.prod: summary: SUSE Linux Enterprise Server 11 SP2 name version: SUSE_SLES 11.2 SP, release: 2 (none) arch: s390x repository:obs://build.suse.de/SUSE:SLE-11-SP2:Update/standard repository:obs://build.suse.de/SUSE:SLE-11-SP2:GA/standard repository:obs://build.suse.de/SUSE:SLE-11-SP1:Update/snapshot-SP2 repository:obs://build.suse.de/SUSE:SLE-11-SP1:GA/standard repository:obs://build.suse.de/SUSE:SLE-11:Update/snapshot-SP2 repository:obs://build.suse.de/SUSE:SLE-11:GA/standard *** Found package repositories: 0 (reference 12, skipped 84, need refresh 0) *** Considered packages: Packages belonging to defined products: 850 Signed with accepted key:850 3rd party packages: 2 Skipped gpg-key packages:8 *** Identified Service Packs for packages (total: 850) Product SP Exclusive/ % Shared/ % Total / % -- SUSE_SLES 11 GA 0 0.0% 282 33.2%282 33.18% SUSE_SLES 11 SP1100 11.8% 399 46.9%499 58.71% SUSE_SLES 11 SP2326 38.4% 369 43.4%695 81.76% sle-sdk 11GA 0 0.0% 11 1.3% 11 1.29% sle-sdk 11 SP1 5 0.6% 13 1.5% 18 2.12% sle-sdk 11 SP2 5 0.6% 12 1.4% 17 2.00% other 9 1.06% Notes: - Exclusive - packages in one servicepack only - Shared- packages shared among several servicepacks - packages may reside in several SPs - percentage is calculated against total number of signed packages found on system matching some reference repository - 'other' covers all signed SUSE/Novell packages not found in reference repos Result: No product seems to fully cover the installed system. *** Unsatisfied package dependencies: NONE
Re: Another SLES11 SMT mirroring repository question
How can we tell the SLES11-SP2-Updates was not getting refreshed? From: Mark Post mp...@suse.com To: LINUX-390@vm.marist.edu, Date: 09/07/2012 04:14 PM Subject:Re: Another SLES11 SMT mirroring repository question Sent by:Linux on 390 Port LINUX-390@vm.marist.edu From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Peter E. Abresch Jr. - at Pepco We upgraded to SLES11-SP2 from our local SMT server repositories. We are mirroring the following locally: | Yes | 5 | nu | SLES11-SP1-Pool | sle-11-s390x | SLES11-SP1-Pool for sle-11-s390x | Yes | No | | Yes | 6 | nu | SLES11-SP1-Updates| sle-11-s390x | SLES11-SP1-Updates for sle-11-s390x| Yes | No | | Yes | 7 | nu | SLES11-SP2-Core | sle-11-s390x | SLES11-SP2-Core for sle-11-s390x | Yes | No | | Yes | 8 | nu | SLES11-SP2-Updates| sle-11-s390x | SLES11-SP2-Updates for sle-11-s390x| Yes | No | This looks like your problem. zypper is telling you that SLES11-SP2-Updates for sle-11-s390x is not getting refreshed. zypper mr -r SLES11-SP2-Updates zypper ref Might be what you need. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
message There was an error in the repository initialization when using YaST2 Online Update option
We are trying to update some of our Linux guests through YaST2/Online Updates and are receiving the following message: There was an error in the repository initialization This is now occurring on all our Linux guests. Is this issue on our side or Novell's side? There is not much more information other than the window with the error message. Thanks for any info. 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 lists...@vm.marist.edu 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/
Re: message There was an error in the repository initialization when using YaST2 Online Update option
This was an interesting issue. We had a local NFS repository configured and enabled to all our Linux server guests. I had no idea what was going on as this was working fine last night. I ran a: zypper update which revealed the that there was no access to the offending NFS repository. This repository was on a server next to me which I unplugged from the network so that I could plug my laptop into. This prevented any updates from any repositories showing up in YaST2. I ended up disabling this repository for now and all is working again. I was unaware that the unavailability of one repository prevents the whole process, even when the Novell?s repositories are enabled and selected. Does this make sense? Peter From: Mark Post mp...@suse.com To: LINUX-390@vm.marist.edu, Date: 08/30/2012 11:02 AM Subject:Re: message There was an error in the repository initialization when using YaST2 Online Update option Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 8/30/2012 at 08:58 AM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: We are trying to update some of our Linux guests through YaST2/Online Updates and are receiving the following message: There was an error in the repository initialization This is now occurring on all our Linux guests. Is this issue on our side or Novell's side? There is not much more information other than the window with the error message. Thanks for any info. That's going to depend on whether your systems are going against nu.novell.com, or a local SMT server. /var/log/YaST2/y2log will have more information about the process than you probably want to see. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
Re: Which SLES11 SP2 repos to mirror?
Thanks, that document was a big help. It never mentioned anything about: SLE11-SMT-SP2-Pool SLE11-SMT-SP2-Updates But SLES11-SP2-Core SLES11-SP2-Updates looks like what we needed. We mirrored these repos and used YaST to upgrade one of our Linux guest from SLES11-SP1 to SLES11-SP2. The upgrade seemed to go eerily smooth and we are in the process of completing our initial testing. It seems like we still need to continue to mirror: SLES11-SP1-Pool SLES11-SP1-Updates even after we upgrade all our Linux guests from SP1 to SP2. Is this true? Peter From: Marcy Cortes marcy.d.cor...@wellsfargo.com To: LINUX-390@vm.marist.edu, Date: 08/27/2012 03:09 PM Subject:Re: Which SLES11 SP2 repos to mirror? Sent by:Linux on 390 Port LINUX-390@vm.marist.edu This might help. http://www.novell.com/support/kb/doc.php?id=7001199 Marcy -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Peter E. Abresch Jr. - at Pepco Sent: Monday, August 27, 2012 11:46 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Which SLES11 SP2 repos to mirror? We are currently running SuSE SLES 11-SP1. We are beginning to look at updating to SLES 11-SP2. We use a local Linux SMT guest to mirror the updates. We currently mirror: SLES11-SP1-Pool SLES11-SP1-Updates So I assume we need to mirror: SLES11-SP2-Core SLES11-SP2-Updates But I also noticed the following: SLE11-SMT-SP2-Pool SLE11-SMT-SP2-Updates So now I am confused. Which repositories should I mirror on my local SMT server so that we can use YaST to upgrade our SLES11-SP1 guests from our local SMT server guest? Thanks for any clarification. 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
Which SLES11 SP2 repos to mirror?
We are currently running SuSE SLES 11-SP1. We are beginning to look at updating to SLES 11-SP2. We use a local Linux SMT guest to mirror the updates. We currently mirror: SLES11-SP1-Pool SLES11-SP1-Updates So I assume we need to mirror: SLES11-SP2-Core SLES11-SP2-Updates But I also noticed the following: SLE11-SMT-SP2-Pool SLE11-SMT-SP2-Updates So now I am confused. Which repositories should I mirror on my local SMT server so that we can use YaST to upgrade our SLES11-SP1 guests from our local SMT server guest? Thanks for any clarification. 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 lists...@vm.marist.edu 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/
Re: When LDAP Fails
We use YaST to configure everything and it made no difference. We also eliminated PAM as the problem as well. Additional testing results are as follows: If we shut down the remote LDAP server everything is fine, nss will get ?not available? and will continue with the local files. This allows us to logon to the Linux Console as root since root is a local Linux account. However, if we lose the network connection, (simulated by shutting down the network interface), nss will hang and the logon will timeout, no matter how high the timeout value is increased. Another words, not root or any local account authentication can occurred when specifying the following in nsswitch.conf when the network is down. passwd: ldap files shadow: ldap files group: ldap files We believe the problem lies with is nss_ldap. We are running nss_ldap-262-11.32.31.1. The problem seems to be that nss is not recognizing the timeout parameter in /etc/ldap.conf. If the network connection is not there, then it just keeps trying instead of timing out and looking at the local files. If the network is there, it immediately recognizes that LDAP is not running and moves on. Googling this issue reveals many hits identical to this. Bug 176209 (https://bugzilla.redhat.com/show_bug.cgi?id=176209) seems to address it. There are others that describe various symptoms of this same problem. How can I tell if this is a known issue with SuSE, Novell, or Attachmate? Is anyone else using LDAP and experiencing this problem? Peter From: Mark Post mp...@novell.com To: LINUX-390@vm.marist.edu Date: 01/26/2012 04:52 PM Subject:Re: When LDAP Fails Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 1/26/2012 at 04:35 PM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: II configured /etc/ldap.conf manually following the recommendations outline in an IBM Rebook about RACF LDAP server. I took the defaults with the following exceptions: host conprod base o=PHI timelimit 30 bind_timelimit 30 bind_policy soft pam_lookup_policy yes pam_check_host_attr yes pam_password racf nss_initgroups_ignoreusers root,postfix nss_schema rfc2307bis nss_map_attribute uniqueMember member Any ideas? I would be tempted to use YaST to configure all this, and compare the results with what has already been done. Perhaps the Redbook missed something subtle, or things changed somewhat between when it was published and SLES11 SP1, etc. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
When LDAP Fails
We are running SLES11-SP1 at latest maintenance levels. We use RACF LDAP and authenticate our Linux users to z/OS RACF. Everything works fine with no problems. Our root user is not defined in LDAP but to the local Linux. We have the following /etc/pam.d/login: #%PAM-1.0 auth required pam_securetty.so auth required pam_nologin.so auth sufficient pam_ldap.so auth requisite pam_unix2.so auth required pam_env.so auth required pam_mail.so account sufficient pam_ldap.so account required pam_unix2.so password sufficient pam_ldap.so password required pam_pwcheck.so nullok password required pam_unix2.so nullok use_first_pass use_authtok session required pam_loginuid.so session required pam_limits.so session required pam_unix2.so session optional pam_umask.so session required pam_lastlog.sonowtmp session optional pam_mail.so standard session optional pam_ck_connector.so It all works, for the most part. When we login with root, or any other ID not defined to LDAP, it will authenticate to the local Linux. However, here is the crux: When the RACF LDAP server on z/OS is down or if there is a network issue, the process hangs. Instead of failing at: auth sufficient pam_ldap.so and moving on to auth requisite pam_unix2.so auth required pam_env.so auth required pam_mail.so it just hangs and the login times out and fails: In other words we have no access to the system to do anything. I do not know if this a pam issue, an LDAP issue or an nss issue. I have been unsuccessful in resolving this and am open to suggestions. Thanks in advance. 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 lists...@vm.marist.edu 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/
Re: When LDAP Fails
II configured /etc/ldap.conf manually following the recommendations outline in an IBM Rebook about RACF LDAP server. I took the defaults with the following exceptions: host conprod base o=PHI timelimit 30 bind_timelimit 30 bind_policy soft pam_lookup_policy yes pam_check_host_attr yes pam_password racf nss_initgroups_ignoreusers root,postfix nss_schema rfc2307bis nss_map_attribute uniqueMember member Any ideas? Peter From: Mark Post mp...@novell.com To: LINUX-390@vm.marist.edu Date: 01/26/2012 02:35 PM Subject:Re: When LDAP Fails Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 1/26/2012 at 01:36 PM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: In other words we have no access to the system to do anything. I do not know if this a pam issue, an LDAP issue or an nss issue. I have been unsuccessful in resolving this and am open to suggestions. Thanks in advance. Did you use YaST to set up the authenticate via LDAP configuration, or did you do it manually? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
Re: Cannot Ping SLES11 guests from z/VM through hypersockets
We do have multiple interfaces. It seems when net.ipv6.conf.all.forwarding is 0 or 2 it works fine. When it is set to 1, I cannot ping the SLES11-SP1 hypersockets from z/VM. The only reason we care is that there are some Computer Operation scripts that go out and verify various Linux guests and one of the verifications is ping. For now, I have net.ipv6.conf.all.forwarding = 2 for all my SLES11-SP1 guests and all is well with the world, at least my little virtualized part of it. Thanks to everyone. This would have consume large amounts of my time trying to figure this one out. Peter From: Steffen Maier ma...@linux.vnet.ibm.com To: LINUX-390@vm.marist.edu Date: 10/19/2011 06:44 AM Subject:Re: Cannot Ping SLES11 guests from z/VM through hypersockets Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 10/19/2011 01:56 AM, Peter E. Abresch Jr. - at Pepco wrote: Maybe, net.ipv4.conf.all.rp_filter was set to 1. I took one of my SLES11-SP1 guest and set it to 2. It now pings from z/VM. When I set it back to 1, it still pings. When I set it to 0, it still pings. I went to a different SLES11 guest. It did not ping, but once I set net.ipv4.conf.all.rp_filter to 0, it pinged fine. I returned it to 1 and it still pings. I am confused. Why is it pinging all of a sudden or is it just the nature of the beast. I suppose that once you had loosened the reverse path filtering, you got routing cache entries and then rp_filter no longer checks the FIB (forwarding information base == routing table(s)) as long as a corresponding cache entry is still there even if you have set rp_filter back to 1 for strict checking. /sbin/ip route list table cache The routing cache is volatile. You can cross check my assumption by flushing the routing cache after having set rp_filter back to 1 for strict filtering and checking whether ping fails to work again. /sbin/ip route flush table cache Should I set it to 2 globally? Probably this depends on your network topology and security requirements. Do you have any asymmetric routing or multiple interfaces to the same subnet [1] in the same virtual machine and need such configuration? [1] http://www.mail-archive.com/linux-390@vm.marist.edu/msg57175.html From: Michael O'Reillymik...@us.ibm.com Are you by any chance hitting: Applying SLES 11 SP 1 Causing Communication Issues http://www.novell.com/support/search.do?cmd=displayKCdocType=kcexternalId=7007649sliceId=1docTypeID=DT_TID_1_1 On 10/18/2011 at 06:42 PM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: We are running z/VM Version 5 Release 4.0, service level 1001 (64-bit). We can ping all of our SLES10 guests through our real hypersockets from z/VM. however we cannot ping our SLES11 guests from z/VM through our real hypersockets. All our Linux guests (SLES10 and SLES11) can ping each other fine through hypersockets. z/OS can ping SLES10 and SLES11 guests through hypersockets fine. SLES10 and SLES11 Linux guest can ping everything fine through hypersockets. The only problem is pinging SLES11 guests from z/VM. Has anyone else experienced this problem or have any suggestions? Steffen Linux on System z Development IBM Deutschland Research Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu
sam output vs SPident under SLES11-SP1
When I run sam (no longer SPident), all seems to work fine except for that last paragraph of the output. SAM complains about the following repositories: 'SUSE-Linux-Enterprise-Server-11-SP1_11.1.1-1.152_DVD1' 'SUSE-Linux-Enterprise-Server-11-SP1_11.1.1-1.152_DVD2' I have disabled these repositories as I have smt mirroring repositories SLES11-SP1-Pool and SLES11-SP-Updates. However, sam still seems to be looking at them and I get the follwing: - One or more repositories need to be updated. SAM was not able to check if your installed Novell software has the versions required to be supported. Please update your repositories for example by running 'zypper refresh'. Then re-run SAM. - repository 'SUSE-Linux-Enterprise-Server-11-SP1_11.1.1-1.152_DVD1' - repository 'SUSE-Linux-Enterprise-Server-11-SP1_11.1.1-1.152_DVD2' a zypper refresh does not change the outcome. Should I simply delete these repositories? The support people want to see the coveted system up to date message similar to the old SPident. Is that even possible? linuxsmt:~ zypper lr # | Alias | Name | Enabled | Refresh ---++---+ -+ 1 | SLES11-SP1-Pool| SLES11-SP1-Pool | Yes| Yes 2 | SLES11-SP1-Updates | SLES11-SP1-Updates | Yes | Yes 3 | SMT-Media1 | SMT-Media1 | No| No 4 | SMT-Media2 | SMT-Media2 | No| No 5 | SUSE-Linux-Enterprise-Server-11-SP1_11.1.1-1.152_DVD1 | SUSE-Linux-Enterprise-Server-11-SP1 11.1.1-1.152 DVD1 | No| No 6 | SUSE-Linux-Enterprise-Server-11-SP1_11.1.1-1.152_DVD2 | SUSE-Linux-Enterprise-Server-11-SP1 11.1.1-1.152 DVD2 | No| No 7 | SUSE-Linux-Enterprise-Server-11-SP1_11.1.1-1.152_SDK_1 | SUSE-Linux-Enterprise-Server-11-SP1 11.1.1-1.152 SDK | Yes| Yes 8 | nu_novell_com:SLE11-SP1-Debuginfo-Pool | SLE11-SP1-Debuginfo-Pool | No| Yes 9 | nu_novell_com:SLE11-SP1-Debuginfo-Updates | SLE11-SP1-Debuginfo-Updates | No| Yes 10 | nu_novell_com:SLE11-WebYaST-SP1-Pool | SLE11-WebYaST-SP1-Pool| No| Yes 11 | nu_novell_com:SLE11-WebYaST-SP1-Updates| SLE11-WebYaST-SP1-Updates | No| Yes 12 | nu_novell_com:SLES11-Extras| SLES11-Extras | No| Yes 13 | nu_novell_com:SLES11-SP1-Pool | SLES11-SP1-Pool | No| Yes 14 | nu_novell_com:SLES11-SP1-Updates | SLES11-SP1-Updates| No| Yes 15 | tst_update | tst update | No| No linuxsmt:~ sam Supportability Analysis Module 0.8.2 *** Report by 'sam' *** Installed versions: suse-sam-data0.8.2-0.5.1 satsolver-tools 0.14.18-0.4.1 suse-sam 0.8.2-0.6.2 perl-satsolver 0.14.18-0.4.1 *** Installed products: 1 (known vendors: 1) System architecture: s390x Baseproduct: SUSE_SLES.prod SUSE_SLES.prod: summary: SUSE Linux Enterprise Server 11 SP1 name version: SUSE_SLES 11.1 SP, release: 1 1.152 arch: s390x repository:obs://build.suse.de/SUSE:SLE-11-SP1:GA/standard repository:obs://build.suse.de/SUSE:SLE-11:Update/snapshot-SP1 repository:obs://build.suse.de/SUSE:SLE-11:GA/standard *** Found package repositories: 2 (reference 8, skipped 53, need refresh 2) Repository #1: name: SUSE-Linux-Enterprise-Server-11-SP1 11.1.1-1.152 DVD2 label: SUSE Linux Enterprise Server 11 SP1 (1) distribution: SUSE_SLE version: 11 Repository #2: name: SUSE-Linux-Enterprise-Server-11-SP1 11.1.1-1.152 DVD1 label: SUSE Linux Enterprise Server 11 SP1 (3) distribution: SUSE_SLE version: 11 *** Considered packages: Packages belonging to defined products: 819 Signed with accepted key:819 3rd party packages: 4 Skipped gpg-key packages:8 *** Unsatisfied package dependencies: NONE *** Novell packages depending on 3rd party packages: NONE *** Package version checks: all up to date ***
Re: sam output vs SPident under SLES11-SP1
That got rid of the repository errors but sam is still suggesting that Novell support is iffy. I know different. It looks like it is due to the following 4 non-Novell RPMs. Is there a mechanism to exclude these checks? With a number of changes, your system can receive support from Novell. In order to ensure supportability, please resolve the following item(s): - Package(s) not created by Novell have been found: - rmfpms-2.4.44-2339.s390x - sudosh2-1.0.4-1.el5.s390x - usermin-1.480-1.noarch - webmin-1.560-1.noarch These packages are not part of your Novell product. Novell support engineers might ask you to direct support requests to the manufacturer of these packages. From: Mark Post mp...@novell.com To: LINUX-390@vm.marist.edu Date: 10/19/2011 12:07 PM Subject:Re: sam output vs SPident under SLES11-SP1 Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 10/19/2011 at 11:31 AM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: Should I simply delete these repositories? The support people want to see the coveted system up to date message similar to the old SPident. Is that even possible? Since you have the SLES11-SP1-Pool channel enabled, there's little reason to keep the DVD sources around. So yes, go ahead and delete them. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
Cannot Ping SLES11 guests from z/VM through hypersockets
We are running z/VM Version 5 Release 4.0, service level 1001 (64-bit). We can ping all of our SLES10 guests through our real hypersockets from z/VM. however we cannot ping our SLES11 guests from z/VM through our real hypersockets. All our Linux guests (SLES10 and SLES11) can ping each other fine through hypersockets. z/OS can ping SLES10 and SLES11 guests through hypersockets fine. SLES10 and SLES11 Linux guest can ping everything fine through hypersockets. The only problem is pinging SLES11 guests from z/VM. Has anyone else experienced this problem or have any suggestions? SLES10 Guest HSI0 hsi0 Link encap:Ethernet HWaddr 06:00:EF:05:00:06 inet addr:161.186.86.150 Bcast:162.186.86.191 Mask:255.255.255.192 inet6 addr: fe80::600:ef9f:4005:6/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:16384 Metric:1 RX packets:207 errors:0 dropped:0 overruns:0 frame:0 TX packets:291 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:16704 (16.3 Kb) TX bytes:33137 (32.3 Kb) SLES11 Guest HSI0 hsi0 Link encap:Ethernet HWaddr 06:00:EF:05:00:1A inet addr:161.186.86.154 Bcast:161.186.86.191 Mask:255.255.255.192 inet6 addr: fe80::400:efff:fe05:1a/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:16384 Metric:1 RX packets:98 errors:0 dropped:0 overruns:0 frame:0 TX packets:154 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:8816 (8.6 Kb) TX bytes:16149 (15.7 Kb) 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 lists...@vm.marist.edu 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/
Re: Cannot Ping SLES11 guests from z/VM through hypersockets
Yes, PTF shows applied UK46027: VMFSRV1226I TCPIP (5VMTCP40%TCPIP) APAR PK80882 (PTF UK46027) status: VMFSRV1226IRECEIVED 06/17/10 07:50:18 VMFSRV1226IAPPLIED 10/06/09 20:16:49 VMFSRV1226IBUILT 06/17/10 07:51:47 VMFSRV1226IPUT2PROD 06/17/10 09:18:43 VMFSRV2760I SERVICE processing completed successfully From: Mark Post mp...@novell.com To: LINUX-390@vm.marist.edu Date: 10/18/2011 06:53 PM Subject:Re: Cannot Ping SLES11 guests from z/VM through hypersockets Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 10/18/2011 at 06:42 PM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: We are running z/VM Version 5 Release 4.0, service level 1001 (64-bit). We can ping all of our SLES10 guests through our real hypersockets from z/VM. however we cannot ping our SLES11 guests from z/VM through our real hypersockets. All our Linux guests (SLES10 and SLES11) can ping each other fine through hypersockets. z/OS can ping SLES10 and SLES11 guests through hypersockets fine. SLES10 and SLES11 Linux guest can ping everything fine through hypersockets. The only problem is pinging SLES11 guests from z/VM. Has anyone else experienced this problem or have any suggestions? Do you have the fix for z/VM APAR PK80882 installed? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
Re: Cannot Ping SLES11 guests from z/VM through hypersockets
Maybe, net.ipv4.conf.all.rp_filter was set to 1. I took one of my SLES11-SP1 guest and set it to 2. It now pings from z/VM. When I set it back to 1, it still pings. When I set it to 0, it still pings. I went to a different SLES11 guest. It did not ping, but once I set net.ipv4.conf.all.rp_filter to 0, it pinged fine. I returned it to 1 and it still pings. I am confused. Why is it pinging all of a sudden or is it just the nature of the beast. Should I set it to 2 globally? Peter From: Michael O'Reilly mik...@us.ibm.com To: LINUX-390@vm.marist.edu Date: 10/18/2011 07:24 PM Subject:Re: Cannot Ping SLES11 guests from z/VM through hypersockets Sent by:Linux on 390 Port LINUX-390@vm.marist.edu Peter, Are you by any chance hitting: Applying SLES 11 SP 1 Causing Communication Issues http://www.novell.com/support/search.do?cmd=displayKCdocType=kcexternalId=7007649sliceId=1docTypeID=DT_TID_1_1 Mike O'Reilly IBM Linux Change Team Peter E. Abresch Jr. - at Pepco peabresch@pepco. To com LINUX-390@vm.marist.edu Sent by: Linux on cc 390 Port linux-...@vm.mar Subject ist.edu Re: Cannot Ping SLES11 guests from z/VM through hypersockets 10/18/2011 04:04 PM Please respond to Linux on 390 Port linux-...@vm.mar ist.edu Yes, PTF shows applied UK46027: VMFSRV1226I TCPIP (5VMTCP40%TCPIP) APAR PK80882 (PTF UK46027) status: VMFSRV1226IRECEIVED 06/17/10 07:50:18 VMFSRV1226IAPPLIED 10/06/09 20:16:49 VMFSRV1226IBUILT 06/17/10 07:51:47 VMFSRV1226IPUT2PROD 06/17/10 09:18:43 VMFSRV2760I SERVICE processing completed successfully From: Mark Post mp...@novell.com To: LINUX-390@vm.marist.edu Date: 10/18/2011 06:53 PM Subject:Re: Cannot Ping SLES11 guests from z/VM through hypersockets Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 10/18/2011 at 06:42 PM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: We are running z/VM Version 5 Release 4.0, service level 1001 (64-bit). We can ping all of our SLES10 guests through our real hypersockets from z/VM. however we cannot ping our SLES11 guests from z/VM through our real hypersockets. All our Linux guests (SLES10 and SLES11) can ping each other fine through hypersockets. z/OS can ping SLES10 and SLES11 guests through hypersockets fine. SLES10 and SLES11 Linux guest can ping everything fine through hypersockets. The only problem is pinging SLES11 guests from z/VM. Has anyone else experienced this problem or have any suggestions? Do you have the fix for z/VM APAR PK80882 installed? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: 500 Internal Server Error with smt-mirror
This issue was caused by a cloning error on my part. I rebuilt the certificate for LINUXSMT using the following procedures: http://www.novell.com/support/php/search.do?cmd=displayKCdocType=kcexternalId=7006024 Now all is well and I move on to the next stage. Thanks everyone. Peter From: Peter E Abresch/EP/PEP To: Linux on 390 Port LINUX-390@vm.marist.edu Date: 10/14/2011 05:17 PM Subject:Re: 500 Internal Server Error with smt-mirror It looks like Novell has corrected their problem. I finished my SMT testing and then went to the client. I ran the following script: ./clientSetup4SMT.sh --host linuxsmt.pepcoholdings.biz And all was looking good until then end when I get the following messages: All repositories have been refreshed. ERROR: SSL peer certificate or SSH md5 fingerprint was not OK: (51) (2) ERROR: SSL peer certificate or SSH md5 fingerprint was not OK: (51) (2) What is this telling me? From: Peter E Abresch/EP/PEP To: Linux on 390 Port LINUX-390@vm.marist.edu Date: 10/14/2011 03:33 PM Subject:Re: 500 Internal Server Error with smt-mirror Thanks, I reported it to Novell, hopefully it will not be too long. Peter From: Mark Post mp...@novell.com To: LINUX-390@vm.marist.edu Date: 10/14/2011 03:25 PM Subject:Re: 500 Internal Server Error with smt-mirror Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 10/14/2011 at 02:51 PM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: Is the 500 Internal Server Error on my end or Novell?s end? Looks like Novell's end is the problem. I just pointed my web browser to nu.novell.com, and got this back: 500 Internal Server Error All LDAP Servers down. Please contact the Helpdesk. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
500 Internal Server Error with smt-mirror
I was working with SMT and everything seem to be working and now, all of a sudden I am seeing the following: Mirroring: https://nu.novell.com/repo/$RCE/SLES11-SP1-Pool/sle-11-s390x/ Target:/srv/www/htdocs/repo/$RCE/SLES11-SP1-Pool/sle-11-s390x E 'https://nu.novell.com/repo/$RCE/SLES11-SP1-Pool/sle-11-s390x/repodata/repomd.xml': 500 Internal Server Error Is the 500 Internal Server Error on my end or Novell?s end? 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 lists...@vm.marist.edu 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/
Re: 500 Internal Server Error with smt-mirror
No, I was just doing some testing and doing some minor tweaks and now I the 500 message. I do not know if I did something or there is an issue with Novell. Peter From: Marcy Cortes marcy.d.cor...@wellsfargo.com To: LINUX-390@vm.marist.edu Date: 10/14/2011 03:10 PM Subject:Re: 500 Internal Server Error with smt-mirror Sent by:Linux on 390 Port LINUX-390@vm.marist.edu Did you recently patch perl-libwww-perl? Marcy -Original Message- From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Peter E. Abresch Jr. - at Pepco Sent: Friday, October 14, 2011 11:52 AM To: LINUX-390@vm.marist.edu Subject: [LINUX-390] 500 Internal Server Error with smt-mirror I was working with SMT and everything seem to be working and now, all of a sudden I am seeing the following: Mirroring: https://nu.novell.com/repo/$RCE/SLES11-SP1-Pool/sle-11-s390x/ Target:/srv/www/htdocs/repo/$RCE/SLES11-SP1-Pool/sle-11-s390x E 'https://nu.novell.com/repo/$RCE/SLES11-SP1-Pool/sle-11-s390x/repodata/repomd.xml': 500 Internal Server Error Is the 500 Internal Server Error on my end or Novell?s end? 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
Re: 500 Internal Server Error with smt-mirror
Thanks, I reported it to Novell, hopefully it will not be too long. Peter From: Mark Post mp...@novell.com To: LINUX-390@vm.marist.edu Date: 10/14/2011 03:25 PM Subject:Re: 500 Internal Server Error with smt-mirror Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 10/14/2011 at 02:51 PM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: Is the 500 Internal Server Error on my end or Novell?s end? Looks like Novell's end is the problem. I just pointed my web browser to nu.novell.com, and got this back: 500 Internal Server Error All LDAP Servers down. Please contact the Helpdesk. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
Re: 500 Internal Server Error with smt-mirror
It looks like Novell has corrected their problem. I finished my SMT testing and then went to the client. I ran the following script: ./clientSetup4SMT.sh --host linuxsmt.pepcoholdings.biz And all was looking good until then end when I get the following messages: All repositories have been refreshed. ERROR: SSL peer certificate or SSH md5 fingerprint was not OK: (51) (2) ERROR: SSL peer certificate or SSH md5 fingerprint was not OK: (51) (2) What is this telling me? From: Peter E Abresch/EP/PEP To: Linux on 390 Port LINUX-390@vm.marist.edu Date: 10/14/2011 03:33 PM Subject:Re: 500 Internal Server Error with smt-mirror Thanks, I reported it to Novell, hopefully it will not be too long. Peter From: Mark Post mp...@novell.com To: LINUX-390@vm.marist.edu Date: 10/14/2011 03:25 PM Subject:Re: 500 Internal Server Error with smt-mirror Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 10/14/2011 at 02:51 PM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: Is the 500 Internal Server Error on my end or Novell?s end? Looks like Novell's end is the problem. I just pointed my web browser to nu.novell.com, and got this back: 500 Internal Server Error All LDAP Servers down. Please contact the Helpdesk. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
Re: DASD assignment different between SLES10 and SLES11
Added ?dasd_mod.dasd=0.0.150-0.0.15f? to the zipl.conf and ran zipl. These caused massive I/O errors and I had to back out. I analyzed this problem further and realized that I had two virtual DASD addresses mapped to this z/VM guest, leftover from a previous Reiserfs to EXT3 conversion. I had taken them off with the dasd_configure command months previouz. In other words, these I/O errors were ok and made now made sense. I updated the z/VM guest?s configuration and removed these DASD devices. I then added updated zipl.conf as follows: [ipl] image = /boot/image target = /boot/zipl ramdisk = /boot/initrd,0x200 parameters = root=/dev/disk/by-path/ccw-0.0.0150-part1 dasd_mod.dasd=0.0.0150-0.0.015f TERM=dumb I ran zipl and rebooted. Now everything is in its normal predictable slot as follows: linuxm02:~ lsdasd Bus-ID Status Name Device Type BlkSz Size Blocks == 0.0.0150 active dasda 94:0ECKD 4096 2347MB600840 0.0.0151 active dasdb 94:4ECKD 4096 2347MB600840 0.0.0152 active dasdc 94:8ECKD 4096 2347MB600840 0.0.0153 active dasdd 94:12 ECKD 4096 2347MB600840 0.0.0154 active dasde 94:16 ECKD 4096 2347MB600840 0.0.015f active dasdp 94:60 ECKD 4096 589MB 150840 Thanks to everyone that responded. Enjoy your weekend. Peter From: Ronald van der Laan nl50...@gmail.com To: LINUX-390@vm.marist.edu Date: 09/29/2011 04:26 PM Subject:Re: DASD assignment different between SLES10 and SLES11 Sent by:Linux on 390 Port LINUX-390@vm.marist.edu Peter, Have you tried: parameters = root=/dev/disk/by-path/ccw-0.0.0150-part1 dasd=0.0.0150-0.0.015f TERM=dumb Ronald van der Laan -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
DASD assignment different between SLES10 and SLES11
Under SLES10, we see the following: 0.0.0150(ECKD) at ( 94: 0) is dasda : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.0151(ECKD) at ( 94: 4) is dasdb : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.0152(ECKD) at ( 94: 8) is dasdc : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.0153(ECKD) at ( 94: 12) is dasdd : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.0154(ECKD) at ( 94: 16) is dasde : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.015f(ECKD) at ( 94: 60) is dasdp : active at blocksize 4096, 150840 blocks, 589 MB Notice that 0.0.015f is dasdp Under SLES11, we see the following: Bus-ID Status Name Device Type BlkSz Size Blocks == 0.0.0150 active dasda 94:0ECKD 4096 2347MB600840 0.0.0151 active dasdb 94:4ECKD 4096 2347MB600840 0.0.0152 active dasdc 94:8ECKD 4096 2347MB600840 0.0.0155 active dasdd 94:12 ECKD 4096 2347MB600840 0.0.0156 active dasde 94:16 ECKD 4096 2347MB600840 0.0.015f active dasdf 94:20 ECKD 4096 589MB 150840 Notice that 0.0.015f is dasdf rather than dasdp. How can I insure that 0.0.015f is always dasdp? I read that this behavior had change but naturally now that I need this doc, I cannot find it anywhere. I do not remember where I read it. E. Can anyone point me in the right direction? Thanks as always. 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 lists...@vm.marist.edu 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/
Re: DASD assignment different between SLES10 and SLES11
Yes, our root is always dasda and our swap is always dasdp. This is what our original automated Linux cloning process expects and we wish to not re-engineer our cloning process at this time. Under SLES10, in /etc/zipl.conf we have the following: parameters = root=/dev/dasda1 dasd=150-15f TERM=dumb Under SLES11, in /etc/zipl.conf we have the following: parameters = root=/dev/disk/by-path/ccw-0.0.0150-part1 TERM=dumb I am thinking this is where I need to make my change, but my own memory is slow to swap back in for me to remember all of it. But . . . readlink -f /dev/disk/by-path/ccw-0.0.$15F reveals /dev/disk/by-path/ccw-0.0.5F - it seems to strip the 1 from the 15f. In my SLES10 cloning script, where I have the following: echo Creating DASD swap space on /dev/dasdp1 swapoff -a echo Formatting DASD swap space on /dev/dasdp1 dasdfmt -vy -f /dev/dasdp -d cdl -l swap01 -b 4096 echo Partitioning DASD swap space on /dev/dasdp1 fdasd -l swap01 -a /dev/dasdp echo Making DASD swap space on /dev/dasdp1 sleep 5 mkswap /dev/dasdp1 echo Activating DASD swap space on /dev/dasdp1 swapon -a echo Verifying DASD swap space on /dev/dasdp1 swapon ?s I can change in my SLES11 cloning script to: echo Creating DASD swap space on /dev/disk/by-path/ccw-0.0.5F swapoff -a echo Formatting DASD swap space on /dev/disk/by-path/ccw-0.0.5F dasdfmt -vy -f /dev/disk/by-path/ccw-0.0.5F -d cdl -l swap01 -b 4096 echo Partitioning DASD swap space on /dev/disk/by-path/ccw-0.0.5F fdasd -l swap01 -a /dev/disk/by-path/ccw-0.0.5F echo Making DASD swap space on /dev/disk/by-path/ccw-0.0.5F sleep 5 mkswap /dev/disk/by-path/ccw-0.0.5F echo Activating DASD swap space on /dev/disk/by-path/ccw-0.0.5F swapon -a echo Verifying DASD swap space on /dev/disk/by-path/ccw-0.0.5F swapon ?s Is this what I should do? I am hesitant as there might me other scripted mounts that do /dev/dasdx# . Should I eat the bullet now or defer? Peter From: Ron Foster at Baldor-IS rfos...@baldor.com To: LINUX-390@vm.marist.edu Date: 09/29/2011 11:38 AM Subject:Re: DASD assignment different between SLES10 and SLES11 Sent by:Linux on 390 Port LINUX-390@vm.marist.edu Peter, Actually we observed this behavior as far back as SLES10 SP3. We started using persistent device names and forgot about it. The documentation for this is in the release notes. From the release notes: Installation using Persistent Device names If you plan to add additional storage devices to your system after the OS installation, we strongly recommend to use persistent device names for all storage devices during installation. The installer by default uses the kernel device names. There is additional information in the SLES11 device driver manual on the developerworks site. From the Device Drivers, Features, and Commands manual SC34-2595-01 (from page 35) autodetect causes the DASD device driver to allocate device names and the corresponding minor numbers to all DASD devices and set them online during the boot process. See ?DASD naming scheme? on page 31 for the naming scheme. The device names are assigned in order of ascending subchannel numbers. Auto-detection can yield confusing results if you change your I/O configuration and reboot, or if you are running as a guest operating system in VM because the devices might appear with different names and minor numbers after rebooting. What may have changed is how dasd= is specified and/or how it works. It is different between the SLES10 and SLES11 manuals. Ron Foster From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Peter E. Abresch Jr. - at Pepco [peabre...@pepco.com] Sent: Thursday, September 29, 2011 9:59 AM To: LINUX-390@VM.MARIST.EDU Subject: DASD assignment different between SLES10 and SLES11 Under SLES10, we see the following: 0.0.0150(ECKD) at ( 94: 0) is dasda : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.0151(ECKD) at ( 94: 4) is dasdb : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.0152(ECKD) at ( 94: 8) is dasdc : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.0153(ECKD) at ( 94: 12) is dasdd : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.0154(ECKD) at ( 94: 16) is dasde : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.015f(ECKD) at ( 94: 60) is dasdp : active at blocksize 4096, 150840 blocks, 589 MB Notice that 0.0.015f is dasdp Under SLES11, we see the following: Bus-ID Status Name Device Type BlkSz Size Blocks == 0.0.0150 active dasda 94:0ECKD 4096 2347MB600840 0.0.0151 active dasdb 94:4ECKD 4096 2347MB600840 0.0.0152 active dasdc 94:8ECKD 4096 2347MB600840 0.0.0155 active dasdd 94:12 ECKD 4096 2347MB600840 0.0.0156 active dasde 94:16 ECKD
Re: DASD assignment different between SLES10 and SLES11
Wow, you have to get that command just right:
linuxm02:~ readlink -f /dev/disk/by-path/ccw-0.0.15f
/dev/disk/by-path/ccw-0.0.15f
linuxm02:~ readlink -f /dev/disk/by-path/ccw-0.0.15F
/dev/disk/by-path/ccw-0.0.15F
linuxm02:~ readlink -f /dev/disk/by-path/ccw-0.0.Peter
/dev/disk/by-path/ccw-0.0.Peter
linuxm02:~ readlink -f /dev/disk/by-path/ccw-0.0.015f
/dev/dasdf
I am going to do some more analysis.
I also added the following to the zipl.conf:
parameters = root=/dev/disk/by-path/ccw-0.0.0150-part1
dasd_mod.dasd=0.0.150-0.0.15f
TERM=dumb
and ran a zipl but that generated pages of pages of errors during boot. I
will have to look into that a little deeper as well.
Coding the device path in the cloning script generated other errors.
Again, more analysis on my part.
Peter
From: Christian Paro christian.p...@gmail.com
To: LINUX-390@vm.marist.edu
Date: 09/29/2011 01:23 PM
Subject:Re: DASD assignment different between SLES10 and SLES11
Sent by:Linux on 390 Port LINUX-390@vm.marist.edu
On the readlink example, the $ indicates a variable. So in a script you
could set vdev='015f' and then reference that value as ${vdev}. Or you
could
just hard code in the 015f.
...also note that the by-path disk nodes always zero-pad the beginning of
a
virtual device number, so it'll be four characters in length.
It's stripping out the 1 in $15f because it's assuming you mean $1 as
a
variable, and (since you never initialized a $1 or passed it in as an
argument/parameter) interpreting it as an empty string.
If your script is always dealing with the same virtual device numbers,
though, and not dealing with something that *has* to use the dasd* format,
you may as well just hard-code the by-path name of the disk.
You can find other mounts by /dev/dasd* in your scripts by running a grep
through them, if that's a concern. Unlike network interfaces (which have a
configurable persistent mapping in
/etc/udev/rules.d/70-persistent-net.rules), there is not any way I'm aware
of to force the assignment of a virtual disk to a particular letter in
the
/dev/dasd* scheme. Those assignments happen to usually remain stable -
but,
as you've seen, they can change if something changes the order in which
they
are brought on line.
On Thu, Sep 29, 2011 at 12:59 PM, Ron Foster at Baldor-IS
rfos...@baldor.com wrote:
Peter,
We do not have SLES11, but from the manual, on page 21 (Module
parameters
on the kernel parameter line), it appears that the appropriate format
of
the dasd= parameter might be:
dasd_mod.dasd=0.0.150-0.0.15f
so your parameter line would be:
parameters = root=/dev/disk/by-path/ccw-0.0.0150-part1
dasd_mod.dasd=0.0.150-0.0.15f
TERM=dumb
Ron Foster
From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Peter E.
Abresch Jr. - at Pepco [peabre...@pepco.com]
Sent: Thursday, September 29, 2011 11:09 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DASD assignment different between SLES10 and SLES11
Yes, our root is always dasda and our swap is always dasdp. This is what
our original automated Linux cloning process expects and we wish to not
re-engineer our cloning process at this time.
Under SLES10, in /etc/zipl.conf we have the following:
parameters = root=/dev/dasda1 dasd=150-15f TERM=dumb
Under SLES11, in /etc/zipl.conf we have the following:
parameters = root=/dev/disk/by-path/ccw-0.0.0150-part1 TERM=dumb
I am thinking this is where I need to make my change, but my own memory
is
slow to swap back in for me to remember all of it.
But . . .
readlink -f /dev/disk/by-path/ccw-0.0.$15F
reveals /dev/disk/by-path/ccw-0.0.5F - it seems to strip the 1 from the
15f.
In my SLES10 cloning script, where I have the following:
echo Creating DASD swap space on /dev/dasdp1
swapoff -a
echo Formatting DASD swap space on /dev/dasdp1
dasdfmt -vy -f /dev/dasdp -d cdl -l swap01 -b 4096
echo Partitioning DASD swap space on /dev/dasdp1
fdasd -l swap01 -a /dev/dasdp
echo Making DASD swap space on /dev/dasdp1
sleep 5
mkswap /dev/dasdp1
echo Activating DASD swap space on /dev/dasdp1
swapon -a
echo Verifying DASD swap space on /dev/dasdp1
swapon ?s
I can change in my SLES11 cloning script to:
echo Creating DASD swap space on /dev/disk/by-path/ccw-0.0.5F
swapoff -a
echo Formatting DASD swap space on /dev/disk/by-path/ccw-0.0.5F
dasdfmt -vy -f /dev/disk/by-path/ccw-0.0.5F -d cdl -l swap01 -b 4096
echo Partitioning DASD swap space on /dev/disk/by-path/ccw-0.0.5F
fdasd -l swap01 -a /dev/disk/by-path/ccw-0.0.5F
echo Making DASD swap space on /dev/disk/by-path/ccw-0.0.5F
sleep 5
mkswap /dev/disk/by-path/ccw-0.0.5F
echo Activating DASD swap space on /dev/disk/by-path/ccw-0.0.5F
swapon -a
echo Verifying DASD swap space on /dev/disk/by-path/ccw-0.0.5F
swapon ?s
Is this what I should do? I am hesitant as there might me other scripted
mounts that do /dev/dasdx# . Should I eat the bullet now or defer?
Peter
Re: udevd-349-: nss_ldap: failed to bind to LDAP server ldap:// . . .
Thanks for responding. I agree that changing the order to ?files ldap? for passwd, shadow, and group will eliminate the overly burdensome messages, I question if this is the correct approach. All our external information is stored in LDAP and is intended to be share with multiple Linux systems. Some IDs are defined locally and to LDAP as these IDs would be used when there are LDAP issues that cause authentication issues. I made the change as suggested and with some slight PAM config changes, confirmed that these messages are eliminated. However, I am thinking that we would still rather go to LDAP first and files second. I understand that these messages are produced because the network is not available and communications to the ldap server is lost. This occurs during shutdown and IPL. I believe this is why the LDAP parameter nss_initgroups_ignoreusers was developed. By specifying a list of known local users that will be running between network availability and network unavailability in the nss_initgroups_ignoreusers, that NSS will simply return a notfound condition. Of course this parameter can also be used to prevent a wasted LDAP lookup for local users we know are not defined to ldap. The default nss action is to continue so when we have ?ldap files?, the call to ldap is bypassed and we move on to files. It is my understanding that the notfound condition is immediately passed thus eliminating any ldap interaction for those users specified in nss_initgroups_ignoreusers. I have the following specified: nss_initgroups_ignoreusers root,ldap,haldaemon,messagebus,dbus,bin,daemon,postfix,sshd,polkituser,uuidd,100,101 I know I probably only need a few of these but I wanted to eliminate the messages. This does not appear to be working as expected. Of course my expectations could be off. What are everyone?s thoughts on this? Is this an issue that I need to push to support? What are others doing with Linux RACF LDAP authorizations? All comments are welcome. Thanks Peter From: Patrick Spinler spinler.patr...@mayo.edu To: LINUX-390@vm.marist.edu Date: 08/18/2011 03:37 PM Subject:Re: udevd-349-: nss_ldap: failed to bind to LDAP server ldap:// . . . Sent by:Linux on 390 Port LINUX-390@vm.marist.edu Your nsswitch says to search ldap before anything local. I use passwd: files ldap (same for shadow group). Thus, it never even tries ldap if it finds a local entry. This has also come in handy for a few weird exceptions where the application absolutely had to do something weird and exceptional: I could override it on the local box. For example, two apps which absolutely had to use the same group name, with different memberships. Here, we have an enterprise oracle group with dozens of hosts for which their dba's are all members of a common group. We also have a couple of one off oracle hosts for non-enterprise groups who want the same names but different memberships. It's a bit of a pain to manage those specific host exceptions, but at least it's possible using 'files ldap'. -- Pat On 8/18/11 12:47 PM, Peter E. Abresch Jr. - at Pepco wrote: I have the following set in /etc/ldap.conf bind_policy soft nss_initgroups_ignoreusers root,ldap,haldaemon,messagebus,dbus,bin,daemon,postfix,sshd,polkituser,uuidd,100,101 However, these messages are overwhelming. I get them for udevd and vol_id. These might be a startup timing issue as soon as the network is available, they go away. However, the nss_initgroups_ignoreusers should ignore this. Am I still missing something? /etc/nsswitch.conf contains: passwd: ldap compat shadow: ldap compat group: ldap compat hosts: files dns networks: files dns services: files protocols: files rpc:files ethers: files netmasks: files netgroup: files nis publickey: files bootparams: files automount: files nis aliases:files From: Peter E Abresch/EP/PEP To: LINUX-390@vm.marist.edu Date: 08/18/2011 09:00 AM Subject:udevd-349-: nss_ldap: failed to bind to LDAP server ldap:// . . . We finally have RACF LDAP server running on z/OS with the TDBM backend and native authentication. We thought we were done as all our testing completed successfully. However, when the operator booted Linux, the console is flooded with the following messages on the shutdown and startup. It is very difficult to catch a real error with these flood of messages. Also, these messages are somewhat misleading as the LDAP server is up and running and available. I am thinking that these messages are produced as some service is shutdown and before some service starts. Here is the challenge: How can we eliminate these messages during shutdowns and boots? There are all coming from udevd. Thanks in advance. Peter udevd-349-: nss_ldap: failed to bind to LDAP server ldap://contest: Can't contact LDAP server udevd-349
Re: udevd-349-: nss_ldap: failed to bind to LDAP server ldap:// . . .
Thanks, I saw that, the default is root,ldap but that did not make a difference. I also tried other combinations and a couple of times with only root with the same results. There are many hits on a google search for this condition but no resolutions. I am seeing this condition for udevd, securitytty, and some othe services. I assume these all run under root as there are no ids or groups specifically for udevd and the rest. I am kind of stumped. I am leaning towards a possible bug at this point. Maybe something will come to be over a couple (or six) beers this weekend. Peter From: Mark Post mp...@novell.com To: LINUX-390@vm.marist.edu Date: 08/19/2011 02:45 PM Subject:Re: udevd-349-: nss_ldap: failed to bind to LDAP server ldap:// . . . Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 8/19/2011 at 10:53 AM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: I have the following specified: nss_initgroups_ignoreusers root,ldap,haldaemon,messagebus,dbus,bin,daemon,postfix,sshd,polkituser,uuidd ,100,101 I know I probably only need a few of these but I wanted to eliminate the messages. This does not appear to be working as expected. Of course my expectations could be off. What are everyone?s thoughts on this? Is this an issue that I need to push to support? What are others doing with Linux RACF LDAP authorizations? All comments are welcome. Thanks A Google search found something that indicates perhaps having too many users listed can be a problem. They were able to get the ignore list to work with 2 entries, but having 13 didn't. This was on RHEL5 from June of this year, so fairly recent. Give that a try and see what happens. Then regardless of the result, open up a support request. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
udevd-349-: nss_ldap: failed to bind to LDAP server ldap:// . . .
We finally have RACF LDAP server running on z/OS with the TDBM backend and native authentication. We thought we were done as all our testing completed successfully. However, when the operator booted Linux, the console is flooded with the following messages on the shutdown and startup. It is very difficult to catch a real error with these flood of messages. Also, these messages are somewhat misleading as the LDAP server is up and running and available. I am thinking that these messages are produced as some service is shutdown and before some service starts. Here is the challenge: How can we eliminate these messages during shutdowns and boots? There are all coming from udevd. Thanks in advance. Peter udevd-349-: nss_ldap: failed to bind to LDAP server ldap://contest: Can't contact LDAP server udevd-349-: nss_ldap: failed to bind to LDAP server ldap://contest: Can't contact LDAP server udevd-349-: nss_ldap: could not search LDAP server - Server is unavailable udevd-349-: nss_ldap: failed to bind to LDAP server ldap://contest: Can't contact LDAP server udevd-349-: nss_ldap: failed to bind to LDAP server ldap://contest: Can't contact LDAP server udevd-349-: nss_ldap: could not search LDAP server - Server is unavailable udevd-349-: nss_ldap: failed to bind to LDAP server ldap://contest: Can't contact LDAP server udevd-349-: nss_ldap: failed to bind to LDAP server ldap://contest: Can't contact LDAP server 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 lists...@vm.marist.edu 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/
Re: udevd-349-: nss_ldap: failed to bind to LDAP server ldap:// . . .
I have the following set in /etc/ldap.conf bind_policy soft nss_initgroups_ignoreusers root,ldap,haldaemon,messagebus,dbus,bin,daemon,postfix,sshd,polkituser,uuidd,100,101 However, these messages are overwhelming. I get them for udevd and vol_id. These might be a startup timing issue as soon as the network is available, they go away. However, the nss_initgroups_ignoreusers should ignore this. Am I still missing something? /etc/nsswitch.conf contains: passwd: ldap compat shadow: ldap compat group: ldap compat hosts: files dns networks: files dns services: files protocols: files rpc:files ethers: files netmasks: files netgroup: files nis publickey: files bootparams: files automount: files nis aliases:files From: Peter E Abresch/EP/PEP To: LINUX-390@vm.marist.edu Date: 08/18/2011 09:00 AM Subject:udevd-349-: nss_ldap: failed to bind to LDAP server ldap:// . . . We finally have RACF LDAP server running on z/OS with the TDBM backend and native authentication. We thought we were done as all our testing completed successfully. However, when the operator booted Linux, the console is flooded with the following messages on the shutdown and startup. It is very difficult to catch a real error with these flood of messages. Also, these messages are somewhat misleading as the LDAP server is up and running and available. I am thinking that these messages are produced as some service is shutdown and before some service starts. Here is the challenge: How can we eliminate these messages during shutdowns and boots? There are all coming from udevd. Thanks in advance. Peter udevd-349-: nss_ldap: failed to bind to LDAP server ldap://contest: Can't contact LDAP server udevd-349-: nss_ldap: failed to bind to LDAP server ldap://contest: Can't contact LDAP server udevd-349-: nss_ldap: could not search LDAP server - Server is unavailable udevd-349-: nss_ldap: failed to bind to LDAP server ldap://contest: Can't contact LDAP server udevd-349-: nss_ldap: failed to bind to LDAP server ldap://contest: Can't contact LDAP server udevd-349-: nss_ldap: could not search LDAP server - Server is unavailable udevd-349-: nss_ldap: failed to bind to LDAP server ldap://contest: Can't contact LDAP server udevd-349-: nss_ldap: failed to bind to LDAP server ldap://contest: Can't contact LDAP server 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 lists...@vm.marist.edu 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/
Re: RACF LDAP and Linux passwd command
After a good night sleep, I delved into this problem further. I do not think this is an ACL issue as I can change the password using the ldapmodify command. On the z/OS LDAP Server, we are using TDBM and RACF for native authentication. We have the following: Server Configuration adminDN: cn=ldapadm, o=PHI adminPW: *not configured* allowAnonymousBinds: on armName: GLDSRVR audit 1: off commThreads: 10 db2StartUpRetryInterval: 45 db2StartUpRetryLimit: 0 db2Terminate: recover dnCacheSize: 1000 idleConnectionTimeout: 0 listen 1: ldap://:389 logfile: /tmp/gldlog.output maxConnections: 65535 operationsMonitor: IPANY operationsMonitorSize: 1000 pcIdleConnectionTimeout: 0 pcThreads: 10 pwSearchOutput: binary schemaPath: /var/ldap/schema schemaReplaceByValue: on securityLabel: off sendV3StringsOverV2As: UTF-8 serverCompatLevel: 5 serverEtherAddr: 4020980269E6 serverSysplexGroup: undefined sizeLimit: 500 srvStartUpError: ignore sslAuth: serverAuth sslCertificate: none sslCipherSpecs: 050435363738392F303132330A1613100D0915120F0C0306 sslMapCertificate: off fail supportKrb5: off tcpTerminate: recover timeLimit: 3600 validateIncomingV2Strings: on database TDBM GLDBTD31 TDBM-0001 aclSourceCacheSize: 100 attrOverflowCount: 512 attrOverflowSize: 255 changeLoggingParticipant: on dbUserid: LDAPSRV dnToEidCacheSize: 1000 entryCacheSize: 5000 entryOwnerCacheSize: 100 extendedGroupSearching: off filterCacheBypassLimit: 100 filterCacheSize: 5000 krbIdentityMap: off multiServer: off nativeAuthSubtree: all nativeUpdateAllowed: on persistentSearch: off pwCryptCompat: on pwEncryption: none readOnly: off secretEncryption: none serverName: USPHIDSNC sizeLimit: 500 suffix 1: o=PHI timeLimit: 3600 useNativeAuth: all I have the following specified in SLES11-SP1?s /etc/ldap.conf pam_password racf /etc/pam.d/passwd looks like the following: auth required pam_env.so auth sufficientpam_ldap.so auth required pam_unix2.so account sufficientpam_ldap.so account required pam_unix2.so password sufficientpam_ldap.so session sufficientpam_ldap.so session required pam_limits.so session required pam_unix2.so session optional pam_umask.so The Red Paper titled ?Securing Linux for zSeries with Central z/OS LDAP Server (RACF)? available at http://www.redbooks.ibm.com/redpapers/pdfs/redp0221.pdf on page 21 suggest that the pam_password racf in the Linux ldap.conf allows the Linux passwd command to work with RACF. Am I missing something or have something misconfigured? Any experiences out there? Thanks as always. Peter From: Peter E Abresch/EP/PEP To: Linux on 390 Port LINUX-390@vm.marist.edu Date: 08/15/2011 05:51 PM Subject:RACF LDAP and Linux passwd command We have RACF LDAP server setup under z/OS Version 1.11. We are using SLES11-SP1 Linux. We are using LDAP to authenticate with RACF passwords and DB2 for the TDBM backend. We populated the TDBM and everything is working great with one exception. We cannot change the RACF password from Linux using the passwd command. This should work. Here is what we are seeing: x062tst@linuxm02:~ passwd Changing password for x062tst. Enter login(LDAP) password: New password: Re-enter new password: LDAP password information update failed: Protocol error R006010 Unsupported extended operation '1.3.6.1.4.1.4203.1.11.1' (srv_process_extended_request) passwd: Permission denied I am thinking this is an ACL issue but am clueless how to setup the ldif file for the ACL permission for the ldapmodify command. This is how it looks now: # ESE Testing ID, ESE, IT, PHI dn: cn=ESE Testing ID,ou=ESE,ou=IT,o=PHI cn: ESE Testing ID aclentry: cn=this:critical:w aclentry: cn=anybody:NORMAL:RSC:SYSTEM:RSC aclpropagate: TRUE aclsource: ou=ESE, ou=IT, o=PHI entryowner: access-id:cn=ldapadm,o=PHI ownerpropagate: TRUE ownersource: ou=ESE, ou=IT, o=PHI Does anyone have experience with this or can point be in the right direction. Thanks in advance. 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
Re: RACF LDAP and Linux passwd command
Thanks, I saw Rich?s presentation. This really had me stumped so I figure this had to be something on my side. I went back to the drawing board and reviewed everything and then by mistake, I found the issue. In /etc/ldap.conf, I had pam_password racf configured correctly but later on in the ldap.conf there was a pam_password exop configured. I commented out pam_password exop and now everything is working correctly. So far, RACF LDAP with TDBM is working great now. Thanks to all that viewed this issue. Peter From: Alan Altmark alan_altm...@us.ibm.com To: LINUX-390@vm.marist.edu Date: 08/16/2011 11:38 AM Subject:Re: RACF LDAP and Linux passwd command Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On Tuesday, 08/16/2011 at 07:35 EDT, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: After a good night sleep, I delved into this problem further. I do not think this is an ACL issue as I can change the password using the ldapmodify command. That's a bit confusing since R006010 Unsupported extended operation '1.3.6.1.4.1.4203.1.11.1' is a reference to Modify password. Consider looking, too, at Rich Smrcina's presentation, http://linuxvm.org/present/SHARE112/S9156rs.pdf. The z/VM LDAP server is at the z/OS R10 level. Alan Altmark Senior Managing z/VM and Linux Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
RACF LDAP and Linux passwd command
We have RACF LDAP server setup under z/OS Version 1.11. We are using SLES11-SP1 Linux. We are using LDAP to authenticate with RACF passwords and DB2 for the TDBM backend. We populated the TDBM and everything is working great with one exception. We cannot change the RACF password from Linux using the passwd command. This should work. Here is what we are seeing: x062tst@linuxm02:~ passwd Changing password for x062tst. Enter login(LDAP) password: New password: Re-enter new password: LDAP password information update failed: Protocol error R006010 Unsupported extended operation '1.3.6.1.4.1.4203.1.11.1' (srv_process_extended_request) passwd: Permission denied I am thinking this is an ACL issue but am clueless how to setup the ldif file for the ACL permission for the ldapmodify command. This is how it looks now: # ESE Testing ID, ESE, IT, PHI dn: cn=ESE Testing ID,ou=ESE,ou=IT,o=PHI cn: ESE Testing ID aclentry: cn=this:critical:w aclentry: cn=anybody:NORMAL:RSC:SYSTEM:RSC aclpropagate: TRUE aclsource: ou=ESE, ou=IT, o=PHI entryowner: access-id:cn=ldapadm,o=PHI ownerpropagate: TRUE ownersource: ou=ESE, ou=IT, o=PHI Does anyone have experience with this or can point be in the right direction. Thanks in advance. 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 lists...@vm.marist.edu 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/
Re: SLES11 Updates
Yes, I can confirm that this is corrected. A simple zypper ref and I can now go into YaST2 and download all the updates. Thanks everyone. Peter From: Mark Post mp...@novell.com To: LINUX-390@vm.marist.edu Date: 07/14/2011 02:28 PM Subject:Re: SLES11 Updates Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 7/14/2011 at 01:02 PM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: I hope that it is that simple. Any idea when the issue will be resolved? I I'm told that it is now fixed, so try a refresh, or if that fails a re-registration. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
Re: SLES11 Updates
Thanks for the reply. I will create another server and install SMT. However, I still have a problem with YaST2 and pulling the updates. I register the updates and everything seems to complete successfully, however there are never any update repositories saved. I What am I missing? Where does YaST2 store this info? Peter From: Marcy Cortes marcy.d.cor...@wellsfargo.com To: LINUX-390@vm.marist.edu Date: 07/13/2011 11:05 AM Subject:Re: SLES11 Updates Sent by:Linux on 390 Port LINUX-390@vm.marist.edu We use SMT for both sles 10 and 11. I did have to get a fix for SMT to work with our proxy server. That's likely already been included though so maybe its not your timeout problem. Marcy -Original Message- From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Peter E. Abresch Jr. - at Pepco Sent: Wednesday, July 13, 2011 7:29 AM To: LINUX-390@vm.marist.edu Subject: Re: [LINUX-390] SLES11 Updates The gateway timeout issue must have been a web service issue as I retried and it is working. Is SMT what everyone is using for mirroring updates in SLES11? Peter From: Peter E Abresch/EP/PEP To: Linux on 390 Port LINUX-390@vm.marist.edu Date: 07/13/2011 08:22 AM Subject:SLES11 Updates With SLES9 we used a YOUSERVER and with SLES10 we use YUP to mirror updates locally where we then installed them. What is the best method for SLES11. Is it SMT and when I select the options to mirror in YaST is that what it will use? Whenever I try to register for updates I get the ERROR 504: 504 Gateway Time-out. Is there an issue with the Novell Web server or is this on my end? Thanks for any clarification. 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
Re: SLES11 Updates
Thanks Mark, I hope that it is that simple. Any idea when the issue will be resolved? I am still finalizing my master image and am not in a position to create the SMT instance just yet. Peter From: Mark Post mp...@novell.com To: LINUX-390@vm.marist.edu Date: 07/14/2011 12:05 PM Subject:Re: SLES11 Updates Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 7/14/2011 at 08:09 AM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: I register the updates and everything seems to complete successfully, however there are never any update repositories saved. I What am I missing? I just received an internal email saying that our NCC backend is having some problems. New registrations are failing. Your SMT server might work, however, since it depends on your mirroring credentials that you can find in the NCC web interface. Let us know. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
SLES11 Updates
With SLES9 we used a YOUSERVER and with SLES10 we use YUP to mirror updates locally where we then installed them. What is the best method for SLES11. Is it SMT and when I select the options to mirror in YaST is that what it will use? Whenever I try to register for updates I get the ERROR 504: 504 Gateway Time-out. Is there an issue with the Novell Web server or is this on my end? Thanks for any clarification. 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 lists...@vm.marist.edu 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/
Re: SLES11 Updates
The gateway timeout issue must have been a web service issue as I retried and it is working. Is SMT what everyone is using for mirroring updates in SLES11? Peter From: Peter E Abresch/EP/PEP To: Linux on 390 Port LINUX-390@vm.marist.edu Date: 07/13/2011 08:22 AM Subject:SLES11 Updates With SLES9 we used a YOUSERVER and with SLES10 we use YUP to mirror updates locally where we then installed them. What is the best method for SLES11. Is it SMT and when I select the options to mirror in YaST is that what it will use? Whenever I try to register for updates I get the ERROR 504: 504 Gateway Time-out. Is there an issue with the Novell Web server or is this on my end? Thanks for any clarification. 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 lists...@vm.marist.edu 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/
*** No repository found when installing SLES11 with NFS option under z/VM
We are making our first attempt to installed SLES11. We previously have installed SLES8-SLES10 in the past. I copied the DVD installation to my NFS server and configured the proper permissions. We go through the process up to where it prompts to enter the server directory, see below: Enter the directory on the server -/usr/local/share/sles11-s390x/DVD1- *** No repository found. What are we missing, from the NFS server I see the following: 2ua61914jt:/usr/local/share/sles11-s390x/DVD1 # ls -l total 10006 -rw-r--r-- 1 x062pea users 4773764 2010-06-29 12:53 ARCHIVES.gz drwx-- 4 x062pea users 128 2010-06-29 12:55 boot -rw-r--r-- 1 x062pea users 4960271 2010-06-29 12:53 ChangeLog -rw-r--r-- 1 x062pea users 13076 2010-06-29 12:54 content -rw-r--r-- 1 x062pea users 307 2010-06-29 12:54 content.asc -rw-r--r-- 1 x062pea users 613 2010-06-29 12:54 content.key -rw-r--r-- 1 x062pea users 55168 2010-06-29 12:54 control.xml -rw-r--r-- 1 x062pea users 17992 2010-06-29 12:54 COPYING -rw-r--r-- 1 x062pea users 25733 2010-06-29 12:54 COPYING.de -rw-r--r-- 1 x062pea users1455 2010-06-29 12:54 COPYRIGHT -rw-r--r-- 1 x062pea users1620 2010-06-29 12:54 COPYRIGHT.de -rw-r--r-- 1 x062pea users 465 2010-06-29 12:55 directory.yast drwx-- 17 x062pea users 528 2010-06-29 12:58 docu -rw-r--r-- 1 x062pea users 877 2010-06-29 12:55 gpg-pubkey-0dfb3188-41ed929b.asc -rw-r--r-- 1 x062pea users1032 2010-06-29 12:55 gpg-pubkey-1d061a62-4bd70bfa.asc -rw-r--r-- 1 x062pea users 613 2010-06-29 12:55 gpg-pubkey-307e3d54-4be01a65.asc -rw-r--r-- 1 x062pea users1694 2010-06-29 12:55 gpg-pubkey-3d25d3d9-36e12d04.asc -rw-r--r-- 1 x062pea users 938 2010-06-29 12:55 gpg-pubkey-7e2e3b05-4be037ca.asc -rw-r--r-- 1 x062pea users1698 2010-06-29 12:55 gpg-pubkey-9c800aca-4be01999.asc -rw-r--r-- 1 x062pea users1803 2010-06-29 12:55 gpg-pubkey-a1912208-446a0899.asc -rw-r--r-- 1 x062pea users1348 2010-06-29 12:55 gpg-pubkey-b37b98a9-4be01a1a.asc -rw-r--r-- 1 x062pea users 28642 2010-06-29 12:55 INDEX.gz -rw-r--r-- 1 x062pea users 110070 2010-06-29 12:57 license.tar.gz -rw-r--r-- 1 x062pea users 45813 2010-06-29 12:57 ls-lR.gz drwx-- 2 x062pea users 216 2010-06-29 12:58 media.1 -rw-r--r-- 1 x062pea users 111657 2010-06-29 12:58 NEWS -rw-r--r-- 1 x062pea users6774 2010-06-29 12:58 pubring.gpg -rw-r--r-- 1 x062pea users3246 2010-06-29 12:58 README drwx-- 6 x062pea users 144 2010-06-29 12:52 suse -rw-r--r-- 1 x062pea users 210 2010-06-29 13:00 suse.ins 2ua61914jt:/usr/local/share/sles11-s390x/DVD1 # Thanks as always. 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 lists...@vm.marist.edu 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/
Re: *** No repository found when installing SLES11 with NFS option under z/VM
No, that was not it. Enter the directory on the server -/usr/local/share/sles11-s390x/DVD1/- *** No repository found. From: Luciano Mannucci luci...@vespaperitivo.it To: LINUX-390@vm.marist.edu Date: 03/10/2011 02:09 PM Subject:Re: *** No repository found when installing SLES11 with NFS option under z/VM Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On Thu, 10 Mar 2011 13:31:56 -0500 Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: Enter the directory on the server -/usr/local/share/sles11-s390x/DVD1- *** No repository found. What are we missing Maybe a trailing / ? Cheers, Luciano Mannucci. -- /\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL/ E-MAIL: posthams...@sublink.sublink.org / \ AND POSTINGS/ WWW: http://www.mannucci.ORG/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
Re: *** No repository found when installing SLES11 with NFS option under z/VM
The umask on this system was: 2ua61914jt:/ # umask 0022 I entered the find command as suggested and retried. I made it further along the install where it is now prompting for display type. I am now trying to remember how I created the DVD image as it has been about 8 months ago. Thanks to everyone that responded. This group is the best when it comes to assistance. Peter From: Mark Post mp...@novell.com To: LINUX-390@vm.marist.edu Date: 03/10/2011 02:11 PM Subject:Re: *** No repository found when installing SLES11 with NFS option under z/VM Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 3/10/2011 at 01:31 PM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: We are making our first attempt to installed SLES11. We previously have installed SLES8-SLES10 in the past. I copied the DVD installation to my NFS server and configured the proper permissions. We go through the process up to where it prompts to enter the server directory, see below: Enter the directory on the server -/usr/local/share/sles11-s390x/DVD1- *** No repository found. What are we missing, from the NFS server I see the following: 2ua61914jt:/usr/local/share/sles11-s390x/DVD1 # ls -l total 10006 -rw-r--r-- 1 x062pea users 4773764 2010-06-29 12:53 ARCHIVES.gz drwx-- 4 x062pea users 128 2010-06-29 12:55 boot -snip- drwx-- 17 x062pea users 528 2010-06-29 12:58 docu -snip- drwx-- 2 x062pea users 216 2010-06-29 12:58 media.1 -snip- drwx-- 6 x062pea users 144 2010-06-29 12:52 suse Try running find . -type d -print0 | xargs -0 chmod 755 and see if that helps. The fact that there are no group or other read/execute permissions on those directories makes me think that's your problem. (What's your umask set to on that system?) Mark -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
Re: kernel: page allocation failure recommendations
Thanks to all that responded. I appreciate everyone's responsiveness. I increased vm.swappiness from 60 to 80. It is too early to tell if it made any significant difference. We have also accelerated our plans to move forward with our SLE-10-s390x-SP3 production implementation. Peter Shane Ginnane sginn...@isi.com.au Sent by: Linux on 390 Port LINUX-390@vm.marist.edu 08/04/2010 10:10 PM Please respond to Linux on 390 Port LINUX-390@vm.marist.edu To LINUX-390@vm.marist.edu cc Subject Re: kernel: page allocation failure recommendations I quite liked this from one of the kernel devs: quote But please bear in mind, this page allocation failure message is purely a developer diagnostic thing. The reason it is there is so that if some random toaster driver oopses over a failure to handle an allocation failure, the person who reports the bug can say I saw an allocation failure and then your driver crashed. Which tells the driver developer where to look. /quote Although recoverable, I'd be looking at adding storage to the guest. I can't see swappiness helping in this context - but I don't see it harming either, and I generally agree with the sentiment that it should be lower in a z/ environment. Getting up to date on the kernel would also be a good idea as Mark suggested - lots of reports on late 2.5 and early 2.6 kernels. Shane ... (interestingly I don't see this post on the maillist archive) Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 05/08/2010 02:56:54 AM: We are running the following Linux: Linux linuxp01 2.6.5-7.315-s390x #1 SMP Wed Nov 26 13:03:18 UTC 2008 s390x s390x s390x GNU/Linux with SLES-9-s390x-SP4 + online updates under /VM Version 5 Release 4.0, service level 0902 (64-bit). Linux is defined with 768MB of memory. We recently implemented CICS Transaction Gateway version 6.0.1 fix pack and since then are seeing some page fault errors. However, I am not really seeing memory shortage issues with the z/VM monitor or the Linux free ?m errors. I am thinking about lowering vm.swappiness from 60. What does everyone think, is that worth doing? Any other recommendations? We are limited on memory resources but if push came to shove, I could increase from 768MB to 1024MB and increase the swap space accordingly. I know, I know, all this stuff is old, but we are in the process of upgrading. 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 lists...@vm.marist.edu 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/
SLES11install doc for z/Series
I am downloading SLES11-SP1 for z/Series. However, I have not found any documentation to get me started installing this as a z/VM guest. In the past, I mounted the image via NFS and started the process. Does anyone have a link or something to get me started or is the z/Series install doc part of the ISO image? Any changes since SLES10? Thanks. 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 lists...@vm.marist.edu 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/
Re: SLES11install doc for z/Series
Thanks. That is what I was looking for. Peter Mike Friesenegger mfrieseneg...@novell.com Sent by: Linux on 390 Port LINUX-390@vm.marist.edu 06/29/2010 11:45 AM Please respond to Linux on 390 Port LINUX-390@vm.marist.edu To LINUX-390@vm.marist.edu cc Subject Re: SLES11install doc for z/Series Peter, http://www.novell.com/documentation/sles11/book_sle_deployment/data/cha_zseries.html is the System z specific information in the SLES11 documentation. The install for SLES11 SP1 nearly identical to SLES10. Punch the IMAGE, PARMFILE and INITRD. IPL the reader to start the installer and then point the installation to a NFS, FTP or HTTP install source. I hope this helps. Mike On 6/29/2010 at 08:57 AM, in message ofc5a6e9e7.b738bc67-on85257751.00520d0c-85257751.00523...@pepco.com, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: I am downloading SLES11-SP1 for z/Series. However, I have not found any documentation to get me started installing this as a z/VM guest. In the past, I mounted the image via NFS and started the process. Does anyone have a link or something to get me started or is the z/Series install doc part of the ISO image? Any changes since SLES10? Thanks. 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu 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/ 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 lists...@vm.marist.edu 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/
/var/lib/zypp/cache/ is on my nerves
We have various Linux SLES10 SP3 guests under z/VM. We use YaST to apply the patches using our local YUM server. However, I see the following directory continue to grow. /var/lib/zypp/cache/ This directory contains many other directories in the form of Source.random characters/repodata. Each of these directories contains various patches. Question 1: Why/how does this directory grow? We checked novell-zmd and it is set to off so it should not be running. Question 2: Space is limited in our shop. Can I delete these directories? I have these same patches on our local YUM server and this seems to be a waste of space. Thanks as always. 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: /var/lib/zypp/cache/ is on my nerves
Thanks, but it looks like yum clean only applies to the yum server, unless I mis-understood something. I am seeing these issues on my SLES10 SP3 guests where I do not run the yum server. On these guests, I use YaST and point it to our local YUM server. This growth appears to be from Novell?s zmd, even though I have it configured off, it continues to fill our /var/ directory with patches that we already have on the YUM server. I do not know how, or why. We do not knowingly use rug either. Is it safe to clear these directories out? Peter Pat Carroll pcarr...@llbean.com Sent by: Linux on 390 Port LINUX-390@vm.marist.edu 04/23/2010 09:51 AM Please respond to Linux on 390 Port LINUX-390@vm.marist.edu To LINUX-390@vm.marist.edu cc Subject Re: /var/lib/zypp/cache/ is on my nerves See: yum clean Patrick Carroll | Technology Architect II L.L.Bean, Inc.(r) | Double L St. | Freeport ME 04033 http://www.llbean.com | pcarr...@llbean.com | 207.552.2426 CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s). Any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Peter E. Abresch Jr. - at Pepco Sent: Friday, April 23, 2010 9:46 AM To: LINUX-390@VM.MARIST.EDU Subject: /var/lib/zypp/cache/ is on my nerves We have various Linux SLES10 SP3 guests under z/VM. We use YaST to apply the patches using our local YUM server. However, I see the following directory continue to grow. /var/lib/zypp/cache/ This directory contains many other directories in the form of Source.random characters/repodata. Each of these directories contains various patches. Question 1: Why/how does this directory grow? We checked novell-zmd and it is set to off so it should not be running. Question 2: Space is limited in our shop. Can I delete these directories? I have these same patches on our local YUM server and this seems to be a waste of space. Thanks as always. 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: /var/lib/zypp/cache/ is on my nerves
Thanks for those that responded. The yum command is not available on these Linux guests. Did you want me to run this on my YUM sever? My YUM server does not know about these Linux guests? I ran the command as follows: linuxd02:/var/lib/zypp/cache # rug get-prefs | grep cache cache-cleanup-enabled | True | Automatically clean up the cache cache-directory| /var/cache/zmd/web | The directory to store cached packages and metadata cache-max-size-hard-limit | False | If true, never allow the cache to grow past the maximum size cache-max-size-in-mb | 300| The maximum size of the cache (in mb) max-cache-age | 30 | The maximum number of days to cache a file Is there any hope here? Peter Mark Post mp...@novell.com Sent by: Linux on 390 Port LINUX-390@vm.marist.edu 04/23/2010 11:58 AM Please respond to Linux on 390 Port LINUX-390@vm.marist.edu To LINUX-390@vm.marist.edu cc Subject Re: /var/lib/zypp/cache/ is on my nerves On 4/23/2010 at 09:45 AM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: Question 2: Space is limited in our shop. Can I delete these directories? I have these same patches on our local YUM server and this seems to be a waste of space. No. This is the information your system needs to do dependency checking and to figure out what patches are needed for your system when you decide it's time to update. If you do a rug get-prefs | grep cache what comes back? (You'll need to temporarily start zmd for this to work). Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: /var/lib/zypp/cache/ is on my nerves
Thanks, I made the changes. I also notice the following in /var/cache/zmd/web/files/nu.novell.com/repo/$RCE: linuxd02:/var/cache/zmd/web/files/nu.novell.com/repo/$RCE # ls -l total 0 drwxr-xr-x 3 root root 80 Apr 11 20:16 SLE10-SP1-Debuginfo-Updates drwxr-xr-x 3 root root 80 Apr 11 20:23 SLE10-SP2-Debuginfo-Updates drwxr-xr-x 3 root root 80 Apr 11 20:28 SLE10-SP3-Debuginfo-Online drwxr-xr-x 3 root root 80 Apr 11 20:28 SLE10-SP3-Debuginfo-Pool drwxr-xr-x 3 root root 80 Apr 11 20:27 SLE10-SP3-Debuginfo-Updates drwxr-xr-x 3 root root 80 Apr 11 20:08 SLES10-SP1-Online drwxr-xr-x 3 root root 80 Apr 11 20:11 SLES10-SP1-Updates drwxr-xr-x 3 root root 80 Apr 11 20:17 SLES10-SP2-Online drwxr-xr-x 3 root root 80 Apr 11 20:25 SLES10-SP2-Pool drwxr-xr-x 3 root root 80 Apr 11 20:18 SLES10-SP2-Updates drwxr-xr-x 3 root root 80 Mar 4 06:59 SLES10-SP3-Online drwxr-xr-x 3 root root 80 Apr 11 20:27 SLES10-SP3-Pool drwxr-xr-x 3 root root 80 Apr 11 20:25 SLES10-SP3-Updates Again, all these look like patches, I can I stop these and since we are SP3 everywhere, can I safely delete all the non-SP3 directories? Peter Mark Post mp...@novell.com Sent by: Linux on 390 Port LINUX-390@vm.marist.edu 04/23/2010 12:18 PM Please respond to Linux on 390 Port LINUX-390@vm.marist.edu To LINUX-390@vm.marist.edu cc Subject Re: /var/lib/zypp/cache/ is on my nerves On 4/23/2010 at 12:06 PM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: cache-max-size-hard-limit | False | If true, never allow the cache to grow past the maximum size cache-max-size-in-mb | 300| The maximum size of the cache (in mb) max-cache-age | 30 | The maximum number of days to cache a file Is there any hope here? By changing these values you can limit how much space is taken up on your systems. I'm not sure just how much you're going to be saving though. On the system I checked, /var/lib/zypp/ is only taking up about 12MB. Another one is using 40MB. In any case, you can use rug set-prefs to change them, one preference at a time: rug set-prefs cache-max-size-hard-limit true rug set-prefs cache-max-size-in-mb 200 and so on. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: yast procedure for going from SLE-10-s390x-SP2 to SLE-10-s390x-SP3
Thanks to all that responded. Novell had to delete my mirror credentials and regenerate them and Lord and behold, YUP is downloading my SP3 stuff. I have since upgraded one of my Linux guest to SP3. 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
yast procedure for going from SLE-10-s390x-SP2 to SLE-10-s390x-SP3
Hello everyone, I have been away for awhile. We are currently running SLE-10-s390x-SP2 + online updates. We will like to upgrade to SP3. I like to use our local yup repository and use Yast2 to upgrade by applying the move-to-sles10-sp3 patch. I changed the following on our YUM server config file /etc/sysconfig/yup: From YUP_SUBVERSIONS=SP2 To YUP_SUBVERSIONS=SP2 SP3 And ran /usr/sbin/yup After yup ran, I still only see the following in directory in our yup repository: drwxr-xr-x 3 root root 80 Jun 16 2008 SLES10-SP2-Online drwxr-xr-x 3 root root 80 Jun 16 2008 SLES10-SP2-Updates What did I miss? Is there a link to some procedures for this? Thanks for any info. 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: yast procedure for going from SLE-10-s390x-SP2 to SLE-10-s390x-SP3
Thanks, I read through the link. The link for the yup rpm is dead. We are currently running yup-232-2.2. I signed on to the Novell Support site but could not find the new yup package. If memory serves me, the yup package was not included with the normal SLES stuff. Does anyone have a link to the latest and greatest yup rpm? Thanks. Peter Marcy Cortes marcy.d.cor...@wellsfargo.com Sent by: Linux on 390 Port LINUX-390@vm.marist.edu 03/01/2010 11:45 AM Please respond to Linux on 390 Port LINUX-390@vm.marist.edu To LINUX-390@vm.marist.edu cc Subject Re: yast procedure for going from SLE-10-s390x-SP2 to SLE-10-s390x-SP3 http://forums.novell.com/tags/yup%20sp3%20sles10%20s390x.html I think you need a new yup. Marcy Cortes Team Lead, Enterprise Virtualization - z/VM and z/Linux Enterprise Hosting Services, Mainframe/Midrange Services MAC A0187-050 201 3rd St. San Francisco, CA 94103 w. (415) 477-6343 c. (415) 517-0895 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: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Peter E. Abresch Jr. - at Pepco Sent: Monday, March 01, 2010 8:28 AM To: LINUX-390@vm.marist.edu Subject: [LINUX-390] yast procedure for going from SLE-10-s390x-SP2 to SLE-10-s390x-SP3 Hello everyone, I have been away for awhile. We are currently running SLE-10-s390x-SP2 + online updates. We will like to upgrade to SP3. I like to use our local yup repository and use Yast2 to upgrade by applying the move-to-sles10-sp3 patch. I changed the following on our YUM server config file /etc/sysconfig/yup: From YUP_SUBVERSIONS=SP2 To YUP_SUBVERSIONS=SP2 SP3 And ran /usr/sbin/yup After yup ran, I still only see the following in directory in our yup repository: drwxr-xr-x 3 root root 80 Jun 16 2008 SLES10-SP2-Online drwxr-xr-x 3 root root 80 Jun 16 2008 SLES10-SP2-Updates What did I miss? Is there a link to some procedures for this? Thanks for any info. 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: yast procedure for going from SLE-10-s390x-SP2 to SLE-10-s390x-SP3
Thanks, I found it here and was able to download it and upgrade. We are now running yup-232-12.1. I ran the yup process again and see the following: drwxr-xr-x 3 root root 80 Jun 16 2008 SLES10-SP2-Online drwxr-xr-x 3 root root 80 Jun 16 2008 SLES10-SP2-Updates drwxr-xr-x 3 root root 80 Mar 1 13:57 SLES10-SP3-Online drwxr-xr-x 3 root root 80 Mar 1 13:57 SLES10-SP3-Updates /var/cache/yup/SLES10-SP3-Online/sles-10-s390x/repodata but contains nothing more. Also, /var/cache/yup/SLES10-SP3-Updates/sles-10-s390x/repodata contains nothing more. Not the data I was expecting. I review the logs of the yup process and see the following: Using https://nu.novell.com/repo/$RCE/SLES10-SP3-Updates/sles-10-s390x Fetching https://nu.novell.com/repo/$RCE/SLES10-SP3-Updates/sles-10-s390x/repodata/repomd.xml.asc.. . FAILED with exit code 22 Failure details: Warning: Illegal date format for -z/--timecond (and not a file name). Warning: Disabling time condition. See curl_getdate(3) for valid date syntax. * About to connect() to nu.novell.com port 443 * Trying 69.192.150.34... connected * Connected to nu.novell.com (69.192.150.34) port 443 * successfully set certificate verify locations: * CAfile: /usr/share/curl/curl-ca-bundle.crt CApath: none * SSLv2, Client hello (1): SSLv3, TLS handshake, Server hello (2): SSLv3, TLS handshake, CERT (11): SSLv3, TLS handshake, Server finished (14): SSLv3, TLS handshake, Client key exchange (16): SSLv3, TLS change cipher, Client hello (1): SSLv3, TLS handshake, Finished (20): SSLv3, TLS change cipher, Client hello (1): SSLv3, TLS handshake, Finished (20): SSL connection using AES256-SHA * Server certificate: *subject: /C=US/ST=Utah/L=Provo/O=Novell, Inc./CN=nu.novell.com *start date: 2009-10-12 10:06:49 GMT *expire date: 2010-11-13 01:29:03 GMT *common name: nu.novell.com (matched) *issuer: /C=US/O=Equifax/OU=Equifax Secure Certificate Authority * SSL certificate verify ok. * Server auth using Basic with user '336262' GET /repo/$RCE/SLES10-SP3-Updates/sles-10-s390x/repodata/repomd.xml.asc HTTP/1.1 This continued but to say the least, nothing was downloaded. Is this a problem with yup-232-12.1 or did I miss something else. Peter Quay, Jonathan (IHG) jonathan.q...@ihg.com Sent by: Linux on 390 Port LINUX-390@vm.marist.edu 03/01/2010 01:33 PM Please respond to Linux on 390 Port LINUX-390@vm.marist.edu To LINUX-390@vm.marist.edu cc Subject Re: yast procedure for going from SLE-10-s390x-SP2 to SLE-10-s390x-SP3 This looks like it too. http://download.opensuse.org/repositories/home:/msmeissn/SLE_10/noarch/ -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Peter E. Abresch Jr. - at Pepco Sent: Monday, March 01, 2010 1:21 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: yast procedure for going from SLE-10-s390x-SP2 to SLE-10-s390x-SP3 Thanks, I read through the link. The link for the yup rpm is dead. We are currently running yup-232-2.2. I signed on to the Novell Support site but could not find the new yup package. If memory serves me, the yup package was not included with the normal SLES stuff. Does anyone have a link to the latest and greatest yup rpm? Thanks. Peter Marcy Cortes marcy.d.cor...@wellsfargo.com Sent by: Linux on 390 Port LINUX-390@vm.marist.edu 03/01/2010 11:45 AM Please respond to Linux on 390 Port LINUX-390@vm.marist.edu To LINUX-390@vm.marist.edu cc Subject Re: yast procedure for going from SLE-10-s390x-SP2 to SLE-10-s390x-SP3 http://forums.novell.com/tags/yup%20sp3%20sles10%20s390x.html I think you need a new yup. Marcy Cortes Team Lead, Enterprise Virtualization - z/VM and z/Linux Enterprise Hosting Services, Mainframe/Midrange Services MAC A0187-050 201 3rd St. San Francisco, CA 94103 w. (415) 477-6343 c. (415) 517-0895 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: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Peter E. Abresch Jr. - at Pepco Sent: Monday, March 01, 2010 8:28 AM To: LINUX-390@vm.marist.edu Subject: [LINUX-390] yast procedure for going from SLE-10-s390x-SP2 to SLE-10-s390x-SP3 Hello everyone, I have been away for awhile. We are currently running SLE-10-s390x-SP2 + online updates. We will like to upgrade to SP3. I like to use our local yup repository and use Yast2 to upgrade by applying the move-to-sles10-sp3 patch. I changed the following on our YUM server config file /etc/sysconfig/yup: From YUP_SUBVERSIONS=SP2 To YUP_SUBVERSIONS=SP2 SP3 And ran /usr
Re: yast procedure for going from SLE-10-s390x-SP2 to SLE-10-s390x-SP3
Thanks Mark, Can I install SMT11 under SLES10? I am not in a position to install sles11 at the moment. I have previously upgraded to SP1 and from SP1 to SP2 but it has been a while and I do not know the steps that I had to take. If yup will not work, what process should I use? Does Novell have SLES10-SP2 to SLES10-SP3 upgrade procedures that I can follow? Peter Mark Post mp...@novell.com Sent by: Linux on 390 Port LINUX-390@vm.marist.edu 03/01/2010 01:53 PM Please respond to Linux on 390 Port LINUX-390@vm.marist.edu To LINUX-390@vm.marist.edu cc Subject Re: yast procedure for going from SLE-10-s390x-SP2 to SLE-10-s390x-SP3 On 3/1/2010 at 11:27 AM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: We will like to upgrade to SP3. I like to use our local yup repository and use Yast2 to upgrade by applying the move-to-sles10-sp3 patch. I don't know that using a YUP repository is going to work for this type of upgrade. There is some interaction between the system being upgraded and the update server to get the new update catalogs visible and subscribed. YUP isn't going to do that for you. If you haven't already (and it seems clear you haven't), it's time to turn your YUP server into a SLES11/SMT11 server. I think you'll like it better, and it's supported. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: yast procedure for going from SLE-10-s390x-SP2 to SLE-10-s390x-SP3
Yeah, throwing up SLES11 is not easy for me. I have to get SLES10-SP3 running, migrate my SLES9x to SLES10-SP3 so I can free up some DASD to even think about SLES11. This problem is similar for me when I was going from SP1 to SP2. The problem was caused by Mirroring Credentials. Do I have to change the Mirroring Credentials for SP3? Peter Marcy Cortes marcy.d.cor...@wellsfargo.com Sent by: Linux on 390 Port LINUX-390@vm.marist.edu 03/01/2010 04:26 PM Please respond to Linux on 390 Port LINUX-390@vm.marist.edu To LINUX-390@vm.marist.edu cc Subject Re: yast procedure for going from SLE-10-s390x-SP2 to SLE-10-s390x-SP3 Well, I'm not Peter, but some of us can't just throw up a sles11 for use without it having the other layered prereqs (security, authentication, blah blah) on top of it. And those involve other groups that also have too much on their plates. I did send him the procedure I used to online update from SP2 to SP3 probably 120+ servers. I didn't send to the whole list becaues I'd have to weed out the stuff that is specific to me. If anyone would like it as is, let me know. 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: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Post Sent: Monday, March 01, 2010 12:33 PM To: LINUX-390@vm.marist.edu Subject: Re: [LINUX-390] yast procedure for going from SLE-10-s390x-SP2 to SLE-10-s390x-SP3 On 3/1/2010 at 03:12 PM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: Thanks Mark, Can I install SMT11 under SLES10? I am not in a position to No. install sles11 at the moment. I have previously upgraded to SP1 and from SP1 to SP2 but it has been a while and I do not know the steps that I had to take. If yup will not work, what process should I use? Does Novell have SLES10-SP2 to SLES10-SP3 upgrade procedures that I can follow? Yes, but they all involve down server upgrades unless you have a correctly configured update server available. You could use the official nu.novell.com web site, but that means everything you update would have to go out over the Internet. Alternatively, you could use SMT 1.0, but that isn't available for System z, so you'd have to use an Intel/AMD box for that. I suspect installing SLES11 and SMT11 on a new z/VM guest would be a lot faster, but I don't know why you say you're not in a position to do that. Mark -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: yast procedure for going from SLE-10-s390x-SP2 to SLE-10-s390x-SP3
Thanks for your continued patience. When I use a web browser and point it to? https://nu.novell.com/repo/$RCE/SLES10-SP3-Updates/ and sign on, I get the following: Index of /repo/$RCE/SLES10-SP3-Updates NameLast modified Size Description Parent Directory - sles-10-i586/ 01-Oct-2009 04:25- sles-10-ia64/ 01-Oct-2009 04:25- sles-10-ppc/01-Oct-2009 04:25- sles-10-s390x/ 01-Oct-2009 04:25- sles-10-x86_64/ 01-Oct-2009 04:25- However, if I select sles-10-s390x I get 403 Forbidden Information Alert Status : 403 Forbidden Description : Access to this page is restricted because of access control policies. This process works fine for: https://nu.novell.com/repo/$RCE/SLES10-SP2-Updates/ what gives? Peter Mark Post mp...@novell.com Sent by: Linux on 390 Port LINUX-390@vm.marist.edu 03/01/2010 05:09 PM Please respond to Linux on 390 Port LINUX-390@vm.marist.edu To LINUX-390@vm.marist.edu cc Subject Re: yast procedure for going from SLE-10-s390x-SP2 to SLE-10-s390x-SP3 On 3/1/2010 at 04:43 PM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: This problem is similar for me when I was going from SP1 to SP2. The problem was caused by Mirroring Credentials. Do I have to change the Mirroring Credentials for SP3? No. Your company's NCC account shows that your mirroring credentials cover SLES10 SP3. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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. inline: image/gifinline: image/gifinline: image/gifinline: image/gifinline: image/gifinline: image/gifinline: image/gifinline: image/gifinline: image/gifinline: image/gif
Re: z/VM 5.1 to 5.3 upgrade ( a little handholding requested) Many Thanks
I want to thank everyone on this list that assisted us with their ideas and recommendations on our z/VM Upgrade (z/VM Handholding). We were able to gleam through all the great ideas and develop a z/VM installation, testing, and implementation philosophy that made sense to our years of z/OS ideology. This ideology allowed our operators to implement z/VM with an IPL or back it out with an IPL. This also works with z/VM maintenance. We successfully upgraded our z/VM from version 5.1 to version 5.3 without incident this past weekend and have gained a better understanding and respect for z/VM in the process. z/VM exist in our shop strictly for managing Linux and as such, we know we barely scratch the surface for unlocking the many hidden strengths and possible potentials of z/VM, outside of those required for managing Linux. However, we no longer look at z/VM maintenance and upgrades with intrepidation. Thanks again. 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
Re: Linux guest on a diet
-23 12:19:32 0 linuxyum(3142) [zypp]
ExternalProgram.cc(start_program):283 pid 3213 launched
2008-06-23 12:19:32 0 linuxyum(3142) [zypp] PathInfo.cc(copy_dir):462
/bin/cp: cannot access `/var/adm/mount/AP_0x0002/media.1': Permission
denied
2008-06-23 12:19:32 0 linuxyum(3142) [zypp]
ExternalProgram.cc(checkStatus):330 pid 3213 exited with status 1
2008-06-23 12:19:32 0 linuxyum(3142) [zypp] PathInfo.cc(_Log_Result):296
FAILED: returned 1
2008-06-23 12:19:32 5 linuxyum(3142) [base] Exception.cc(log):94
SuseTagsImpl.cc(downloadMetadata):340 THROW:
SuseTagsImpl.cc(downloadMetadata):340: Unable to copy media directory to
/var/tmp/TmpDir.q1EmBx/MEDIA
2008-06-23 12:19:32 0 linuxyum(3142) [zypp] PathInfo.cc(_Log_Result):296
recursive_rmdir /var/tmp/TmpDir.q1EmBx
2008-06-23 12:19:32 0 linuxyum(3142) [zypp] TmpPath.cc(~Impl):78 TmpPath
cleaned up /var/tmp/TmpDir.q1EmBx{d 0700 0/0}
2008-06-23 12:19:32 0 linuxyum(3142) [zypp] PathInfo.cc(_Log_Result):296
recursive_rmdir /var/tmp/TmpDir.ExrBeL
2008-06-23 12:19:32 0 linuxyum(3142) [zypp] TmpPath.cc(~Impl):78 TmpPath
cleaned up /var/tmp/TmpDir.ExrBeL{d 0700 0/0}
2008-06-23 12:19:32 5 linuxyum(3142) [base] Exception.cc(log):94
SourceImpl.cc(factoryCtor):187 RETHROW:
SuseTagsImpl.cc(downloadMetadata):340: Unable to copy media directory to
/var/tmp/TmpDir.q1EmBx/MEDIA
2008-06-23 12:19:32 5 linuxyum(3142) [base] Exception.cc(log):94
SourceFactory.cc(createSourceImplWorkflow):184 CAUGHT:
SourceImpl.cc(factoryCtor):187: Unable to copy media directory to
/var/tmp/TmpDir.q1EmBx/MEDIA
2008-06-23 12:19:32 1 linuxyum(3142) [YCP] PackageCallbacks.ycp:887
Source create: error: url:
nfs://10.10.33.245/usr/local/share/sles10-s390x/DVD, error: UNKNOWN,
description: Unknown Error: Unable to copy media directory to
/var/tmp/TmpDir.q1EmBx/MEDIA
Mark Post [EMAIL PROTECTED]
Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU
06/20/2008 12:55 PM
Please respond to
Linux on 390 Port LINUX-390@VM.MARIST.EDU
To
LINUX-390@VM.MARIST.EDU
cc
Subject
Re: Linux guest on a diet
On Fri, Jun 20, 2008 at 12:50 PM, in message
[EMAIL PROTECTED],
Peter
E. Abresch Jr. - at Pepco [EMAIL PROTECTED] wrote:
Thanks as always Mark,
Do I have to order the SP2 media or does Novell ship it automatically?
Neither. Go to http://download.novell.com/Download?buildid=A-zpMLVoXGg~
and download the DVD .iso file. You only need DVD1 unless you also want
all the source RPMs (which most people don't).
Mark Post
--
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
Re: Linux guest on a diet
That was it. The DVD image had the drwx-- for all the directory entries off of the DVD?s root. I had to issued the following: chmod 555 -R boot chmod 555 -R docu chmod 555 -R dosutils chmod 555 -R media.1 chmod 555 -R patches That seems to have taken care of it. H. Thanks Peter Mark Post [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 06/23/2008 01:34 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: Linux guest on a diet On Mon, Jun 23, 2008 at 12:35 PM, in message [EMAIL PROTECTED], Peter E. Abresch Jr. - at Pepco [EMAIL PROTECTED] wrote: I downloaded the SLES10-SP2 DVD ISO and copied it to my local Linux server in directory /usr/local/share/sles10-s390x/DVD. I have the following directories, the CDx is from my original SLES10 installation. drwxr-xr-x 7 root root 944 Apr 19 2007 CD1 drwxr-xr-x 4 root root 224 Apr 19 2007 CD2 drwxr-xr-x 4 root root 224 Apr 19 2007 CD3 drwxr-xr-x 4 root root 224 Apr 19 2007 CD4 drwxr-xr-x 8 root root 968 Jun 20 15:48 DVD I go into YaST2 and add another NFS installation source. I enter my NFS IP address and Path to directory image is /usr/local/share/sles10-s390x/DVD. ISO Image option is not checked. The file structure looks just like that of CD1. However, it fails with the following from the YaST2 log: This looks to be the most relevant messages: 2008-06-23 12:19:32 0 linuxyum(3142) [zypp] ExternalProgram.cc(start_program):172 copy_dir /var/adm/mount/AP_0x0002/media.1 - /var/tmp/TmpDir.q1EmBx/MEDIA Executing '/bin/cp' '-dR' '--' '/var/adm/mount/AP_0x0002/media.1' '/var/tmp/TmpDir.q1EmBx/MEDIA' 2008-06-23 12:19:32 0 linuxyum(3142) [zypp] ExternalProgram.cc(start_program):283 pid 3213 launched 2008-06-23 12:19:32 0 linuxyum(3142) [zypp] PathInfo.cc(copy_dir):462 /bin/cp: cannot access `/var/adm/mount/AP_0x0002/media.1': Permission denied 2008-06-23 12:19:32 0 linuxyum(3142) [zypp] ExternalProgram.cc(checkStatus):330 pid 3213 exited with status 1 2008-06-23 12:19:32 0 linuxyum(3142) [zypp] PathInfo.cc(_Log_Result):296 FAILED: returned 1 So, for whatever reason, the media.1 directory on the NFS server is not readable due to permissions. Take a look at it from both the NFS server side, and the NFS client side to see what the permissions are. Mark Post -- 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
Linux guest on a diet
I removed many packages and in affect, put my Linux guests on a diet. Just a few more questions: I used local yum servers and YaST2 to perform all my maintenance and product installations. Can I remove the contents of the following which tends to grow. I think these grow whenever I change the installation sources and YaST2 performs a sync by default. /var/lib/zmd /var/lib/zypp We clone our Linux guests from a master guest which have already been converted to SLES10-SP2. Once I have my other Linux systems upgraded to SP2, can I remove the following and stop mirroring these channels in yup since SP2 is a replacement? /var/cache/yup/SLES10-SP1-Online /var/cache/yup/SLES10-SP1-Updates Are there any other DASD space saving ideas? Thanks 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
Re: Linux guest on a diet
Thanks as always Mark, Do I have to order the SP2 media or does Novell ship it automatically? Peter Mark Post [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 06/20/2008 12:45 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: Linux guest on a diet On Fri, Jun 20, 2008 at 11:05 AM, in message [EMAIL PROTECTED], Peter E. Abresch Jr. - at Pepco [EMAIL PROTECTED] wrote: -snip- Can I remove the contents of the following which tends to grow. I think these grow whenever I change the installation sources and YaST2 performs a sync by default. /var/lib/zmd I wouldn't delete anything here. If you want the zmd.db database file to get rebuilt, you can do a rug restart --clean command. It will be no bigger then necessary, but still in the tens of megabytes. /var/lib/zypp I can't really recommend deleting stuff out of here. If you decide to do it anyway, don't delete any of the directory structure, just the files. I've run into problems (recently) where I got a little over-zealous and had to put back some directories manually. We clone our Linux guests from a master guest which have already been converted to SLES10-SP2. Once I have my other Linux systems upgraded to SP2, can I remove the following and stop mirroring these channels in yup since SP2 is a replacement? /var/cache/yup/SLES10-SP1-Online /var/cache/yup/SLES10-SP1-Updates Yes. You probably won't need the SP2-Online channel either. Note that if you decide you need to install packages that you haven't installed previously, you'll want to have the full SP2 media laying around somewhere as well. Mark Post -- 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
SPident not showing SLES10-SP2
I upgraded to SLES10-SP2 and all seems well. I then enter SPident because I like seeing SP2 installed and I get the following: CONCLUSION: System is NOT up-to-date! foundSLE-10-s390x-SP1 + online updates expected SLE-10-s390x-SP2 e! a SPident ?vvv indicates the following: - cdparanoia-32bit IIIalpha9.8-562.4 IIIalpha9.8-562.7 What is this? I tried to uninstall this but started to receive many dependency chains. Did anyone else have this problem? Would it be easier to install IIIalpha9.8-562.7 ? Thanks for any insights. 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
Re: SPident not showing SLES10-SP2
Agreed, this distribution is not the most optimized distribution (I do not if any are) for big blue. I cannot find 562.7 anywhere either. Peter Kim Goldenberg [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 06/19/2008 01:16 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: SPident not showing SLES10-SP2 Peter E. Abresch Jr. - at Pepco wrote: I upgraded to SLES10-SP2 and all seems well. I then enter SPident because I like seeing SP2 installed and I get the following: CONCLUSION: System is NOT up-to-date! foundSLE-10-s390x-SP1 + online updates expected SLE-10-s390x-SP2 e! a SPident ?vvv indicates the following: - cdparanoia-32bit IIIalpha9.8-562.4 IIIalpha9.8-562.7 What is this? I tried to uninstall this but started to receive many dependency chains. Did anyone else have this problem? Would it be easier to install IIIalpha9.8-562.7 ? I get a bit concerned when a group (Novell) should know better than to require a cd-ripper on System z! The copy of SP2 I just downloaded a day or two ago only has 562.4, not 562.7! Kim -- 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. kgoldenberg.vcf Description: Binary data
Re: SPident not showing SLES10-SP2
I do not know about these scripts. Where can I get a copy or am I too late? I would love to put my SLES on a diet. Things slip in because it is a dependency of a dependency of a dependency of a dependency . . . Peter Mark Post [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 06/19/2008 01:28 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: SPident not showing SLES10-SP2 On Thu, Jun 19, 2008 at 1:21 PM, in message [EMAIL PROTECTED], David Stuart [EMAIL PROTECTED] wrote: And what about USB support? What about it? I've published (two now) scripts to generate AutoYaST installation files that eliminate stuff like that. If you're not willing to use those tools, well Mark Post -- 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
Re: How do I pull the SP2 updates down with YUM?
My YUP configuration were using the values from /etc/zmd/deviceid and /etc/zmd/secret which had been working fine. But now Novell wants us to use mirroring credentials so I had to go into the website and extract our mirroring credentials and use them. This might make sense to everybody but I did not realize that mirroring credentials even existed. Not only did that ship sail past me, I was not even on the dock to see it. Anyway, it seems to be was working fine now, until I ran out of space. Errr! Thanks to everyone that pointed me in the right direction. Peter Mark Post [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 06/11/2008 01:18 AM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: How do I pull the SP2 updates down with YUM? On Tue, Jun 10, 2008 at 7:46 PM, in message [EMAIL PROTECTED], Marcy Cortes [EMAIL PROTECTED] wrote: I get not authorized as well when pulling with that wget command and my NCC id. It does work, however with the credentials from my /etc/sysconfig/yup (YUP_ID and YUP_PASS) - those were the mirror credentials from ncc for my SLES 10 product in there. Thanks for refreshing my memory. Darn it. :) (I hate when being on call wipes my brain clean.) This brings me back to one of my earlier comments. If you want to download maintenance for SP2, you have to either register an SP2 system, and use the contents of /etc/zmd/deviceid and /etc/zmd/secret from that system as your YUP_ID and YUP_PASS variables, or (as Marcy just reminded me) you have to use the mirroring credentials that you can find on Novell Customer Center. Refer to http://www.zjournal.com/index.cfm?section=articleaid=992 Setting Up a SUSE Linux Enterprise Server 10 Maintenance Repository/Mirror for details. To refer to a previous question about registering an SP2 system: Being able or unable to access updates from nu.novell.com has nothing to do with downloading the SP2 installation media from download.novell.com. So, it's not a Catch-22 situation at all. Mark Post -- 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
Re: How do I pull the SP2 updates down with YUM?
From the YUP log I see the following Illegal date format error which starts the errors off. I do not think this has any relation to authorization problems but then I do not claim to be an expert on the internal tickings of YUP. Marcy, we are running yup-232-2.2 and you said you are running yup-232-2.1? Mark, which version of yup are you running? Maybe this is a yup problem? Using https://nu.novell.com/repo/$RCE/SLES10-SP2-Updates/sles-10-s390x Fetching https://nu.novell.com/repo/$RCE/SLES10-SP2-Updates/sles-10-s390x/repodata/repomd.xml.asc.. . FA ILED with exit code 22 Failure details: Warning: Illegal date format for -z/--timecond (and not a file name). Warning: Disabling time condition. See curl_getdate(3) for valid date syntax. * About to connect() to nu.novell.com port 443 * Trying 72.246.210.34... connected * Connected to nu.novell.com (72.246.210.34) port 443 * successfully set certificate verify locations: * CAfile: /usr/share/curl/curl-ca-bundle.crt CApath: none * SSLv2, Client hello (1): Peter E Abresch/EP/PEP 06/09/2008 02:22 PM To Linux on 390 Port LINUX-390@VM.MARIST.EDU cc Subject Re: How do I pull the SP2 updates down with YUM? Yes, I am pulling the SP1 updates just fine. The errors only occur for SP2 Marcy Cortes [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 06/09/2008 02:07 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: How do I pull the SP2 updates down with YUM? It might be possible that you have to register an SP2 system first. FWIW - I don't have one registered. Peter does SP1 work ok for you? 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: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Monday, June 09, 2008 10:30 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] How do I pull the SP2 updates down with YUM? On Mon, Jun 9, 2008 at 12:48 PM, in message [EMAIL PROTECTED], Peter E. Abresch Jr. - at Pepco [EMAIL PROTECTED] wrote: Thanks Marcy and Marc, I downloaded the latest yup (yup-232-2.2) but am still having problems. I am seeing curl: (22) The requested URL returned error: 403 -- -- Fetching https://nu.novell.com/repo/$RCE/SLES10-SP2-Online/sles-10-s390x/repodata /repomd. xml.. . FAILED with e xit code 22 Failure details: -- -- Warning: Illegal date format for -z/--timecond (and not a file name). Warning: Disabling time condition. See curl_getdate(3) for valid date syntax. * About to connect() to nu.novell.com port 443 * Trying 72.246.210.34... connected * Connected to nu.novell.com (72.246.210.34) port 443 * successfully set certificate verify locations: * CAfile: /usr/share/curl/curl-ca-bundle.crt CApath: none I noticed that in the yup config I have the following new parameter but do not quite understand what I should specify or whether it is causing the problem. Any ideas? YUP_SP_SUBCHANS= The YaST /etc/sysconfig editor will tell you what can go there. Essentially it will be -Updates or -Online or both. I just tested on my system, and I don't see the 403 errors. That almost always means some sort of authorization/permissions error on the server side. It might be possible that you have to register an SP2 system first. If that doesn't work, and you can still mirror SP1 updates, then I would open an SR with Novell to find out why you don't seem to have access to the SP2 channels. Mark Post -- 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
Re: How do I pull the SP2 updates down with YUM?
Thanks for your patience, Mark, I enter the command and got exactly what you expected. Resolving nu.novell.com... 72.246.210.34 Connecting to nu.novell.com|72.246.210.34|:443... connected. HTTP request sent, awaiting response... 401 Unauthorized Reusing existing connection to nu.novell.com:443. HTTP request sent, awaiting response... 401 Unauthorized Authorization failed. I am still confused. I do not understand why I am not authorized. I am registered for SLES10. I am fine with SLES10-SP1. How do I authorized for SLES10-SP2? Peter Mark Post [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 06/10/2008 02:48 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: How do I pull the SP2 updates down with YUM? On Tue, Jun 10, 2008 at 7:30 AM, in message [EMAIL PROTECTED], Peter E. Abresch Jr. - at Pepco [EMAIL PROTECTED] wrote: From the YUP log I see the following Illegal date format error which starts the errors off. I do not think this has any relation to authorization problems but then I do not claim to be an expert on the internal tickings of YUP. The order the error messages come out don't necessarily reflect chronology due to buffering or something. If you cannot successfully issue this command (with appropriate substitutions for nccuserid and nccpassword): wget --http-user=nccuserid --http-password=nccpassword https://nu.novell.com/repo/\$RCE/SLES10-SP2-Updates/sles-10-s390x/repodata/repomd.xml.asc then you have a permissions problem. Marcy, we are running yup-232-2.2 and you said you are running yup-232-2.1? Mark, which version of yup are you running? Maybe this is a yup problem? # rpm -q yup yup-232-2.2 Mark Post -- 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
How do I pull the SP2 updates down with YUM?
How do I pull the SP2 updates down with YUM? I changed YUP_SUBVERSIONS=SP1? to YUP_SUBVERSIONS=SP1 SP2 in the YUP configuration. I also have YUP_DEST_DIR=/var/cache/yup so I created the following SP2 directories there: drwxr-xr-x 3 root root 80 Jun 27 2007 SLES10-SP1-Online drwxr-xr-x 3 root root 80 Jul 10 2007 SLES10-SP1-Updates drwxr-xr-x 3 root root 80 Jun 9 09:44 SLES10-SP2-Online drwxr-xr-x 3 root root 80 Jun 9 09:45 SLES10-SP2-Updates However, after running yup, the SP2 directories are empty. I have been pulling SP1 updates successfully for quite some time. I know I am missing something but cannot determine what. I am running yup-224-27.1 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
Re: How do I pull the SP2 updates down with YUM?
Thanks Marcy and Marc, I downloaded the latest yup (yup-232-2.2) but am still having problems. I am seeing curl: (22) The requested URL returned error: 403 Fetching https://nu.novell.com/repo/$RCE/SLES10-SP2-Online/sles-10-s390x/repodata/repomd.xml.. . FAILED with e xit code 22 Failure details: Warning: Illegal date format for -z/--timecond (and not a file name). Warning: Disabling time condition. See curl_getdate(3) for valid date syntax. * About to connect() to nu.novell.com port 443 * Trying 72.246.210.34... connected * Connected to nu.novell.com (72.246.210.34) port 443 * successfully set certificate verify locations: * CAfile: /usr/share/curl/curl-ca-bundle.crt CApath: none I noticed that in the yup config I have the following new parameter but do not quite understand what I should specify or whether it is causing the problem. Any ideas? YUP_SP_SUBCHANS= Mark Post [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 06/09/2008 11:32 AM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: How do I pull the SP2 updates down with YUM? On Mon, Jun 9, 2008 at 10:24 AM, in message [EMAIL PROTECTED], Peter E. Abresch Jr. - at Pepco [EMAIL PROTECTED] wrote: -snip- However, after running yup, the SP2 directories are empty. I have been pulling SP1 updates successfully for quite some time. I know I am missing something but cannot determine what. I am running yup-224-27.1 In that version, there's a hard-coded reference to GA or SP1 for SLES10. The newer version Marcy talks about adds a check for SP2. Before SP3 comes out, the new Subscription Management Tool will be released, so hopefully this is the last update to YUP you'll need to install. Mark Post -- 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
Re: How do I pull the SP2 updates down with YUM?
What do you mean regester a SP2 system? Does that mean I must have a SP2 up and running and then use that system to register (even thought I cannot get the updates because I am not registered)? Mark Post [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 06/09/2008 01:36 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: How do I pull the SP2 updates down with YUM? On Mon, Jun 9, 2008 at 12:48 PM, in message [EMAIL PROTECTED], Peter E. Abresch Jr. - at Pepco [EMAIL PROTECTED] wrote: Thanks Marcy and Marc, I downloaded the latest yup (yup-232-2.2) but am still having problems. I am seeing curl: (22) The requested URL returned error: 403 Fetching https://nu.novell.com/repo/$RCE/SLES10-SP2-Online/sles-10-s390x/repodata/repomd . xml.. . FAILED with e xit code 22 Failure details: Warning: Illegal date format for -z/--timecond (and not a file name). Warning: Disabling time condition. See curl_getdate(3) for valid date syntax. * About to connect() to nu.novell.com port 443 * Trying 72.246.210.34... connected * Connected to nu.novell.com (72.246.210.34) port 443 * successfully set certificate verify locations: * CAfile: /usr/share/curl/curl-ca-bundle.crt CApath: none I noticed that in the yup config I have the following new parameter but do not quite understand what I should specify or whether it is causing the problem. Any ideas? YUP_SP_SUBCHANS= The YaST /etc/sysconfig editor will tell you what can go there. Essentially it will be -Updates or -Online or both. I just tested on my system, and I don't see the 403 errors. That almost always means some sort of authorization/permissions error on the server side. It might be possible that you have to register an SP2 system first. If that doesn't work, and you can still mirror SP1 updates, then I would open an SR with Novell to find out why you don't seem to have access to the SP2 channels. Mark Post -- 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
Re: How do I pull the SP2 updates down with YUM?
Yes, I am pulling the SP1 updates just fine. The errors only occur for SP2 Marcy Cortes [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 06/09/2008 02:07 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: How do I pull the SP2 updates down with YUM? It might be possible that you have to register an SP2 system first. FWIW - I don't have one registered. Peter does SP1 work ok for you? 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: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Monday, June 09, 2008 10:30 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] How do I pull the SP2 updates down with YUM? On Mon, Jun 9, 2008 at 12:48 PM, in message [EMAIL PROTECTED], Peter E. Abresch Jr. - at Pepco [EMAIL PROTECTED] wrote: Thanks Marcy and Marc, I downloaded the latest yup (yup-232-2.2) but am still having problems. I am seeing curl: (22) The requested URL returned error: 403 -- -- Fetching https://nu.novell.com/repo/$RCE/SLES10-SP2-Online/sles-10-s390x/repodata /repomd. xml.. . FAILED with e xit code 22 Failure details: -- -- Warning: Illegal date format for -z/--timecond (and not a file name). Warning: Disabling time condition. See curl_getdate(3) for valid date syntax. * About to connect() to nu.novell.com port 443 * Trying 72.246.210.34... connected * Connected to nu.novell.com (72.246.210.34) port 443 * successfully set certificate verify locations: * CAfile: /usr/share/curl/curl-ca-bundle.crt CApath: none I noticed that in the yup config I have the following new parameter but do not quite understand what I should specify or whether it is causing the problem. Any ideas? YUP_SP_SUBCHANS= The YaST /etc/sysconfig editor will tell you what can go there. Essentially it will be -Updates or -Online or both. I just tested on my system, and I don't see the 403 errors. That almost always means some sort of authorization/permissions error on the server side. It might be possible that you have to register an SP2 system first. If that doesn't work, and you can still mirror SP1 updates, then I would open an SR with Novell to find out why you don't seem to have access to the SP2 channels. Mark Post -- 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
z/VM 5.1 to 5.3 upgrade ( a little handholding requested) PART 3
Thanks to everyone that responded to my previous requests. Our z/VM 5.3 testing as a second level guest is progressing. My second level z/VM looks like the following: USER VMTESTSV 256M 256M BG ACCOUNT SYSTEMS IPL CMS MACH XA OPTION LNKNOPAS CONSOLE 0009 3215 NICDEF 0600 TYPE QDIO LAN SYSTEM VSWTCH00 SPECIAL 0100 3270 SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 0190 0190 RR LINK MAINT 019E 019E RR MDISK 0191 3390 11 5 VMUSR1 MR MDISK 3390 1 5 VMUSR1 MR MDISK 22CC 3390 6 5 VMUSR1 MR MDISK 2CF1 3390 16 120 VMUSR1 MR I wish to test our TCP/IP configuration as second level and then use the same configuration when we go first level. Our OSA UCBs are: F800-F802 F900-F902 FC00-FC02 FD00-FD02 What is the best method of adding these UCBs to VMTESTSV?s directory entry so I can build my second level TCPIP configuration using the real UCBs. I hope this makes sense. We only run z/VM for our Linux guests so our z/VM expertise is slow coming. Peter Remember, we are old MVSers but very young VMers. Go slow. 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
z/VM 5.1 to 5.3 upgrade ( a little handholding requested) PART 2
Thanks to everyone that responded to my original hand holding request. With everyone?s response we were able to install z/VM 5.3 as a second level guest to our z/VM V5.1. We also applied the latest RSU maintenance and have performed backups of our 5.3 system. We are now looking to migrate our users (system programmers). Remember, we only use z/VM for Linux guest only. I was going to migrate (cut and paste) our z/VM 5.1 guest directory entries into our z/VM 5.3 user direct and perform a DIRECTXA which should work. We only have about 20. But. . . . we have some sharing concerns. For example: I want to cut the following entry from user direct on z/VM 5.1 and paste it in user direct on z/VM 5.3 and put it online. USER X062PEA 64M 100M ABCDEFG INCLUDE IBMDFLT ACCOUNT 1 SYSPROG IPL CMS MACH XA OPTION MAINTCCW LNKS LNKE LNKNOPAS LINK TCPMAINT 0592 0592 RR MDISK 0191 3390 11 5 VMUSR0 MR MDISK 0199 3390 31 100 VMUSR0 RR Volume VMUSR0 looks like the following under our current 5.1 system: DASD 6815 CP SYSTEM VMUSR0 13 Here are the questions. Can I attach 6815 to my second level z/VM 5.3 guest and then logon with x062pea or do I need to detach it to our first level z/VM 5.1 system. Are they any sharing concerns that I need to be aware of? Our final z/VM 5.3 test will be ipling it in a separate LPAR. Are their additional sharing concerns I have to worry about? Anthing that will get us on the right track is appreciated. We want to make sure that we do not cause problems with our production z/VM, especially over the long holiday. Thanks as always. Peter Remember, we are old MVSers but very young VMers. Go slow. 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
Re: z/VM 5.1 to 5.3 upgrade ( a little handholding requested) PART 2
This sounds intriguing. What do you mean about link to a full pack mini disk? Take the following statement from my directory entry for example: MDISK 0191 3390 11 5 VMUSR0 MR Currently, VMUSR0 looks like the following under the first level z/VM v5.1: CP Q SYSTEM 6815 DASD 6815 ATTACHED SYSTEM 0012 VMUSR0 VMTESTSV 0191 R/W , VMTESTSV 2CF1 R/W , VMTESTSV 22CC R/W VMTESTSV R/W , LINUXD01 0191 R/O , LINUXP01 0191 R/O LINUXM03 0191 R/O , LINUXYOU 0191 R/O , LINUXYUM 0191 R/O VSWCTRL1 0191 R/W , OPERATOR 0199 R/O , MAINT0199 R/O Of course, VMTESTSV is my second level z/VM 5.3 system. What exactly do I need to do to have a full pack link? Thanks. Peter Stephen Frazier [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 05/23/2008 01:38 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: z/VM 5.1 to 5.3 upgrade ( a little handholding requested) PART 2 So far your approach is good. See some comments below. Peter E. Abresch Jr. - at Pepco wrote: Thanks to everyone that responded to my original hand holding request. With everyone?s response we were able to install z/VM 5.3 as a second level guest to our z/VM V5.1. We also applied the latest RSU maintenance and have performed backups of our 5.3 system. We are now looking to migrate our users (system programmers). Remember, we only use z/VM for Linux guest only. I was going to migrate (cut and paste) our z/VM 5.1 guest directory entries into our z/VM 5.3 user direct and perform a DIRECTXA which should work. We only have about 20. But. . . . we have some sharing concerns. Yes, copy the user entries from the old directory to the new directory. For example: I want to cut the following entry from user direct on z/VM 5.1 and paste it in user direct on z/VM 5.3 and put it online. USER X062PEA 64M 100M ABCDEFG INCLUDE IBMDFLT ACCOUNT 1 SYSPROG IPL CMS MACH XA OPTION MAINTCCW LNKS LNKE LNKNOPAS LINK TCPMAINT 0592 0592 RR MDISK 0191 3390 11 5 VMUSR0 MR MDISK 0199 3390 31 100 VMUSR0 RR Volume VMUSR0 looks like the following under our current 5.1 system: DASD 6815 CP SYSTEM VMUSR0 13 Here are the questions. Can I attach 6815 to my second level z/VM 5.3 guest and then logon with x062pea or do I need to detach it to our first level z/VM 5.1 system. I would use a link to a full pack minidisk to give your second level guest access to the disk. If you use link then both first and second level users can access different minidisks on the disk at the same time. If you use detach and attach then you can not have users on both systems at the same time. Are they any sharing concerns that I need to be aware of? Do not have the same user log on to both first and second level at the same time. Two users should not have write access to a minidisk at one time. In your example minidisk 0199 is read only so it doesn't matter how many users have it. However, minidisk 0191 is set so that it will get a write access to the minidisk if no one else has one when it logs on. But, it will get read only access if someone else (at the same level on this lpar) has write access. If you are an experienced VM systems programmer you would have set up your machine to propagate the protection across lpars and levels. If you are not experienced enough to do this then be careful not to have two write links at the same time. Our final z/VM 5.3 test will be ipling it in a separate LPAR. Are their additional sharing concerns I have to worry about? If you followed my advice to use link instead of attach then there is no change in sharing concerns when you run both VMs in lpars instead of one under the other. If you were using attach when running in one lpar when you bring it up in a second lpar you will have the disk attached to both VM at the same time. That introduces all the concerns that you would have if you used link. Anthing that will get us on the right track is appreciated. We want to make sure that we do not cause problems with our production z/VM, especially over the long holiday. Thanks as always. Peter Remember, we are old MVSers but very young VMers. Go slow. Right, that is why I didn't try to explain how to set up cross domain data sharing. -- 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 -- 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
Quick z/VM maintenance question (I hope)
We have the following z/VM V5.3 maintenance that we downloaded and detersed: S7832162 SERVLINK C1 V 4005109 94 5/22/08 12:43:47 S7832160 SERVLINK C1 F 80672 14 5/22/08 12:37:40 SHIPRSU3 SERVLINK C1 V 4005 18621 16040 5/22/08 12:26:53 SHIPRSU2 SERVLINK C1 V 4005 27038 25191 5/22/08 12:26:29 SHIPRSU1 SERVLINK C1 V 4005 19310 17021 5/22/08 12:25:59 S7832160 SHIPRSU3 C1 F 1024 34725 8682 5/22/08 12:17:11 S7832162 SHIPDOCS C1 F 1024 64 16 5/22/08 12:17:11 S7832160 SHIPRSU2 C1 F 1024 49257 12315 5/22/08 12:17:06 S7832160 SHIPRSU1 C1 F 1024 21071 5268 5/22/08 12:17:01 S7832160 SHIPDOC C1 F 1024 11 3 5/22/08 12:16:58 We then run the following command just like the manual says: service all S7832162 VMFSRV2760I SERVICE processing started VMFSUI2760I VMFSUFIN processing started VMFSIP1965E The command, EXECIO * DISKW VM $VMFUT1$ D, failed with return code 113 VMFSUI1965E The command, VMFSIM MODIFY, failed with return code 100 when issued with the argument(s): VM SYSREST D STEM UREST. ( REPLACE VMFSUI2760I VMFSUFIN processing completed unsuccessfully VMFSRV1965E The command, VMFSUFIN, failed with return code 100 when issued with the argument(s): ALL ( NOPROMPT CORENV S7832162 VMFSRV2760I SERVICE processing completed unsuccessfully Ready(00100); T=0.20/0.21 12:55:15 We do not know what we are doing wrong. We are z/VM newbies but old MVSers. Any suggestions are welcomed. Thanks as always. 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
Re: Quick z/VM maintenance question (I hope)
This is what we have: q disk LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL MNT191 191 A R/W 175 3390 4096 34171-01 31329 31500 MNT5E5 5E5 B R/W 9 3390 4096 131 1288-80332 1620 MNT500 500 C R/W 600 3390 4096 11 99919-93 8081 108000 MNT51D 51D D R/W26 3390 4096 282 4679-99 1 4680 MNT190 190 S R/O 100 3390 4096 687 14592-81 3408 18000 MNT19E 19E Y/S R/O 250 3390 4096 1010 26738-59 18262 45000 Jihad K Kawkabani [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 05/22/2008 01:22 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: Quick z/VM maintenance question (I hope) Do you have MAINT's 51D disk accessed R/W as MAINT's D drive? In MAINT's profile exec there should be a ACC 51D D statement. Regards, Jihad K. Kawkabani IT Systems Engineer Consultant Voice: 440.395.0740 Network: 575.0740 Cell: 440.465.2969 Peter E. Abresch Jr. - at Pepco [EMAIL PROTECTED] To com LINUX-390@VM.MARIST.EDU Sent by: Linux on cc 390 Port [EMAIL PROTECTED] Subject IST.EDU Quick z/VM maintenance question (I hope) 05/22/2008 12:57 PM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU We have the following z/VM V5.3 maintenance that we downloaded and detersed: S7832162 SERVLINK C1 V 4005109 94 5/22/08 12:43:47 S7832160 SERVLINK C1 F 80672 14 5/22/08 12:37:40 SHIPRSU3 SERVLINK C1 V 4005 18621 16040 5/22/08 12:26:53 SHIPRSU2 SERVLINK C1 V 4005 27038 25191 5/22/08 12:26:29 SHIPRSU1 SERVLINK C1 V 4005 19310 17021 5/22/08 12:25:59 S7832160 SHIPRSU3 C1 F 1024 34725 8682 5/22/08 12:17:11 S7832162 SHIPDOCS C1 F 1024 64 16 5/22/08 12:17:11 S7832160 SHIPRSU2 C1 F 1024 49257 12315 5/22/08 12:17:06 S7832160 SHIPRSU1 C1 F 1024 21071 5268 5/22/08 12:17:01 S7832160 SHIPDOC C1 F 1024 11 3 5/22/08 12:16:58 We then run the following command just like the manual says: service all S7832162 VMFSRV2760I SERVICE processing started VMFSUI2760I VMFSUFIN processing started VMFSIP1965E The command, EXECIO * DISKW VM $VMFUT1$ D, failed with return code 113 VMFSUI1965E The command, VMFSIM MODIFY, failed with return code 100 when issued with the argument(s): VM SYSREST D STEM UREST. ( REPLACE VMFSUI2760I VMFSUFIN processing completed unsuccessfully VMFSRV1965E The command, VMFSUFIN, failed with return code 100 when issued with the argument(s): ALL ( NOPROMPT CORENV S7832162 VMFSRV2760I SERVICE processing completed unsuccessfully Ready(00100); T=0.20/0.21 12:55:15 We do not know what we are doing wrong. We are z/VM newbies but old MVSers. Any suggestions are welcomed. Thanks as always. 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
Re: Quick z/VM maintenance question (I hope)
This is a brand new z/VM 5.3 that we just installed. We installed the RSU DVD maintenance and now we are installing the latest RSU maintenance from ShopZseries. Is it the 51D disk that is full? If so, what are the steps to make it larger? Peter Chris Langford [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 05/22/2008 01:43 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: Quick z/VM maintenance question (I hope) Peter E. Abresch Jr. - at Pepco wrote: We have the following z/VM V5.3 maintenance that we downloaded and detersed: S7832162 SERVLINK C1 V 4005109 94 5/22/08 12:43:47 S7832160 SERVLINK C1 F 80672 14 5/22/08 12:37:40 SHIPRSU3 SERVLINK C1 V 4005 18621 16040 5/22/08 12:26:53 SHIPRSU2 SERVLINK C1 V 4005 27038 25191 5/22/08 12:26:29 SHIPRSU1 SERVLINK C1 V 4005 19310 17021 5/22/08 12:25:59 S7832160 SHIPRSU3 C1 F 1024 34725 8682 5/22/08 12:17:11 S7832162 SHIPDOCS C1 F 1024 64 16 5/22/08 12:17:11 S7832160 SHIPRSU2 C1 F 1024 49257 12315 5/22/08 12:17:06 S7832160 SHIPRSU1 C1 F 1024 21071 5268 5/22/08 12:17:01 S7832160 SHIPDOC C1 F 1024 11 3 5/22/08 12:16:58 We then run the following command just like the manual says: service all S7832162 VMFSRV2760I SERVICE processing started VMFSUI2760I VMFSUFIN processing started VMFSIP1965E The command, EXECIO * DISKW VM $VMFUT1$ D, failed with return code 113 snip When EXECIO receives a return code from a CMS I/O operation it adds 100 to generate a return code As the operation is DISKW one can speculate that the I/O request was FSWRITE. Return code 13 from FSWRITE indicates disk is full (or your SFS file space limit is reached) -- Chris Langford, Cestrian Software -- 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
Re: Quick z/VM maintenance question (I hope)
Thanks to all that responded. We were confused ourselves as what could be hogging all the space on the 51D drive but for some reason, never went and checked. We just installed z/VM 5.3 and were having all kinds of little undocumented gotchas that we assumed this was one of them. Anyway, what happened was that one of the untersed service envelopes got FTPed to the maint?s D disk instead of the C (500) disk. This untersed envelope caused our grief. As soon as we did our sort, we realized our embarrassment. We deleted the file and it went back to 28 percent. We will try the service all command in the morning and are hoping for better results now. On a side note, after we put2prod all the maintenance, do we need to keep anything on maint?s 500 disk or can we delete the files without harm? Peter Romanowski, John (OFT) [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 05/22/2008 02:36 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: Quick z/VM maintenance question (I hope) As someone suggested, your 51d is full. For comparison my VM5.3 51D with all the recent VM maintenance applied is 28% and I have 295 files to your 282. FILELIST your 51D D-disk, press PF6 to sort by size and see which files are taking up so much space. Maybe those files were misplaced there by someone/thing and should be moved or erased? My Q DISK D output: LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL MNT51D 51D D R/W26 3390 4096 295 1330-28 3350 4680 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. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Peter E. Abresch Jr. - at Pepco Sent: Thursday, May 22, 2008 1:56 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Quick z/VM maintenance question (I hope) This is what we have: q disk LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL MNT191 191 A R/W 175 3390 4096 34171-01 31329 31500 MNT5E5 5E5 B R/W 9 3390 4096 131 1288-80332 1620 MNT500 500 C R/W 600 3390 4096 11 99919-93 8081 108000 MNT51D 51D D R/W26 3390 4096 282 4679-99 1 4680 MNT190 190 S R/O 100 3390 4096 687 14592-81 3408 18000 MNT19E 19E Y/S R/O 250 3390 4096 1010 26738-59 18262 45000 Jihad K Kawkabani [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 05/22/2008 01:22 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: Quick z/VM maintenance question (I hope) Do you have MAINT's 51D disk accessed R/W as MAINT's D drive? In MAINT's profile exec there should be a ACC 51D D statement. Regards, Jihad K. Kawkabani IT Systems Engineer Consultant Voice: 440.395.0740 Network: 575.0740 Cell: 440.465.2969 Peter E. Abresch Jr. - at Pepco [EMAIL PROTECTED] To com LINUX-390@VM.MARIST.EDU Sent by: Linux on cc 390 Port [EMAIL PROTECTED] Subject IST.EDU Quick z/VM maintenance question (I hope) 05/22/2008 12:57 PM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU We have the following z/VM V5.3 maintenance that we downloaded and detersed: S7832162 SERVLINK C1 V 4005109 94 5/22/08 12:43:47 S7832160 SERVLINK C1 F 80672 14 5/22/08 12:37:40 SHIPRSU3 SERVLINK C1 V 4005 18621 16040 5/22/08 12:26:53 SHIPRSU2 SERVLINK C1 V 4005 27038 25191 5/22/08 12:26:29 SHIPRSU1 SERVLINK C1 V 4005 19310 17021 5/22/08 12:25:59 S7832160 SHIPRSU3 C1 F 1024 34725 8682 5/22/08 12:17:11 S7832162 SHIPDOCS C1 F 1024 64 16 5/22/08 12:17:11 S7832160 SHIPRSU2 C1 F 1024 49257 12315 5/22/08 12:17:06 S7832160 SHIPRSU1 C1 F 1024 21071 5268 5/22/08 12:17:01 S7832160 SHIPDOC C1 F 1024 11 3 5/22/08 12:16:58 We then run the following command just like the manual says: service all S7832162 VMFSRV2760I SERVICE processing started VMFSUI2760I VMFSUFIN processing started VMFSIP1965E The command, EXECIO * DISKW VM $VMFUT1$ D, failed with return code
z/VM 5.1 to 5.3 upgrade ( a little handholding requested)
z/VM 5.1 to 5.3 upgrade handholding We are starting our upgrade from z/VM 5.1 to z/VM 5.3. We use z/VM strictly for Linux. We are all old MVSers that originally installed z/VM 5.1. Now we are rethinking our z/VM installation and maintenance methodology. We have talked to various VMers but have become overwhelmed with the many methods of accomplishing this. Here is what we wish to do. We wish to install z/VM 5.3 as a second level guest in our current z/VM 5.1 system. We wish to develop an environment where we can test the hell out of it and once we are happy with it, we wish to implement it into production by simply changing the IPL address for our z/VM LPAR. This methodology will hold true for z/VM maintenance as well. Another words, we will always have a production and a test z/VM. This is not uncommon as we all know. We have chosen to install second level using FTP from the install DVD on a Linux server. We are calling our second level VM VMTESTSV and created the following entry (please provide comments if this entry is not all that it can be). USER VMTESTSV VMTES530 256M 256M BG ACCOUNT SYSTEMS IPL CMS MACH XA OPTION LNKNOPAS CONSOLE 0009 3215 NICDEF 0600 TYPE QDIO LAN SYSTEM VSWTCH00 SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 0190 0190 RR LINK MAINT 019E 019E RR MDISK 0191 3390 371 25 VMUSR0 MR MDISK 3390 241 5 VMUSR0 MR MDISK 22CC 3390 246 5 VMUSR0 MR MDISK 2CF1 3390 251 120 VMUSR0 MR We will install z/VM to the following DASD volsers: Pack Type ProdTest RES 530RES (can we change this volser?) SPOOL VMSPLP VMSPLT PAGEVMPAGP VMPAGT USER1 VMWK01 VMWK01 (shared) USER2 VMWK02 VMWK02 (shared) USER3 VMWK03 VMWK03 (shared) I know, we have to migrate our customization and users over after we install. Let?s say we do all that and completed our testing and are ready for production implementation. We wish to copy the RES volume to another volser and IPL the LPAR from that address. Is this possible and what will be involved? Are we on the right track? Go slow, remember we are old MVSers and very young VMers. Thanks as always. 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
Re: Has anyone order z/VM from ShopZseries?
Thanks Les You are right. How do we order z/VM and not get z/VM? (rhetorical). I do not know what went wrong but we ordered it again. The problem with fool proof methods is that they only account for the fools I guess. Peter Les Geer (607-429-3580) [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 04/15/2008 09:41 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Has anyone order z/VM from ShopZseries? According to Sue Baloga, it looks like this order consisted of DFSMS only, which could be a valid VM/SDO order. You can order the z/VM base system and/or optional licensed products. When anything is ordered through the VM/SDO,base or LP, the optional product enabling aid is also shipped. The installation instructions has two links; one for the operating system (z/VM System Deliverable) and one for the optional licensed products (z/VM Licensed Products). If you ordered optional products only, you should use the second link Here's what the page looks like: IBM Systems System z z/VM Installation Instructions for Electronically Delivered z/VM System Deliverable and Licensed Products. For instructions on installing the electronic files (zip) for the z/VM Operating System go to: * Installation Instructions for Electronically Delivered z/VM System Deliverable For instructions on installing the electronic product envelope (servlink) files for z/VM Licensed Products go to: * Installation Instructions for Electronically Delivered z/VM License Products If doesn't appear the base operating system (z/VM System Deliverable) was ordered. Best Regards, Les Geer IBM z/VM and Linux Development I ordered z/VM V5.3 from ShopZseries and received the following downloads: Opt Prod Enabling Aid Download ? V6720401.TERS0014 (0.730 MB) DFSMS/VM FL221 Download ? V6720403.TERS0014 (63.8 MB) DFSMS/VM Kanji Download ? V6720402.TERS0004 (2.8 MB) and some electronic Documentation. The doc refers to zip files and creating DVDs but this is all I see. Am I= correct in assuming there is more to z/VM 5.3 and that something is missing? Thanks. -- 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
Has anyone order z/VM from ShopZseries?
I ordered z/VM V5.3 from ShopZseries and received the following downloads: Opt Prod Enabling Aid Download ? V6720401.TERS0014 (0.730 MB) DFSMS/VM FL221 Download ? V6720403.TERS0014 (63.8 MB) DFSMS/VM Kanji Download ? V6720402.TERS0004 (2.8 MB) and some electronic Documentation. The doc refers to zip files and creating DVDs but this is all I see. Am I correct in assuming there is more to z/VM 5.3 and that something is missing? Thanks. 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
Re: booting kernel - versions 0,1,2 - need info
With SLES10, I had the following menu: 1 = SLES_10_SP1_2 2 = ipl 3 = failsafe However, I experienced the same problem even using failsafe. I do not see much difference between all 3 of these options. What parameters can I specify in /etc/zipl.conf that will force Linux boot selection into single usermode? Peter Mark Post [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 04/09/2008 11:47 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: booting kernel - versions 0,1,2 - need info On Wed, Apr 9, 2008 at 11:09 PM, in message [EMAIL PROTECTED], Dennis Foreman [EMAIL PROTECTED] wrote: Thanks Mark. Where is the list kept and is it in plain-text form? Or is there a program to modify it? It's in /etc/zipl.conf on most systems. I'm not 100% sure about Debian, or if there's some source file that gets migrated to /etc/zipl.conf. It's plain text. I doubt there's a program to modify it. I use vi myself. Mark Post -- 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
Re: Linux Guest recovery at Sungard not going well
With SLES10, I had the following menu: 1 = SLES_10_SP1_2 2 = ipl 3 = failsafe However, I experience the same problem even using failsafe. I do not see much difference between all 3 of these options. What parameters can I specify in /etc/zipl.conf that will force Linux boot selection into single usermode? Peter Mark Post [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 04/08/2008 08:37 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: Linux Guest recovery at Sungard not going well On Mon, Apr 7, 2008 at 7:45 PM, in message [EMAIL PROTECTED], Peter E. Abresch Jr. - at Pepco [EMAIL PROTECTED] wrote: Bingo!, what an idea. We use LVM so I simply detached all DASD except my root and IPL my Linux guest. It was a mess but it did enter single user mode and prompted me for a root password. Prior to your next drill, you might want to make sure your systems have an IPL menu so that to get into single user mode a little easier by doing a #cp vi vmsg boot# 1 where boot# is 0 for default, 1 for the first boot option in /etc/zipl.conf, etc. http://www2.marist.edu/htbin/wlvtype?LINUX-VM.69219 Mark Post -- 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
Re: booting kernel - versions 0,1,2 - need info
I apoligize guys. I replied to the wrong thread here. It has been a long week. Peter Peter E Abresch/EP/PEP 04/11/2008 10:50 AM To Linux on 390 Port LINUX-390@VM.MARIST.EDU cc Subject Re: booting kernel - versions 0,1,2 - need info With SLES10, I had the following menu: 1 = SLES_10_SP1_2 2 = ipl 3 = failsafe However, I experienced the same problem even using failsafe. I do not see much difference between all 3 of these options. What parameters can I specify in /etc/zipl.conf that will force Linux boot selection into single usermode? Peter Mark Post [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 04/09/2008 11:47 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: booting kernel - versions 0,1,2 - need info On Wed, Apr 9, 2008 at 11:09 PM, in message [EMAIL PROTECTED], Dennis Foreman [EMAIL PROTECTED] wrote: Thanks Mark. Where is the list kept and is it in plain-text form? Or is there a program to modify it? It's in /etc/zipl.conf on most systems. I'm not 100% sure about Debian, or if there's some source file that gets migrated to /etc/zipl.conf. It's plain text. I doubt there's a program to modify it. I use vi myself. Mark Post -- 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
Re: Linux Guest recovery at Sungard not going well
OK, I understand now what you were trying to tell me. I created the following boot menu: zIPL v1.5.6 interactive boot menu 0. default (IPL) 1. IPL 2. Single_User_Mode Note: VM users please use '#cp vi vmsg input' Please choose (default will boot in 10 seconds): I added the following to /etc/zipl.conf [Single_User_Mode] target = /boot/zipl image = /boot/image ramdisk = /boot/initrd parameters = 1 dasd=150-15f root=/dev/dasda1 selinux=0 TERM=dumb elevator=cfq It was the ?1? in parameters= that I missed. I know I do not have to have a special menu but it allows me to change the procedures to have operators to IPL in single user mode by issuing: ipl 150 loadparm 2 clear That will take them directly to Singe User Mode with no prompting and avoiding any costly typeos along the way. Thanks as always. Peter Mark Post [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 04/11/2008 11:39 AM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: Linux Guest recovery at Sungard not going well On Fri, Apr 11, 2008 at 10:52 AM, in message [EMAIL PROTECTED], Peter E. Abresch Jr. - at Pepco [EMAIL PROTECTED] wrote: With SLES10, I had the following menu: -snip- What parameters can I specify in /etc/zipl.conf that will force Linux boot selection into single usermode? -snip- You don't have to put anything into /etc/zipl.conf, if you follow my original suggestion: Prior to your next drill, you might want to make sure your systems have an IPL menu so that to get into single user mode a little easier by doing a #cp vi vmsg boot# 1 where boot# is 0 for default, 1 for the first boot option in /etc/zipl.conf, etc. If you really want to put something into /etc/zipl.conf, I would duplicate your ipl entry, rename it to singleuser and add the character 1 (numeric one) to your kernel parameters for that entry. Mark Post -- 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
Re: Linux Guest recovery at Sungard not going well
I promised to share what I found out about CAesm that caused all this to begin with. I did not find out all that much but here is what I determined: I traced the problem to the following statements in nsswitch.conf passwd: CA_esm compat group: CA_esm compat We had no network connectivity at this point so CAesm could not authenticate out. This is understandable. However, I was disturbed that it prevented us from even logging on to a VM Linux console. I came home and conducted some tests. This problem is easily duplicated. I reviewed the CA_esm.conf settings and did some experimenting but could not find any combination that forced a timeout where the prompt would appear. I ended up opening an issue with Computer Associates to see if they can provide any solutions. In the meantime, booting up in single user mode should work fine in the interim. I wish there was more. Thanks to everyone that contributed. Enjoy the weekend. Peter Peter E Abresch/EP/PEP 04/07/2008 07:45 PM To Linux on 390 Port LINUX-390@VM.MARIST.EDU cc Subject Re: Linux Guest recovery at Sungard not going well Bingo!, what an idea. We use LVM so I simply detached all DASD except my root and IPL my Linux guest. It was a mess but it did enter single user mode and prompted me for a root password. I then logged on and systematically disabled startups. It was not NFS that was the cause of my grief but CAesm, which is CA?s External Security Manager ACF2 PAM interface which we upgraded to version 12 since the last test. Once I disabled CAesm and reattached my DASD, all was well. I get the logon prompt and successfully reconfigured LINUX and rebooted successfully. Now I got to figure out what is wrong with CAesm. Thanks to everyone. I will post my final resolution. Peter David K. Kelly [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 04/07/2008 05:08 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: Linux Guest recovery at Sungard not going well Peter, Edit the VM file that gives permission's to the Linux guest to access your VM disk. Remove the permission for one of the Linux guest to access the disk where the /opt file system lives. For us it's is disk 0202. See below: more /proc/dasd/devices ... 0.0.0202(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 60084 0 blocks, 2347 MB df -h /opt FilesystemSize Used Avail Use% Mounted on /dev/dasdc1 2.3G 563M 1.8G 24% /opt (This forces the Linux guest to boot into single user mode). (Sorry, I'm a Linux person and not a VM person so don't know the correct VM speak for this) Now do a hardware level reboot (#CP LOGOFF) for that Linux guest. and this will force the Linux guest to boot into single user mode. In single user mode using a 3270 terminal you should be able to access your Linux guest console. And now with a Linux prompt you can slow enable the various services in run level 5 (/etc/init.d/rc5.d) and differentiate what is stopping you from getting a Linux guest network prompt. Hope this helps and is not to confusing David K. Ron Foster at Baldor-IS [EMAIL PROTECTED] To om LINUX-390@VM.MARIST.EDU Sent by: Linux on cc 390 Port [EMAIL PROTECTED] Subject IST.EDU Re: Linux Guest recovery at Sungard not going well 04/07/2008 04:34 PM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU 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
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 LINUX-390@VM.MARIST.EDU 04/07/2008 07:42 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU 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: LINUX-390@VM.MARIST.EDU 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 LINUX-390@VM.MARIST.EDU 04/07/2008 04:37 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU 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
Linux Guest recovery at Sungard not going well
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
Re: Linux Guest recovery at Sungard not going well
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 LINUX-390@VM.MARIST.EDU 04/07/2008 04:37 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU 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
Re: Linux Guest recovery at Sungard not going well
Bingo!, what an idea. We use LVM so I simply detached all DASD except my root and IPL my Linux guest. It was a mess but it did enter single user mode and prompted me for a root password. I then logged on and systematically disabled startups. It was not NFS that was the cause of my grief but CAesm, which is CA?s External Security Manager ACF2 PAM interface which we upgraded to version 12 since the last test. Once I disabled CAesm and reattached my DASD, all was well. I get the logon prompt and successfully reconfigured LINUX and rebooted successfully. Now I got to figure out what is wrong with CAesm. Thanks to everyone. I will post my final resolution. Peter David K. Kelly [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 04/07/2008 05:08 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: Linux Guest recovery at Sungard not going well Peter, Edit the VM file that gives permission's to the Linux guest to access your VM disk. Remove the permission for one of the Linux guest to access the disk where the /opt file system lives. For us it's is disk 0202. See below: more /proc/dasd/devices ... 0.0.0202(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 60084 0 blocks, 2347 MB df -h /opt FilesystemSize Used Avail Use% Mounted on /dev/dasdc1 2.3G 563M 1.8G 24% /opt (This forces the Linux guest to boot into single user mode). (Sorry, I'm a Linux person and not a VM person so don't know the correct VM speak for this) Now do a hardware level reboot (#CP LOGOFF) for that Linux guest. and this will force the Linux guest to boot into single user mode. In single user mode using a 3270 terminal you should be able to access your Linux guest console. And now with a Linux prompt you can slow enable the various services in run level 5 (/etc/init.d/rc5.d) and differentiate what is stopping you from getting a Linux guest network prompt. Hope this helps and is not to confusing David K. Ron Foster at Baldor-IS [EMAIL PROTECTED] To om LINUX-390@VM.MARIST.EDU Sent by: Linux on cc 390 Port [EMAIL PROTECTED] Subject IST.EDU Re: Linux Guest recovery at Sungard not going well 04/07/2008 04:34 PM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU 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
Re: z/VM Version 5.1 to z/VM Version 5.3 migration?
tickle Has anyone made the jump from z/VM 5.1 to z/VM 5.3 and wish to discuss their experiences? Peter Peter E Abresch/EP/PEP 01/23/2008 03:59 PM To Linux on 390 Port LINUX-390@VM.MARIST.EDU cc Subject z/VM Version 5.1 to z/VM Version 5.3 migration? We have to upgrade our z/VM version 5.1 to version 5.3. We run z/VM only to support our Linux guests. We reviewed the z/VM Migration Guide and see in chapter 2 where the following is hinted at: Support is provided for simplified migration to z/VM V5.3 from either z/VM V5.2 or z/VM V5.1. We do not know what this means and can not find any elaboration anywhere? Does anyone have a clue? We also can use z/VM Getting Started with Linux on System z to install z/VM into another LPAR. This is how we originally installed and configured z/VM version 5.1, but it was a new z/VM install back then. If we go this route, we will have to redefine all our Linux users and mini-disks all over again or is there some type of migration tool or assistance. Is there a manual or cookbook type doc that better documents this migration process? Would we migrate our Linux guests using the ?big bang? approach or is there a more subtle approach? As always, any help and assistance is much appreciated. Thanks. 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
z/VM Version 5.1 to z/VM Version 5.3 migration?
We have to upgrade our z/VM version 5.1 to version 5.3. We run z/VM only to support our Linux guests. We reviewed the z/VM Migration Guide and see in chapter 2 where the following is hinted at: Support is provided for simplified migration to z/VM V5.3 from either z/VM V5.2 or z/VM V5.1. We do not know what this means and can not find any elaboration anywhere? Does anyone have a clue? We also can use z/VM Getting Started with Linux on System z to install z/VM into another LPAR. This is how we originally installed and configured z/VM version 5.1, but it was a new z/VM install back then. If we go this route, we will have to redefine all our Linux users and mini-disks all over again or is there some type of migration tool or assistance. Is there a manual or cookbook type doc that better documents this migration process? Would we migrate our Linux guests using the ?big bang? approach or is there a more subtle approach? As always, any help and assistance is much appreciated. Thanks. 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
SuSE sudo levels
SuSE sudo levels We are working on a project to consolidate Linux userid management. We are moving our Linux Users from each Linux Guest and will manage them using CA-ACF2 and PAM. However we ran into a slight problem. We use sudo to control root access and then define the privileged users to group wheel. We do this for all our guests. The problem appears to be sudo not recognizing group wheel if it is not the users primary group and the group is assigned outside of /etc/group, for example, ldap. In our case, we changed nsswitch.conf to reflect the following: passwd: CA_esm compat group: CA_esm compat We think this problem has been corrected with sudo version 1.6.9 (see http://www.sudo.ws/sudo/current.html ) Sudo now uses the supplemental group vector for matching. This fixes problems with split group lines in /etc/group as well as multiple group sources in nsswitch.conf. Here is the problem, we are running the following guests: SuSE SLES10x SP1 Kernel 2.6.16.53-0.18-default with Sudo version 1.6.8p12 SuSE SLES9x SP3 Kernel 2.6.5-7.287.3 with Sudo version 1.6.7p5 Unfortunately these are the latest versions of sudo that Novell has released for these Linux Distributions according to YaST. We pay for updates and patches so the question is, Can we get the latest sudo version from Novell or do I have to download it and build it myself? If I have to build it myself, does it void any support type warranties with Novell? As always, thanks in advance. 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
Re: Local YOU server failing for some patches (resolved)
No matter what I tried, my local YOU server failed while attempting to download patch-11816: Security update for Linux kernel. Once this failed, no subsequent patches could be downloaded. In order to resolve this, I had to manually download and apply patch-11966: YOU update for YaST Online Update from Novell. Once this patch was applied, I resynchronized my local YOU server successfully and all is well with the world. Go figure. Peter E Abresch/EP/PEP 11/19/2007 02:30 PM To Linux on 390 Port LINUX-390@VM.MARIST.EDU cc Subject Re: Local YOU server failing for some patches Thanks for your response I reran the YOU sync from YaST2 again and it fails with ?Error Synchronization failed for: SUSE CORE 9 https://you.novell.com/update Check whether the requested server is up. If yes, Make sure that the user name and the password are set correctly (see ?Edit? dialog).? looking in /var/lib/YaST2/you I see no indication of any userid/password problem however I get to patch-11816 and cannot get any further. Here are the last few lines in the youlog: 2007-11-19 14:15:07 (11949): Retrieving patch-11802: Security update for KDE libraries 2007-11-19 14:15:13 (11949): Ok 2007-11-19 14:15:13 (11949): Retrieving patch-11814: Security update for fetchmail 2007-11-19 14:15:13 (11949): Ok 2007-11-19 14:15:13 (11949): Retrieving patch-11816: Security update for Linux kernel 2007-11-19 14:15:41 (11949): Error: Cannot get files. The filespace seems ok: FilesystemSize Used Avail Use% Mounted on /dev/mapper/linuxyou-var 6.4G 5.6G 864M 87% /var I see no indication of any problems other then that last error in the youlog. What could be causing this? Peter Mark Post [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 11/19/2007 01:23 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: Local YOU server failing for some patches On Mon, Nov 19, 2007 at 1:04 PM, in message [EMAIL PROTECTED], Peter E. Abresch Jr. - at Pepco [EMAIL PROTECTED] wrote: Local YOU server failing for some patches: I am trying to put some patches on my SLES9x SP3 server. When I pull the patches from my local YOU Server using YaST2 Online Update, I get the following: ERROR(Media:file not found)[HTTP returncode: 404 (URL: http://linuxyou/YOU/s390x/update/SUSE-CORE/9/rpm/s390x/yast2-online-update-2.9.2 2-0.2.3.s390x.rpm ) Package:yast2-online-update-2.9.22-0.2.3 Patch: patch-11966 -snip- Does anyone have any ideas or suggestions? Thanks in advance. The particular RPM you reference is on you.novell.com. So, whatever you're using to mirror the YOU server, re-run it, and see if more files show up. Mark Post -- 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
Re: Local YOU server failing for some patches
Thanks for your response I reran the YOU sync from YaST2 again and it fails with ?Error Synchronization failed for: SUSE CORE 9 https://you.novell.com/update Check whether the requested server is up. If yes, Make sure that the user name and the password are set correctly (see ?Edit? dialog).? looking in /var/lib/YaST2/you I see no indication of any userid/password problem however I get to patch-11816 and cannot get any further. Here are the last few lines in the youlog: 2007-11-19 14:15:07 (11949): Retrieving patch-11802: Security update for KDE libraries 2007-11-19 14:15:13 (11949): Ok 2007-11-19 14:15:13 (11949): Retrieving patch-11814: Security update for fetchmail 2007-11-19 14:15:13 (11949): Ok 2007-11-19 14:15:13 (11949): Retrieving patch-11816: Security update for Linux kernel 2007-11-19 14:15:41 (11949): Error: Cannot get files. The filespace seems ok: FilesystemSize Used Avail Use% Mounted on /dev/mapper/linuxyou-var 6.4G 5.6G 864M 87% /var I see no indication of any problems other then that last error in the youlog. What could be causing this? Peter Mark Post [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 11/19/2007 01:23 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: Local YOU server failing for some patches On Mon, Nov 19, 2007 at 1:04 PM, in message [EMAIL PROTECTED], Peter E. Abresch Jr. - at Pepco [EMAIL PROTECTED] wrote: Local YOU server failing for some patches: I am trying to put some patches on my SLES9x SP3 server. When I pull the patches from my local YOU Server using YaST2 Online Update, I get the following: ERROR(Media:file not found)[HTTP returncode: 404 (URL: http://linuxyou/YOU/s390x/update/SUSE-CORE/9/rpm/s390x/yast2-online-update-2.9.2 2-0.2.3.s390x.rpm ) Package:yast2-online-update-2.9.22-0.2.3 Patch: patch-11966 -snip- Does anyone have any ideas or suggestions? Thanks in advance. The particular RPM you reference is on you.novell.com. So, whatever you're using to mirror the YOU server, re-run it, and see if more files show up. Mark Post -- 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
Are these files necessary?
I am running SuSE SLES10-SP1. I notice some high space utilization in the following files: /var/lib/zypp/cache/* /var/lib/zmd/zmd.db I think these files were created while playing with novell-zmd. I use YUP and a local YUM server to retrieve my updates and then use YaST2 Online Updates pointing to my YUM server. The question is: Do I still need these files and/or directory entries? Can I safely delete them? As always, thanks. 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
Unknown Error: Downloading metadata failed . . .
My Linux YUM file system ran out of space. I added more space and YUP seems to be working however I am now receiving the following when I try to apply updates to my YUM server from my YUM server using YOU. dir:///var/cache/yup/SLES10-SP1-Updates/sles-10-s390x/ Unknown Error: Downloading metadata failed (is YUM source?) or user did not accept remote source. Aborting refresh That is the correct directory. How can I correct this? Thanks for any info. 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
Preparing and Upgrading to SLES10-SP1 (my experience)
One of the problems I encountered during my SLES10 to SLES10-SP1 upgrade was that SLES10-SP1 downloaded many packages that were already mirrored to my local YUM server. It also took a bit of time to download SP1 itself. This severely increased the upgrade time and it took over 8 hours and used much more space. While the upgrade eventually completed successfully, I ended up restoring everything back to SLES10. An 8-hour outage window for my production Linux guests is hard to come by. Here are the steps that I used to reduce this outage time. I started with my local YUM server. I applied the switch-update-server patch to switch and register the new update server from update.novell.com to nu.novell.com. I upgraded my YUP package. I was running yup-47-0.10 and upgraded to yup-222-26.1. You can get the latest YUP at http://software.opensuse.org/download/home:/mge1512/SLE_10/noarch/ . I made the following changes to my YUP configuration. I chose directory /var/cache/yup. YUP_DEST_DIR=/var/cache/yup YUP_ID=device ID YUP_PASS=secret YUP_SERVER=nu.novell.com YUP_ARCH=s390x YUP_SUBVERSIONS=GA SP1 My existing YUM server was storing its updates in /var/cache/yum/SLES10/s390x/. I rename this to /var/cache/yum/SLES10-Updates/sles-10-s390x/. I also copied the contents to /var/cache/yup/SLES10-SP1-Online/sles-10-s390x/rpm/s390x to avoid re-downloading duplicate packages. My YUP directories are really logical volumes within their own volume group that I be-bop back and forth using NFS. I exec YUP using: /usr/sbin/yup /tmp/yup.`date +\%b\%d-\%Y-\%H\%M\%S` And reviewed the messages. After YUP completed, I have the following: /var/cache/yup/SLES10-SP1-Online /var/cache/yup/SLES10-SP1-Updates /var/cache/yup/SLES10-Updates SLES10-Updates contain my former SLES10 update RPMs. There should not be much syncing anymore in this directory. SLES10-SP1-Online contains SP1 RPMs. SLES10-SP1-Updates is empty and remained empty even after upgrading my YUM to SLES10-SP1. I was told that this might simply be due to no post SLES10-SP1 updates having been released yet. I added SLES10-Updates and SLES10-SP1-Online to the installation sources under YaST2. These were local directories for my YUM server and NFS directories for my various SLES10 guests. I backed up my YUM server and installed move-to-sles10-sp1 using YaST2 Online Updates which were pointing to my local YUM repositories. Patch move-to-sles10-sp1 brought in some other patches and a YaST2 update that required restarting YaST2. Windows containing instructions were popped as appropriate by YaST and I simply followed these directions. Additional instructions are also available at http://www.novell.com/support/search.do?cmd=displayKCdocType=kcexternalId=3509359sliceId=dialogID=39225710stateId=0%200%2039235512 . During the update process, I received CHOWN errors on my automounted NFS file systems. This occurred whether the file systems were mounted or not. I traced the patch to filesystem-10-1.12.s390x.rpm. To get around it, I had to unmount them (if there were mounted), terminate the autofs daemon, and click retry where the update successfully recovered and continued. The upgrade also requested and used my original SuSE SLES10 installation CD4. Since this was available on a NFS server, I almost did not notice it. I do not know why. Since the updates were stored locally, the download time was significantly reduced but the application of the SP1 patches still took about 1 hour. The SP1 update will request a reboot which went off without a hitch. I did notice that my local mods were lost from the following: /etc/shells /etc/bash.bashrc I keep good records for local mods so this was not a problem. However, others should be aware of it. Also, while rebooting SLES10-SP1, it looks like it tries to crank the spinning slash during the Reiser file systems check, which just ends up looking like crap on our 3270 consoles. If anyone knows how to prevent this, please let me know. YaST2 looks completely different and functions seem slower but everything is there. What is really frustrating is that there is no way of closing the YaST2 window. Prior to SP1, you could simply click file/quit but that option is no longer available. Of course you can always kill the yastcontrolcenter daemon. My root file systems did increase 5-10 percent depending on the Linux guest I was upgrading. Other then the obvious kernel change from 2.6.16.27-0.9-default #1 SMP Tue Feb 13 09:35:18 UTC 2007 to 2.6.16.46-0.12-default #1 SMP Thu May 17 14:00:09 UTC 2007 a quick comparison of RPMs showed the following additional products were installed: audit-libs-32bit dbus kdebase3-32bit libgssapi-32bit libiniparser libmudflap libnscd-32bit libssui limal-nfs-server limal-nfs-server-perl mono-winforms net-snmp-32bit pciutils-ids switch-update-server yast2-control-center-gnome yast2-registration zypper kdebase3-32bit was the largest of these products. I ended up deleting all the KDE packages and bought back some
Re: SLES10 to SLES10 SP1 Migration . . .
Thanks Mark, I am working on a document that I will send the list outlining our experiences mirroring and upgrading to SP1. It is quite different then SLES9. We also experienced some gotchas as well. Hopefully I will post it this week before someone else runs into the same problems we did. Peter Mark Post [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 07/06/2007 04:36 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: SLES10 to SLES10 SP1 Migration . . . On Tue, Jun 26, 2007 at 12:30 PM, in message [EMAIL PROTECTED], Peter E. Abresch Jr. - at Pepco [EMAIL PROTECTED] wrote: -snip- SLES10-Updates directory structure was renamed from SLES10. I updated /etc/sysconfig/yup as follows: YUP_DEST_DIR=/var/cache/yup YUP_SERVER=nu.novell.com YUP_SERVER_SLES=nu.novell.com However, when I run YUP, it creates the SLES10 directory in /var/cache/yup and starts to download everything again. So I am confused again. I thought that making the above changes, the nu.novell.com and yup will mirror the SP1 stuff in the directory so I can have my SP1 stuff stored local before making the upgrade to SP1? What am I missing? First, make sure you have a version of YUP that understands SP1 exists. The version I have is yup-218-26.1. Then, check /etc/sysconfig/yup, and make sure there is a parameter called YUP_SUBVERSIONS. If it's not there, you're not using the right version of YUP. If it is there, update it so that it looks like this: YUP_SUBVERSIONS=GA SP1 If you don't want to keep mirroring the updates to the GA version, you can leave the GA string out of the parameter. There won't be any _new_ updates to that channel, from what I'm told. Just FYI, but if you want YUP_SERVER_SLES to be the same as YUP_SERVER, just set YUP_SERVER and YUP_SERVER_SLES (and YUP_SERVER_SLED) will default to have the same value. Mark Post -- 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
qeth: No memory for packet received on hsi0.
I am seeing the following in my message log many times for my Hipersocket. Does anyone know what it means and how I can eliminate it? Jul 5 13:34:45 linuxp01 kernel: Normal: empty Jul 5 13:34:45 linuxp01 kernel: HighMem: empty Jul 5 13:34:45 linuxp01 kernel: Swap cache: add 1670971, delete 1648898, find 511457/855362, race 0+1 Jul 5 13:34:45 linuxp01 kernel: Free swap: 367032kB Jul 5 13:34:45 linuxp01 kernel: 196608 pages of RAM Jul 5 13:34:45 linuxp01 kernel: 5724 reserved pages Jul 5 13:34:45 linuxp01 kernel: 41364 pages shared Jul 5 13:34:45 linuxp01 kernel: 22073 pages swap cached Jul 5 13:34:45 linuxp01 kernel: qeth: No memory for packet received on hsi0. Jul 5 13:34:45 linuxp01 kernel: cclclnt: page allocation failure. order:3, mode:0x20 Jul 5 13:34:45 linuxp01 kernel: 018c76c8 0038 0059aa88 00370268 Jul 5 13:34:45 linuxp01 kernel:00133ec4 018c75d8 0400 0400 Jul 5 13:34:45 linuxp01 kernel: 0003 0001 0020 Jul 5 13:34:45 linuxp01 kernel: 00372fe8 001072d6 018c7628 Jul 5 13:34:45 linuxp01 kernel: 0020 0400a194 0400a194 Jul 5 13:34:45 linuxp01 kernel: Call Trace: Jul 5 13:34:45 linuxp01 kernel: [0017085a] __alloc_pages+0x4d6/0x4e0 Jul 5 13:34:45 linuxp01 kernel: [00170962] __get_free_pages+0x4e/0x8c Jul 5 13:34:45 linuxp01 kernel: [0017526a] cache_alloc_refill+0x2a6/0x868 Jul 5 13:34:45 linuxp01 kernel: [00175908] __kmalloc+0xdc/0xe0 Jul 5 13:34:45 linuxp01 kernel: [002cb9ec] alloc_skb+0x60/0x104 Jul 5 13:34:45 linuxp01 kernel: [31458b0a] qeth_qdio_input_handler+0xc86/0x1a94 [qeth] Jul 5 13:34:45 linuxp01 kernel: [313dca66] tiqdio_tl+0xa36/0x1144 [qdio] Jul 5 13:34:45 linuxp01 kernel: [001398b8] tasklet_hi_action+0xa4/0x17c Jul 5 13:34:45 linuxp01 kernel: [00139e68] __do_softirq+0x70/0x104 Jul 5 13:34:45 linuxp01 kernel: [00139f62] do_softirq+0x66/0x6c Jul 5 13:34:45 linuxp01 kernel: [0011fb98] do_call_softirq+0x38/0x44 Jul 5 13:34:45 linuxp01 kernel: Jul 5 13:34:45 linuxp01 kernel: Mem-info: Jul 5 13:34:45 linuxp01 kernel: DMA per-cpu: 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
