[sles-beta] Yast Expert Partitioner - RC2
Waite, Dick (External)
Dick.Waite at softwareag.com
Mon Sep 5 08:11:59 MDT 2016
Many Thanks Vincent. Bug 997254 created. I also found looking at my home_office machines, they would like to install NetworkManager 1.0.12-7.2 but "libqdialogsolve" is missing so it does not install, so I do not get the issues with Partitioner.
I'm in Ireland from early tomorrow until next Monday. Not much internet access, Blackberry only, so I hope there is enough on the forum and this bug to fix this. I checked with SLES12-SP1 and there is was either no NetworkManager or NetworkManager 0.9.8.10-3.9 which works Okay with Partitioner.
Enjoy,
__R
________________________________________
From: Vincent Moutoussamy [vmoutoussamy at suse.com]
Sent: 05 September 2016 15:55
To: Waite, Dick (External)
Cc: Arvin Schnell; sles-beta at lists.suse.com
Subject: Re: [sles-beta] Yast Expert Partitioner - RC2
Hi,
Please create a bug report for this!
here is the direct link to create the bug report:
https://bugzilla.suse.com/enter_bug.cgi?product=Beta%20SUSE%20Linux%20Enterprise%20Server%2012%20SP2
Thanks,
Regards,
--
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager
> On 05 Sep 2016, at 10:27, Waite, Dick (External) <Dick.Waite at softwareag.com> wrote:
>
> Many Thanks to A.N.Other, I was asked not to give a name...
>
> NetworkManager 0.9.8.10-3.9 works
> NetworkManager 1.0.12-7.2 gives the issue
>
> If I try to update from the lower version on Windows I get "nothing provides NetworkManager-branding needed by ....So it stays at the lower (working) level. On Linux host it finds the "branding" so uses the high, non working version.
>
> So there we are, simple when you know a version of NetworkManger is broken. I'll be back from my road-trip for the new drop, maybe then there is a fix to the grand NetworkManager....
>
> __R
>
>
> ________________________________________
> From: Waite, Dick (External)
> Sent: 05 September 2016 10:03
> To: 'Vincent Moutoussamy'
> Cc: 'Arvin Schnell'; 'sles-beta at lists.suse.com'
> Subject: RE: [sles-beta] Yast Expert Partitioner - RC2
>
> Just in case I'm asked, I can clone a working machine from home_office to SAG and it will fail, I can clone a failing machine from SAG to home_office and it will work. From my eye-balls the Networks are the same, all NAT but home_office is simple 192.168.2.1 and SAG is well there is quite a large group looking after it ;o)
> __R
> ________________________________________
> From: Waite, Dick (External)
> Sent: 05 September 2016 09:58
> To: 'Vincent Moutoussamy'
> Cc: 'Arvin Schnell'; 'sles-beta at lists.suse.com'
> Subject: RE: [sles-beta] Yast Expert Partitioner - RC2
>
> Grand New Monday,
>
> Not sure many are interested but I'm still getting a n minute delay on some machines when using Partitioner and it's still there with RC2... On a non-delay macine we get "Name or service not known", on a machine that get a depaly it's "Temporary failure in name resolution"
> So maybe a SUSE good person can take a look and let me know what I should change. You do have time as I'm on the road for the next few days. I do not get an issue on my home_office, simpel 192.168.2.1 using NAT it's in the SG office and using NAT I sometimes get an issue. On a VMware Linux host very often, on a Windows 7 hosting VMware not so often, if ever. Ther are both using the same level of VMware Workstation and tools are from SUSE
> I agree it's no show stopper but it's not working as required...A SUSE network person knows why the word "temporary" comes up, can you let me know why and maybe I can fix the issue and we can all enjoy peace....
>
> This is a part of a working log...
>
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [libstorage] Storage.cc(createBackupState):8063 ret:0
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [libstorage] Storage.cc(equalBackupStates):8134 lhs:expert-partitioner rhs: verbose:true
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [libstorage] Storage.cc(equalBackupStates):8184 ret:true
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [libstorage] Storage.cc(createBackupState):8065 comp:true
> 2016-09-05 09:18:43 <3> rjw3-12-2-00(12135) [bash] ShellCommand.cc(shellcommand):78 hostname: Name or service not known <=========== We use a fallback hostname, no delay
> 2016-09-05 09:18:43 <2> rjw3-12-2-00(12135) [Ruby] modules/Hostname.rb:161 Using fallback hostname
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [Ruby] modules/Hostname.rb:171 Current FQDN: rjw3-12-2-00.eur.ad.sag
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YPath.cc(YPath):49 Given filename: libyui-qt-graph.so.7
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YSettings.cc(progDir):73 progDir: "/usr/share/YaST2"
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YPath.cc(YPath):65 Preferring subdir: /usr/share/YaST2
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YPath.cc(YPath):66 Subdir given with filename:
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YPath.cc(YPath):67 Looking for: libyui-qt-graph.so.7
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YPath.cc(lsDir):138 Looking in /usr/lib64/yui
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YPath.cc(YPath):121 Could NOT find libyui-qt-graph.so.7 by looking recursive inside /usr/lib64/yui
> 2016-09-05 09:18:43 <3> rjw3-12-2-00(12135) [ui] YUIPlugin.cc(YUIPlugin):50 Could not load UI plugin "qt-graph": libyui-qt-graph.so.7: cannot open shared object file: No such file or directory
> 2016-09-05 09:18:43 <3> rjw3-12-2-00(12135) [qt-ui] YQGraphPluginStub.cc(YQGraphPluginStub):46 Plugin qt-graph does not provide GP symbol
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YIconLoader.cc(findIcon):100 Found yast-disk.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YIconLoader.cc(findIcon):100 Found yast-disk.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YIconLoader.cc(findIcon):100 Found yast-raid.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YIconLoader.cc(findIcon):100 Found yast-lvm_config.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YIconLoader.cc(findIcon):100 Found yast-encrypted.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YIconLoader.cc(findIcon):100 Found yast-device-mapper.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YIconLoader.cc(findIcon):100 Found yast-nfs.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YIconLoader.cc(findIcon):100 Found yast-nfs.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YIconLoader.cc(findIcon):100 Found yast-nfs.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YIconLoader.cc(findIcon):100 Found yast-unused-device.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YIconLoader.cc(findIcon):100 Found yast-disk.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YIconLoader.cc(findIcon):100 Found yast-spanner.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 09:18:43 <1> rjw3-12-2-00(12135) [ui] YIconLoader.cc(findIcon):100 Found yast-messages.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 09:18:44 <3> rjw3-12-2-00(12135) [bash] ShellCommand.cc(shellcommand):78 hostname: Name or service not known
> 2016-09-05 09:18:44 <2> rjw3-12-2-00(12135) [Ruby] modules/Hostname.rb:161 Using fallback hostname
> 2016-09-05 09:18:44 <1> rjw3-12-2-00(12135) [Ruby] modules/Hostname.rb:171 Current FQDN: rjw3-12-2-00.eur.ad.sag
> 2016-09-05 09:18:44 <1> rjw3-12-2-00(12135) [Ruby] modules/Partitions.rb:150 EfiBoot ret:false
> 2016-09-05 09:18:44 <1> rjw3-12-2-00(12135) [Ruby] modules/FileSystems.rb:461 SuggestMPoints ret:["/home", "/srv", "/tmp", "/usr/local"]
> 2016-09-05 09:18:44 <1> rjw3-12-2-00(12135) [Ruby] modules/FileSystems.rb:470 SuggestTmpfsMPoints ret:["/run", "/var/run", "/tmp", "/var/lock"]
> 2016-09-05 09:18:44 <1> rjw3-12-2-00(12135) [libstorage] Storage.cc(getIgnoreFstab):3145 device:/dev/sda
>
> This is part of a non-working log
>
> 2016-09-05 08:05:13 <1> rjw8-12-2-00(13285) [libstorage] Storage.cc(createBackupState):8062 states:disk,expert-partitioner,initial
> 2016-09-05 08:05:13 <1> rjw8-12-2-00(13285) [libstorage] Storage.cc(createBackupState):8063 ret:0
> 2016-09-05 08:05:13 <1> rjw8-12-2-00(13285) [libstorage] Storage.cc(equalBackupStates):8134 lhs:expert-partitioner rhs: verbose:true
> 2016-09-05 08:05:13 <1> rjw8-12-2-00(13285) [libstorage] Storage.cc(equalBackupStates):8184 ret:true
> 2016-09-05 08:05:13 <1> rjw8-12-2-00(13285) [libstorage] Storage.cc(createBackupState):8065 comp:true
> 2016-09-05 08:08:23 <3> rjw8-12-2-00(13285) [bash] ShellCommand.cc(shellcommand):78 hostname: Temporary failure in name resolution <----------------- Temporary, note the delay of 3 mins
> 2016-09-05 08:08:23 <2> rjw8-12-2-00(13285) [Ruby] modules/Hostname.rb:161 Using fallback hostname
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [Ruby] modules/Hostname.rb:171 Current FQDN: rjw8-12-2-00.eur.ad.sag
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YPath.cc(YPath):49 Given filename: libyui-qt-graph.so.7
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YSettings.cc(progDir):73 progDir: "/usr/share/YaST2"
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YPath.cc(YPath):65 Preferring subdir: /usr/share/YaST2
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YPath.cc(YPath):66 Subdir given with filename:
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YPath.cc(YPath):67 Looking for: libyui-qt-graph.so.7
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YPath.cc(lsDir):138 Looking in /usr/lib64/yui
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YPath.cc(YPath):121 Could NOT find libyui-qt-graph.so.7 by looking recursive inside /usr/lib64/yui
> 2016-09-05 08:08:23 <3> rjw8-12-2-00(13285) [ui] YUIPlugin.cc(YUIPlugin):50 Could not load UI plugin "qt-graph": libyui-qt-graph.so.7: cannot open shared object file: No such file or directory
> 2016-09-05 08:08:23 <3> rjw8-12-2-00(13285) [qt-ui] YQGraphPluginStub.cc(YQGraphPluginStub):46 Plugin qt-graph does not provide GP symbol
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YIconLoader.cc(findIcon):100 Found yast-disk.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YIconLoader.cc(findIcon):100 Found yast-disk.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YIconLoader.cc(findIcon):100 Found yast-raid.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YIconLoader.cc(findIcon):100 Found yast-lvm_config.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YIconLoader.cc(findIcon):100 Found yast-encrypted.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YIconLoader.cc(findIcon):100 Found yast-device-mapper.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YIconLoader.cc(findIcon):100 Found yast-nfs.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YIconLoader.cc(findIcon):100 Found yast-nfs.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YIconLoader.cc(findIcon):100 Found yast-nfs.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YIconLoader.cc(findIcon):100 Found yast-unused-device.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YIconLoader.cc(findIcon):100 Found yast-disk.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YIconLoader.cc(findIcon):100 Found yast-spanner.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 08:08:23 <1> rjw8-12-2-00(13285) [ui] YIconLoader.cc(findIcon):100 Found yast-messages.png in /usr/share/YaST2/theme/current/icons/ search path
> 2016-09-05 08:11:34 <3> rjw8-12-2-00(13285) [bash] ShellCommand.cc(shellcommand):78 hostname: Temporary failure in name resolution <----------------- Temporary !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> 2016-09-05 08:11:34 <2> rjw8-12-2-00(13285) [Ruby] modules/Hostname.rb:161 Using fallback hostname
> 2016-09-05 08:11:34 <1> rjw8-12-2-00(13285) [Ruby] modules/Hostname.rb:171 Current FQDN: rjw8-12-2-00.eur.ad.sag
> 2016-09-05 08:11:34 <1> rjw8-12-2-00(13285) [Ruby] modules/Partitions.rb:150 EfiBoot ret:false
>
>
> __R
> ________________________________________
> From: Waite, Dick (External)
> Sent: 30 August 2016 09:20
> To: 'Vincent Moutoussamy'
> Cc: 'Arvin Schnell'; 'sles-beta at lists.suse.com'
> Subject: RE: [sles-beta] Yast Expert Partitioner - RC1
>
> If it helps. I was on a LEAP42.1 machine and used @Partitioner@ and got these messages, I also got the GUI output after a while. With RC2 just around the corner I'll pause on this issue, I'm sure it's fixed by then.
>
> __R
>
> rjw8-os-42-1:~ # yast2
> Run command: /sbin/yast2 disk &
> *** Error in `/sbin/dmraid': free(): invalid pointer: 0x0000000001263520 ***
> ======= Backtrace: =========
> /lib64/libc.so.6(+0x7277f)[0x7f4de73f177f]
> /lib64/libc.so.6(+0x78026)[0x7f4de73f7026]
> /lib64/libdmraid.so.1.0.0.rc16-3(+0x8338)[0x7f4de7b7d338]
> /lib64/libdmraid.so.1.0.0.rc16-3(+0x7c7c)[0x7f4de7b7cc7c]
> /lib64/libdmraid.so.1.0.0.rc16-3(discover_devices+0xb2)[0x7f4de7b7d162]
> /lib64/libdmraid.so.1.0.0.rc16-3(lib_perform+0xe0)[0x7f4de7b834f0]
> /sbin/dmraid(main+0x64)[0x401824]
> /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f4de73a0b25]
> /sbin/dmraid[0x401855]
> ======= Memory map: ========
> 00400000-00404000 r-xp 00000000 fe:00 237817 /sbin/dmraid
> 00603000-00604000 r--p 00003000 fe:00 237817 /sbin/dmraid
> 00604000-00605000 rw-p 00004000 fe:00 237817 /sbin/dmraid
> 01263000-01284000 rw-p 00000000 00:00 0 [heap]
> 7f4de64a0000-7f4de64b6000 r-xp 00000000 fe:00 262290 /lib64/libgcc_s.so.1
> 7f4de64b6000-7f4de66b5000 ---p 00016000 fe:00 262290 /lib64/libgcc_s.so.1
> 7f4de66b5000-7f4de66b6000 r--p 00015000 fe:00 262290 /lib64/libgcc_s.so.1
> 7f4de66b6000-7f4de66b7000 rw-p 00016000 fe:00 262290 /lib64/libgcc_s.so.1
> 7f4de66b7000-7f4de66be000 r-xp 00000000 fe:00 262449 /lib64/librt-2.19.so
> 7f4de66be000-7f4de68bd000 ---p 00007000 fe:00 262449 /lib64/librt-2.19.so
> 7f4de68bd000-7f4de68be000 r--p 00006000 fe:00 262449 /lib64/librt-2.19.so
> 7f4de68be000-7f4de68bf000 rw-p 00007000 fe:00 262449 /lib64/librt-2.19.so
> 7f4de68bf000-7f4de6924000 r-xp 00000000 fe:00 451145 /usr/lib64/libpcre.so.1.2.1
> 7f4de6924000-7f4de6b23000 ---p 00065000 fe:00 451145 /usr/lib64/libpcre.so.1.2.1
> 7f4de6b23000-7f4de6b24000 r--p 00064000 fe:00 451145 /usr/lib64/libpcre.so.1.2.1
> 7f4de6b24000-7f4de6b25000 rw-p 00065000 fe:00 451145 /usr/lib64/libpcre.so.1.2.1
> 7f4de6b25000-7f4de6b3d000 r-xp 00000000 fe:00 262370 /lib64/libpthread-2.19.so
> 7f4de6b3d000-7f4de6d3c000 ---p 00018000 fe:00 262370 /lib64/libpthread-2.19.so
> 7f4de6d3c000-7f4de6d3d000 r--p 00017000 fe:00 262370 /lib64/libpthread-2.19.so
> 7f4de6d3d000-7f4de6d3e000 rw-p 00018000 fe:00 262370 /lib64/libpthread-2.19.so
> 7f4de6d3e000-7f4de6d42000 rw-p 00000000 00:00 0
> 7f4de6d42000-7f4de6d53000 r-xp 00000000 fe:00 450606 /usr/lib64/libudev.so.1.4.0
> 7f4de6d53000-7f4de6f52000 ---p 00011000 fe:00 450606 /usr/lib64/libudev.so.1.4.0
> 7f4de6f52000-7f4de6f53000 r--p 00010000 fe:00 450606 /usr/lib64/libudev.so.1.4.0
> 7f4de6f53000-7f4de6f54000 rw-p 00011000 fe:00 450606 /usr/lib64/libudev.so.1.4.0
> 7f4de6f54000-7f4de6f75000 r-xp 00000000 fe:00 262495 /lib64/libselinux.so.1
> 7f4de6f75000-7f4de7174000 ---p 00021000 fe:00 262495 /lib64/libselinux.so.1
> 7f4de7174000-7f4de7175000 r--p 00020000 fe:00 262495 /lib64/libselinux.so.1
> 7f4de7175000-7f4de7176000 rw-p 00021000 fe:00 262495 /lib64/libselinux.so.1
> 7f4de7176000-7f4de7178000 rw-p 00000000 00:00 0
> 7f4de7178000-7f4de717e000 r-xp 00000000 fe:00 262375 /lib64/libdevmapper-event.so.1.02
> 7f4de717e000-7f4de737d000 ---p 00006000 fe:00 262375 /lib64/libdevmapper-event.so.1.02
> 7f4de737d000-7f4de737e000 r--p 00005000 fe:00 262375 /lib64/libdevmapper-event.so.1.02
> 7f4de737e000-7f4de737f000 rw-p 00006000 fe:00 262375 /lib64/libdevmapper-event.so.1.02
> 7f4de737f000-7f4de751d000 r-xp 00000000 fe:00 262410 /lib64/libc-2.19.so
> 7f4de751d000-7f4de771d000 ---p 0019e000 fe:00 262410 /lib64/libc-2.19.so
> 7f4de771d000-7f4de7721000 r--p 0019e000 fe:00 262410 /lib64/libc-2.19.so
> 7f4de7721000-7f4de7723000 rw-p 001a2000 fe:00 262410 /lib64/libc-2.19.so
> 7f4de7723000-7f4de7727000 rw-p 00000000 00:00 0
> 7f4de7727000-7f4de772a000 r-xp 00000000 fe:00 262416 /lib64/libdl-2.19.so
> 7f4de772a000-7f4de7929000 ---p 00003000 fe:00 262416 /lib64/libdl-2.19.so
> 7f4de7929000-7f4de792a000 r--p 00002000 fe:00 262416 /lib64/libdl-2.19.so
> 7f4de792a000-7f4de792b000 rw-p 00003000 fe:00 262416 /lib64/libdl-2.19.so
> 7f4de792b000-7f4de7971000 r-xp 00000000 fe:00 262350 /lib64/libdevmapper.so.1.02
> 7f4de7971000-7f4de7b70000 ---p 00046000 fe:00 262350 /lib64/libdevmapper.so.1.02
> 7f4de7b70000-7f4de7b71000 r--p 00045000 fe:00 262350 /lib64/libdevmapper.so.1.02
> 7f4de7b71000-7f4de7b74000 rw-p 00046000 fe:00 262350 /lib64/libdevmapper.so.1.02
> 7f4de7b74000-7f4de7b75000 rw-p 00000000 00:00 0
> 7f4de7b75000-7f4de7ba8000 r-xp 00000000 fe:00 262366 /lib64/libdmraid.so.1.0.0.rc16-3
> 7f4de7ba8000-7f4de7da8000 ---p 00033000 fe:00 262366 /lib64/libdmraid.so.1.0.0.rc16-3
> 7f4de7da8000-7f4de7da9000 r--p 00033000 fe:00 262366 /lib64/libdmraid.so.1.0.0.rc16-3
> 7f4de7da9000-7f4de7dab000 rw-p 00034000 fe:00 262366 /lib64/libdmraid.so.1.0.0.rc16-3
> 7f4de7dab000-7f4de7dcc000 r-xp 00000000 fe:00 262284 /lib64/ld-2.19.so
> 7f4de7f95000-7f4de7f9c000 rw-p 00000000 00:00 0
> 7f4de7fc9000-7f4de7fcb000 rw-p 00000000 00:00 0
> 7f4de7fcb000-7f4de7fcc000 r--p 00020000 fe:00 262284 /lib64/ld-2.19.so
> 7f4de7fcc000-7f4de7fcd000 rw-p 00021000 fe:00 262284 /lib64/ld-2.19.so
> 7f4de7fcd000-7f4de7fce000 rw-p 00000000 00:00 0
> 7ffdbd2b3000-7ffdbd2d4000 rw-p 00000000 00:00 0 [stack]
> 7ffdbd39b000-7ffdbd39d000 r--p 00000000 00:00 0 [vvar]
> 7ffdbd39d000-7ffdbd39f000 r-xp 00000000 00:00 0 [vdso]
> ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
> rjw8-os-42-1:~ #
>
> ________________________________________
> From: Waite, Dick (External)
> Sent: 29 August 2016 10:32
> To: 'Vincent Moutoussamy'
> Cc: 'Arvin Schnell'; 'sles-beta at lists.suse.com'
> Subject: RE: [sles-beta] Yast Expert Partitioner - RC1
>
> For those who want to see a working version....
>
> __R
> ________________________________________
> From: Waite, Dick (External)
> Sent: 29 August 2016 07:59
> To: 'Vincent Moutoussamy'
> Cc: 'Arvin Schnell'; 'sles-beta at lists.suse.com'
> Subject: RE: [sles-beta] Yast Expert Partitioner - RC1
>
> Grand Morning,
>
> Last look at this issue. The Y2log and var/log/messages. There are some nags in the messages about the right time...
>
> 2016-08-29T07:34:31.923195+02:00 rjw5-12-2-01 wickedd-dhcp4[1360]: eth0: Committed DHCPv4 lease with address 192.168.6.129 (lease time 1800 sec, renew in 900 sec, rebind in 1575 sec)
> 2016-08-29T07:34:31.934475+02:00 rjw5-12-2-01 wickedd[1377]: route ipv4 0.0.0.0/0 via 192.168.6.2 dev eth0#2 type unicast table main scope universe protocol dhcp covered by a ipv4:dhcp lease
> 2016-08-29T07:35:02.402894+02:00 rjw5-12-2-01 kernel: [ 954.162537] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
> 2016-08-29T07:35:02.402909+02:00 rjw5-12-2-01 kernel: [ 954.162550] EDD information not available.
>
> Regards,
>
> __R
> ________________________________________
> From: Waite, Dick (External)
> Sent: 28 August 2016 16:57
> To: 'Vincent Moutoussamy'
> Cc: 'Arvin Schnell'; 'sles-beta at lists.suse.com'
> Subject: RE: [sles-beta] Yast Expert Partitioner - RC1
>
> Grand Sunny Sunday,
>
> I will be in SAG tomorrow morning, Monday 29th, if you let me know what debug info you need I'll try and obtain it. I can not access these machines from outside of SAG. Looking at the logs inside Partitioner I don't think it is the "hostname" stuff, it's what's going on before hand . Would be grand to fix this before RCn on Sept 1st.
> I'm not in SAG Sept 30th and 31st.
>
> __R
>
> ________________________________________
> From: Waite, Dick (External)
> Sent: 23 August 2016 13:04
> To: 'Vincent Moutoussamy'
> Cc: 'Arvin Schnell'; 'sles-beta at lists.suse.com'
> Subject: RE: [sles-beta] Yast Expert Partitioner - RC1
>
> Grand Tuesday August 23, 2016,
>
> I have some VMware machines very happy running Partitioner and some get there in the end after some name issues. This is with RC1 and up-2-date version on VM-tools.
> Some machines run without issues. If I'm given some more information to give you some more information maybe we can fix this...
>
> __R
>
>
>
> -----Original Message-----
> From: Waite, Dick (External)
> Sent: Dienstag, 16. August 2016 10:11
> To: 'Vincent Moutoussamy'
> Cc: Arvin Schnell; sles-beta at lists.suse.com
> Subject: RE: [sles-beta] Yast Expert Partitioner
>
> Grand Sunny Tuesday, August 16, 2016
>
> It's still an issue with RC1 Vincent.
>
> ShellCommand.cc(shellcommand):78 hostname: Temporary failure in name resolution
>
> Should I create a SR ? One does get the GUI output in the end but with a L O N G delay of 14 mins
>
> __R
>
> -----Original Message-----
> From: Vincent Moutoussamy [mailto:vmoutoussamy at suse.com]
> Sent: Freitag, 12. August 2016 17:23
> To: Waite, Dick (External)
> Cc: Arvin Schnell; sles-beta at lists.suse.com
> Subject: Re: [sles-beta] Yast Expert Partitioner
>
> Hi,
>
> Let us know, if you find the root cause of this issue and if you can reproduce it with RC1 ; ).
>
> Have a nice week-end,
>
> Regards
> --
> Vincent Moutoussamy
> SUSE Beta Program and SDK Project Manager
>
>
>
>> On 01 Aug 2016, at 12:42, Waite, Dick (External) <Dick.Waite at softwareag.com> wrote:
>>
>> Many Thanks Arvin,
>>
>> I see it's getting stuck on "Hostname" for three mins, twice... the cmd hostnamectl status returns the correct name. Knowing what the issue is I can work on and come back to this one later. Again many thanks for the speedy response.
>>
>> 2016-08-01 11:11:20 <1> rjw5-12-2-02(4225) [libstorage]
>> Storage.cc(equalBackupStates):8134 lhs:expert-partitioner rhs:
>> verbose:true
>> 2016-08-01 11:11:20 <1> rjw5-12-2-02(4225) [libstorage]
>> Storage.cc(equalBackupStates):8184 ret:true
>> 2016-08-01 11:11:20 <1> rjw5-12-2-02(4225) [libstorage]
>> Storage.cc(createBackupState):8065 comp:true
>> 2016-08-01 11:14:31 <3> rjw5-12-2-02(4225) [bash]
>> ShellCommand.cc(shellcommand):78 hostname: Temporary failure in name
>> resolution
>> 2016-08-01 11:14:31 <2> rjw5-12-2-02(4225) [Ruby]
>> modules/Hostname.rb:161 Using fallback hostname
>> 2016-08-01 11:14:31 <1> rjw5-12-2-02(4225) [Ruby]
>> modules/Hostname.rb:171 Current FQDN: rjw5-12-2-02.eur.ad.sag
>> 2016-08-01 11:14:31 <1> rjw5-12-2-02(4225) [ui] YPath.cc(YPath):49
>> Given filename: libyui-qt-graph.so.7
>> 2016-08-01 11:14:31 <1> rjw5-12-2-02(4225) [ui] YSettings.cc(progDir):73 progDir: "/usr/share/YaST2"
>> 2016-08-01 11:14:31 <1> rjw5-12-2-02(4225) [ui] YPath.cc(YPath):65
>> Preferring subdir: /usr/share/YaST2
>> 2016-08-01 11:14:31 <1> rjw5-12-2-02(4225) [ui] YPath.cc(YPath):66 Subdir given with filename:
>> 2016-08-01 11:14:31 <1> rjw5-12-2-02(4225) [ui] YPath.cc(YPath):67
>> Looking for: libyui-qt-graph.so.7
>> 2016-08-01 11:14:31 <1> rjw5-12-2-02(4225) [ui] YPath.cc(lsDir):138
>> Looking in /usr/lib64/yui
>> 2016-08-01 11:14:31 <1> rjw5-12-2-02(4225) [ui] YPath.cc(YPath):121
>> Could NOT find libyui-qt-graph.so.7 by looking recursive inside
>> /usr/lib64/yui
>> 2016-08-01 11:14:31 <3> rjw5-12-2-02(4225) [ui]
>> YUIPlugin.cc(YUIPlugin):50 Could not load UI plugin "qt-graph":
>> libyui-qt-graph.so.7: cannot open shared object file: No such file or
>> directory
>>
>> 2016-08-01 11:14:31 <1> rjw5-12-2-02(4225) [ui]
>> YIconLoader.cc(findIcon):100 Found yast-spanner.png in
>> /usr/share/YaST2/theme/current/icons/ search path
>> 2016-08-01 11:14:31 <1> rjw5-12-2-02(4225) [ui]
>> YIconLoader.cc(findIcon):100 Found yast-messages.png in
>> /usr/share/YaST2/theme/current/icons/ search path
>> 2016-08-01 11:17:41 <3> rjw5-12-2-02(4225) [bash]
>> ShellCommand.cc(shellcommand):78 hostname: Temporary failure in name
>> resolution
>> 2016-08-01 11:17:41 <2> rjw5-12-2-02(4225) [Ruby]
>> modules/Hostname.rb:161 Using fallback hostname
>> 2016-08-01 11:17:41 <1> rjw5-12-2-02(4225) [Ruby]
>> modules/Hostname.rb:171 Current FQDN: rjw5-12-2-02.eur.ad.sag
>> 2016-08-01 11:17:41 <1> rjw5-12-2-02(4225) [Ruby]
>> modules/Partitions.rb:150 EfiBoot ret:false
>> 2016-08-01 11:17:41 <1> rjw5-12-2-02(4225) [Ruby]
>> modules/FileSystems.rb:461 SuggestMPoints ret:["/home", "/srv",
>> "/tmp", "/usr/local"]
>> 2016-08-01 11:17:41 <1> rjw5-12-2-02(4225) [Ruby]
>> modules/FileSystems.rb:470 SuggestTmpfsMPoints ret:["/run",
>> "/var/run", "/tmp", "/var/lock"]
>> 2016-08-01 11:17:41 <1> rjw5-12-2-02(4225) [libstorage]
>> Storage.cc(getIgnoreFstab):3145 device:/dev/sda
>>
>> rjw5-12-2-02:~ # hostnamectl
>> Static hostname: rjw5-12-2-02.eur.ad.sag Transient hostname:
>> rjw5-12-2-02
>> Icon name: computer-vm
>> Chassis: vm
>> Machine ID: 84fe036142867102e170848d515a752d
>> Boot ID: 292213543b8a4fce91b5a29d27e23e1d
>> Virtualization: vmware
>> Operating System: SUSE Linux Enterprise Server 12 SP2
>> CPE OS Name: cpe:/o:suse:sles:12:sp2
>> Kernel: Linux 4.4.15-53-default
>> Architecture: x86-64
>>
>>
>> rjw5-12-2-02:~ # uname -a
>> Linux rjw5-12-2-02 4.4.15-53-default #1 SMP Mon Jul 18 13:39:49 UTC
>> 2016 (0b50c2c) x86_64 x86_64 x86_64 GNU/Linux
>>
>>
>> -----Original Message-----
>> From: sles-beta-bounces at lists.suse.com
>> [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Arvin Schnell
>> Sent: Montag, 1. August 2016 11:03
>> To: sles-beta at lists.suse.com
>> Subject: Re: [sles-beta] Yast Expert Partitioner
>>
>> On Mon, Aug 01, 2016 at 08:55:27AM +0000, Waite, Dick (External) wrote:
>>> Grand Day, I'm running Beta5 and on my VMware machines the "partitioner" is taking a long time in the "initializing" phase. I did not use this with Beta3 or 4 that I remember. I have a number of machines that I "clone" with VMware from SP1 to SP2 and with SP1 the "partitioner" is faster, much faster. I have not tried this with physical machines yet. Has anybody else noticed this ?
>>> SUSE can I run this in a debug mode to try and find out where the issues are ?
>>
>> Since the expert partitioner mainly uses external commands to probe the system you can grep for "stopwatch" in /var/log/YaST/y2log. Lines look like:
>>
>> [...] stopwatch 0.263198s for "/usr/sbin/parted -s '/dev/sda' unit cyl print unit s print"
>>
>> Maybe some external command is very slow.
>>
>> Kind Regards,
>> Arvin
>>
>> --
>> Arvin Schnell, <aschnell at suse.com>
>> Senior Software Engineer, Research & Development SUSE Linux GmbH, GF:
>> Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG
>> N?rnberg) Maxfeldstra?e 5
>> 90409 N?rnberg
>> Germany
>> _______________________________________________
>> sles-beta mailing list
>> sles-beta at lists.suse.com
>> http://lists.suse.com/mailman/listinfo/sles-beta
>>
>> 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), Eric Duffaut, Dr. Wolfram Jost, Arnd
>> Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory
>> Board: Dr. Andreas Bereczky - http://www.softwareag.com
>>
>> _______________________________________________
>> sles-beta mailing list
>> sles-beta at lists.suse.com
>> http://lists.suse.com/mailman/listinfo/sles-beta
>
>
> 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), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com
>
More information about the sles-beta
mailing list