[opensuse-autoinstall] openSUSE 12.2 and autoyast-configured services
Hello list, I'm having difficulties enabling systemd services in openSUSE 12.2 from the autoyast file. Our current way doesn't work anymore: <runlevel> <default>3</default> <services config:type="list"> <service> <service_name>rpcbind</service_name> <service_status>enable</service_status> </service> </services> </runlevel> At least not for rpcbind. My workaround currently is to use a post-script to do a "systemctl enable rpcbind.service". -- Kind regards. Conny Seidel ################################################################## # Email : conny.seidel@amd.com GnuPG-Key : 0xA6AB055D # # Fingerprint: 17C4 5DB2 7C4C C1C7 1452 8148 F139 7C09 A6AB 055D # ################################################################## # Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach # # General Managers: Alberto Bozzo # # Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen # # HRB Nr. 43632 # ################################################################## -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
On Tue, Jun 26, 2012 at 2:21 PM, Conny Seidel <conny.seidel@amd.com> wrote:
I'm having difficulties enabling systemd services in openSUSE 12.2 from the autoyast file. [...] At least not for rpcbind. My workaround currently is to use a post-script to do a "systemctl enable rpcbind.service".
"Have you tried turning it off and on again?" Seriously, as described in the other thread, I'm seeing a similar problem on 12.*1* where systemd/systemctl does neither display correctly nor bring up the <runlevel>-defined services during first boot. When I use <general><mode><final_reboot config:type="boolean">true</final_reboot></mode></general>, the services are correctly configured and running after the reboot. -- Kind regards 686f6c6d / Christopher 'm4z' Holm -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
On Tue, 26 Jun 2012 15:35:44 +0200 686f6c6d <686f6c6d@googlemail.com> wrote:
On Tue, Jun 26, 2012 at 2:21 PM, Conny Seidel <conny.seidel@amd.com> wrote:
I'm having difficulties enabling systemd services in openSUSE 12.2 from the autoyast file. [...] At least not for rpcbind. My workaround currently is to use a post-script to do a "systemctl enable rpcbind.service".
"Have you tried turning it off and on again?"
Yes, but rpcbind isn't working even after an reboot so our systemd-service file to start testing, which relies on $remotefs, doesn't start and the machine just boots and does nothing.
Seriously, as described in the other thread, I'm seeing a similar problem on 12.*1* where systemd/systemctl does neither display correctly nor bring up the <runlevel>-defined services during first boot. When I use <general><mode> <final_reboot><config:type="boolean">true</final_reboot> </mode></general>, the services are correctly configured and running after the reboot.
I knew that. ;) But unfortunately it doesn't work. rpcbind seems to get enabled, but without enabling rpcbind.socket, which pretty much renders nfs-mounts useless without the "-o nolock" option. Our way with systemctl shows this in the logfile, we generate for each script we run within the install process: ln -s '/lib/systemd/system/rpcbind.service' \ '/etc/systemd/system/multi-user.target.wants/rpcbind.service' ln -s '/lib/systemd/system/rpcbind.socket' \ '/etc/systemd/system/sockets.target.wants/rpcbind.socket' -- Kind regards. Conny Seidel ################################################################## # Email : conny.seidel@amd.com GnuPG-Key : 0xA6AB055D # # Fingerprint: 17C4 5DB2 7C4C C1C7 1452 8148 F139 7C09 A6AB 055D # ################################################################## # Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach # # General Managers: Alberto Bozzo # # Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen # # HRB Nr. 43632 # ##################################################################
On 27.06.2012 13:02, Conny Seidel wrote:
rpcbind seems to get enabled, but without enabling rpcbind.socket, which pretty much renders nfs-mounts useless without the "-o nolock" option.
Our way with systemctl shows this in the logfile, we generate for each script we run within the install process: ln -s '/lib/systemd/system/rpcbind.service' \ '/etc/systemd/system/multi-user.target.wants/rpcbind.service' ln -s '/lib/systemd/system/rpcbind.socket' \ '/etc/systemd/system/sockets.target.wants/rpcbind.socket'
but that sounds like a general problem with rpcbind on 12.2 You should open a bugreport for that. At least that's independent from the bug I opened today, where services are only started after a reboot of the installed system. -- ciao, Uwe Gansert SUSE LINUX Products GmbH, HRB 16746 (AG Nürnberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer Home: http://www.suse.de/~ug - Blog: http://suse.gansert.net -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
On 07/04/2012 01:30 PM, Uwe Gansert wrote:
On 27.06.2012 13:02, Conny Seidel wrote:
rpcbind seems to get enabled, but without enabling rpcbind.socket, which pretty much renders nfs-mounts useless without the "-o nolock" option.
Our way with systemctl shows this in the logfile, we generate for each script we run within the install process: ln -s '/lib/systemd/system/rpcbind.service' \ '/etc/systemd/system/multi-user.target.wants/rpcbind.service' ln -s '/lib/systemd/system/rpcbind.socket' \ '/etc/systemd/system/sockets.target.wants/rpcbind.socket'
but that sounds like a general problem with rpcbind on 12.2 You should open a bugreport for that. At least that's independent from the bug I opened today, where services are only started after a reboot of the installed system.
Just to add my 2¢, I configure NIS client and NFS server with autoyast in their respective sections (not in <services>). Is my setup rpcbind starts (after reboot, see Bug 769924) and is enabled. I guess this issue only happens when rpcbind is enabled manually and not by dependency. Best regards Robert -- Robert Klein - Max Planck-Institut für Polymerforschung Ackermannweg 10 55128 Mainz -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
Hello, I am coming back to this thread, because I have a problem with services **not** starting, although configured in AutoYast. I my profile I have: ------------------ <mode> ... <forceboot config:type="boolean">false</forceboot> </mode> <runlevel> <default>5</default> <services config:type="list"> <service> <service_name>sshd</service_name> <service_start>3 5</service_start> </service> ... </services> </runlevel> ------------------ I y2log I see: ------------------ 2012-11-12 16:08:48 <1> lab05(4646) [YCP] RunlevelEd.ycp:545 Setting sshd: ["3", "5"] 2012-11-12 16:08:48 <3> lab05(4646) [bash] ShellCommand.cc(shellcommand):78 insserv: Note: sysvinit service sshd is shadowed by systemd sshd.service, 2012-11-12 16:08:48 <3> lab05(4646) [bash] ShellCommand.cc(shellcommand):78 Forwarding request to '/bin/systemctl --no-reload --root / disable sshd.service'. 2012-11-12 16:08:48 <3> lab05(4646) [bash] ShellCommand.cc(shellcommand):78 insserv: Forward service request to systemctl returned error status : 256 2012-11-12 16:08:48 <3> lab05(4646) [bash] ShellCommand.cc(shellcommand):78 2012-11-12 16:08:48 <3> lab05(4646) [bash] ShellCommand.cc(shellcommand):78 Note: This output shows SysV services only and does not include native 2012-11-12 16:08:48 <3> lab05(4646) [bash] ShellCommand.cc(shellcommand):78 systemd services. SysV configuration data might be overridden by native 2012-11-12 16:08:48 <3> lab05(4646) [bash] ShellCommand.cc(shellcommand):78 systemd configuration. 2012-11-12 16:08:48 <3> lab05(4646) [bash] ShellCommand.cc(shellcommand):78 2012-11-12 16:08:48 <1> lab05(4646) [YCP] Service.ycp:256 Calling /sbin/chkconfig -s -f sshd 35 2012-11-12 16:08:48 <3> lab05(4646) [bash] ShellCommand.cc(shellcommand):78 insserv: Note: sysvinit service sshd is shadowed by systemd sshd.service, 2012-11-12 16:08:48 <3> lab05(4646) [bash] ShellCommand.cc(shellcommand):78 Forwarding request to '/bin/systemctl --no-reload --root / enable sshd.service'. 2012-11-12 16:08:48 <3> lab05(4646) [bash] ShellCommand.cc(shellcommand):78 ln -s '///lib/systemd/system/sshd.service' '///etc/systemd/system/multi-user.target.wants/sshd.service' 2012-11-12 16:08:48 <3> lab05(4646) [bash] ShellCommand.cc(shellcommand):78 insserv: Forward service request to systemctl returned error status : 256 ------------------ After the installation is finished, sshd (and all other non-default services from above) is *not* running. But 'chkconfig sshd' shows that it is enabled. Looks like AutoYast fails to start configured service when KEXECing into the installed system?!? Is this the same problem as discussed in this thread previously? It looks like the conclusion was a rpcbind specific problem... If not, does anyone experience the same problem and can confirm it? Best regards, J Brauchle
participants (5)
-
686f6c6d -
Conny Seidel -
Joschi Brauchle -
Robert Klein -
Uwe Gansert