Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Need help with understanding Console code

Having trouble with Processing application.

It worked fine all day, now suddenly does not launch.

Uninstalled (by dragging it to trash)/Reinstalled


Early 2008 Mac Pro, 10.7.5


If I knew which section to reveal in console to identify the problem, I could share that code so someone could help me pinpoint what's wrong.

Any help will be appreciated.

Mac Pro

Posted on Jun 10, 2013 4:36 PM

Reply
58 replies

Jun 14, 2013 1:28 PM in response to Linc Davis

Tried the suggested script:

open $TMPDIR../C


again and this time, got a folder that popped up named C that had lots of other folders inside.

I deleted all of them, shut down, restarted, tried to open the application and it failed.


Here is the output of: ls -@Oaen $TMPDIR.. | open -f -a TextEdit


total 16

drwxr-xr-x 6 501 20 - 204 Jun 14 16:19 .

drwxr-xr-x 3 0 0 - 102 Jan 16 17:12 ..

-rw-r--r--@ 1 501 20 - 6148 Jun 14 16:15 .DS_Store

com.apple.FinderInfo 32

drwxr-xr-x 3 501 20 - 102 May 19 10:10 0

drwx------ 12 501 20 - 408 Jun 14 16:23 C

drwx------ 7 501 20 - 238 Jun 14 16:23 T

Jun 14, 2013 5:04 PM in response to LisaK442

Back up all data to at least two different storage devices.


Boot into Recovery mode, launch Disk Utility, and erase the startup volume. This operation will destroy all data on the volume, so you had be better be sure of your backups. Quit Disk Utility and install OS X. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade, so make a note of those before you begin.


When you reboot, you'll be prompted to go through the initial setup process. That’s when you transfer the data from one of your backups. For a walkthrough, see here:


Using Setup Assistant


Don't transfer the Guest account, if it was enabled on the old system.

If you installed the Java runtime distributed by Apple and still need it, you'll have to reinstall it.

Jun 14, 2013 6:40 PM in response to LisaK442

I'm making the recommendation because the only theory I can think of that fits the facts you've stated is that there's a corrupt sector on your boot volume. Erasing it and restoring the data would most likely fix that, unless the drive is on the verge of total failure (which it might be.)


It's also possible that I'm completely wrong and that the suggested action will be a waste of time.

Jun 14, 2013 8:17 PM in response to LisaK442

when a drive has a Bad Block, the drive controller knows this, and marks that Block for replacement with a spare from the spares pool. It makes a note of that and sometimes reflects that in the SMART Status, but often not until several blocks are Bad.


A Bad Block cannot be replaced until new data are available to be written to that Block. If the Block is still bad after re-write with new data, the drive controller will substitute a nearby replacement block, and make a permanent substitution for that block number.


So Linc Davis' suggestion of erasing and re-Installing Mac OS X and your data will cause it to have all good blocks by the time you are done, unless the drive has many Bad Blocks. And the image of Mac OS X will be a clean one.


A technician in a professional situation is likley to simply replace the drive with a new one and do that same re-install and a restore -- exactly what you would do minus the new drive. He does not have time for a surface scan for Bad Blocks, which takes hours and is often inconclusive.


This is not necessarily superior. He cannot take the risk of spending hours on this problem only to find the drive must be replaced anyway. So the "Pro" in this situation is almost forced to take the more extreme course of action, because it is guaranteed to work.


He may hand you back the old drive and suggest you erase it and use it for backups, as it is not dead, it is just four hours end-to-end to check, and four more to re-write.

Jun 26, 2013 5:39 AM in response to Grant Bennet-Alder

Took my Mac Pro in to service provider with the information posted on this discussion.

He did his own diagnostics and determined that the Home directory was corrupt, causing Processing failure to launch. He created a new account, migrated everything from the old Home into that new account, then created a new Home and put everything back into the new Home. Processing is now working.


Again, I appreciate very much the help posted in this discussion.

Best wishes

Need help with understanding Console code

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.