On Tue, Jul 22, 2008 at 7:46 AM, Mike McGrath mmcgrath@redhat.com wrote:
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.
- 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
I would put this as a separate living document that ties into the main one. It would need to be living because well, EL-2.1 problems are differtent from EL-5 from F-10 (why doesn't my changes to /etc/sysconfig/network-scripts seem to work?)
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
csi-devel mailing list csi-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/csi-devel