From urs.frey at post.ch Wed May 1 08:18:50 2013 From: urs.frey at post.ch (urs.frey at post.ch) Date: Wed, 1 May 2013 14:18:50 +0000 Subject: [sles-beta] Difference in Packages, when installing BASE pattern Message-ID: <40637DBB36AF3941B243A286A432CA0B0E24549B@HXMB12.pnet.ch> Hi I wondered, what the difference is, between installing a SLES11-SP2 x86_64 on a XEN HVM Client using BASE pattern only, and doning exact the same operation using SLES11-SP3 RC1: Here is the difference of package names, when having previously saved : rpm -qa --queryformat '%{NAME}\n'| sort > outfile One can see, that there are new libraries coming, when observing the > outputs for SLES11-SP3 freyu at h039uc:~> diff c04szo_pkg_sl11-2_name.txt c04szo_pkg_sl11-3_name.txt 23d22 < blt 124a124,125 > gpg-pubkey > gpg-pubkey 202a204 > libgcc43 204c206,207 < libgcc46-32bit --- > libgcc_s1 > libgcc_s1-32bit 208c211 < libgomp46 --- > libgomp1 250a254,255 > libstdc++43 > libstdc++43-32bit 252a258,259 > libstdc++6 > libstdc++6-32bit 345a353 > perl-Module-Build 350a359 > perl-Test-Simple 400d408 < python-tk 410a419 > ruby-devel 453d461 < tk 478d485 < xorg-x11-libfontenc 480d486 < xorg-x11-libs 486,492d491 < xorg-x11-libXfixes < xorg-x11-libxkbfile < xorg-x11-libXmu < xorg-x11-libXp < xorg-x11-libXpm < xorg-x11-libXprintUtil < xorg-x11-libXrender 494d492 < xorg-x11-libXv freyu at h039uc:~> best regards Urs Frey Die Schweizerische Post Services Informationstechnologie Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX : ++41 (0)58 667 30 07 E-Mail: urs.frey at post.ch From urs.frey at post.ch Wed May 1 09:30:48 2013 From: urs.frey at post.ch (urs.frey at post.ch) Date: Wed, 1 May 2013 15:30:48 +0000 Subject: [sles-beta] SLES11-SP3 RC1 question concerning zypper dist-upgrade when upgrading from SLES11-SP2, why additional 32bit libraries on a x86_64 bit server? Message-ID: <40637DBB36AF3941B243A286A432CA0B0E2454BB@HXMB12.pnet.ch> Hi I am doing SLES11-SP3 upgrade testing from SLES11-SP2 x86_64 to SLES11-SP3 RC1 x86_64 I installed SLES11-SP2 base pattern, to latest patch-update When invoking zipper dist-upgrade, I can see that some new packages get installed. So far OK. What worries me, that there are new libraries-32 being installed. I mean, when having a pure x86_64 SLES11-SP2 64bit installation, why get 32bit libraries newly installed? So is there any idea why I get libgcc43-32bit & libgcc_s1-32bit & libstdc++43-32bit & libstdc++6-32bit 32bit libraries in addition? Here what I see when issuing : /usr/bin/zypper --non-interactive dist-upgrade --auto-agree-with-licenses Loading repository data... Reading installed packages... Removed 0 locks. Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Loading repository data... Reading installed packages... Computing distribution upgrade... The following NEW packages are going to be installed: libgcc43 libgcc43-32bit libgcc_s1 libgcc_s1-32bit libgomp1 libgomp43 liblzmadec0 libstdc++43 libstdc++43-32bit libstdc++6 libstdc++6-32bit lzma perl-Module-Build perl-Test-Simple release-notes-sles ruby-devel The following packages are going to be upgraded: OpenIPMI aaa_base acpid augeas-lenses autoyast2 autoyast2-installation bash bash-doc binutils brocade-firmware checkmedia cpp43 cpupower crash crash-sial desktop-translations device-mapper efibootmgr elilo ethtool fontconfig gcc43 gdb glib2 glib2-lang glibc glibc-32bit glibc-devel glibc-i18ndata glibc-locale grub hwinfo insserv inst-source-utils iproute2 irqbalance kdump kernel-default kernel-default-base kernel-default-devel kernel-firmware kernel-source kexec-tools keyutils keyutils-libs klogd kpartx libaugeas0 libblkid1 libgcc46 libgcc46-32bit libglib-2_0-0 libgobject-2_0-0 libgomp46 libgthread-2_0-0 libldap-2_4-2 libldapcpp1 libreadline5 libstdc++46 libstdc++46-32bit libtalloc2 libudev0 libuuid1 libzypp linux-kernel-headers lvm2 makedumpfile mcelog mdadm microcode_ctl mkinitrd module-init-tools multipath-tools nfsidmap nscd openldap2-client openssh parted pciutils-ids perl perl-Bootloader perl-Config-IniFiles perl-base perl-doc pmtools postfix readline-doc rsync rubygems sg3_utils sles-release sles-release-DVD smartmontools sudo supportutils suse-build-key suseRegister suspend sysconfig syslinux sysstat udev util-linux util-linux-lang uuid-runtime xen-kmp-default xorg-x11-libxcb yast2 yast2-add-on yast2-bootloader yast2-dirinstall yast2-dns-server yast2-installation yast2-iscsi-client yast2-kdump yast2-kerberos-client yast2-ldap yast2-ldap-client yast2-mail yast2-mail-plugins yast2-ncurses yast2-network yast2-nfs-client yast2-nis-server yast2-ntp-client yast2-online-update yast2-online-update-frontend yast2-packager yast2-pkg-bindings yast2-registration yast2-registration-branding-SLE yast2-samba-client yast2-samba-server yast2-security yast2-slp yast2-squid yast2-storage yast2-storage-lib yast2-tftp-server yast2-trans-en_US yast2-update yast2-users yast2-vm yast2-wagon zlib zypper zypper-log The following product is going to be upgraded: SUSE Linux Enterprise Server 11 SP3 The following packages are going to be downgraded: gzip libpcap0 libxslt yast2-ldap-server The following packages are not supported by their vendor: liblzmadec0 lzma ruby-devel rubygems 147 packages to upgrade, 4 to downgrade, 16 new. Overall download size: 228.3 MiB. After the operation, additional 33.0 MiB will be used. Continue? [y/n/?] (y): y Automatically agreeing with SUSE Linux Enterprise Server 11 SP3 product license. Thanks for your feedback Best regards Urs Frey Die Schweizerische Post Services Informationstechnologie Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX : ++41 (0)58 667 30 07 E-Mail: urs.frey at post.ch From kukuk at suse.de Wed May 1 09:45:36 2013 From: kukuk at suse.de (Thorsten Kukuk) Date: Wed, 1 May 2013 17:45:36 +0200 Subject: [sles-beta] SLES11-SP3 RC1 question concerning zypper dist-upgrade when upgrading from SLES11-SP2, why additional 32bit libraries on a x86_64 bit server? In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0E2454BB@HXMB12.pnet.ch> References: <40637DBB36AF3941B243A286A432CA0B0E2454BB@HXMB12.pnet.ch> Message-ID: <20130501154536.GA1172@suse.de> Hi, On Wed, May 01, urs.frey at post.ch wrote: > Hi > > I am doing SLES11-SP3 upgrade testing from SLES11-SP2 x86_64 to SLES11-SP3 RC1 x86_64 > I installed SLES11-SP2 base pattern, to latest patch-update > > When invoking zipper dist-upgrade, I can see that some new packages get installed. So far OK. > What worries me, that there are new libraries-32 being installed. > I mean, when having a pure x86_64 SLES11-SP2 64bit installation, why get 32bit libraries newly installed? But you didn't had a pure x86_64 installation, as your zypper output shows. So it is expected that the new gcc runtime dependencies are fullfilled. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From urs.frey at post.ch Wed May 1 09:48:12 2013 From: urs.frey at post.ch (urs.frey at post.ch) Date: Wed, 1 May 2013 15:48:12 +0000 Subject: [sles-beta] SLES11-SP3 RC1 question concerning zypper dist-upgrade when upgrading from SLES11-SP2, why additional 32bit libraries on a x86_64 bit server? In-Reply-To: <20130501154536.GA1172@suse.de> References: <40637DBB36AF3941B243A286A432CA0B0E2454BB@HXMB12.pnet.ch> <20130501154536.GA1172@suse.de> Message-ID: <40637DBB36AF3941B243A286A432CA0B0E2454DA@HXMB12.pnet.ch> Ok thanks for double check Urs Frey????????????????????????????????????????????? Die Schweizerische Post Services Informationstechnologie Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX???? : ++41 (0)58 667 30 07 E-Mail:?? urs.frey at post.ch -----Urspr?ngliche Nachricht----- Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Thorsten Kukuk Gesendet: Wednesday, May 01, 2013 5:46 PM An: SUSE Linux Enterprise Server Authorized Beta Program Betreff: Re: [sles-beta] SLES11-SP3 RC1 question concerning zypper dist-upgrade when upgrading from SLES11-SP2, why additional 32bit libraries on a x86_64 bit server? Hi, On Wed, May 01, urs.frey at post.ch wrote: > Hi > > I am doing SLES11-SP3 upgrade testing from SLES11-SP2 x86_64 to SLES11-SP3 RC1 x86_64 > I installed SLES11-SP2 base pattern, to latest patch-update > > When invoking zipper dist-upgrade, I can see that some new packages get installed. So far OK. > What worries me, that there are new libraries-32 being installed. > I mean, when having a pure x86_64 SLES11-SP2 64bit installation, why get 32bit libraries newly installed? But you didn't had a pure x86_64 installation, as your zypper output shows. So it is expected that the new gcc runtime dependencies are fullfilled. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From uwedr at suse.com Fri May 3 03:45:19 2013 From: uwedr at suse.com (Uwe Drechsel) Date: Fri, 3 May 2013 11:45:19 +0200 Subject: [sles-beta] SLES11-SP3 RC1 - Autoyast Problem In-Reply-To: <517FDBEC.3010408@oce.com> References: <517E9DDC.5000507@oce.com> <20130430094149.GK22286@suse.de> <517FDBEC.3010408@oce.com> Message-ID: <20130503094519.GK23511@suse.de> Thanks Klaus, this is marked as fixed in RC2. -Uwe On Tue, Apr 30, Klaus Gmeinwieser wrote: > Hallo Uwe, > > ich habe SR 10827610471 zu diesem Thema aufgemacht und die alle > Dateien aus /var/log/YaST2 angeh?ngt. Ich hoffe das ist erst einmal > ausreichend. Ich bin leider erst wieder am 6.5 im B?ro f?r weitere > Tests oder Logs. > > Gr??e > Klaus > > Am 30.04.2013 11:41, schrieb Uwe Drechsel: > >Klaus, > > > >a first quick test failed to reproduce this. > > > >Could you please open a Service Request and attach the logs, so that we > >can investigate? > > > > > > > >Thanks > >Uwe > > > >-- > >Uwe Drechsel > >SUSE Linux Beta Program Manager > >SUSE Linux Products GmbH > >GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) > > > > > >On Mon, Apr 29, Klaus Gmeinwieser wrote: > > > >>Hi, > >> > >>I did some testing on the RC1 today and got the following issues: > >> > >>- Update from Beta4 to RC1 worked seamlessly for my configuration > >> > >>- Fresh installation as unattended installation failed every time > >>for using regular boot parameters like > >> > >>"autoyast=usb" or "autoyast=floppy" > >> > >>- NFS V3 Server configured with YaST works, but share is not > >>writeable even if configured > >> > >>/uPD *(rw,no_root_squash,sync,no_subtree_check) > >> > >>All of these problems apply to both of my test servers Fujitsu > >>Tx150S5 (SAS) and TX150S7 (Sata). > >> > >>I was able to get unattended installation work for using parameter > >>device://sdd1/autoinst.xml (for my USB Stick) or > >>device://fd0/autoinst.xml for using floppies. The keywords USB or > >>floppy do not work anymore. > >> > >>In the KDE Menu - the "Terminal - Super User Mode" still opens a > >>regular user shell.... > >> > >>Will continue tomorrow with testing.... > >> > >>Regards > >>Klaus From Dick.Waite at softwareag.com Mon May 6 02:36:23 2013 From: Dick.Waite at softwareag.com (Waite, Dick) Date: Mon, 6 May 2013 08:36:23 +0000 Subject: [sles-beta] SLES11-SP3 - zLinux - fsck - Volume manager Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D24E34DD4@hqmbx6.eur.ad.sag> Grand Day, On one zLinux machine being updated from SP2 to SP3 the "volume manager" did not start. One could bring it on-line by hand and bring on the disks being used and the system ran. This was first noted at Beta3 but as other zLinux machines updated Okay it was noted and I'll check later... RC1 ran Okay on zLinux but again on one machine, the same one that had issues in Beta3 I had the same issues with Volume manager. I had not applied Beta 4 to this machine due to time issues. This time it was looked at. A "fsck" was over due, so I ran fsck on the require volumes and then applied RC1 again, this time no issues with Volume manager. I will try to get some time to check this on another zlinux machine but I do have a feeling in the water that something is not quite happy when there is an fsck outstanding when one applies an update. I would also agree one should check with fsck before the update, but this was not done....I'm sure it will be done in the future. I have not seen this on the many Intel x86_64's I have update over the years. The zlinux machine are supported by z/VM 6.2 .04 SL1301 the file system was ext3 There was only one logical volume group defined. Regards, ___________________________________________ Dick Waite Senior R&D Consultant Phone: +49 6151 92-1505 Mobile: +49 171 8393 769 Software AG Uhlandstr. 12 | 64297 Darmstadt | Germany www.softwareag.com ___________________________________________ Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From john.dallman at siemens.com Tue May 7 04:05:44 2013 From: john.dallman at siemens.com (Dallman, John) Date: Tue, 7 May 2013 10:05:44 +0000 Subject: [sles-beta] rlogin server not working in SLES11sp3 Message-ID: It worked OK in SLES11sp1 and sp2, but we haven't been able to get it going in sp3, either betas or RC1. Any suggestions? We use rlogin because it's convenient, and the machines are in a well-protected environment, not exposed to the Internet. Yes, we'll switch to SSH someday, but now is not a good time. -- John Dallman ----------------- Siemens Industry Software Limited is a limited company registered in England and Wales. Registered number: 3476850. Registered office: Faraday House, Sir William Siemens Square, Frimley, Surrey, GU16 8QD. From urs.frey at post.ch Tue May 7 04:06:04 2013 From: urs.frey at post.ch (urs.frey at post.ch) Date: Tue, 7 May 2013 10:06:04 +0000 Subject: [sles-beta] SLES11-SP3 x86_64 RC1 Problem Storage SAN lpfc module FCF discovery Message-ID: <40637DBB36AF3941B243A286A432CA0B0E24A7B6@HXMB12.pnet.ch> Hi I am testing SLES11-SP3 RC1 x86_64 on a HP Pr0liant Blade BL465cG7 AMD Opteron, attached to SAN EMC VMAx, FCoE, NC551i Emulex OneConnect 10GB CNA Suddenly during normal operation, I loose a SAN path on my test server. Instead of a re-instate after coming up of the SAN path again, I can see thousands of messages like this in my /var/log/messages May 6 21:43:01 h04wwl /usr/sbin/cron[1686]: (root) CMD (/usr/local/scripts/cpqhealth_mon > /dev/null 2>&1) May 6 21:45:01 h04wwl /usr/sbin/cron[1862]: (root) CMD (/usr/local/scripts/check_multipath.sh > /dev/null 2>&1) May 6 21:45:01 h04wwl /usr/sbin/cron[1863]: (oracle) CMD (/appl/ora/oraenv/bck/dynarcbck.sh > /dev/null 2>&1) May 6 21:49:01 h04wwl /usr/sbin/cron[2224]: (root) CMD (/usr/local/scripts/query_patchnix.sh > /dev/null 2>&1) May 6 21:50:01 h04wwl /usr/sbin/cron[2412]: (root) CMD (/usr/local/scripts/check_multipath.sh > /dev/null 2>&1) May 6 21:50:01 h04wwl /usr/sbin/cron[2413]: (oracle) CMD (/appl/ora/oraenv/bck/dynarcbck.sh > /dev/null 2>&1) May 6 21:55:01 h04wwl /usr/sbin/cron[2860]: (root) CMD (/usr/local/scripts/check_multipath.sh > /dev/null 2>&1) May 6 21:55:01 h04wwl /usr/sbin/cron[2861]: (oracle) CMD (/appl/ora/oraenv/bck/dynarcbck.sh > /dev/null 2>&1) May 6 21:58:22 h04wwl kernel: [621025.614280] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery May 6 21:58:22 h04wwl kernel: [621025.680799] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x3, index:x0 May 6 21:58:22 h04wwl kernel: [621025.680820] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery May 6 21:58:22 h04wwl kernel: [621025.726467] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x4, index:x0 May 6 21:58:22 h04wwl kernel: [621025.726485] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery May 6 21:58:22 h04wwl kernel: [621025.772060] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x5, index:x0 May 6 21:58:22 h04wwl kernel: [621025.772078] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery May 6 21:58:22 h04wwl kernel: [621025.825965] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x6, index:x0 May 6 21:58:22 h04wwl kernel: [621025.825983] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery May 6 21:58:22 h04wwl kernel: [621025.871796] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x7, index:x0 Upon issuing manually a LIP on the CNA again, the SAN path gets re-detected and reinstated. I could observe quite a similar behavior also on SLES11-SP3 Beta4. Why is there no automatic reinstate of the SAN path? What is does this mean "In-use FCF (0) modified, perform FCF rediscovery". I mean this should be solved in fully automatic mode, no manual intervention necessary. This works best on SLES11-SP2, and also worked fine until SLES11-SP3 Beta4 I assume, that we either do have a problem with the lpfc.ko kernel module, or in the SLES11-SP3 RC1 kernel itself I can reproduce it by simply taking down one CNA switch path and getting it up again. BUT when disabling one SAN path on the VMAx itself, multipath does work best and does also reinstate without a problem after enabling the SAN path again. So there must be a different event causing the problem. Question: What to set for save operation on SAN? What is about the lpfc_fcf_failover_policy? Thank you for your feedback Best regards Urs Frey Die Schweizerische Post Services Informationstechnologie Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX : ++41 (0)58 667 30 07 E-Mail: urs.frey at post.ch From meissner at suse.de Tue May 7 05:04:20 2013 From: meissner at suse.de (Marcus Meissner) Date: Tue, 7 May 2013 13:04:20 +0200 Subject: [sles-beta] rlogin server not working in SLES11sp3 In-Reply-To: References: Message-ID: <20130507110420.GK6592@suse.de> On Tue, May 07, 2013 at 10:05:44AM +0000, Dallman, John wrote: > It worked OK in SLES11sp1 and sp2, but we haven't been able to get > it going in sp3, either betas or RC1. Any suggestions? > > We use rlogin because it's convenient, and the machines are in a > well-protected environment, not exposed to the Internet. Yes, we'll > switch to SSH someday, but now is not a good time. What does "not work" mean in symptoms? Ciao, marcus From hare at suse.com Tue May 7 04:55:40 2013 From: hare at suse.com (Hannes Reinecke) Date: Tue, 07 May 2013 12:55:40 +0200 Subject: [sles-beta] SLES11-SP3 x86_64 RC1 Problem Storage SAN lpfc module FCF discovery In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0E24A7B6@HXMB12.pnet.ch> References: <40637DBB36AF3941B243A286A432CA0B0E24A7B6@HXMB12.pnet.ch> Message-ID: <5188DDAC.1050403@suse.com> On 05/07/2013 12:06 PM, urs.frey at post.ch wrote: > Hi > I am testing SLES11-SP3 RC1 x86_64 on a HP Pr0liant Blade BL465cG7 AMD Opteron, attached to SAN EMC VMAx, FCoE, NC551i Emulex OneConnect 10GB CNA > > Suddenly during normal operation, I loose a SAN path on my test server. > Instead of a re-instate after coming up of the SAN path again, I can see thousands of messages like this in my /var/log/messages > > May 6 21:43:01 h04wwl /usr/sbin/cron[1686]: (root) CMD (/usr/local/scripts/cpqhealth_mon > /dev/null 2>&1) > May 6 21:45:01 h04wwl /usr/sbin/cron[1862]: (root) CMD (/usr/local/scripts/check_multipath.sh > /dev/null 2>&1) > May 6 21:45:01 h04wwl /usr/sbin/cron[1863]: (oracle) CMD (/appl/ora/oraenv/bck/dynarcbck.sh > /dev/null 2>&1) > May 6 21:49:01 h04wwl /usr/sbin/cron[2224]: (root) CMD (/usr/local/scripts/query_patchnix.sh > /dev/null 2>&1) > May 6 21:50:01 h04wwl /usr/sbin/cron[2412]: (root) CMD (/usr/local/scripts/check_multipath.sh > /dev/null 2>&1) > May 6 21:50:01 h04wwl /usr/sbin/cron[2413]: (oracle) CMD (/appl/ora/oraenv/bck/dynarcbck.sh > /dev/null 2>&1) > May 6 21:55:01 h04wwl /usr/sbin/cron[2860]: (root) CMD (/usr/local/scripts/check_multipath.sh > /dev/null 2>&1) > May 6 21:55:01 h04wwl /usr/sbin/cron[2861]: (oracle) CMD (/appl/ora/oraenv/bck/dynarcbck.sh > /dev/null 2>&1) > May 6 21:58:22 h04wwl kernel: [621025.614280] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.680799] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x3, index:x0 > May 6 21:58:22 h04wwl kernel: [621025.680820] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.726467] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x4, index:x0 > May 6 21:58:22 h04wwl kernel: [621025.726485] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.772060] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x5, index:x0 > May 6 21:58:22 h04wwl kernel: [621025.772078] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.825965] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x6, index:x0 > May 6 21:58:22 h04wwl kernel: [621025.825983] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.871796] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x7, index:x0 > > Upon issuing manually a LIP on the CNA again, the SAN path gets re-detected and reinstated. > I could observe quite a similar behavior also on SLES11-SP3 Beta4. > Why is there no automatic reinstate of the SAN path? > What is does this mean "In-use FCF (0) modified, perform FCF rediscovery". > I mean this should be solved in fully automatic mode, no manual intervention necessary. > > This works best on SLES11-SP2, and also worked fine until SLES11-SP3 Beta4 > I assume, that we either do have a problem with the lpfc.ko kernel module, or in the SLES11-SP3 RC1 kernel itself > > I can reproduce it by simply taking down one CNA switch path and getting it up again. > BUT when disabling one SAN path on the VMAx itself, multipath does work best and does also reinstate without a problem after enabling the SAN path again. > > So there must be a different event causing the problem. > This is already a bugzilla entry for this: 816065 We already have an lpfc update from Emulex, which might fix this issue. Can you try with the latest KOTD? Cheers, Hannes From urs.frey at post.ch Tue May 7 05:25:58 2013 From: urs.frey at post.ch (urs.frey at post.ch) Date: Tue, 7 May 2013 11:25:58 +0000 Subject: [sles-beta] SLES11-SP3 x86_64 RC1 Problem Storage SAN lpfc module FCF discovery In-Reply-To: <5188DDAC.1050403@suse.com> References: <40637DBB36AF3941B243A286A432CA0B0E24A7B6@HXMB12.pnet.ch> <5188DDAC.1050403@suse.com> Message-ID: <40637DBB36AF3941B243A286A432CA0B0E24B812@HXMB12.pnet.ch> Hi Thanks >This is already a bugzilla entry for this: 816065 >We already have an lpfc update from Emulex, which might fix this issue. >Can you try with the latest KOTD? YES of course I would like to try. Can you please give me a link, from where I can download the needed packages to install? Thank you very much Best regards Urs Urs Frey????????????????????????????????????????????? Die Schweizerische Post Services Informationstechnologie Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX???? : ++41 (0)58 667 30 07 E-Mail:?? urs.frey at post.ch -----Urspr?ngliche Nachricht----- Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Hannes Reinecke Gesendet: Tuesday, May 07, 2013 12:56 PM An: sles-beta at lists.suse.com Betreff: Re: [sles-beta] SLES11-SP3 x86_64 RC1 Problem Storage SAN lpfc module FCF discovery On 05/07/2013 12:06 PM, urs.frey at post.ch wrote: > Hi > I am testing SLES11-SP3 RC1 x86_64 on a HP Pr0liant Blade BL465cG7 AMD Opteron, attached to SAN EMC VMAx, FCoE, NC551i Emulex OneConnect 10GB CNA > > Suddenly during normal operation, I loose a SAN path on my test server. > Instead of a re-instate after coming up of the SAN path again, I can see thousands of messages like this in my /var/log/messages > > May 6 21:43:01 h04wwl /usr/sbin/cron[1686]: (root) CMD (/usr/local/scripts/cpqhealth_mon > /dev/null 2>&1) > May 6 21:45:01 h04wwl /usr/sbin/cron[1862]: (root) CMD (/usr/local/scripts/check_multipath.sh > /dev/null 2>&1) > May 6 21:45:01 h04wwl /usr/sbin/cron[1863]: (oracle) CMD (/appl/ora/oraenv/bck/dynarcbck.sh > /dev/null 2>&1) > May 6 21:49:01 h04wwl /usr/sbin/cron[2224]: (root) CMD (/usr/local/scripts/query_patchnix.sh > /dev/null 2>&1) > May 6 21:50:01 h04wwl /usr/sbin/cron[2412]: (root) CMD (/usr/local/scripts/check_multipath.sh > /dev/null 2>&1) > May 6 21:50:01 h04wwl /usr/sbin/cron[2413]: (oracle) CMD (/appl/ora/oraenv/bck/dynarcbck.sh > /dev/null 2>&1) > May 6 21:55:01 h04wwl /usr/sbin/cron[2860]: (root) CMD (/usr/local/scripts/check_multipath.sh > /dev/null 2>&1) > May 6 21:55:01 h04wwl /usr/sbin/cron[2861]: (oracle) CMD (/appl/ora/oraenv/bck/dynarcbck.sh > /dev/null 2>&1) > May 6 21:58:22 h04wwl kernel: [621025.614280] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.680799] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x3, index:x0 > May 6 21:58:22 h04wwl kernel: [621025.680820] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.726467] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x4, index:x0 > May 6 21:58:22 h04wwl kernel: [621025.726485] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.772060] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x5, index:x0 > May 6 21:58:22 h04wwl kernel: [621025.772078] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.825965] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x6, index:x0 > May 6 21:58:22 h04wwl kernel: [621025.825983] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.871796] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x7, index:x0 > > Upon issuing manually a LIP on the CNA again, the SAN path gets re-detected and reinstated. > I could observe quite a similar behavior also on SLES11-SP3 Beta4. > Why is there no automatic reinstate of the SAN path? > What is does this mean "In-use FCF (0) modified, perform FCF rediscovery". > I mean this should be solved in fully automatic mode, no manual intervention necessary. > > This works best on SLES11-SP2, and also worked fine until SLES11-SP3 Beta4 > I assume, that we either do have a problem with the lpfc.ko kernel module, or in the SLES11-SP3 RC1 kernel itself > > I can reproduce it by simply taking down one CNA switch path and getting it up again. > BUT when disabling one SAN path on the VMAx itself, multipath does work best and does also reinstate without a problem after enabling the SAN path again. > > So there must be a different event causing the problem. > This is already a bugzilla entry for this: 816065 We already have an lpfc update from Emulex, which might fix this issue. Can you try with the latest KOTD? Cheers, Hannes _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From urs.frey at post.ch Tue May 7 05:31:35 2013 From: urs.frey at post.ch (urs.frey at post.ch) Date: Tue, 7 May 2013 11:31:35 +0000 Subject: [sles-beta] SLES11-SP3 x86_64 RC1 Problem Storage SAN lpfc module FCF discovery References: <40637DBB36AF3941B243A286A432CA0B0E24A7B6@HXMB12.pnet.ch> <5188DDAC.1050403@suse.com> Message-ID: <40637DBB36AF3941B243A286A432CA0B0E24C82C@HXMB12.pnet.ch> Hi Got it: http://ftp.suse.com/pub/projects/kernel/kotd/SLE11-SP3/x86_64/ Will try and keep you informed Best regards Urs Urs Frey????????????????????????????????????????????? Die Schweizerische Post Services Informationstechnologie Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX???? : ++41 (0)58 667 30 07 E-Mail:?? urs.frey at post.ch -----Urspr?ngliche Nachricht----- Von: Frey Urs, IT222 Gesendet: Tuesday, May 07, 2013 1:26 PM An: 'SUSE Linux Enterprise Server Authorized Beta Program' Betreff: AW: [sles-beta] SLES11-SP3 x86_64 RC1 Problem Storage SAN lpfc module FCF discovery Hi Thanks >This is already a bugzilla entry for this: 816065 >We already have an lpfc update from Emulex, which might fix this issue. >Can you try with the latest KOTD? YES of course I would like to try. Can you please give me a link, from where I can download the needed packages to install? Thank you very much Best regards Urs Urs Frey????????????????????????????????????????????? Die Schweizerische Post Services Informationstechnologie Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX???? : ++41 (0)58 667 30 07 E-Mail:?? urs.frey at post.ch -----Urspr?ngliche Nachricht----- Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Hannes Reinecke Gesendet: Tuesday, May 07, 2013 12:56 PM An: sles-beta at lists.suse.com Betreff: Re: [sles-beta] SLES11-SP3 x86_64 RC1 Problem Storage SAN lpfc module FCF discovery On 05/07/2013 12:06 PM, urs.frey at post.ch wrote: > Hi > I am testing SLES11-SP3 RC1 x86_64 on a HP Pr0liant Blade BL465cG7 AMD Opteron, attached to SAN EMC VMAx, FCoE, NC551i Emulex OneConnect 10GB CNA > > Suddenly during normal operation, I loose a SAN path on my test server. > Instead of a re-instate after coming up of the SAN path again, I can see thousands of messages like this in my /var/log/messages > > May 6 21:43:01 h04wwl /usr/sbin/cron[1686]: (root) CMD (/usr/local/scripts/cpqhealth_mon > /dev/null 2>&1) > May 6 21:45:01 h04wwl /usr/sbin/cron[1862]: (root) CMD (/usr/local/scripts/check_multipath.sh > /dev/null 2>&1) > May 6 21:45:01 h04wwl /usr/sbin/cron[1863]: (oracle) CMD (/appl/ora/oraenv/bck/dynarcbck.sh > /dev/null 2>&1) > May 6 21:49:01 h04wwl /usr/sbin/cron[2224]: (root) CMD (/usr/local/scripts/query_patchnix.sh > /dev/null 2>&1) > May 6 21:50:01 h04wwl /usr/sbin/cron[2412]: (root) CMD (/usr/local/scripts/check_multipath.sh > /dev/null 2>&1) > May 6 21:50:01 h04wwl /usr/sbin/cron[2413]: (oracle) CMD (/appl/ora/oraenv/bck/dynarcbck.sh > /dev/null 2>&1) > May 6 21:55:01 h04wwl /usr/sbin/cron[2860]: (root) CMD (/usr/local/scripts/check_multipath.sh > /dev/null 2>&1) > May 6 21:55:01 h04wwl /usr/sbin/cron[2861]: (oracle) CMD (/appl/ora/oraenv/bck/dynarcbck.sh > /dev/null 2>&1) > May 6 21:58:22 h04wwl kernel: [621025.614280] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.680799] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x3, index:x0 > May 6 21:58:22 h04wwl kernel: [621025.680820] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.726467] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x4, index:x0 > May 6 21:58:22 h04wwl kernel: [621025.726485] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.772060] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x5, index:x0 > May 6 21:58:22 h04wwl kernel: [621025.772078] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.825965] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x6, index:x0 > May 6 21:58:22 h04wwl kernel: [621025.825983] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.871796] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x7, index:x0 > > Upon issuing manually a LIP on the CNA again, the SAN path gets re-detected and reinstated. > I could observe quite a similar behavior also on SLES11-SP3 Beta4. > Why is there no automatic reinstate of the SAN path? > What is does this mean "In-use FCF (0) modified, perform FCF rediscovery". > I mean this should be solved in fully automatic mode, no manual intervention necessary. > > This works best on SLES11-SP2, and also worked fine until SLES11-SP3 Beta4 > I assume, that we either do have a problem with the lpfc.ko kernel module, or in the SLES11-SP3 RC1 kernel itself > > I can reproduce it by simply taking down one CNA switch path and getting it up again. > BUT when disabling one SAN path on the VMAx itself, multipath does work best and does also reinstate without a problem after enabling the SAN path again. > > So there must be a different event causing the problem. > This is already a bugzilla entry for this: 816065 We already have an lpfc update from Emulex, which might fix this issue. Can you try with the latest KOTD? Cheers, Hannes _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From john.dallman at siemens.com Tue May 7 07:30:11 2013 From: john.dallman at siemens.com (Dallman, John) Date: Tue, 7 May 2013 13:30:11 +0000 Subject: [sles-beta] rlogin server not working in SLES11sp3 In-Reply-To: <20130507110420.GK6592@suse.de> References: <20130507110420.GK6592@suse.de> Message-ID: Marcus Meissner wrote: > What does "not work" mean in symptoms? My test case is working from a SLES11sp2 machine, cbrlx64i60, to a SLES11sp3rc1 machine, cbli6004 (we're part-way through a change of our machine naming convention). Both machines are using the site NIS, in which my account name is "jgd", and have my user directory mounted on /sdl/prairie/users/jgd. My .rhosts file contains the line cbrlx64i60.cbr.ugs.com jgd I can rsh from cbrlx64i60 to cbli6004, thus: $ rsh cbli6004 pwd /sdl/prairie/users/jgd When I try to rlogin to cbli6004, I get: $ rlogin cbli6004 rlogin: connection closed. Which happens pretty well instantly. SLES11sp3beta2 behaved in just the same way. However, we have a SLES11sp3beta2 VM, running under VMware ESX, and rlogin to that works. The sysadmin swears he didn't set it up any differently. He was wondering if the different network hardware on the SLES11sp3rc1 physical machine was responsible, but has changed the network card without any change in behaviour. I have root access if I need it, but I am not a skilled sysadmin: I'm a developer who specialises in platforms and compilers. I've never done a UNIX or Linux installation, but I'm the guy with access to the beta programme and who has the need for a solution to this problem. Please tell me what else you need to know. thanks, -- John Dallman ----------------- Siemens Industry Software Limited is a limited company registered in England and Wales. Registered number: 3476850. Registered office: Faraday House, Sir William Siemens Square, Frimley, Surrey, GU16 8QD. From john.dallman at siemens.com Tue May 7 07:50:49 2013 From: john.dallman at siemens.com (Dallman, John) Date: Tue, 7 May 2013 13:50:49 +0000 Subject: [sles-beta] rlogin server not working in SLES11sp3 In-Reply-To: <5189042D.2010504@suse.com> References: <20130507110420.GK6592@suse.de> <5189042D.2010504@suse.com> Message-ID: Kai Dupke wrote: > Could you please check what's in the logfile at the moment you do an rsh > and later an rlogin? If this isn't generic it might help to identify > what happened. Assuming you mean /var/log/xinetd.log, rsh to do a pwd produces: 13/5/7 at 14:46:37: START: shell from=134.244.155.31 13/5/7 at 14:46:37: EXIT: shell status=0 duration=0(sec) and the rlogin produces: 13/5/7 at 14:48:38: START: login from=134.244.155.31 13/5/7 at 14:48:38: EXIT: login status=0 duration=0(sec) Running a command that takes a few seconds via rsh produces: 13/5/7 at 14:49:27: START: shell from=134.244.155.31 13/5/7 at 14:49:44: EXIT: shell status=0 duration=17(sec) thanks, -- John Dallman greetings Kai Dupke Senior Product Manager Server Product Line -- Phone: +49-(0)5102-9310828 Mail: kai.dupke at suse.com Mobile: +49-(0)173-5876766 WWW: www.suse.com SUSE Linux Products GmbH - Maxfeldstr. 5 - 90409 Nuernberg (Germany) GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG Nurnberg) ----------------- Siemens Industry Software Limited is a limited company registered in England and Wales. Registered number: 3476850. Registered office: Faraday House, Sir William Siemens Square, Frimley, Surrey, GU16 8QD. From urs.frey at post.ch Wed May 8 01:59:20 2013 From: urs.frey at post.ch (urs.frey at post.ch) Date: Wed, 8 May 2013 07:59:20 +0000 Subject: [sles-beta] SLES11-SP3 x86_64 RC1 Problem Storage SAN lpfc module FCF discovery In-Reply-To: <5188DDAC.1050403@suse.com> References: <40637DBB36AF3941B243A286A432CA0B0E24A7B6@HXMB12.pnet.ch> <5188DDAC.1050403@suse.com> Message-ID: <40637DBB36AF3941B243A286A432CA0B0E24C9D3@HXMB12.pnet.ch> Hi When using KOTD from May-6th-2013 with new lpfc version there is no more problem to see so far Testing on HP Blade BL456cG7 AMD Opteron FCoE NC551i Emulex OneConnect FW 4.1.450.16 Testing on HP Blade BL460c-Gen8 Intel Xeon FCoE 554FLB Flex LOM Emulex OneConnect FW 4.2.401.605 h05cni:~ # uname -a Linux h05cni 3.0.76-5.gdd92f67-default #1 SMP Mon May 6 13:46:12 UTC 2013 (dd92f67) x86_64 x86_64 x86_64 GNU/Linux h05cni:~ # modinfo lpfc | grep version version: 0:8.3.7.10.3p srcversion: E6E116CD33960F502A11BB8 vermagic: 3.0.76-5.gdd92f67-default SMP mod_unload modversions h05cni:~ # grep FCF /var/log/messages h05cni:~ # h04wwl:~ # uname -a Linux h04wwl 3.0.76-5.gdd92f67-default #1 SMP Mon May 6 13:46:12 UTC 2013 (dd92f67) x86_64 x86_64 x86_64 GNU/Linux h04wwl:~ # modinfo lpfc | grep version version: 0:8.3.7.10.3p srcversion: E6E116CD33960F502A11BB8 vermagic: 3.0.76-5.gdd92f67-default SMP mod_unload modversions h04wwl:~ # grep FCF /var/log/messages h04wwl:~ # Will go on with testing under load, and different SAN events Best regards Urs Frey????????????????????????????????????????????? Die Schweizerische Post Services Informationstechnologie Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX???? : ++41 (0)58 667 30 07 E-Mail:?? urs.frey at post.ch -----Urspr?ngliche Nachricht----- Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Hannes Reinecke Gesendet: Tuesday, May 07, 2013 12:56 PM An: sles-beta at lists.suse.com Betreff: Re: [sles-beta] SLES11-SP3 x86_64 RC1 Problem Storage SAN lpfc module FCF discovery On 05/07/2013 12:06 PM, urs.frey at post.ch wrote: > Hi > I am testing SLES11-SP3 RC1 x86_64 on a HP Pr0liant Blade BL465cG7 AMD Opteron, attached to SAN EMC VMAx, FCoE, NC551i Emulex OneConnect 10GB CNA > > Suddenly during normal operation, I loose a SAN path on my test server. > Instead of a re-instate after coming up of the SAN path again, I can see thousands of messages like this in my /var/log/messages > > May 6 21:43:01 h04wwl /usr/sbin/cron[1686]: (root) CMD (/usr/local/scripts/cpqhealth_mon > /dev/null 2>&1) > May 6 21:45:01 h04wwl /usr/sbin/cron[1862]: (root) CMD (/usr/local/scripts/check_multipath.sh > /dev/null 2>&1) > May 6 21:45:01 h04wwl /usr/sbin/cron[1863]: (oracle) CMD (/appl/ora/oraenv/bck/dynarcbck.sh > /dev/null 2>&1) > May 6 21:49:01 h04wwl /usr/sbin/cron[2224]: (root) CMD (/usr/local/scripts/query_patchnix.sh > /dev/null 2>&1) > May 6 21:50:01 h04wwl /usr/sbin/cron[2412]: (root) CMD (/usr/local/scripts/check_multipath.sh > /dev/null 2>&1) > May 6 21:50:01 h04wwl /usr/sbin/cron[2413]: (oracle) CMD (/appl/ora/oraenv/bck/dynarcbck.sh > /dev/null 2>&1) > May 6 21:55:01 h04wwl /usr/sbin/cron[2860]: (root) CMD (/usr/local/scripts/check_multipath.sh > /dev/null 2>&1) > May 6 21:55:01 h04wwl /usr/sbin/cron[2861]: (oracle) CMD (/appl/ora/oraenv/bck/dynarcbck.sh > /dev/null 2>&1) > May 6 21:58:22 h04wwl kernel: [621025.614280] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.680799] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x3, index:x0 > May 6 21:58:22 h04wwl kernel: [621025.680820] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.726467] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x4, index:x0 > May 6 21:58:22 h04wwl kernel: [621025.726485] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.772060] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x5, index:x0 > May 6 21:58:22 h04wwl kernel: [621025.772078] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.825965] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x6, index:x0 > May 6 21:58:22 h04wwl kernel: [621025.825983] lpfc 0000:04:00.2: 0:3300 In-use FCF (0) modified, perform FCF rediscovery > May 6 21:58:22 h04wwl kernel: [621025.871796] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x7, index:x0 > > Upon issuing manually a LIP on the CNA again, the SAN path gets re-detected and reinstated. > I could observe quite a similar behavior also on SLES11-SP3 Beta4. > Why is there no automatic reinstate of the SAN path? > What is does this mean "In-use FCF (0) modified, perform FCF rediscovery". > I mean this should be solved in fully automatic mode, no manual intervention necessary. > > This works best on SLES11-SP2, and also worked fine until SLES11-SP3 Beta4 > I assume, that we either do have a problem with the lpfc.ko kernel module, or in the SLES11-SP3 RC1 kernel itself > > I can reproduce it by simply taking down one CNA switch path and getting it up again. > BUT when disabling one SAN path on the VMAx itself, multipath does work best and does also reinstate without a problem after enabling the SAN path again. > > So there must be a different event causing the problem. > This is already a bugzilla entry for this: 816065 We already have an lpfc update from Emulex, which might fix this issue. Can you try with the latest KOTD? Cheers, Hannes _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From kukuk at suse.de Fri May 17 04:43:28 2013 From: kukuk at suse.de (Thorsten Kukuk) Date: Fri, 17 May 2013 12:43:28 +0200 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 RC2 available Message-ID: <20130517104328.GA1727@suse.de> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Dear Beta Tester, we are happy to announce SUSE Linux Enterprise Server 11 SP3 RC2 This is the last release candidate before GMC! ISO images are now available for download now. Please go to http://www.novell.com/beta and select "View my beta page". Here you should see all Beta's you are part of. We offer 3 DVD ISOs: DVD1 contains the binaries, the second DVD the sources and the third DVD the debuginfo packages. The final product will not contain the debuginfo packages on the media. Please verify the md5sum of the ISO using the MD5SUMS file, which can be found in the same directory on the download servers. Thanks in advance for all your testing Your SUSE Linux Enterprise Team -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From uwedr at suse.com Fri May 17 07:44:07 2013 From: uwedr at suse.com (Uwe Drechsel) Date: Fri, 17 May 2013 15:44:07 +0200 Subject: [sles-beta] Final survey Message-ID: <20130517134407.GA31257@suse.de> Dear participants, with the release of RC2 the end of this beta test is getting closer (SLED and HA are currently still on their way to the download servers). We would like to ask you to provide us with some feedback on the products and also the beta test itself: http://www.surveymonkey.com/s/8D7W5TY The survey will be open until June 2. Thank you Uwe Drechsel -- SUSE Linux Beta Program Manager tel: +49 911 74053-0 SUSE Linux Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From urs.frey at post.ch Fri May 17 08:14:16 2013 From: urs.frey at post.ch (urs.frey at post.ch) Date: Fri, 17 May 2013 14:14:16 +0000 Subject: [sles-beta] SLES11-SP2 RC2 first experience Message-ID: <40637DBB36AF3941B243A286A432CA0B0E250263@HXMB12.pnet.ch> Hi I just downloaded SLES11-SP2 RC2 x86_64 and installed on HP Proliant DL385G5 and HP Blade BL460cG7 FCoE attached to SAN BUG 817279: multipath.conf +13, invalid keyword: getuid_callout: => is resolved, works OK, no weird message anymore even though getuid_callout is deprecated BUG 816065 [HP BCS SLES11 Bug] Regression - "New FCF event" related boot fail on SLES 11 SP3 BETA4 => on my Blade server so far no FCF event messages with lpfc kernel module version: 0:8.3.7.10.3p and kernel 3.0.76-0.7-default General: Installation with autoyast runs smoothly Installed pattern base + oracle_server Installed pattern Minimal + xen_server Thanks all for your excellent work at SuSE && Best regards Urs Frey Die Schweizerische Post Services Informationstechnologie Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX : ++41 (0)58 667 30 07 E-Mail: urs.frey at post.ch From aj at suse.com Fri May 17 08:37:03 2013 From: aj at suse.com (Andreas Jaeger) Date: Fri, 17 May 2013 16:37:03 +0200 Subject: [sles-beta] SLES11-SP2 RC2 first experience In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0E250263@HXMB12.pnet.ch> References: <40637DBB36AF3941B243A286A432CA0B0E250263@HXMB12.pnet.ch> Message-ID: <5196408F.5070600@suse.com> On 05/17/2013 04:14 PM, urs.frey at post.ch wrote: > Hi > > I just downloaded SLES11-SP2 RC2 x86_64 and installed on HP Proliant DL385G5 and HP Blade BL460cG7 FCoE attached to SAN > > BUG 817279: multipath.conf +13, invalid keyword: getuid_callout: > => is resolved, works OK, no weird message anymore even though getuid_callout is deprecated > > BUG 816065 [HP BCS SLES11 Bug] Regression - "New FCF event" related boot fail on SLES 11 SP3 BETA4 > => on my Blade server so far no FCF event messages with lpfc kernel module version: 0:8.3.7.10.3p and kernel 3.0.76-0.7-default > > General: > Installation with autoyast runs smoothly > Installed pattern base + oracle_server > Installed pattern Minimal + xen_server > > > Thanks all for your excellent work at SuSE && Thanks for your testing and the report! Have a nice weekend, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From Klaus.Gmeinwieser at oce.com Tue May 21 05:54:44 2013 From: Klaus.Gmeinwieser at oce.com (Klaus Gmeinwieser) Date: Tue, 21 May 2013 13:54:44 +0200 Subject: [sles-beta] SLES11-SP2 RC2 first experience Message-ID: <519B6084.9060504@oce.com> Hi All, I installed RC2 on several servers also with our own application... --OK :)-- - Unattended Installation works again - Quick test on ftp,samba server and client works fine - root konsole start menu entry in KDE is okay --Questions-- NFS file transfer seems to periodically (every 10s) freeze the client (KDE4) for about a second if client copies a large file to remote server --Still not OK :(-- - Screensaver configuration in KDE Control Center is still broken - Xnest connection from SP3 to SP3 via XDMCP produces unuseable graphics, Xephyr works fine Will do some deeper tests these days and post my results. Thanks to all for the good work!!!! Klaus -- Klaus Gmeinwieser email: klaus.gmeinwieser at oce.com voice: +49 8121 72 4358 Oc? Printing Systems GmbH - A Canon Group Company This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation. From john.dallman at siemens.com Tue May 21 06:42:44 2013 From: john.dallman at siemens.com (Dallman, John) Date: Tue, 21 May 2013 12:42:44 +0000 Subject: [sles-beta] rlogin server not working in SLES11sp3 In-Reply-To: References: <20130507110420.GK6592@suse.de> <5189042D.2010504@suse.com> Message-ID: > Kai Dupke wrote: > > > Could you please check what's in the logfile at the moment you do an rsh > > and later an rlogin? If this isn't generic it might help to identify > > what happened. > > Assuming you mean /var/log/xinetd.log, rsh to do a pwd produces: > > 13/5/7 at 14:46:37: START: shell from=134.244.155.31 > 13/5/7 at 14:46:37: EXIT: shell status=0 duration=0(sec) > > and the rlogin produces: > > 13/5/7 at 14:48:38: START: login from=134.244.155.31 > 13/5/7 at 14:48:38: EXIT: login status=0 duration=0(sec) > > Running a command that takes a few seconds via rsh produces: > > 13/5/7 at 14:49:27: START: shell from=134.244.155.31 > 13/5/7 at 14:49:44: EXIT: shell status=0 duration=17(sec) Any ideas, anyone? This is a nuisance, and rather diminishes our enthusiasm for a mass upgrade to SLES11sp3. thanks, -- John Dallman ----------------- Siemens Industry Software Limited is a limited company registered in England and Wales. Registered number: 3476850. Registered office: Faraday House, Sir William Siemens Square, Frimley, Surrey, GU16 8QD. From gjn at gjn.priv.at Wed May 22 08:07:25 2013 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Wed, 22 May 2013 16:07:25 +0200 Subject: [sles-beta] YaST2-Kerberos Sever Module broken (RC2) Message-ID: <1475230.4IooCxznfN@techz.gjn.prv> Hello, Bad News ;) the YaST2 Module Kerberos Server is broken with LDAP Installation. In the SP2 (SP1) the kerberos.schema is copy to the /etc/openlad/schema and configured correct on a system with LDAP & kerberos. With SP3 this is all broken :(. -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From behlert at suse.de Thu May 23 02:23:20 2013 From: behlert at suse.de (Stefan Behlert) Date: Thu, 23 May 2013 10:23:20 +0200 Subject: [sles-beta] YaST2-Kerberos Sever Module broken (RC2) In-Reply-To: <1475230.4IooCxznfN@techz.gjn.prv> References: <1475230.4IooCxznfN@techz.gjn.prv> Message-ID: <20130523082320.GC6144@suse.de> Hi, On May 22, 13 16:07:25 +0200, G?nther J. Niederwimmer wrote: > Hello, > > Bad News ;) the YaST2 Module Kerberos Server is broken with LDAP Installation. Hm, nothing in that module directly has been changed for SP3. So we need a bugreport (service request) and logfiles to see what's causing it. Stefan > In the SP2 (SP1) the kerberos.schema is copy to the /etc/openlad/schema and > configured correct on a system with LDAP & kerberos. > > With SP3 this is all broken :(. > -- > mit freundlichen Gr??en / best Regards, > > G?nther J. Niederwimmer > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Stefan Behlert, SUSE LINUX Project Manager Enterprise Desktop Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE LINUX Products GmbH, Nuernberg; GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer, HRB 16746 (AG Nuernberg) From lslezak at suse.cz Thu May 23 02:55:16 2013 From: lslezak at suse.cz (Ladislav Slezak) Date: Thu, 23 May 2013 10:55:16 +0200 Subject: [sles-beta] YaST2-Kerberos Sever Module broken (RC2) In-Reply-To: <20130523082320.GC6144@suse.de> References: <1475230.4IooCxznfN@techz.gjn.prv> <20130523082320.GC6144@suse.de> Message-ID: <519DD974.6000508@suse.cz> Dne 23.5.2013 10:23, Stefan Behlert napsal(a): > Hi, > > On May 22, 13 16:07:25 +0200, G?nther J. Niederwimmer wrote: >> Hello, >> >> Bad News ;) the YaST2 Module Kerberos Server is broken with LDAP Installation. > > Hm, nothing in that module directly has been changed for SP3. Yes, yast2-kerberos-server package has not been changed since SP2, the SP3 version is the same as in SP2. So it's strange that it stopped working, there must be some other change in the system... Please, open a bug report for this and attach YaST logs. -- Ladislav Slez?k Appliance department / YaST Developer Lihovarsk? 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak at suse.com SUSE From gjn at gjn.priv.at Thu May 23 03:25:24 2013 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Thu, 23 May 2013 11:25:24 +0200 Subject: [sles-beta] YaST2-Kerberos Sever Module broken (RC2) In-Reply-To: <519DD974.6000508@suse.cz> References: <1475230.4IooCxznfN@techz.gjn.prv> <20130523082320.GC6144@suse.de> <519DD974.6000508@suse.cz> Message-ID: <16704897.rKo4Mi2B13@techz.gjn.prv> Hello, Am Donnerstag, 23. Mai 2013, 10:55:16 schrieb Ladislav Slezak: > Dne 23.5.2013 10:23, Stefan Behlert napsal(a): > > Hi, > > > > On May 22, 13 16:07:25 +0200, G?nther J. Niederwimmer wrote: > >> Hello, > >> > >> Bad News ;) the YaST2 Module Kerberos Server is broken with LDAP > >> Installation.> > > Hm, nothing in that module directly has been changed for SP3. > > Yes, yast2-kerberos-server package has not been changed since SP2, > the SP3 version is the same as in SP2. So it's strange that it > stopped working, there must be some other change in the system... > > Please, open a bug report for this and attach YaST logs. SR # 10831265721 is created. -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From gjn at gjn.priv.at Thu May 23 03:47:09 2013 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Thu, 23 May 2013 11:47:09 +0200 Subject: [sles-beta] Grub Install "MBR" selection Message-ID: <3274127.1EN9EV7tcX@techz.gjn.prv> Hello, I have for test a older Board with Intel Matrix Storage (Raid1) installed. Is it "normal" that the Installer use the /boot Partition to install the bootloader. This is not working with a Software Raid. I have to set it, EXTRA to "MBR" by the Installation then this Systems are booting in the second stage. Only a Question ;). -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From Glenn.Andersson at ostersund.se Fri May 24 10:09:56 2013 From: Glenn.Andersson at ostersund.se (Glenn Andersson sf) Date: Fri, 24 May 2013 18:09:56 +0200 Subject: [sles-beta] Auto-Yast Mail Issue Message-ID: Hej, ?r p? utbildning. ?ter den 3/6. Vid br?dskande ?renden kontakta kundservice p? 063-140600. M V H Glenn Andersson Datacenter ?stersunds Kommun -------------- next part -------------- An HTML attachment was scrubbed... URL: From Glenn.Andersson at ostersund.se Sat May 25 11:34:47 2013 From: Glenn.Andersson at ostersund.se (Glenn Andersson sf) Date: Sat, 25 May 2013 19:34:47 +0200 Subject: [sles-beta] Mellanox ConnectX3 Message-ID: Hej, ?r p? utbildning. ?ter den 3/6. Vid br?dskande ?renden kontakta kundservice p? 063-140600. M V H Glenn Andersson Datacenter ?stersunds Kommun -------------- next part -------------- An HTML attachment was scrubbed... URL: From Glenn.Andersson at ostersund.se Mon May 27 02:25:18 2013 From: Glenn.Andersson at ostersund.se (Glenn Andersson sf) Date: Mon, 27 May 2013 10:25:18 +0200 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 RC2 available Message-ID: Hej, ?r p? utbildning. ?ter den 3/6. Vid br?dskande ?renden kontakta kundservice p? 063-140600. M V H Glenn Andersson Datacenter ?stersunds Kommun -------------- next part -------------- An HTML attachment was scrubbed... URL: From uwedr at suse.com Tue May 28 03:10:11 2013 From: uwedr at suse.com (uwedr at suse.com) Date: Tue, 28 May 2013 11:10:11 +0200 Subject: [sles-beta] Final survey - reminder In-Reply-To: <20130517134407.GA31257@suse.de> References: <20130517134407.GA31257@suse.de> Message-ID: <20130528091011.GC8061@suse.de> Dear testers, just in case you haven't had a look yet: We would appreciate if you could spend a few minutes on our final survey about this Beta Test to help us improve both the products and the test itself: http://www.surveymonkey.com/s/8D7W5TY Thank you Uwe Drechsel -- SUSE Linux Beta Program Manager SUSE Linux Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) On Fri, May 17, Uwe Drechsel wrote: > Dear participants, > > with the release of RC2 the end of this beta test is getting closer > (SLED and HA are currently still on their way to the download servers). > > We would like to ask you to provide us with some feedback on the products > and also the beta test itself: > > http://www.surveymonkey.com/s/8D7W5TY > > The survey will be open until June 2. > > > Thank you > Uwe Drechsel From Glenn.Andersson at ostersund.se Tue May 28 03:10:30 2013 From: Glenn.Andersson at ostersund.se (Glenn Andersson sf) Date: Tue, 28 May 2013 11:10:30 +0200 Subject: [sles-beta] Final survey - reminder Message-ID: Hej, ?r p? utbildning. ?ter den 3/6. Vid br?dskande ?renden kontakta kundservice p? 063-140600. M V H Glenn Andersson Datacenter ?stersunds Kommun -------------- next part -------------- An HTML attachment was scrubbed... URL: