Comment 3 for bug 1452345

I'm not sure how keystone-all is meant to know keystone is supposed to run under httpd. I've done a number of test scenarios where I'll configure keystone under both and swap between. The port already in use is a valid error (while cryptic) and correct as it isn't guaranteed to be keystone on the port.