[Bug 860142] New: ifup doesn't work when systemd has closed /run/systemd/private - openSUSE Bugs - openSUSE Mailing Lists

newer
[Bug 864550] New: osc: provide...

[Bug 860142] New: ifup doesn't work when systemd has closed /run/systemd/private

older
[Bug 861952] New: Installation...

bugzilla_noreply＠novell.com

23 Jan 2014 23 Jan '14

17:14

https://bugzilla.novell.com/show_bug.cgi?id=860142 https://bugzilla.novell.com/show_bug.cgi?id=860142#c0 Summary: ifup doesn't work when systemd has closed /run/systemd/private Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: Ralf.Friedl@online.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 When systemd closes /run/systemd/private (problem with systemd, see also Bug 860139), it is no longer possible to use ifup. The reason is that function get_network_service_id tries to connect to /run/systemd/private, and if it fails, it gives an empty result. I changed line 245 to accept an empty string in this case, but it would be better to fix the underlying problem. Unfortunately I access this computer only via network, so it's bad if it no longer executes ifup. 244 network_service_id=`get_network_service_id` 245 if [ -n "$network_service_id" -a "x$network_service_id" != "xnetwork.service" ] ; then Reproducible: Always Steps to Reproduce: 1. Systemd closes /run/systemd/private (no idea why) 2. run ifup eth0 Actual Results: Message "Network is managed by '' -> skipping" Expected Results: Network interface is configured -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

Show replies by date

bugzilla_noreply＠novell.com

10 Feb 10 Feb

12:33

New subject: [Bug 860142] ifup doesn't work when systemd has closed /run/systemd/private

https://bugzilla.novell.com/show_bug.cgi?id=860142 https://bugzilla.novell.com/show_bug.cgi?id=860142#c Bernhard Wiedemann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann@suse.com, | |mt@suse.com AssignedTo|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

13:09

New subject: [Bug 860142] ifup doesn't work when systemd has closed /run/systemd/private

https://bugzilla.novell.com/show_bug.cgi?id=860142 https://bugzilla.novell.com/show_bug.cgi?id=860142#c1 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |werner@suse.com InfoProvider| |Ralf.Friedl@online.de --- Comment #1 from Dr. Werner Fink 2014-02-10 13:09:47 UTC --- What are you doing? Why does systemd closes its socket on your system? I've never ever seen that, not on a 12.3 nor 13.1 nor any other system around here. As long as I'm not able to reproduce I'm not able to fix this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

14:54

New subject: [Bug 860142] ifup doesn't work when systemd has closed /run/systemd/private

https://bugzilla.novell.com/show_bug.cgi?id=860142 https://bugzilla.novell.com/show_bug.cgi?id=860142#c2 Ralf Friedl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|Ralf.Friedl@online.de | --- Comment #2 from Ralf Friedl 2014-02-10 14:54:10 UTC --- As far as I see I don't do anything special. I have a system that is usually up for months, unless there is an update that requires a reboot. Sometimes systemd has a problem in that it closes it's pipes and doesn't respond to signals. This is that same as in #860139. I discovered #860139 when in such a situation I wanted to restart systemd with SIGTERM, but it didn't react. According to the man page, SIGTERM is mostly equivalent to "systemctl daemon-reexec", but that can't work if the pipes are closed. Also I still have the problem from #798287. To work around that I have a script that executes ping and if it doesn't receive an answer, it will unbind/bind the driver. This will cause the interface to disappear and reappear, and ifup will be called automatically for the interface. This is not elegant, but after a short disruption the system is again available. Now if also systemd closes /run/systemd/private then ifup will not configure the interface when it comes up, and I can't access the system via network. So the preferred solution would be to fix the issue with systemd, and the issue with the network card/driver, but the workaround lets me at least access the system, although I probably can't do a clean reboot as long as systemd doesn't respond. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

15:02

New subject: [Bug 860142] ifup doesn't work when systemd has closed /run/systemd/private

https://bugzilla.novell.com/show_bug.cgi?id=860142 https://bugzilla.novell.com/show_bug.cgi?id=860142#c3 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC|werner@suse.com |bpoirier@suse.com --- Comment #3 from Dr. Werner Fink 2014-02-10 15:02:03 UTC --- Hmmm ... this smells like a hardware (driver) problem with r8169 or related to r8169 and the network. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

15:12

New subject: [Bug 860142] ifup doesn't work when systemd has closed /run/systemd/private

https://bugzilla.novell.com/show_bug.cgi?id=860142 https://bugzilla.novell.com/show_bug.cgi?id=860142#c4 --- Comment #4 from Ralf Friedl 2014-02-10 15:12:52 UTC --- I have the same network problem (and the related scripts) on two different systems with slightly different ASUS boards (M5A97-LE-R20 and M5A97-EVO-R20) and 32GB ECC RAM. Except for the occasional network problems, which got better with newer kernels, and the rare problems with systemd, they run for months without problems. So I suspect the network problem more likely has something to to with the interaction between driver and hardware, and I consider it unlikely that a hardware problem would only affect systemd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

15:24

New subject: [Bug 860142] ifup doesn't work when systemd has closed /run/systemd/private

https://bugzilla.novell.com/show_bug.cgi?id=860142 https://bugzilla.novell.com/show_bug.cgi?id=860142#c5 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |werner@suse.com --- Comment #5 from Dr. Werner Fink 2014-02-10 15:24:34 UTC --- If systemd looses its sockets due such a problem it will not work anymore -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

13 Feb 13 Feb

13:12

New subject: [Bug 860142] ifup doesn't work when systemd has closed /run/systemd/private

https://bugzilla.novell.com/show_bug.cgi?id=860142 https://bugzilla.novell.com/show_bug.cgi?id=860142#c6 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |Ralf.Friedl@online.de --- Comment #6 from Dr. Werner Fink 2014-02-13 13:12:04 UTC --- IMHO thos could be happen if systemd crashes. Has systemd crashed on your system? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

16:48

New subject: [Bug 860142] ifup doesn't work when systemd has closed /run/systemd/private

https://bugzilla.novell.com/show_bug.cgi?id=860142 https://bugzilla.novell.com/show_bug.cgi?id=860142#c7 Ralf Friedl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|Ralf.Friedl@online.de | --- Comment #7 from Ralf Friedl 2014-02-13 16:48:58 UTC --- That depends on the meaning of "has crashed". Obviously something is wrong with systemd in this state, so you could call it "crashed". But it didn't terminate, because as PID 1 it would have halted the system immediately, so you could also call it "not crashed". Or should I look for something specific in the logs? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

14 Feb 14 Feb

07:46

New subject: [Bug 860142] ifup doesn't work when systemd has closed /run/systemd/private

https://bugzilla.novell.com/show_bug.cgi?id=860142 https://bugzilla.novell.com/show_bug.cgi?id=860142#c8 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |Ralf.Friedl@online.de --- Comment #8 from Dr. Werner Fink 2014-02-14 07:46:47 UTC --- (In reply to comment #7) systemd can segfault without dieing .. search the logs with journalctl or the log file if you're using a system logger like rsyslog. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

10:10

New subject: [Bug 860142] ifup doesn't work when systemd has closed /run/systemd/private

https://bugzilla.novell.com/show_bug.cgi?id=860142 https://bugzilla.novell.com/show_bug.cgi?id=860142#c9 Ralf Friedl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|Ralf.Friedl@online.de | --- Comment #9 from Ralf Friedl 2014-02-14 10:10:29 UTC --- I found these lines in the log: 2014-01-22T22:15:45.322706 dbus-daemon[666]: dbus[666]: [system] Reloaded configuration 2014-01-22T22:15:45.323581 dbus[666]: [system] Reloaded configuration 2014-01-22T22:15:45.326300 dbus-daemon[666]: dbus[666]: [system] Reloaded configuration 2014-01-22T22:15:45.327010 dbus[666]: [system] Reloaded configuration 2014-01-22T22:15:46.455168 systemd[1]: Reloading. 2014-01-22T22:15:46.498749 systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited with exit status 1. 2014-01-22T22:15:46.544437 systemd[1]: Failed deactivating swap /dev/disk/by-partlabel/swap. 2014-01-22T22:15:46.544668 systemd[1]: Failed deactivating swap /dev/disk/by-id/ata-ST3000VX000-9YW166_Z1F1WWPL-part1. 2014-01-22T22:15:46.544868 systemd[1]: Failed deactivating swap /dev/disk/by-id/scsi-1ATA_ST3000VX000-9YW166_Z1F1WWPL-part1. 2014-01-22T22:15:46.545058 systemd[1]: Failed deactivating swap /dev/disk/by-id/scsi-SATA_ST3000VX000-9YW1_Z1F1WWPL-part1. 2014-01-22T22:15:46.545306 systemd[1]: Failed deactivating swap /dev/disk/by-id/wwn-0x5000c5004f402cbf-part1. 2014-01-22T22:15:46.545543 systemd[1]: Failed deactivating swap /dev/disk/by-partuuid/6f76fff6-d751-4ce6-8253-c9de7a5dec78. 2014-01-22T22:15:46.545739 systemd[1]: Failed deactivating swap /dev/disk/by-path/pci-0000:00:11.0-scsi-2:0:0:0-part1. 2014-01-22T22:15:46.545929 systemd[1]: Failed deactivating swap /dev/disk/by-uuid/36b49c00-edad-41ab-819a-693c0c83a770. 2014-01-22T22:15:46.546132 systemd[1]: Failed to reload: Address already in use 2014-01-22T22:15:46.565992 systemd[1]: Reloading. 2014-01-22T22:15:46.579785 systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited with exit status 1. 2014-01-22T22:15:46.618919 systemd[1]: Expecting device dev-sdb1.device... 2014-01-22T22:15:46.619318 systemd[1]: Stopping CUPS Printing Service... 2014-01-22T22:15:46.620196 systemd[1]: Starting CUPS Printing Service... 2014-01-22T22:15:46.638839 systemd[1]: Started CUPS Printing Service. I don't know why dbus reloads twice in a few milliseconds, maybe from installing updates. The systemd reloading is more than a minute later, so I don't know whether the dbus messages are related. The CUPS restart also suggests that this is part of an update, because CUPS is not really used on this machine, it is just part of the default install. So I would have no reason to restart it manually. It also shows that systemd could still be reached to do the restart. The message "Failed to reload: Address already in use" doesn't say which socket can't be recreated, but it might be the one needed here. Before that I found some "Write-error on swap-device" messages, but no "Read-error on swap-device", so the failure might be related to that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

19 Feb 19 Feb

09:26

New subject: [Bug 860142] ifup doesn't work when systemd has closed /run/systemd/private

https://bugzilla.novell.com/show_bug.cgi?id=860142 https://bugzilla.novell.com/show_bug.cgi?id=860142#c10 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC|werner@suse.com | InfoProvider| |Ralf.Friedl@online.de --- Comment #10 from Dr. Werner Fink 2014-02-19 09:26:22 UTC --- Attach your /etc/fstab please .. beside this you may check your disk(s) including cables and/or the power consumption of the system in comparision to the power supply. Also the timings of the memory of your system could be to aggressive ... In short: all settings which may cause an unstable system. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

3727

Age (days ago)

3754

Last active (days ago)

Download

11 comments

1 participants

tags

participants (1)

bugzilla_noreply＠novell.com