Console says "Failures everywhere"

Question

I experienced some strange behaviour today. It seems to be OK now, but Iäd like to understand what went on.
Earlier today, I was surfing the internet, reading news and some forums. Nothing extraordinary, and no dodgy websites -- honest! Anyway, after a brief while I logged out, and my Mac seemed to be doing what it always does. However, instead of ending up with the login window, it just stayed solid blue, no login window at all. The cursor was there, and could be moved around without trouble. After an hour or so, I pressed the re-boot button on the G4 tower. I haven't noticed any malfunctions since then, nor any strange behaviour.
I looked in the console. At quarter to seven, I decide to log out. I did not chose "sleep", unless I did so by accident, but that seems to be of minor importance.
[quote]
Jun 12 18:47:10 XXXXXXXs-G4 kernel[0]: System Sleep
Jun 12 18:47:10 XXXXXXXs-G4 kernel[0]: System Wake
Jun 12 18:47:10 XXXXXXXs-G4 kernel[0]: Wake event 0800
Jun 12 18:47:12 XXXXXXXs-G4 kernel[0]: UniNEnet::monitorLinkStatus - Link is up at 100 Mbps - Full Duplex
Jun 12 18:47:23 XXXXXXXs-G4 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Support/ATSServer: FOExceptionMainHandler caught a fatal exception at 0x0000ede4\n
Jun 12 18:47:23 XXXXXXXs-G4 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Support/ATSServer: ATSServer: Failed to revive database from presistent store. status = -4\n
Jun 12 18:47:23 XXXXXXXs-G4 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Support/ATSServer: FOExceptionMainHandler caught a fatal exception at 0x0000ede4\n
Jun 12 18:47:23 XXXXXXXs-G4 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Support/ATSServer: ATSServer: Failed on retry of revive database from presistent store. status = -4\n
Jun 12 18:47:23 XXXXXXXs-G4 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Support/ATSServer: (-4) Failures everywhere, trying one last time - switching to old FODB cache code[/quote]
I assume that it is at this point I get a solid blue screen. No login window, and nothing is happening. So I press the on/off button on my disply, which is set to put the computer to sleep. The screen goes black. I go away from the computer.
[quote]
Jun 12 20:07:25 XXXXXXXs-G4 loginwindow[863]: sendQuitEventToApp (LOGINserver): AESendMessage returned error -609
Jun 12 20:07:36 XXXXXXXs-G4 /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Jun 12 20:07:37 XXXXXXXs-G4 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Support/ATSServer: Attempting to swich to new persistent store code
Jun 12 20:07:37 XXXXXXXs-G4 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Support/ATSServer: FOExceptionMainHandler caught a fatal exception at 0x0000ede4\n
Jun 12 20:07:37 XXXXXXXs-G4 loginwindow[976]: Login Window Started Security Agent[/quote]
I come back, and press the on/off button on the display. The compuer starts, but all I get is a solid blue screen. So I press the re-boot button on the tower instead, and it starts normally.
[quote]
Jun 12 20:43:04 XXXXXXXs-G4 kernel[0]: System Sleep[/quote]
The only thing I have installed recently is the Last Resort Font from Unicode. And seeing that the ATSServer is involved above, maybe that has something to do with all this.
Nothing seems to be problematic right now, and I have no specific problem. However, the phrase "Failures everywhere, trying one last time" does sound quite dramatic. I've seen enough disaster movies to know not to ignore stuff like that. So in order to prevent the world from certain and horrible doom, I'd like to understand what went on above.
Any ideas?

Answer 1

HI,
We need a crash report please. How to locate a crash log:
1. Open Finder.
2. Click "Go" in the menu, then select "Go to Folder".
3. Copy and paste this path into the Finder dialog:
~/Library/Logs/CrashReporter/
4. Click the Go button.
5. Finder opens the folder containing the crash log. Look for a the crash file with a date field that looks like the most recent.
Have you tried booting from your install disk?
Insert the installer disk and Restart, holding down the "C" key until grey Apple appears.
Go to Installer menu (Panther and earlier) or Utilities menu (Tiger and later) and launch Disk Utility.
Select your HDD (manufacturer ID) in the left panel.
Select First Aid in the Main panel.
(Check S.M.A.R.T Status of HDD at the bottom of right panel. It should say: Verified)
Click Repair Disk on the bottom right.
If DU reports disk does not need repairs quit DU and restart.
If DU reports errors Repair again and again until DU reports disk is repaired.
When you are finished with DU, from the Menu Bar, select Utilities/Startup Manager.
Select your start up disk and click Restart
If you cannot boot from your install disk, try booting in Safe Mode
Make sure you have sufficient disk space.
Right or control click the MacintoshHD icon. Click Get Info. In the Get Info window you will see
Capacity and Available. Make sure you always have a minimum of 10% to 15% free disk space at all times.
Carolyn