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.

On Tue, 22 Jul 2008, Jeroen van Meeuwen wrote: > 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.

On Tue, Jul 22, 2008 at 7:46 AM, Mike McGrath <mmcgrath(a)redhat.com&gt; 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. > > 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 > 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?)

Mike McGrath wrote: > On Sat, 26 Jul 2008, Stephen John Smoogen wrote: >> 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?) >> > > Yeah, Seems like I'll have to think on it some more on where to put it and > exactly what should be in there. > We could distinct between "common problems while running through this little HOWTO guide I've included in the Standard" and "(common) problems you should already be able to address", the latter being developed/maintained somewhere else, outside our Standards framework, because well... standards are standards, not dummy guides. FWIW, I've just recently started developing the course materials for students and teachers on fedorahosted[1], since I'm doing the work anyway (I teach a little Linux within the company I work for) and I really wanted it to be public, open and usable by anyone else. This is where "why don't these changes work?" could be addressed in a form of training/exercises, without cluttering up the standard, maybe?

On Mon, 2008-07-21 at 19:59 -0400, 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. How about referencing a canonical place on the Wiki for each standard where people can collect that kind of thing, something like a FAQ about the standard ?