[Bug 965473] New: lockdown by "init 3" command
http://bugzilla.opensuse.org/show_bug.cgi?id=965473 Bug ID: 965473 Summary: lockdown by "init 3" command Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: misi@ship.hu QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After launching the "init 3" command the system closes the (remote) connections. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
Misi Mókus
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
Misi Mókus
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
Misi Mókus
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c1
Martin Pluskal
After launching the "init 3" command the system closes the (remote) connections.
You selected Tumbleweed as product and Leap as hardware - which one is it then? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c2
--- Comment #2 from Misi Mókus
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c3
Martin Pluskal
Tumbleweed is not in the rolldown hardware list. You don't have to select this The distribution is Tumbleweed.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c4
--- Comment #4 from Misi Mókus
(In reply to Misi Mókus from comment #2)
Tumbleweed is not in the rolldown hardware list. You don't have to select this The distribution is Tumbleweed.
Thank you. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c5
--- Comment #5 from Bernhard Wiedemann
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c6
--- Comment #6 from Misi Mókus
probably same as bug 966535
if so, please mark as duplicate
I can not decide that clearly. I do not use Networkmanager (I have no wireless connection) but some applications needed it unfortunately (if I remember well), so I had to install it. I use wicked and no wpa-supplicant. In some cases I realize that the system believes that the media in the /media directory is removable... but it it is not obligate at all. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c7
--- Comment #7 from Misi Mókus
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c12
--- Comment #12 from Ludwig Nussel
(In reply to Misi Mókus from comment #6)
The wpa-supplicant should be dynamically drop in. Nevertheless there seems to be a dependency issue which shuts down the network connections (and therefore the remote terminals) and/or the remote connection them self like sshd.
AFAICS the sshd is *ALSO* missed in the presets!
No it's not. sshd gets enabled by YaST if requested. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c13
--- Comment #13 from Misi Mókus
http://bugzilla.opensuse.org/show_bug.cgi?id=965473 Bug 965473 depends on bug 966535, which changed state. Bug 966535 Summary: Tumbleweed, systemd-228, changing runlevel drops internet connection http://bugzilla.opensuse.org/show_bug.cgi?id=966535 What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c14
--- Comment #14 from Misi Mókus
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c15
Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c16
--- Comment #16 from Misi Mókus
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c17
--- Comment #17 from Franck Bui
2. @Franck Bui I made the test above with newest kernel and full update. Please write the test more precise, I do not understand clearly (if the zypper refreshed systemd then it is the newest...).
Try to install systemd from http://download.opensuse.org/repositories/Base:/System/openSUSE_Tumbleweed/: $ zypper ar http://download.opensuse.org/repositories/Base:/System/openSUSE_Tumbleweed/B... $ zypper dup systemd udev $ reboot And then do your test. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c18
--- Comment #18 from Misi Mókus
zypper dup systemd udev
Too many arguments. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c19
--- Comment #19 from Franck Bui
zypper dup systemd udev
Too many arguments.
sorry I meant "zypper up systemd udev". zypper will probably ask you to do instead: "zypper in systemd-228-12.1.x86_64 udev-228-12.1.x86_64" or something similar. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c20
--- Comment #20 from Misi Mókus
(In reply to Misi Mókus from comment #18)
zypper dup systemd udev
Too many arguments.
sorry I meant "zypper up systemd udev".
zypper will probably ask you to do instead: "zypper in systemd-228-12.1.x86_64 udev-228-12.1.x86_64" or something similar.
"Reading installed packages... There is an update candidate for 'systemd', but it is from a different vendor. Use 'zypper install systemd-228-12.1.x86_64' to install this candidate. There is an update candidate for 'systemd', but it comes from a repository with a lower priority. Use 'zypper install systemd-228-12.1.x86_64' to install this candidate. There is an update candidate for 'udev', but it is from a different vendor. Use 'zypper install udev-228-12.1.x86_64' to install this candidate. There is an update candidate for 'udev', but it comes from a repository with a lower priority. Use 'zypper install udev-228-12.1.x86_64' to install this candidate. Resolving package dependencies... Nothing to do." I have installed manually both of them. systemd ok. udev not: "Additional rpm output: Failed to stop udev-control.socket: Unit udev-control.socket not loaded. Failed to stop udev-kernel.socket: Unit udev-kernel.socket not loaded. Additional rpm output: Failed to stop udev-control.socket: Unit udev-control.socket not loaded. Failed to stop udev-kernel.socket: Unit udev-kernel.socket not loaded.^COutput of udev-228-12.1.x86_64.rpm %posttrans script: Creating initrd: /boot/initrd-4.4.3-1-default dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-4.4.3-1-default 4.4.3-1-default dracut: *** Including module: bash *** dracut: *** Including module: systemd *** dracut: *** Including module: warpclock *** dracut: *** Including module: systemd-initrd *** dracut: *** Including module: i18n *** dracut: *** Including module: drm *** dracut: *** Including module: plymouth *** dracut: *** Including module: kernel-modules *** Generating /boot/initrd-4.4.3-1-default targets failed Warning: udev-228-12.1.x86_64.rpm %posttrans script failed (returned 1) There are some running programs that might use files deleted by recent upgrade. You may wish to check and restart some of them. Run 'zypper ps -s' to list these programs." Reboot? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c21
--- Comment #21 from Franck Bui
Reboot?
yes please -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c22
--- Comment #22 from Misi Mókus
(In reply to Misi Mókus from comment #20)
Reboot?
yes please
Init 3 test: servername:~ # init 3 ^C servername:~ # servername:~ # init 5 servername:~ # init 3 servername:~ # init 5 servername:~ # No usual dbus auth messages. NO disconnecting. I am waiting for your instructions. Or check the driver again? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c23
--- Comment #23 from Franck Bui
(In reply to Franck Bui from comment #21)
(In reply to Misi Mókus from comment #20)
Reboot?
yes please
Init 3 test:
servername:~ # init 3
^C servername:~ # servername:~ # init 5 servername:~ # init 3 servername:~ # init 5 servername:~ #
No usual dbus auth messages. NO disconnecting.
So your initial issue you reported in comment #0 is solved ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c24
--- Comment #24 from Misi Mókus
(In reply to Misi Mókus from comment #22)
(In reply to Franck Bui from comment #21)
(In reply to Misi Mókus from comment #20)
Reboot?
yes please
Init 3 test:
servername:~ # init 3
^C servername:~ # servername:~ # init 5 servername:~ # init 3 servername:~ # init 5 servername:~ #
No usual dbus auth messages. NO disconnecting.
So your initial issue you reported in comment #0 is solved ?
Yes. Some cosmetics: the first init 3 stuck, I must type ctrl-C. And it would be more comfortable then the command would send a "successful" message... :) Thanks for your effort. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c25
--- Comment #25 from Franck Bui
(In reply to Franck Bui from comment #23)
So your initial issue you reported in comment #0 is solved ?
Yes.
Therefore it's a duplicate of bug 966535.
Some cosmetics: the first init 3 stuck, I must type ctrl-C. And it would be more comfortable then the command would send a "successful" message... :)
Agreed. However I can't see this behavour here. Is this something reproductible on your side ? after a reboot ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c26
--- Comment #26 from Misi Mókus
(In reply to Misi Mókus from comment #24)
(In reply to Franck Bui from comment #23)
So your initial issue you reported in comment #0 is solved ?
Yes.
Therefore it's a duplicate of bug 966535.
Some cosmetics: the first init 3 stuck, I must type ctrl-C. And it would be more comfortable then the command would send a "successful" message... :)
Agreed.
However I can't see this behavour here.
Is this something reproductible on your side ? after a reboot ?
What I wrote that is exactly the same what I have seen on the server, copied. I did not make driver compilation. Do you want any other evidence? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=965473
http://bugzilla.opensuse.org/show_bug.cgi?id=965473#c27
Franck Bui
participants (1)
-
bugzilla_noreply@novell.com