[Bug 1023460] New: systemd on s390x cannot cope with RestrictAddressFamilies in service files
http://bugzilla.suse.com/show_bug.cgi?id=1023460 Bug ID: 1023460 Summary: systemd on s390x cannot cope with RestrictAddressFamilies in service files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: systemd-maintainers@suse.de Reporter: bg@suse.com QA Contact: qa-bugs@suse.de CC: daniel.molkentin@suse.com, ihno@suse.com, rw@suse.de, trenn@suse.com Found By: --- Blocker: --- With service files like systemd-udevd.service systemd-journald.service the latest systemd update introduced RestrictAddressFamilies. Unfortunately, the services do not start with this option enabled but instead generated errors like: systemd-journaldÝ232š: Failed to create notify socket: Protocol not supported This issue is discussed in https://github.com/systemd/systemd/issues/4575 but it apparently has not been solved on 64bit big-endian machines. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1023460
Berthold Gunreben
http://bugzilla.suse.com/show_bug.cgi?id=1023460
http://bugzilla.suse.com/show_bug.cgi?id=1023460#c1
--- Comment #1 from Daniel Molkentin
http://bugzilla.suse.com/show_bug.cgi?id=1023460
http://bugzilla.suse.com/show_bug.cgi?id=1023460#c2
--- Comment #2 from Daniel Molkentin
http://bugzilla.suse.com/show_bug.cgi?id=1023460
http://bugzilla.suse.com/show_bug.cgi?id=1023460#c4
--- Comment #4 from Daniel Molkentin
http://bugzilla.suse.com/show_bug.cgi?id=1023460
http://bugzilla.suse.com/show_bug.cgi?id=1023460#c5
--- Comment #5 from Franck Bui
http://bugzilla.suse.com/show_bug.cgi?id=1023460
http://bugzilla.suse.com/show_bug.cgi?id=1023460#c6
--- Comment #6 from Daniel Molkentin
http://bugzilla.suse.com/show_bug.cgi?id=1023460
http://bugzilla.suse.com/show_bug.cgi?id=1023460#c7
--- Comment #7 from Berthold Gunreben
http://bugzilla.suse.com/show_bug.cgi?id=1023460
http://bugzilla.suse.com/show_bug.cgi?id=1023460#c8
--- Comment #8 from Franck Bui
And go with something like this in the meantime?
yep exactly. Ok since we all agree, I'll update the patch accordingly and make it part of the next update for TW (which should happen pretty soon). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1023460
http://bugzilla.suse.com/show_bug.cgi?id=1023460#c9
Franck Bui
http://bugzilla.suse.com/show_bug.cgi?id=1023460
http://bugzilla.suse.com/show_bug.cgi?id=1023460#c10
--- Comment #10 from Franck Bui
http://bugzilla.suse.com/show_bug.cgi?id=1023460
http://bugzilla.suse.com/show_bug.cgi?id=1023460#c11
Ruediger Oertel
http://bugzilla.suse.com/show_bug.cgi?id=1023460
Max Lin
http://bugzilla.suse.com/show_bug.cgi?id=1023460
Stefan Behlert
http://bugzilla.suse.com/show_bug.cgi?id=1023460
http://bugzilla.suse.com/show_bug.cgi?id=1023460#c12
--- Comment #12 from Stefan Behlert
http://bugzilla.suse.com/show_bug.cgi?id=1023460
http://bugzilla.suse.com/show_bug.cgi?id=1023460#c13
--- Comment #13 from Franck Bui
reopening. the state that is currently in factory (and as such is being reused for staging) breaks system booting for all platforms except for x86_64, there is not a single working build possible anymore at the moment.
I do not see an open request with the above fix going to factory.
Let me get it correctly: Factory was broken due to the fact that the fix suggested in comment #6 is still missing. Am I understanding your concern correctly ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1023460
http://bugzilla.suse.com/show_bug.cgi?id=1023460#c14
--- Comment #14 from Ruediger Oertel
http://bugzilla.suse.com/show_bug.cgi?id=1023460
http://bugzilla.suse.com/show_bug.cgi?id=1023460#c15
Franck Bui
participants (1)
-
bugzilla_noreply@novell.com