Hi, Since upgrading to 7.3 I am having a problem getting sshd to reload after configuration changes. When I issue the command "systemctl reload sshd.service" I get the following error: "Unit sshd.service cannot be reloaded because it is inactive." It is obviously still running because I am connected over ssh to the machine and netstat shows it is listening. (vnewman pts3) # netstat -tulpn | grep ssh tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 29249/sshd tcp 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN 3012/sshd: root at pts (vnewman pts3) # If I reboot the machine, then everything is OK. Has anyone seen this behavior or more importantly know how to fix it? Regards, -- Tom me at tdiehl.org Spamtrap address me123 at tdiehl.org
Might I suggest using "systemctl restart sshd", instead of reload? At the least - see if it behaves differently for you. - *restart* = stop + start - *reload* = remain running + re-read configuration files. On Thu, Mar 2, 2017 at 9:29 AM, <me at tdiehl.org> wrote:> Hi, > > Since upgrading to 7.3 I am having a problem getting sshd to reload after > configuration changes. When I issue the command "systemctl reload > sshd.service" > > I get the following error: "Unit sshd.service cannot be reloaded because > it is inactive." > > It is obviously still running because I am connected over ssh to the > machine and netstat > shows it is listening. > (vnewman pts3) # netstat -tulpn | grep ssh > tcp 0 0 0.0.0.0:22 0.0.0.0:* > LISTEN 29249/sshd > tcp 0 0 127.0.0.1:6010 0.0.0.0:* > LISTEN 3012/sshd: root at pts > (vnewman pts3) # > > If I reboot the machine, then everything is OK. > > Has anyone seen this behavior or more importantly know how to fix it? > > Regards, > > -- > Tom me at tdiehl.org Spamtrap address > me123 at tdiehl.org > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >-- Natrona County Beekeepers <http://ncbees.org> Casper Amateur Radio Club <http://casperarc.net>
Hi, On Thu, 2 Mar 2017, Tate Belden wrote:> Might I suggest using "systemctl restart sshd", instead of reload? At the > least - see if it behaves differently for you.restart, reload, stop then start all produce the same results. If I do not change the configuration, and just issue the restart, reload, etc. then it behaves as expected. Obviously that is not useful when you have configuration changes. I tested this on a couple of other VM's and get the same results. Regards, -- Tom me at tdiehl.org Spamtrap address me123 at tdiehl.org
On Thu, Mar 02, 2017 at 11:29:24AM -0500, me at tdiehl.org wrote:> Hi, > > Since upgrading to 7.3 I am having a problem getting sshd to reload after > configuration changes. When I issue the command "systemctl reload sshd.service" > > I get the following error: "Unit sshd.service cannot be reloaded because it is inactive."upstream see https://bugzilla.redhat.com/show_bug.cgi?id=1381997 openssh-7.4p1-1.el7 should fix it. Cheers Tru -- Tru Huynh http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20170303/7ce5c3cb/attachment-0001.sig>
On Fri, 3 Mar 2017 08:53:43 Tru Huynh wrote:> On Thu, Mar 02, 2017 at 11:29:24AM -0500, me at tdiehl.org wrote: > > Hi, > > > > Since upgrading to 7.3 I am having a problem getting sshd to reload after > > configuration changes. When I issue the command "systemctl reload sshd.service" > > > > I get the following error: "Unit sshd.service cannot be reloaded because it is inactive." > upstream see https://bugzilla.redhat.com/show_bug.cgi?id=1381997 > > openssh-7.4p1-1.el7 should fix it.Well at least I know I an not going crazy. I missed that in my Google search. Thanks Tru. Regards, -- Tom me at tdiehl.org Spamtrap address me123 at tdiehl.org