- openSUSE Autoinstall

[opensuse-autoinstall] Configure indirect rendering for X
by m.frerichs 08 Nov '16

08 Nov '16

Hello, I find out a problem with visualization under Leap 42.1 and I 'm looking for a permanent configuration of indirect GLX for example in /etc/sysconfig/displaymanager. Under Leap 42.1 the X-Server behaves as if AllowIndirectGLXProtocol = FALSE and because of this OpenGL-Applications don't function per SSh and X11-Forwarding I did some of the proposed configuration i found in the web. 1) Change /etc/X11/xdm/Xservers to :0 local /usr/bin/X -nolisten tcp +iglx -br vt7 But after "rcxdm restart" this option +iglx is not shown in the Xorg-command with ps 2) Change of etc/X11/xorg.conf Section "ServerFlags" Option "AllowIndirectGLX" "on" or "True" EndSection despite of this glxgears shows direct rendering : Yes ------- Our constallation of several workstations is : Leap 42.1 Kernel : 4.1.34-33-default x11-video-nvidiaG04-367.57-27.1 xorg-x11-server-7.6_1.17.2-24.2 DISPLAYMANAGER="kdm" DEFAULT_WM="kde" If you call a visualization-program such as blender or even glxgears locally all is fine , but if you do an ssh-login on the other workstation and even call glxgears , an error occurred. X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 30 Current serial number in output stream: 31 It seems to be a problem with direct rendering . Can anybody help me here? Thanks in advance Kindly regards +----------------------------------------------------------------------+ | Marianne Frerichs | | Juelich Supercomputing Centre (JSC) | | Institute for Advanced Simulation (IAS) | | Forschungszentrum Juelich GmbH | | Email: M.Frerichs(a)fz-juelich.de | +----------------------------------------------------------------------+ ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

1 0

AW: [opensuse-autoinstall] Autoyast init-script files fail to download
by Frank.Hollmann＠lfst.bayern.de 14 Jul '16

14 Jul '16

Hi, location worked form e in SLES12-GA. Bug or Feature was introduced in SLES12-SP1. Workaround: embed the desired Script in xml (CDATA). Regards Frank Hollmann -----Ursprüngliche Nachricht----- Von: Aleksandar Vesic [mailto:vesic@linux.com] Gesendet: Dienstag, 12. Juli 2016 16:27 An: opensuse-autoinstall(a)opensuse.org Betreff: [opensuse-autoinstall] Autoyast init-script files fail to download Hello guys, I tried to install SLES12SP1 but my init-script get ignored and no file gets created at /var/adm/autoinstall/scripts. Same autoyast profile worked for SLES 11 SP4. My post-scripts works fine. An autoyast control file for SLES 12 SP1 with the following init-scripts section fails: <init-scripts config:type="list"> <script> <filename>init12.sh</filename> <interpreter>shell</interpreter> <location>nfs://IP_ADDR/var/lib/autoinstall/repository/scripts /init12.sh</location> </script> Same with: <location><![CDATA[ nfs://IP_ADDR/var/lib/autoinstall/repository/scripts/init12.sh ]]></location> After installation, this script has been executed only if I use following section: <source><![CDATA[ #!/bin/sh #The entire content of the init12.sh ]]> </source> </script> </init-scripts> </scripts> I looked into /usr/share/YaST2/clients/autoinst_scripts2_finish.rb and found this: # Creating init scripts for the autoyast-initscripts.service AutoinstScripts.Write("init-scripts", false) # systemd requires the init script to be activated in 1st stage Can someone help me? Did I miss something? Best Regards Alex ---------------------- vesic(a)linux.com -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

4 3

[opensuse-autoinstall] Autoyast init-script files fail to download
by Aleksandar Vesic 12 Jul '16

12 Jul '16

Hello guys, I tried to install SLES12SP1 but my init-script get ignored and no file gets created at /var/adm/autoinstall/scripts. Same autoyast profile worked for SLES 11 SP4. My post-scripts works fine. An autoyast control file for SLES 12 SP1 with the following init-scripts section fails: <init-scripts config:type="list"> <script> <filename>init12.sh</filename> <interpreter>shell</interpreter> <location>nfs://IP_ADDR/var/lib/autoinstall/repository/scripts /init12.sh</location> </script> Same with: <location><![CDATA[ nfs://IP_ADDR/var/lib/autoinstall/repository/scripts/init12.sh ]]></location> After installation, this script has been executed only if I use following section: <source><![CDATA[ #!/bin/sh #The entire content of the init12.sh ]]> </source> </script> </init-scripts> </scripts> I looked into /usr/share/YaST2/clients/autoinst_scripts2_finish.rb and found this: # Creating init scripts for the autoyast-initscripts.service AutoinstScripts.Write("init-scripts", false) # systemd requires the init script to be activated in 1st stage Can someone help me? Did I miss something? Best Regards Alex ---------------------- vesic(a)linux.com -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

1 0

[opensuse-autoinstall] Re-Installation of a System with md-raid
by Daniel Spannbauer 11 Jul '16

11 Jul '16

Hello, we have successfully installed a opensuse 12.3 with autoyast. The System contains 3 md-raid-sets, all are a raid1. When I try to install the same system again, I get an error message Failure occurred during the following action: Setting disk label of /dev/sda to MSDOS System error code was: -1013 Continue despite the error? Here the complete messages from y2log: -------------------------------------------------------- 2016-07-11 13:00:42 <1> dh136(3694) [libstorage] SystemCmd.cc(execute):90 SystemCmd Executing:"/sbin/mdadm --zero-superblock --force '/dev/sda'" 2016-07-11 13:00:42 <1> dh136(3694) [libstorage] SystemCmd.cc(addLine):592 Adding Line 1 "mdadm: Unrecognised md component device - /dev/sda" 2016-07-11 13:00:42 <1> dh136(3694) [libstorage] SystemCmd.cc(getUntilEOF):558 pid:4675 added lines:1 stderr:true 2016-07-11 13:00:42 <1> dh136(3694) [libstorage] SystemCmd.cc(doExecute):279 stopwatch 0.008789s for "/sbin/mdadm --zero-superblock --force '/dev/sda'" 2016-07-11 13:00:42 <1> dh136(3694) [libstorage] SystemCmd.cc(doExecute):299 system() Returns:0 2016-07-11 13:00:42 <3> dh136(3694) [libstorage] Disk.cc(checkSystemError):417 cmd:/sbin/mdadm --zero-superblock --force '/dev/sda' 2016-07-11 13:00:42 <3> dh136(3694) [libstorage] Disk.cc(checkSystemError):418 err:mdadm: Unrecognised md component device - /dev/sda 2016-07-11 13:00:42 <1> dh136(3694) [libstorage] SystemCmd.cc(execute):90 SystemCmd Executing:"/usr/sbin/parted -s '/dev/sda' mklabel msdos" 2016-07-11 13:00:44 <1> dh136(3694) [libstorage] SystemCmd.cc(addLine):592 Adding Line 1 "Error: Partition(s) 2 on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes." 2016-07-11 13:00:44 <1> dh136(3694) [libstorage] SystemCmd.cc(getUntilEOF):558 pid:4676 added lines:1 stderr:false 2016-07-11 13:00:44 <1> dh136(3694) [libstorage] SystemCmd.cc(doExecute):279 stopwatch 2.151067s for "/usr/sbin/parted -s '/dev/sda' mklabel msdos" 2016-07-11 13:00:44 <1> dh136(3694) [libstorage] SystemCmd.cc(doExecute):299 system() Returns:1 2016-07-11 13:00:44 <1> dh136(3694) [libstorage] SystemCmd.cc(logOutput):625 stdout:Error: Partition(s) 2 on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. 2016-07-11 13:00:44 <1> dh136(3694) [libstorage] Disk.cc(checkSystemError):423 cmd:/usr/sbin/parted -s '/dev/sda' mklabel msdos 2016-07-11 13:00:44 <1> dh136(3694) [libstorage] Disk.cc(checkSystemError):424 out:Error: Partition(s) 2 on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. 2016-07-11 13:00:44 <3> dh136(3694) [libstorage] Disk.cc(checkSystemError):445 retcode:1 2016-07-11 13:00:44 <2> dh136(3694) [libstorage] Container.cc(setExtError):366 called with empty stderr cmd:/usr/sbin/parted -s '/dev/sda' mklabel msdos 2016-07-11 13:00:44 <1> dh136(3694) [libstorage] Disk.cc(doCreateLabel):1654 ret:-1013 2016-07-11 13:00:44 <1> dh136(3694) [libstorage] Disk.cc(commitChanges):1574 ret:-1013 2016-07-11 13:00:44 <1> dh136(3694) [libstorage] Storage.cc(commitPair):5236 err at stage:0 type:DISK cont:true dest:false name:sda 2016-07-11 13:00:44 <1> dh136(3694) [libstorage] Storage.cc(commitErrorPopupCb):6626 COMMIT ERROR POPUP error:-1013 last_action:Setting disk label of /dev/sda to MSDOS extended_message: 2016-07-11 13:00:44 <1> dh136(3694) [YCP] StorageClients.ycp:111 CommitErrorPopup error:-1013 last_action:Setting disk label of /dev/sda to MSDOS extended_message: 2016-07-11 13:00:44 <1> dh136(3694) [YCP] Report.ycp:370 Failure occurred during the following action: Setting disk label of /dev/sda to MSDOS System error code was: -1013 Continue despite the error? -------------------------------------------------------------------- Any hints? Regards Daniel -- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

1 0

[opensuse-autoinstall] Redundant bootloader with mdraid
by Daniel Spannbauer 30 Jun '16

30 Jun '16

Hello, I try to install a machine with a mdraid configuration (raid 1). Raid is working fine, but how do I get a bootloader on both harddisks? At the moment the bootloader is only installed on sda. Regards Daniel -- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 1

[opensuse-autoinstall] Installation repository
by Dr.Peer-Joachim Koch 28 Jun '16

28 Jun '16

Hi, we are using autoinstall for our HPC cluster. However we have to use old releases, because we are using a global file system on the cluster. So we could now migrate to SLES11SP3 and I'm wondering, if there is a way to setup a repository containing all updates for the system (current status), but with the original kernel from the DVD. Is there an easy way to create this kind of repository ? Or just add the update repository while we install the nodes (but what about the kernel ??) .... Any help will be welcome! -- Bye, Peer ________________________________________________________ Max-Planck-Institut für Biogeochemie Dr. Peer-Joachim Koch Hans-Knöll Str.10 Telefon: ++49 3641 57-6705 D-07745 Jena Telefax: ++49 3641 57-7705

4 8

[opensuse-autoinstall] Create own installation media
by Daniel Spannbauer 11 May '16

11 May '16

Hello, I try to create my own installation media with Leap 42.1, but I'm struggeling at signing the content file. How can I get my gpg signature into the initrd of the DVD Image? With 12.3 I exported my key, added it to the installkey.pgp at the root of the initrd, signed the content and everything was fine. But with leap the is no installkey.gpg. Can anybody help me here? Or can anybody tell me who is the maintainer of the Install-System? Regards Daniel -- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 3

[opensuse-autoinstall] AutoYaST2 ignores /etc/default/grub since SLES-12-SP1
by Oliver Schweikert 31 Mar '16

31 Mar '16

Hello all, from a chroot-script I modify the parameter GRUB_CMDLINE_LINUX in the file /etc/default/grub. This worked for SLES-12 and the kernel got the expected append line. With SP1 this does not work anymore (regardless of the value of the "chrooted" parameter). In /var/YaST2/y2log I see, that the script gets called, and in the corresponding log file, I see the success. A few lines later in y2log, the variable GRUB_CMDLINE_LINUX is reported as empty again. Has anybody an idea? Best regards, Oliver -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 2

[opensuse-autoinstall] <files> section in 42.1
by Robert Klein 29 Feb '16

29 Feb '16

Hi, when using the <files> section in an autoyast profile for 42.1, the files don't get deployed. I try to deploy e.g. /etc/ldap.conf, /etc/opelndap/ldap.conf /etc/ntp.conf, /etc/environment. Now, in /var/adm/autoinstall/cache/installedSystem.xml only /etc/environment shows up (though the original autoyast file contains all; I verified this --- the installedSystem.xml has a <service>puppet</service> line I added only _after_ I added the files section. Thanks for git). Additionally, this one file does _NOT_ get deployed. Excerpt from installedSystem.xml: <files> <file> <file_contents><![CDATA[# # This file is parsed by pam_env module # # Syntax: simple "KEY=VAL" pairs on seperate lines # CUPS_SERVER=thps.mpip-mainz.mpg.de ]]></file_contents> <file_owner>root.root</file_owner> <file_path>/etc/environment</file_path> <file_permissions>644</file_permissions> </file> </files> The original autoyast looks like this (the xi:includes replaced by <![CDATA[ ... ]]> sections <files> <file> <file_path>/etc/ntp.conf</file_path> <file_contents> <xi:include file="files/ntp.conf" /> </file_contents> <file_owner>root.ntp</file_owner> <file_permissions>640</file_permissions> </file> <file> <file_path>/etc/ldap.conf</file_path> <file_contents> <xi:include file="files/ldap.conf" /> </file_contents> <file_owner>root.root</file_owner> <file_permissions>644</file_permissions> </file> <file> <file_path>/etc/openldap/ldap.conf</file_path> <file_contents> <xi:include file="files/openldap-ldap.conf" /> </file_contents> <file_owner>root.root</file_owner> <file_permissions>644</file_permissions> </file> <file> <file_path>/etc/environment</file_path> <file_contents> <xi:include file="files/environment" /> </file_contents> <file_owner>root.root</file_owner> <file_permissions>644</file_permissions> </file> </files> Any suggestions? Thank you very much Robert Klein -- Robert Klein UNIX Operations Max Planck-Institut für Polymerforschung Anschrift: Ackermannweg 10, 55128 Mainz -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

3 2

[opensuse-autoinstall] where are the pattern files?
by Werner Hack 16 Feb '16

16 Feb '16

Hi all, I want to install openSUSE Leap 42.1 via pattern list. But I can not find any pattern files in the installation repository (./suse/setup/descr/*.pat.gz) In openSUSE 13.1 pattern files exist but since openSUSE 13.2 they seem to be gone. In yast2 I can see patterns but what are their correct name to use them in a autoyast profile? Where are all the patterns defined now? Thanks in advance Regards Werner

4 3