To follow up on this... (I haven't been able to make our autoyast profile work with the "update" repo enabled yet, so this is with only the suse/install repo, and hence might include bugs that are already fixed in the update repo.) On 06/12/2012 01:53 PM, 686f6c6d wrote:
3. The network comes up during boot (it works flawlessly in stage2 and /etc/sysconfig/network/ifcfg-eth0 and [...]/routes look fine), but then seems to exit for no particular reason, even when I try to start it manually (with "systemctl start network.service"). The only thing in the logs is this: ---------- 8< ---------- ifup: eth0 ifup: IP address: [...] dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... dns-resolver: You can find my version[...] ifdown: eth0 ---------->8 ---------- systemctl shows it as "Active: inactive (dead)" then, with "ExecStart=[...], status=0/SUCCESS". I am *so* clueless what happens.
The problem with eth0 going down seems to have disappeared on its own. I have no clue why.
2. Although "network", "ntp" and "sshd" are shown by chkconfig to be "on" (with ntp and sshd being explicitly specified as "3 5" in <runlevel>), they are not started at boot ("systemctl list-units -t service --all" shows them all as "loaded inactive"). Do I have to change anything else to make yast2-runlevel work with systemd?
With <final_reboot>, both ntpd and sshd come up fine, so it seems to be a problem at first boot only. Thanks for the tip, darix! (It does not seem to be #724777, #725503, #732930, #735943, #736059, #765039; it might be #727771 or #747931; if not, I'll post a new one.) On Tue, Jun 12, 2012 at 8:39 PM, Darin Perusich <Darin.Perusich@ctg.com> wrote:
I've seen this a lot, but not all the time, when upgrading systems from 11.3 to 12.1, via "zypper dup". From what I can gather the problem seems to be due to "netconfig update" exiting with a non-zero status due to resolv.conf not matching the NETCONFIG_DNS_POLICY. I've been mostly successful in working around this by setting NETCONFIG_DNS_POLICY="" in /etc/sysconfig/network/config. I say mostly successfully because the "inactive (dead) networking has happened even after setting NETCONFIG_DNS_POLICY="".
Because our autoyast for 12.1 doesn't work yet, we have actually done a lot of DUPs, but according to our folks in the trenches we never had the problem in that scenario.
This seems to happen more on VM's than on physical servers for me. When dup'ing to 12.1 the VM's don't always like to reboot gracefully so I was doing "reboot -f" after which networking may or may not be "inactive (dead)". I found that when it was dead if I stopped networking and rebooted the VM, networking would function properly subsequently. Also, after dup to 12.1 if I don't "reboot -f" and simply reboot, and once the system hangs up during shutdown if I reset power to the VM networking comes up fine.
We don't have this problem, neither after DUPing nor with fresh 12.1 installs.
Since there's really no verbose|debug logging|output in systemd/systemctl it's REALLY difficult to get to the root of the problem. If anyone has any ideas I'm all ears? I haven't gotten to strace'ing the network.service yet but I have a feeling it may be only way to get an really info about what going on.
A few of all the above bugreports recommend to add "systemd.log_level=debug systemd.log_target=kmsg" to the kernel commandline, but then systemd logs so much that rsyslogd with the default install config can't keep up and drops about 800 lines during boot. It is still helpful though. (Haven't found a bugreport about that yet, will file one in the next weeks if none exists.) -- 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