[Bug 808317] New: enabling sshd via yast2 runlevel doesn't work
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c0 Summary: enabling sshd via yast2 runlevel doesn't work Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: rommel@suse.com QAContact: jsrain@suse.com Found By: Component Test Blocker: --- When launching yast2 runlevel and Enabling the sshd in the simple view (non-export mode) sshd get's started but the service is not persistenly activated. I experienced this only on x86_64. On i586 this worked fine. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c1 --- Comment #1 from Heiko Rommel <rommel@suse.com> 2013-03-11 10:06:03 UTC --- Created an attachment (id=529077) --> (http://bugzilla.novell.com/attachment.cgi?id=529077) YaST2 log -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c Heiko Rommel <rommel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #529077|application/octet-stream |text/ascii mime type| | -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c2 --- Comment #2 from Heiko Rommel <rommel@suse.com> 2013-03-11 10:22:00 UTC --- What is odd is that yast2 reports sshd as being enabled (Yes*) and therefore might consider of not having to do anything. However, in the situation above sshd.service was NOT enabled when starting yast2. In the meantime, to manually fix my system I ran /bin/systemctl enabled sshd.service That changed the display to Yes (without an asterik) in yast2 lan. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c3 --- Comment #3 from Heiko Rommel <rommel@suse.com> 2013-03-11 10:24:32 UTC --- Created an attachment (id=529080) --> (http://bugzilla.novell.com/attachment.cgi?id=529080) output of systemctl status sshd.service after reboot and before starting yast2 runlevel (initial test condition) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c FeiXiang Zhang <fxzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fxzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |yast2-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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c4 Thomas Fehr <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |mvidner@suse.com --- Comment #4 from Thomas Fehr <fehr@suse.com> 2013-03-13 10:16:01 UTC --- Reassigned to maintainer of yast2-runlevel -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c5 Maitreya Maziarz <maitreya.maziarz@co.santa-cruz.ca.us> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maitreya.maziarz@co.santa-c | |ruz.ca.us --- Comment #5 from Maitreya Maziarz <maitreya.maziarz@co.santa-cruz.ca.us> 2013-03-15 16:14:07 UTC --- For me, this behavior applied to apache2 in addition to sshd. I don't know if it's related (and if I ought to file a separate bug report), but, additionally, there are no options in the default runlevel dropdown under advanced settings. I'd like to change my default runlevel to 3. Does anybody know the systemctl command to accomplish 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c6 --- Comment #6 from Wilfred van Velzen <wvvelzen@gmail.com> 2013-05-07 13:39:54 UTC --- I have (kind of) noticed the same behavior after the latest updates (through zypper up). Because of the kernel update I "needed" to reboot. After the reboot sshd wasn't running. It was running before the reboot! sshd.service in systemctl was disabled. Trying to enable it through Yast wasn't possible (the setting wouldn't stick). But 'systemctl enable sshd' did the trick. After that it was enabled in Yast also. (I'll add an extraction of /var/log/zypp/history as attachment, which shows the updates that were installed previous to the reboot) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c7 --- Comment #7 from Wilfred van Velzen <wvvelzen@gmail.com> 2013-05-07 13:41:49 UTC --- Created an attachment (id=538192) --> (http://bugzilla.novell.com/attachment.cgi?id=538192) Possible updates through zypper up that might have caused the regression -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |locilka@suse.com AssignedTo|mvidner@suse.com |locilka@suse.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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c8 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #8 from Lukas Ocilka <locilka@suse.com> 2013-06-11 07:09:07 UTC --- This should be working now. See bug #807507 Already fixed by a maintenance update openSUSE-RU-2013:0533-1 *** This bug has been marked as a duplicate of bug 807507 *** http://bugzilla.novell.com/show_bug.cgi?id=807507 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c9 Wilfred van Velzen <wvvelzen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|DUPLICATE | --- Comment #9 from Wilfred van Velzen <wvvelzen@gmail.com> 2013-06-11 07:29:38 UTC --- (In reply to comment #8)
This should be working now. See bug #807507
Already fixed by a maintenance update openSUSE-RU-2013:0533-1
This update was published on 25 March. What I described above happened in May. The system was fully updated end of April. So what I experienced can't have been bug 807507 !? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c10 --- Comment #10 from Wilfred van Velzen <wvvelzen@gmail.com> 2013-06-11 07:32:13 UTC --- Btw: The UTC time above these comments is wrong. It's now 13:32 UTC ... ? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c11 --- Comment #11 from Lukas Ocilka <locilka@suse.com> 2013-06-25 09:11:25 UTC --- This will hopefully fix the issue: New YaST module as a replacement for YaST Runlevel. Also available for 12.3 http://kobliha-suse.blogspot.cz/2013/06/yast-runlevel-is-dead-long-live-yast... -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c12 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #12 from Lukas Ocilka <locilka@suse.com> 2013-08-15 07:42:28 UTC --- Fixed by implementing new Yast configuration module: Yast Services Manager. It's already in Factory. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c13 --- Comment #13 from Wilfred van Velzen <wvvelzen@gmail.com> 2013-08-15 07:48:31 UTC --- (In reply to comment #12)
Fixed by implementing new Yast configuration module: Yast Services Manager. It's already in Factory.
Will this be fixed in 12.3 also? Or do we have to live with the fact that sshd gets disabled every time you run a "zypper up" ? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c14 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |crrodriguez@opensuse.org Resolution|FIXED | --- Comment #14 from Lukas Ocilka <locilka@suse.com> 2013-08-15 08:25:23 UTC --- If `zypper up` disables the sshd service, then it doesn't seem to be a Yast issue as Yast is not in the play at all. Command `systemctl enable sshd` should enable SSH service in your system. If you then run `zyper up`, reboot, and the service is not running, then it's a ssh issue. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c15 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |wvvelzen@gmail.com --- Comment #15 from Lukas Ocilka <locilka@suse.com> 2013-08-15 08:48:20 UTC --- Wilfred, please try not to use Yast at all and report the result: 1.) Check the SSHD status with `systemctl status sshd` 2.) enable SSHD if not enabled 3.) start SSHD if not started 4.) Check the SSHD status with `systemctl status sshd` 4.) Run `zypper up` 5.) Reboot 6.) Check the SSHD status with `systemctl status sshd` Something could be also found in /var/log/messages I'd like to see all three outputs from the systemctl status. I can't reproduce it on my system. Thanks in advance -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c16 --- Comment #16 from Wilfred van Velzen <wvvelzen@gmail.com> 2013-08-15 09:07:36 UTC --- I already did something similar this morning. Except for the reboot. Because I'm remotely administering this server through an ssh connection, it is _very_ inconvenient if I loose the ssh connection after a reboot. ;) I even have a cronjob that starts the sshd service every hour, just in case this happens again and there is an uncontrolled reboot. But today the sshd service was still enabled after the zypper up. Last week when I did the zypper up however it was disabled afterwards. There were lots of updated packages last week, because of the holiday season the previous zypper up was almost 2 months before that. I can provide for instance /var/log/zypp/history, if that would help? But sshd wasn't updated since April this year. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c17 --- Comment #17 from Lukas Ocilka <locilka@suse.com> 2013-08-15 09:24:33 UTC --- Yep, let's try the zypp history, please. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c18 Wilfred van Velzen <wvvelzen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|wvvelzen@gmail.com | --- Comment #18 from Wilfred van Velzen <wvvelzen@gmail.com> 2013-08-15 09:31:58 UTC --- Created an attachment (id=552728) --> (http://bugzilla.novell.com/attachment.cgi?id=552728) /var/log/zypp/history The attachment contains log from today's and the previous zypper up. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c19 Krasimir Ivanov <kiv@mail.orbitel.bg> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kiv@mail.orbitel.bg --- Comment #19 from Krasimir Ivanov <kiv@mail.orbitel.bg> 2013-09-17 10:41:40 UTC --- I have the same problem with a fully updated openSUSE 12.3 x86_64 installation. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c Alberto Planas Dominguez <aplanas@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| | GOLD -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c20 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED CC| |jreidinger@suse.com Resolution| |DUPLICATE --- Comment #20 from Josef Reidinger <jreidinger@suse.com> 2013-09-27 15:34:38 UTC --- have all related problems with systemd in runlevel in one place *** This bug has been marked as a duplicate of bug 799471 *** http://bugzilla.novell.com/show_bug.cgi?id=799471 -- 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.
participants (1)
-
bugzilla_noreply＠novell.com