https://bz.apache.org/bugzilla/show_bug.cgi?id=57360
James Boyle <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from James Boyle <[email protected]> --- I've experienced this issue as well - I just want to share what I believe to be a common expectation among system administrators / DevOps folks out there. When a daemon fails to load, we expect the reason for the failure to be clearly logged, ideally to syslog. I agreed that the "Configuration Failed" (aka Apache initialization) and Apache returned "1" when it exited, but I hope everyone will admit the following two statements don't really give the administrator a good place to look for things to fix: "AH00016: Configuration Failed" ... and ... "Syntax OK" (from httpd -t) - which implies the configuration is OK I wish it had said something like: "AH00016: Configuration Failed: Security certificate error: /path/to/file" or "AH00016: Configuration Failed: VHost example.com: cannot initialize SSL/TLS" Thankfully I know about strace. Any solution that puts a message that points the administrator to the source of the problem is a win in my book. Thank you! -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
