What is this error: com.apple.fontd[126]FODBCheck: foRec->annexNumber != kI

Question

Level 2

240 points

What is this error: com.apple.fontd[126]FODBCheck: foRec->annexNumber != kI

I have been having boot problems so I decided to look at my logs which I do not understand. This is what I get on my last boot. Could someone please help?

5/3/10 10:05:35 PM com.apple.launchd[1] * launchd[1] has started up. *
5/3/10 10:06:01 PM com.apple.launchd.peruser.501[118] (com.apple.Kerberos.renew.plist[141]) Exited with exit code: 1
5/3/10 10:06:01 PM [0x0-0xa00a].com.kensington.mouseworks.background[148] Kensington FastUserSwitch: Session On Console
5/3/10 10:06:01 PM [0x0-0xa00a].com.kensington.mouseworks.background[148] Kensington FastUserSwitch: Session User ID = 501
5/3/10 10:06:01 PM [0x0-0xa00a].com.kensington.mouseworks.background[148] Kensington FastUserSwitch: Installing User Switch Notifications
5/3/10 10:06:56 PM com.apple.fontd[126] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/3/10 10:07:04 PM com.apple.fontd[126] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/3/10 10:07:20 PM com.apple.fontd[126] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/3/10 10:07:20 PM com.apple.fontd[126] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/3/10 10:07:23 PM com.apple.fontd[126] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/3/10 10:07:24 PM com.apple.fontd[126] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/3/10 10:07:28 PM com.apple.fontd[126] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/3/10 10:07:28 PM com.apple.fontd[126] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/3/10 10:07:29 PM com.apple.fontd[126] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/3/10 10:07:40 PM com.apple.fontd[126] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/3/10 10:07:48 PM com.apple.fontd[126] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/3/10 10:07:51 PM com.apple.fontd[126] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/3/10 10:08:28 PM com.apple.fontd[126] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/3/10 10:08:37 PM com.apple.fontd[126] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/3/10 10:08:45 PM com.apple.fontd[126] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/3/10 10:08:52 PM com.apple.fontd[126] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)

Mac Pro 2.66 5gb ram, Mac OS X (10.6.3)

Posted on May 3, 2010 10:13 PM

Reply

Answer 1

baltwo

Level 9

62,362 points

May 3, 2010 11:42 PM in response to Cindy

IIRC, fontd is what controls the fonts. Boot in safe mode and normally. That will reset the font database, wipe out the font caches, and delete all font collections. Then, launch Font Book, validate all fonts, resolve all conflicts, and remake any font collections.

Reply

Answer 2

Cindy Author

Level 2

240 points

May 4, 2010 8:13 AM in response to baltwo

Where would I delete these font collections. I use FontAgent Pro which checks the fonts that it imports but I think this has to do with FontBook.

Reply

Answer 3

baltwo

Level 9

62,362 points

May 4, 2010 12:16 PM in response to Cindy

Booting into safe mode does it automatically, as I previously described. See Font Management in OS X for more details.

Reply

Answer 4

Cindy Author

Level 2

240 points

May 4, 2010 3:09 PM in response to baltwo

I have done everything from clearing out all the non essential fonts, clearing cache, re-booting in safe mode, etc etc and I still have the font error in the log fine. Pulling out hair....

Reply

Answer 5

Cindy Author

Level 2

240 points

May 4, 2010 3:26 PM in response to Cindy

This is my most recent log file. Looks worse. I have spent all day on this and am getting nowhere. Could someone please look at this?

5/4/10 3:20:18 PM System Preferences[202] * WARNING: Method selectedRowEnumerator in class LoginItemsTableView is deprecated. It will be removed in a future release and should no longer be used.
5/4/10 3:22:57 PM com.apple.launchd.peruser.501[122] ([0x0-0x11011].com.apple.Stickies[161]) Exited: Killed
5/4/10 3:22:57 PM com.apple.launchd.peruser.501[122] ([0x0-0x16016].com.apple.ImageCaptureExtension2[176]) Exited: Killed
5/4/10 3:23:13 PM com.apple.launchd[1] * launchd[1] has started up. *
5/4/10 3:23:36 PM com.apple.launchd.peruser.501[116] (com.apple.Kerberos.renew.plist[140]) Exited with exit code: 1
5/4/10 3:23:42 PM [0x0-0x9009].com.kensington.mouseworks.background[149] Kensington FastUserSwitch: Session On Console
5/4/10 3:23:42 PM [0x0-0x9009].com.kensington.mouseworks.background[149] Kensington FastUserSwitch: Session User ID = 501
5/4/10 3:23:42 PM [0x0-0x9009].com.kensington.mouseworks.background[149] Kensington FastUserSwitch: Installing User Switch Notifications
5/4/10 3:23:55 PM com.apple.fontd[127] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 3:23:57 PM com.apple.fontd[127] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 3:23:58 PM com.apple.WindowServer[98] Tue May 4 15:23:58 CDS2.local WindowServer[98] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
5/4/10 3:24:01 PM com.apple.fontd[127] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 3:24:01 PM com.apple.fontd[127] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 3:24:01 PM com.apple.fontd[127] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 3:24:01 PM com.apple.fontd[127] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 3:24:02 PM com.apple.fontd[127] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 3:24:13 PM com.apple.fontd[127] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 3:24:35 PM com.apple.fontd[127] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 3:24:38 PM com.apple.fontd[127] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)

Reply

Answer 6

baltwo

Level 9

62,362 points

May 4, 2010 4:07 PM in response to Cindy

What happens if you disconnect from the network and its servers? If that solves the issue, seriously consider updating to 10.6.3 and eliminating the Kensington mouse stuff.

Reply

Answer 7

Cindy Author

Level 2

240 points

May 4, 2010 4:14 PM in response to baltwo

I am already using 10.6.3 I need to change it in my profile...

Reply

Answer 8

Cindy Author

Level 2

240 points

May 4, 2010 4:22 PM in response to Cindy

I removed Kensington Mouse Works and here is my log. Not any better.

5/4/10 4:18:53 PM com.apple.launchd.peruser.501[119] (com.apple.pbs) Throttling respawn: Will start in 10 seconds
5/4/10 4:19:01 PM System Preferences[168] * WARNING: Method selectedRowEnumerator in class LoginItemsTableView is deprecated. It will be removed in a future release and should no longer be used.
5/4/10 4:19:19 PM com.apple.launchd.peruser.501[119] ([0x0-0x12012].com.apple.ImageCaptureExtension2[163]) Exited: Killed
5/4/10 4:19:41 PM com.apple.launchd[1] * launchd[1] has started up. *
5/4/10 4:20:06 PM com.apple.launchd.peruser.501[118] (com.apple.Kerberos.renew.plist[140]) Exited with exit code: 1
5/4/10 4:20:17 PM com.apple.Dock.agent[122] CPSPostEventRecordTo failed -600 /Users/Cindy/Library/Widgets/Time Machine Buddy.wdgt/
5/4/10 4:20:26 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:27 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:29 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:29 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:31 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:33 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:46 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:48 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:48 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:53 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:48 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:48 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:53 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:48 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:48 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:53 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:48 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:48 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:53 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:48 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:48 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:53 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:48 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:48 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:53 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:48 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:48 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/4/10 4:20:53 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)

Reply

Answer 9

Cindy Author

Level 2

240 points

May 6, 2010 3:56 PM in response to baltwo

I just went through Font Management for OSX in its entirety. I am sure I cleaned up a few problems which I think might correct my boot problems but I still have the dfont thing showing up in my log as follow. If anyone can offer any more suggestions I sure would appreciate.

5/6/10 3:50:11 PM com.apple.launchd[1] * launchd[1] has started up. *
5/6/10 3:50:39 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/6/10 3:50:40 PM com.apple.launchd.peruser.501[119] (com.apple.Kerberos.renew.plist[143]) Exited with exit code: 1
5/6/10 3:50:40 PM [0x0-0x9009].com.kensington.mouseworks.background[150] Kensington FastUserSwitch: Session On Console
5/6/10 3:50:40 PM [0x0-0x9009].com.kensington.mouseworks.background[150] Kensington FastUserSwitch: Session User ID = 501
5/6/10 3:50:40 PM [0x0-0x9009].com.kensington.mouseworks.background[150] Kensington FastUserSwitch: Installing User Switch Notifications
5/6/10 3:50:47 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/6/10 3:50:47 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/6/10 3:50:47 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/6/10 3:50:51 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/6/10 3:50:52 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/6/10 3:51:12 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/6/10 3:51:15 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/6/10 3:51:15 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/6/10 3:51:15 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
5/6/10 3:51:20 PM com.apple.fontd[129] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)

Reply

Answer 10

baltwo

Level 9

62,362 points

May 6, 2010 4:17 PM in response to Cindy

What happens if you disconnect from the network and its servers, eliminate the Kensington mouse stuff, and boot into safe mode; then, boot normally and rerun FontBook, vailidating fonts and resolving duplicates?

Reply

Answer 11

Cindy Author

Level 2

240 points

May 6, 2010 4:26 PM in response to baltwo

I tried removing the Kensington stuff last night... made no difference.

When you say disconnect from the network, do you mean my dsl? I don't share any fonts over a network or anything like that. Are you saying disconnect the ethernet just to see if the errors go away?

Reply

Answer 12

baltwo

Level 9

62,362 points

May 6, 2010 7:00 PM in response to Cindy

No. I was misled by the Kerberos item, thinking you might be hooked up to some university or corporate server network. Apparently, the OS does that periodically, but I haven't a clue what's triggering it. Have you tried the safe mode boot?

Reply

Answer 13

Cindy Author

Level 2

240 points

May 8, 2010 11:21 AM in response to baltwo

ALL and I mean ALL of my problems were font related. I went through the tutorial on fonts in OSX that was suggested to me in an earlier post but the "com.apple.fontd[126]FODBCheck: foRec->annexNumbe" error persisted. I finally removed FontAgent Pro completely. It went away. I loaded it back up, it came back. I disabled all fonts, it went away. I still havent fount the font that was causing that particular problem.

My whole point is: I think that a lot of problems that people have with slow boots etc are font related. So cleaning up the system folders is big and so is cleaning up your font manager.

Thanks for all the help.

Reply

Answer 14

baltwo

Level 9

62,362 points

May 8, 2010 12:10 PM in response to Cindy

Thanks for the feedback. Good computing.

Reply

Answer 15

Cindy Author

Level 2

240 points

May 8, 2010 12:16 PM in response to baltwo

Thanks! The thing I am sadly finding however is it appears that SL doesn't like a LOT of my Post Script fonts. I can enable them and watch the error pop up in Console.

I found out yesterday that there is no real reason to upgrade to FontAgent Pro 4. I use 3.3.2. I am wondering if it would make a difference. I doubt it. I would try the trial but I think it overwrites things that I don't want it to making it difficult to go back.

Reply