Now that we have an actual error code to work with, a quick Google search reveals that this error is caused by missing files in the installation. This appears to be our culprit! Step 3: Find the Solution Furthermore, toward the end of each block, I'm seeing a consistent message: Since I've run the updater several times to try and get it to work, I'm noticing similar blocks of log material being repeated. Since we've found the log we need, we can browse through it and try to make sense of what our problem is. Sure enough, there's a listing for Adobe near the top, and if we click on the disclosure triangle we can see a few different entries, including one for “Adobe Acrobat Updater.log”. To do this, we'll use the sidebar to look in “~/Library/Logs”. Since we know that the error has something to do with Adobe, we can drill down in the Console to logs that pertain to Adobe's software rather than having to weather the barrage of messages that the “All Messages” view offers us. Google searches for those generic errors have turned up nothing, so are we out of luck? Of course not - Console to the rescue! Step 1: Narrow Down the Search The issue is with Adobe Updater, which has spontaneously stopped updating my copy of Acrobat, offering only vague indications that updates could not be completed.
Since the swiftest way to learn is a trial by fire, let's try and find the root cause of a problem I'm having on my computer. If you're toying with the Console, then chances are you're trying to diagnose an issue with your computer.
On the other hand, “ReportCrash” is OS X's crash reporter and “backupd” is Time Machine, so not everything is incomprehensible. Most of us probably wouldn't expect a name like “mdworker” to refer to the Spotlight process, but it does. The actual process names tend to be fairly obscure. This indicates that the message shown is only a smaller part of a more extensive report, and clicking the icon will open the full text in your text editor. Occasionally, you will also see a small paperclip icon on the far right end of a log message. The anatomy of a Console message: a timestamp, the process or app, and the message itself. The interface is built around the central section where the actual log messages appear, with some basic tools available along the top and a sidebar that you can open or close using the Show/Hide Log List button located in the top left corner. However you call it up, the Console will open to a bewildering list of messages. Alternatively, you could use your Command+Space shortcut to call up Spotlight and begin typing ‘Console' to access it. An Open BookĪccessing the Console app is as easy as opening it from the Applications > Utilities folder. The Console is, at heart, a log viewer, but it packs in some extra features that make sifting through the vast amounts of data more manageable. Not only that, but it makes these records available to you and helps you make use of them to understand what might be going wrong with the system.
Sure, you may write daily missives on the significant things in your life, but your Mac has you beat: it keeps a record of everything it ever does - literally. We'll walk you through what it is and how to use it, so you can become a master at diagnosing your computer's ailments.įun fact: your computer is more diligent about keeping a journal than you are. As operating systems become more advanced, this becomes increasingly challenging, so it's a good thing that OS X includes a handy utility called the Console. The hardest part of fixing a computer problem is often identifying its cause.
0 kommentar(er)
