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>
sshd
3 5
</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