On Tue, 22 Jul 2008, Jeroen van Meeuwen wrote:
Michael McGrath wrote:
Should we include a section with each standard that includes basic problem resolution and troubleshooting?
I hesitate to include it because I'm not sure its the type of thing that would ever be complete.
I can imagine the Configuration Management HOWTO having a section for Common Problems & General Troubleshooting, if that's what you mean?
What were you thinking about?
Well, lets say apache is down.
1) Is apache running? no? run service httpd configtest error? Fix config no error? Start apache, look through logs for outage cause yes? Is the network running? yes? Is it routing? Yes? blah no? restart network / add default route no? start network
Thats a skeleton view of it. Each step would include a test "example.com" for example. You can see how the above could get absolutely huge.
-Mike