Scott Davenport @ Sun: (Mainly) Fault Management

Quite a while back I blogged about the FMA event registry. I recently got a new laptop, and have been preparing it for my "guru" session next week at LISA '08 in San Diego. Loaded OpenSolaris 05.2008 on it, then updated the image to the pre-release of OpenSolaris 11.2008. And the 'erapache' utility in the Event Registry didn't work.

Turns out, Apache isn't included in the base image of OpenSolaris (only so much stuff can fit on a single CD I suppose). "No problem," I thought. "I'll grab Apache from IPS."

% pfexec pkg install SUNWapch22

Apache 2.2 loaded fine, works fine. But still no joy with 'erapache'. Digging around in the library modules of the event registry, tools/lib/ERapacheTool.pm, the problem became obvious:

30 # This utility is very Solaris-dependent because it expects apache 31 # to live where Solaris puts it ... 97 my $httpd = "/usr/apache/bin/httpd";

As folks that use Apache know, Apache 2.2 installs in /usr/apache2/2.2. I first tried a symbolic link to point /usr/apache at /usr/apache2/2.2, but then hit problems with the default httpd.conf the 'erapache' utility constructs. So, reverted to applying the older Apache 1.x IPS package:

% pfexec pkg install SUNWapch

That worked swimmingly, and 'erapache' runs as expected.

So, useful workaround until tools/lib/ERapacheTool.pm is updated to work with a variety of Apache versions.

:wq