Scott Davenport @ Oracle: (Mainly) Fault Management

A couple of weeks ago, I upgraded to build 131 and had a font hiccup. And I thought I'd fixed things up by ensuring that the 'extra' repo was active.

Well, today when I upgraded to build 132 (yes, with 'extra' active) I hit the same problem. This still looks like a match to bug 13912 - image-update of b131 stops when ttf-fonts-core extra package is installed. But when I look at the packages in 'extra', I don't see the ttf-fonts-core package anymore.

I decided to remove my (now, quite old) version of the package:

# pkg uninstall system/font/truetype/ttf-fonts-core

From there, the upgrade went fine. Hopefully I'm out of the woods when build 133 comes along.

:wq

[A new company now, so time to give the weblog a new look.]

And, time to talk about a very cool FMA feature I've been meaning to blog about for a while. It's been termed "historical diagnosis". The crux is having FMD reduce the number of convicted suspects in multi-entry suspect lists by comparing the historical record of other faults diagnosed on that system. When certain correlations are found, FMD auto-acquits some of the suspects in various suspect lists.

Probably best dealt with via an example. Suppose a suspect list is issued indicting two components, FRUA and FRUB. Some time later, another suspect list is issued, this time only indicting FRUA. FMD will discard the newer, single entry suspect list as a duplicate and acquit FRUB in the original suspect list. The end result, only FRUA is indicted. (And yes, component serial numbers are used to ensure the "old" FRUA is the same as the "new" FRUA.)

There are of course many different use cases with variations when the FRUs in the suspect list are in different states (faulty|isolated|replaced|acquitted), but you get the idea. And what's very nice is that all of this is managed by FMD itself. No changes to diagnosis rules or response agents. The changes incorporated into build 125.

:wq

I upgraded to build 131 this morning and hit a hiccup on X11 TrueType fonts. About 75% into the install, Update Manager stopped complaining about files in usr/X11/lib/X11/fonts/TrueType. I moved the TrueType directory out of the way and the install proceeded.

After the upgrade worked, I found 6905518 which shines some light on the problem. The 'TrueType' directory becomes a symlink to /usr/share/fonts/TrueType. So I plopped my fonts in their new location post-upgrade and all is well.

:wq

---

Update:
Happened upon image-update of b131 stops when ttf-fonts-core extra package is installed and sure enough my 'extra' repo wasn't active. Off to update my keys and certificates for 'extra'.

---