Nothing more than what was in messages namely 'code=exited, status=255/n/a' which looks an awful lot like a printf of an uninitialized variable...
Mike On 07/09/2014 11:21 AM, Jonathan Billings wrote: > On Wed, Jul 09, 2014 at 10:54:29AM -0400, Mike McCarthy, W1NR wrote: >> SELinux is not running. Any other ideas? > Checking the firewall is useful, but it sounds like you can't get the > service to start in the first place. > > It might be helpful if you gave us the full error output. Do you get > more information by running: > > systemctl status -l sshd.service > > ... after running the systemctl start? > _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos