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@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,
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@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@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@tdiehl.org Spamtrap address me123@tdiehl.org _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
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,
I have to assume it's something unique to your install, then.
I run about a dozen sshd instances on as many CentOS 7 boxes around here. To a one, systemctl restart sshd is all it takes to implement config changes.
Only time it's given me fits is if I forget to actually write the config file in VIM. That pesky w gets me on rare occasion.
On Thu, Mar 2, 2017 at 11:50 AM, me@tdiehl.org wrote:
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@tdiehl.org Spamtrap address me123@tdiehl.org _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On Thu, 2 Mar 2017, Tate Belden wrote:
I have to assume it's something unique to your install, then.
I run about a dozen sshd instances on as many CentOS 7 boxes around here. To a one, systemctl restart sshd is all it takes to implement config changes.
Did you actually change something before doing the restart? If nothing changes it will restart every time. If I change the configuration to for instance have sshd listen on another port, that is when I have the problem. Oh and selinux is in permissive.
There is nothing special about the environment. a couple of VM's in question are brand new minimal installs. I spin them up for testing push new sshd configs to them with Ansible and tear them down.
Before someone says Ansible is the problem I have tried this by hand also.
Regards,
Oh yea!
That's how I test/implement new configurations.
Make a change restart test make a change Lather, rinse and repeat
On Thu, Mar 2, 2017 at 6:26 PM, me@tdiehl.org wrote:
On Thu, 2 Mar 2017, Tate Belden wrote:
I have to assume it's something unique to your install, then.
I run about a dozen sshd instances on as many CentOS 7 boxes around here. To a one, systemctl restart sshd is all it takes to implement config changes.
Did you actually change something before doing the restart? If nothing changes it will restart every time. If I change the configuration to for instance have sshd listen on another port, that is when I have the problem. Oh and selinux is in permissive.
There is nothing special about the environment. a couple of VM's in question are brand new minimal installs. I spin them up for testing push new sshd configs to them with Ansible and tear them down.
Before someone says Ansible is the problem I have tried this by hand also.
Regards,
-- Tom me@tdiehl.org Spamtrap address me123@tdiehl.org
On Thu, Mar 2, 2017 at 11:50 AM, me@tdiehl.org wrote:
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.
-- Tom me@tdiehl.org Spamtrap address me123@tdiehl.org _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On Thu, Mar 02, 2017 at 11:29:24AM -0500, me@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
On Fri, 3 Mar 2017 08:53:43 Tru Huynh wrote:
On Thu, Mar 02, 2017 at 11:29:24AM -0500, me@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,
-
me＠tdiehl.org -
Tate Belden -
Tru Huynh