https://bugzilla.novell.com/show_bug.cgi?id=808317 https://bugzilla.novell.com/show_bug.cgi?id=808317#c1 --- Comment #1 from Heiko Rommel 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#c2 --- Comment #2 from Heiko Rommel 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#c FeiXiang Zhang 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#c5 Maitreya Maziarz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maitreya.maziarz@co.santa-c | |ruz.ca.us --- Comment #5 from Maitreya Maziarz 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#c7 --- Comment #7 from Wilfred van Velzen 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#c8 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #8 from Lukas Ocilka 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#c10 --- Comment #10 from Wilfred van Velzen 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#c12 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #12 from Lukas Ocilka 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#c14 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |crrodriguez@opensuse.org Resolution|FIXED | --- Comment #14 from Lukas Ocilka 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#c16 --- Comment #16 from Wilfred van Velzen 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#c18 Wilfred van Velzen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|wvvelzen@gmail.com | --- Comment #18 from Wilfred van Velzen 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#c Alberto Planas Dominguez 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.