Since I installed ASL i have been getting one email a minute
It says:
Command executed: /sbin/service sshd restart
Exit value: 255
Signal number: 0
Dumped core?: 0
Stopping sshd: [FAILED]
Starting sshd: /etc/ssh/sshd_config line 140: Directive 'UseDNS' is not allowed within a Match block
[FAILED]
I shut off SSH in WHM but still get the email?
Failed to spawn 'sshd' with '/sbin/service sshd restart'
- mikeshinn
- Atomicorp Staff - Site Admin
- Posts: 4149
- Joined: Thu Feb 07, 2008 7:49 pm
- Location: Chantilly, VA
Re: Failed to spawn 'sshd' with '/sbin/service sshd restart'
Did you modify your sshd_config to use Match blocks?
Michael Shinn
Atomicorp - Security For Everyone
Atomicorp - Security For Everyone
Re: Failed to spawn 'sshd' with '/sbin/service sshd restart'
no but this may be linked to my other problem on the terminalmikeshinn wrote:Did you modify your sshd_config to use Match blocks?
I think the hostmonster admins did
I was having horrible problems with attackers (which eventually brought me to download ASL) and they did something but did not tell me what
to help me.
Do you have an idea where I can look once I get the terminal logging fixed?
- mikeshinn
- Atomicorp Staff - Site Admin
- Posts: 4149
- Joined: Thu Feb 07, 2008 7:49 pm
- Location: Chantilly, VA
Re: Failed to spawn 'sshd' with '/sbin/service sshd restart'
OK, that makes sense. So this means they have added Match directives to your /etc/sshd_config file (there arent any by default). If you arent sure what they are for you can post them here and we can sort this out together. sshd_config is really picky about what directives can be after a Match is declared, and this is one of those that has to happen before the Match entries.
Michael Shinn
Atomicorp - Security For Everyone
Atomicorp - Security For Everyone
Re: Failed to spawn 'sshd' with '/sbin/service sshd restart'
ok i will be back later, Hostmonster is trying to undo what someone did, apparently they are displaying the system log on the terminal making it impossible for me to do much of anything
Re: Failed to spawn 'sshd' with '/sbin/service sshd restart'
Hostmonster was no help
I got the VNC terminal issue fixed and did the following (in case others has a similar issue)
I uninstalled SSH in the VNC Console
# chkconfig sshd off
# service sshd stop
# yum erase openssh-server
Then reinstalled it
yum -y install openssh-server openssh-clients
I just have to check if the ports are open but the one email a minuted has stopped
I checked the service with
ps aux | grep sshd
http://www.cyberciti.biz/faq/howto-unix ... hd-server/
http://www.cyberciti.biz/faq/centos-ssh/
http://www.ewhathow.com/2013/09/how-to- ... -on-linux/
I got the VNC terminal issue fixed and did the following (in case others has a similar issue)
I uninstalled SSH in the VNC Console
# chkconfig sshd off
# service sshd stop
# yum erase openssh-server
Then reinstalled it
yum -y install openssh-server openssh-clients
I just have to check if the ports are open but the one email a minuted has stopped
I checked the service with
ps aux | grep sshd
http://www.cyberciti.biz/faq/howto-unix ... hd-server/
http://www.cyberciti.biz/faq/centos-ssh/
http://www.ewhathow.com/2013/09/how-to- ... -on-linux/
- mikeshinn
- Atomicorp Staff - Site Admin
- Posts: 4149
- Joined: Thu Feb 07, 2008 7:49 pm
- Location: Chantilly, VA
Re: Failed to spawn 'sshd' with '/sbin/service sshd restart'
Thats certainly one way to fix your sshd config. Given all the odd issues you had earlier it sounds like your hosting company made a number of modifications to ssh, including the original stack RWX issue.
If ps auxwww | grep sshd shows sshd running then you can check that box.
If ps auxwww | grep sshd shows sshd running then you can check that box.
Michael Shinn
Atomicorp - Security For Everyone
Atomicorp - Security For Everyone
Re: Failed to spawn 'sshd' with '/sbin/service sshd restart'
that box is checked thanks