Mike McGrath wrote:
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.
True. We're definitely not going to do the Dummy Guide to
Troubleshooting (are we?). We can however document things as:
Problem: 503 Service Temporarily Unavailable after restart of the
puppetmaster service
Solution: Restart the httpd service or wait.
I don't know how far this goes... Simple issues that might occur during
the implementation (eg. parts described in a HOWTO should there be any)
should suffice.
Right?
Kind regards,
Jeroen van Meeuwen
-kanarip