'verify permissions' error

Hello All,
have been following the advice of the MacForums articles on upgrading from Snow Leopard to Mavericks & have so far , probably in reverse, carried out a back up to Time Machine & have just Verified my hard drive = appears ok & finally Verified Permissions where there was a reoccurring error which it fixed on Request to repair but was unable to address the following, whatever this is, outlined below ; FYI I have never as I am completely unable to use Terminal or tackled the Library folder to the affect to make changes, anyone know what the following means & is upgrading to Mavericks still on the table? I've had no issues to date & I will carry out a second back up now that the Start up disk has been Verified before proceeding & awaiting any advice that's out there.
Thanks everyone.
Kind regards,
Capo Dino
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
ps I've never used remote management, a little weird, no?

OS X Disk Utility's Repair Disk Permissions messages that you can safely ignore
It is an innocuous message you can safely ignore. It will repeat every time you repair permissions.

Similar Messages

  • Disk permissions - "Error: No Valid Packages (-9997)"

    Should I worry about this error? It shows up when I try to "verify permissions" via Disk Utility (booted from disk) and I also ran Tinker Tool System and it gave the same error.
    Thanks for the help!
    Ken

    You've either removed the /Library/Receipts/ folder or deleted its contents. Disk Utility will no longer work nor will Software Update.
    Download a shareware utility called Pacifist 2.0. Use it to extract a fresh copy of the BaseSystem.pkg from the file archives on your Tiger DVD. Extract the new copy of BaseSystem.pkg to the /Library/Receipts/ folder. If you've deleted the folder simply make a new folder with that name. In the future do not delete the folder or its contents. They are needed for permissions repair and updating software with Software Update.
    Why reward points?(Quoted from Discussions Terms of Use.)
    The reward system helps to increase community participation. When a community member gives you (or another member) a reward for providing helpful advice or a solution to their question, your accumulated points will increase your status level within the community.
    Members may reward you with 5 points if they deem that your reply is helpful and 10 points if you post a solution to their issue. Likewise, when you mark a reply as Helpful or Solved in your own created topic, you will be awarding the respondent with the same point values.

  • Updating to iTunes 11.1 gave me a lot of disk permissions errors

    I ran a Verify Disk Permissions before the installation of iTunes 11.1 and everything was clean, then I did one after installing iTunes 11.1 and I got a ton of errors. See below:
    After running repair permissions several times, running from the boot drive or from an external booted, after uninstalling and doing a fresh install, nothing changed.
    I also tried to repair the ACLs by booting from the Recovery partition and using resetpassword command.
    I know it's not very important but I like to keep my system in perfect shape.
    Come on Apple, after one single update, this is NOT SERIOUS!

    Same here. But without knowing for sure why Apple did let this messages appear, in short, you should consider them as not important...at least for now...and here is why for the ones interested in some details about the error:
    Permissions differ on “Applications/iTunes.app/Contents/Resources/Dutch.lproj/AACEncoderConfig.nib”; should be drwxr-xr-x ; they are -rwxr-xr-x .
    What this means in Unix language is that permissions check is expecting that "AACEncoderConfig.nib" to be a directory and it's not. You can tell because of "drwxr-xr-x" the d letter at the beginning of the string means "directory" and when compared with the actual value "-rwxr-xr-x", the absence of d means that it refers to a file.
    Now you might ask why is the system expecting a directory?
    Here is a link that describes why: http://support.apple.com/kb/HT1452?viewlocale=en_US&locale=en_US
    OK...but what is this kind of files .nib?
    This files are normally GUI files...and in the past...not so far away...it was based on a directory structure...but iTunes 11.1 is the first released Apple app that is using their new nib file spec. And this is somehow apparent...I mean the error messages we are all seeing when we run the permissions check suggest it.
    Then I need to add, as a guess, it looks like this is due to the coming OSX upgrade...I saw another software giving the same permissions errors and even if I cannot say which app, it's one that is heavily tested right now and it will appear on OSX Lion/Mountain Lion and the new Mavericks.
    Hope this helps!

  • Time Machine And Repair Permissions Error

    Hi.
    I have a new Intel Mac running Leopard. "Set up Assistant" worked like a charm and brought over all my preferences, iTunes, iPhoto etc. with out a hitch. Verified permissions and the disk and came up clean.
    I bought a USB LaCie 500GB external hard drive and connected it up with the idea that I would eventually use it for Time Machine.
    First thing after connecting up the new hard drive, Time Machine came up and asked if I wanted it to use the new drive as a Time Machine drive and I clicked on "cancel." Thanks to all of you I knew enough to need to GUID partition and re-format the hard drive, from the FAT 32 that it came with to Mac OS Extended (journaled) that Time Machine needs. After completing this, again, the dialog box popped up about activating Time Machine and I cancelled it again.
    I have not, yet, activated Time Machine. But running permission verify and repair yielded this error message both times: Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
    This is the same message seen on so many other people's machines and posted here when they run into problems with Time Machine. If I don't resolve this error, will I, too, have problems running Time Machine?
    This is so weird. The only thing I did between the clean permissions verification and the one with the error was connect the USB LaCie hard drive and partition and and re-format it. Time Machine has not yet been activated on this machine.
    What does this SUID warning mean? Is this something I need to worry about? Should I wait to start using Time Machine?
    Or... is this not a problem but there are other things I need to do to insure a good running of Time Machine?
    Thanks so much for any advice you can offer.-Charlotte

    The SUID is nothing to worry about.
    It is documented from Apple stating this.
    Everyone of us has that error.
    It has not bothered Time Machine from doing its thing.

  • Brand new MacBook Pro- tons of permissions errors

    So I just got a brand new MacBook Pro but am having some issues with it. I installed StarCraft 2 but will encounter a black screen that is unresponsive to anything (option-command-esc, for example), when I exit the program and once when I went to view a replay. I have to hold the power button down.
    Blizzard told me that I should try to repar my permissions. Every time I do this, however, I get the same errors and they are never fixed. I don't know if this is causing my problem but this computer is brand new and I shouldn't have all these permission errors.
    Here are the messages that I get:
    Verify permissions for “Macintosh HD”
    Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/dt.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
    Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jce.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
    Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jconsole.ja r", should be lrwxr-xr-x , they are lrw-r--r-- .
    Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/management- agent.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
    User differs on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib", should be 0, user is 95.
    Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/dt.jar", should be -rw-r--r-- , they are -rwxr-xr-x .
    Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/jce.jar", should be -rw-r--r-- , they are -rwxr-xr-x .
    Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/management -agent.jar", should be -rw-r--r-- , they are -rwxr-xr-x .
    Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/security/b lacklist", should be lrwxr-xr-x , they are lrw-r--r-- .
    User differs on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Libraries", should be 0, user is 95.
    Permissions differ on "System/Library/Java/Support/Deploy.bundle/Contents/Resources/JavaPluginCocoa.b undle/Contents/Resources/Java/deploy.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
    Permissions differ on "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk15/hpux-pa_risc2.0/libprofilerinterface.sl", should be -rw-r--r-- , they are -rwxr-xr-x .
    Permissions differ on "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk15/hpux-pa_risc2.0w/libprofilerinterface.sl", should be -rw-r--r-- , they are -rwxr-xr-x .
    Permissions differ on "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk16/hpux-pa_risc2.0/libprofilerinterface.sl", should be -rw-r--r-- , they are -rwxr-xr-x .
    Permissions differ on "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk16/hpux-pa_risc2.0w/libprofilerinterface.sl", should be -rw-r--r-- , they are -rwxr-xr-x .
    Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/dt.jar", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jce.jar", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jconsole.jar ", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/management-a gent.jar", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/dt.jar", should be lrwxr-xr-x , they are -rwxr-xr-x .
    Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/jce.jar", should be lrwxr-xr-x , they are -rwxr-xr-x .
    Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/management- agent.jar", should be lrwxr-xr-x , they are -rwxr-xr-x .
    Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/security/bl acklist", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle", should be drwxr-xr-x , they are lrwxr-xr-x .
    Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/deploy.jar", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/libdeploy.jnilib", should be -rwxr-xr-x , they are lrwxr-xr-x .
    Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
    Permissions verification complete

    I did do a search for a similar topic and I did read that some permissions are of no concern. However, like I said the guys at Blizzard said that it could be the source of the issue. Also, like I said, even if I do "repair permissions" and it says that it completes successfully, it has not really done anything. Even if I run verify permissions immediately after, I see the same problems.

  • After migrating to a new MBP, when saving or opening documents, I sometimes (but not always) get a warning such as: "Word cannot save this document due to a naming or permissions error on the destination volume." Can someone please explain?

    I recently migrated from a MBP with OS 10.6 to a MCB with OS 10.8. Some glitches are popping up. Here's the one on my mind at the moment:
    When saving or opening documents, I get a warning such as: "Word cannot save this document due to a naming or permissions error on the destination volume." Can someone please explain?

    Since this is isolated to a single file, try exporting it to Interchange Format (.inx), then open and save the resulting file as a new InDesign file.
    Since the problem occurs during export, that may not be possible. Another option to try would be to copy all elements, page by page, and "paste in place" into a new document the same size. If you used layers, be sure to enable "paste remembers layers" in the layers panel menu.
    This kind of problem is often indicative of an underlying font issue. You said there are only three fonts, and you should verify that in Type > Find Font... Try replacing, at least temporarily the fonts in use with something else that you know to be reliable from other documents. You might want to do this before the other steps.
    Peter

  • Verify permissions failed: Framework unable to communicate with the Disk Management daemon

    I'm experiencing problems with the Disk Management daemon on my MBPro Retina running Mountain Lion 10.8.2. I discovered it first when I tried to enable file vault and received the "Framework unable to communicate with the Disk Management daemon" error message.
    So I started up Disk Utilities (which started fine) and tried to run Verify Disk Permissions. It failed with the following errror message:
    "Verify permissions failed: Framework unable to communicate with the Disk Management daemon"
    So I booted in to safe mode and tried Verify Disk Permissions again with the same results.
    So I booted in to the recovery partition to run Disk Utilities. It ran fine and the Verify Disk Permissions found some errors which I then fixed.
    I re-booted normally but am still experiencing the same behavior.
    I have turned off my anti-virus (Sophos) to no effect.
    I checked the console and found the following message:
    12/6/12 3:27:02.828 PM Disk Utility[157]: *** WARNING: Method userSpaceScaleFactor in class NSWindow is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.
    Thoughts or suggestions?  Thanks!

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of the test is to determine whether your problem is caused by third-party system modifications that load automatically at startup or login. 
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:
    Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
    When you see the gray Apple logo, release the shift key.
    If you are prompted to log in, type your password, and then hold down the shift key again as you click  Log in.
    *Note: If FileVault is enabled under OS X 10.7 or later, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode. Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin. Test while in safe mode. Same problem? After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

  • Verify Permissions Results don't stick

    I'm tracing another problem and decided to check "Verify permissions" again, having done it a couple days ago.
    What I am seeing, whether or not I log in as my Admin account or as root, is that no matter that Repair permissions finishes, when I Verify Permissions immediately thereafter, the same errors exist. Here's a copy of the results:
    Verify permissions for “Macintosh HD”
    Determining correct file permissions.
    Group differs on ./Private, should be 80, group is 0
    Permissions differ on ./Private, should be drwxrwxr-x , they are drwxr-xr-x
    Permissions differ on ./private/etc/xinetd.d, should be drwxr-xr-x , they are -rwxr-xr-x
    Permissions verification complete
    The privileges have been verified or repaired on the selected volume
    Repairing permissions for “Macintosh HD”
    Determining correct file permissions.
    Group differs on ./Private, should be 80, group is 0
    Permissions differ on ./Private, should be drwxrwxr-x , they are drwxr-xr-x
    Owner and group corrected on ./Private
    Permissions corrected on ./Private
    Permissions differ on ./private/etc/xinetd.d, should be drwxr-xr-x , they are -rwxr-xr-x
    Owner and group corrected on ./private/etc/xinetd.d
    Permissions corrected on ./private/etc/xinetd.d
    Group differs on ./private, should be 0, group is 80
    Permissions differ on ./private, should be drwxr-xr-x , they are drwxrwxr-x
    Owner and group corrected on ./private
    Permissions corrected on ./private
    Permissions repair complete
    The privileges have been verified or repaired on the selected volume
    -------------------------------------------------------------------------------

    well, ok ... hen is it not an issue that despite permissions being listed as fixed, that they appear, once again, to be the same errors?
    I mean, if it's insignificant, then I'll not worry about "why" it does that ... and move on in trying to fix the original problem ... of which you are familiar anyway.
    thanks Ray.

  • Unable to verify permissions

    Hello,
    Yesterday I did a combo upgrade to 10.5.4 on a Macbook 3,1. Before doing the upgrade I attempted to verify the permissions on my hard disk but received an error.
    2008-07-15 23:13:53 -0400: Verify permissions for “Macintosh HD”
    2008-07-15 23:13:54 -0400: Reading permissions database.
    2008-07-15 23:13:54 -0400: Reading the permissions database can take several minutes.
    2008-07-15 23:13:54 -0400: Error: The underlying task reported failure on exit.2008-07-15 23:13:54 -0400:
    2008-07-15 23:13:54 -0400: Disk Utility stopped verifying permissions on “Macintosh HD” because the following error was encountered:
    The underlying task reported failure on exit.
    2008-07-15 23:13:54 -0400: Permissions verification complete
    This only takes a second to happen so I don't think the permissions are ever checked. I attempted to boot from the Install Disk and run the permissions verify from there but get the same error message. The drive verifies with no problem, but the permissions verify can not run.
    I attempted to install 10.5.4 anyway against my better judgment. Everything went fine until it attempted to write the receipt. The installer locked up solid for over an hour and I couldn't do anything but power off the machine. Luckily everything came back up with little to no issue, but I'm concerned with what I'm seeing in the install.log file.
    Jul 15 22:07:07 Fiji installdb[899]: -[IFDBD_SchemaA updateFile:uid:gid:mode:]: database error (1): SQL logic error or missing database
    Jul 15 22:07:07 Fiji /private/tmp/scripts.hRGQ/./postinstall[890]: IFDBExistingReceiptSetFilePerms() = 00000000, 1
    Jul 15 22:07:07 Fiji pkgutil[1128]: Updating receipt 'com.apple.pkg.BaseSystem' path 'System/Library/UserEventPlugins/SCMonitor.plugin/Contents/Info.plist' on '/' with actual metadata from '/System/Library/UserEventPlugins/SCMonitor.plugin/Contents/Info.plist'.
    Jul 15 22:07:13 Fiji installdb[899]: -[IFDBD_SchemaA(Utilities) pathkeyForPath:insert:] database error (1): SQL logic error or missing database
    Jul 15 22:07:13 Fiji installdb[899]: -[IFDBD_SchemaA updateFile:uid:gid:mode:]: database error (1): SQL logic error or missing database
    Jul 15 22:07:13 Fiji installdb[899]: -[IFDBD_SchemaA closeReceipt]: database error (8): attempt to write a readonly database
    Jul 15 22:07:13 Fiji /private/tmp/scripts.hRGQ/./postinstall[890]: IFDBExistingReceiptSetFilePerms() = 00000000, 1
    This is in the system.log:
    Jul 15 23:06:21 Fiji com.apple.SystemStarter[40]: The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
    Jul 15 23:06:21 Fiji com.apple.SystemStarter[40]: Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
    Most of these messages repeat over and over, so I'm a little concerned. Everything seems to be working, but because I had to restart the system during the upgrade, I'm worried something did not complete. This is the third time the system has locked up during an installation so I know something isn't correct. I've attempt to boot in to single user mode to run the fsck, but it says everything is fine and you can't use disk util to repair permissions in single user mode it seems.
    Does anyone have an idea of what these messages mean?
    thx

    Hello and thank you to all who replied.
    I wanted to give a quick update on what I found on my Macbook. I before I continue, I'm going state that I don't recommending doing what I did unless you are extremely comfortable with Unix/Linux.
    After seeing the responses that I had to reinstall the OS I got really curious to what the Mac was doing, so I called up a friend of mine who is a linux admin. I too use linux a bit, but not at his level. He recently purchased a Mac as well.
    He is new to the mac and hadn't heard of checking permissions before updates, so I explained the whole scenario. Once he understood the basics we got to work.
    What we found is, there is a permissions database on the mac located in /Library/Receipts/db called the a.receiptdb. One his new Macbook Pro the file was owned by _installer and group wheel. On my Macbook the file was owned by root and group admin.
    Changing the owner to _installer and group to wheel allowed the permission verify to run but reported some issues. Looking more deeply at the permissions, I also noticed that not only were the directory permissions for the db directory different, but also /Library/Receipts/boms directory and most of the pkg directories. The owner and groups didn't match up. Now I'm not saying mine were wrong, but they didn't match his newer install. So I changed the permissions on all of these files and re-ran the the permission verify.
    It found a ton of permissions that were not correct. On top of that it found a lot of files that were OS and Unix binaries that had been modified so it wasn't going to change the permissions on any of them. I'm guessing this happened because the combo update didn't complete properly the first time.
    After matching up the permissions, I allowed it to repair the permissions then re-installed the combo update while watching the console install.log. Everything finished with no errors. After the reboot, I ran the permission verify again, it only came back with 2 permission differences. I repaired those and was done.
    I'm still getting the:
    Jul 17 23:16:24 Fiji com.apple.SystemStarter[27]: The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
    Jul 17 23:16:24 Fiji com.apple.SystemStarter[27]: Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
    On boot up in the system.log. Apparently something is starting up and getting stuck in a loop at start up so I'll have to see what that is, but overall everything seems to be working much better. I may do a re-install just to be safe at some point, but right now everything seems fine. I just need to track down what is getting stuck on startup.
    It seems all of this was caused because the permissions were wrong on the files that verify the permissions. I'm kind of confused on why some of this is an issue because you enter your admin password before the update, which I thought meant that the installer will run as root, but that doesn't seem to be the case.
    Thx
    Message was edited by: J3P mac

  • Mail won't open, permissions error

    Under Mountain Lion, I am getting an error opening Mail:
    "Mail can’t open because you don’t have the necessary permissions to change the folder where it saves information.
    Mail stores information in /Macintosh HD/Users/cutterd/Dropbox/Mail. If this folder is on your computer, use the Get Info window in the Finder to change your permissions for this folder to “Read & Write.” If this folder is located on a network server, contact the server administrator. After your permissions are changed, open Mail again."
    I have been running this very sucessfully in Lion, and no other machines are using the files (DropBox is off right now). After install, I get the above permissions error.
    I am the owner listed on the folder, and have the correct 'read & write' permissions. I have performed both the 'restart Cmd-R and run permissions reset under the resetpassword', and the 'chmod -RN ~', with no noticable effect.
    I have a cloned machine, and can verify, it works pre 10.8 pefectly.
    Ideas?

    I had the same issue (I keep my Mail folder on a secondary HD in my MacBook since my SSD is small), and found that it requires a symlink rather than an alias to work in 10.8. A symlink is very similar to an alias but is created using the 'ln' command in the Terminal, rather than by the Finder. The command below should do what you need:
    ln -s '/Users/cutterd/Dropbox/Mail/' '/Users/cutterd/Library/Mail'
    And yes, it appears to be a bug (at least in the sense that the error message makes no sense), but it is one that is easily worked around for now.

  • Missing +x perm error after changed Dovecot partition-default

    failed: Permission denied (euid=214(_dovecot) egid=6(mail) missing +x perm: /Volumes/PEGASUS, dir owned by 0:0 mode=0770)
    This after I changed the imap:partition-default location to a directory on an external volume.
    I reviewed permission on the default location of the Server OS volume. Used chown and chgrp to match user and group permissions.
    The server works when I revert imap:partion-default to /Library/Server/Mail/Data/mail
    What is the "missing +x perm"? and the command to apply it?
    I'm thinking I need to "touch" the directory but need clarification.

    Started fresh. I recreated a directory at the root of the external volume. I created this directory as sudo via CLI. Set the permissions as _dovecot:mail with 775.
    Then I stopped Mail service via CLI. Then updated my config to point to the new directory via CLI. Then started Mail service via CLI. Verified mail_location using doveconf -n command. It was pointing to the new location. Then initiated IMAP reception of email.
    Same error message. Error occurs when mail attempts to initialize the user's mail directory: (I changed identity details within the snippet)
    imap(pid 75337 user myuser): Error: user myuser: Initialization failed: Initializing mail storage from mail_location setting failed: stat(/Volumes/PEGASUS/mailarchive/mail/6622A4BF-F9FE-4F8D-8EBB-9D080FF614FD) failed: Permission denied (euid=214(_dovecot) egid=6(mail) missing +x perm: /Volumes/PEGASUS, dir owned by 0:0 mode=0770)
    Jan 22 14:09:30 server.myclient.com log[75283]: imap(pid 75337 user myuser): Error: Invalid user settings. Refer to server log for more information.
    So then I stop mail service and change the config's mail_location to original installation default (/Library/Server/Mail/Data/mail) and no permissions errors -- incoming mail goes into the user's mail folder.
    Is the error specific to the volume /PEGASUS? and thus initialization cannot traverse the path -- gets stuck at the volume?
    Mountain Lion Server 10.8.2 First time using Mail service.

  • Permissions errors, applications not force-quitting

    hi All
    hoping someone might shed some light on this problem for me...
    for the past few weeks, at random, but usually with apple software, my system hangs. A force quit of the app (usually safari, mail, or itunes... but has been firefox a few times too?) apparently 'quits' the program, but it is still visible in my Command + TAB list, as well as having the small blue dot on its icon on the dock.
    trying to relaunch the program gives me an "error -600"
    I have run Yasu, MacJanitor, and DiscUtility to clean preferences and reset permissions (not all at once, at separate times!) however, it continues to be a pain.
    This machine USED to run for weeks without issue, now it requires a Hard Reset at least once a day...
    I have just run Disc Utility in Safe Mode, and attached the junk it spat out. it had errors, but no idea what they mean, or how to fix them...
    any help is always appreciated! thanks!!
    Verifying volume “G5 HD”
    Performing live verification.
    Checking Journaled HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Checking multi-linked files.
    Checking Catalog hierarchy.
    Checking Extended Attributes file.
    Checking volume bitmap.
    Checking volume information.
    The volume G5 HD appears to be OK.
    Verify permissions for “G5 HD”
    Reading permissions database.
    Reading the permissions database can take several minutes.
    Permissions differ on "private/var/log/secure.log", should be -rw------- , they are -rw-r----- .
    Permissions differ on "Library/Application Support/ProApps/Internal Plug-Ins/BrowserKit/iLife.bkplugin/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
    Permissions differ on "System/Library/PrivateFrameworks/BrowserKit.framework/Versions/A/CodeResources ", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/DVD.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSettings.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSources.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Movies.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Music.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Photos.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Podcasts.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/TV.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/BackRow.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/ProKit.framework/Versions/A/Resources/Leopard Panels.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Warning: SUID file "System/Library/Filesystems/AppleShare/afpLoad" has been modified and will not be repaired.
    Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired.
    Warning: SUID file "bin/rcp" has been modified and will not be repaired.
    Warning: SUID file "usr/bin/rlogin" has been modified and will not be repaired.
    Warning: SUID file "usr/bin/rsh" has been modified and will not be repaired.
    Warning: SUID file "usr/sbin/pppd" has been modified and will not be repaired.
    Warning: SUID file "usr/sbin/vpnd" has been modified and will not be repaired.
    ACL found but not expected on "Applications/Utilities".
    Permissions verification complete
    Repairing permissions for “G5 HD”
    Reading permissions database.
    Reading the permissions database can take several minutes.
    Permissions differ on "private/var/log/secure.log", should be -rw------- , they are -rw-r----- .
    Permissions differ on "Library/Application Support/ProApps/Internal Plug-Ins/BrowserKit/iLife.bkplugin/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
    Permissions differ on "System/Library/PrivateFrameworks/BrowserKit.framework/Versions/A/CodeResources ", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/DVD.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSettings.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSources.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Movies.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Music.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Photos.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Podcasts.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/TV.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/BackRow.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/ProKit.framework/Versions/A/Resources/Leopard Panels.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Warning: SUID file "System/Library/Filesystems/AppleShare/afpLoad" has been modified and will not be repaired.
    Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired.
    Warning: SUID file "bin/rcp" has been modified and will not be repaired.
    Warning: SUID file "usr/bin/rlogin" has been modified and will not be repaired.
    Warning: SUID file "usr/bin/rsh" has been modified and will not be repaired.
    Warning: SUID file "usr/sbin/pppd" has been modified and will not be repaired.
    Warning: SUID file "usr/sbin/vpnd" has been modified and will not be repaired.
    ACL found but not expected on "Applications/Utilities".
    Permissions repair complete

    OK. First, never waste your time verifying permissions or the hard drive. Just repair them. Verify does not repair anything.
    Second, your hard drive appears OK. The permissions messages are innocuous as they occur for everyone who installed a Front Row update and/or Java update. Simply put OS X replaced certain folder locations then replaced the original location with alias links to the new location. DU hasn't been fixed to reflect the change so it produces an error message related to these new links. Just ignore it.
    Third, most likely your problem is unrelated to disk or permissions repairs. What you should try is removing cache files. I can make two suggestions here:
    1. Download and install AppleJack - CNet Downloads or MacUpdate. Read the documentation carefully then follow the instructions.
    2. Download a utility such as Leopard Cache Cleaner and use it to remove system, user, and font caches. An immediate restart is then required during which the caches are rebuilt.
    3. Locate and delete the respective preference files for any applications that continue to quit unexpectedly.
    4. See the following for additional assistance:
    Apps unexpectedly quit
    Help - a program quits unexpectedly
    OS X 10.5- Some apps may unexpectedly quit after Java Update 4 is installed

  • Verify permissions Stuck

    I got in way over my head for the knowledge inside it!
    I imported a camcorder movie in imovie added audio from itunes, chapters, and edited movie. Next step was to idvd added music to opening and scene pages
    preview worked fine. used easter egg to burn disk image and then burn DVd
    Leann Rimes is the only audio and she is everywhere except in my itune folder. It is in another user itunes and had been used in last idvd project.
    looked in discussions and found advice to use Macjanitor,Preferential treatment and cache out x. did that
    Then tried verify permissions
    got internal error message
    it will not go foward
    now I am stuck reads stopped by user but will not stop
    if I try quit it tells me that it can leave the disk non-operational
    I have looked at posts about itunes and I had updated
    but I cannot run disk utility to try that fix
    any help for a drowning mac fan outthere??
    Barry
    EMAC   Mac OS X (10.3.9)  
    EMAC   Mac OS X (10.3.9)  

    my TWO apple computers are also stuck when running 1st aid-repair permissions (os-10.3.9)!! i even tried running 1st aid on one of them from the cd-rom. it reported that my hard-drive was perfectly fine (of course it was), but when i went back to my internal h.drive as startup, and ran 1st aid again, the same error message came up.
    i believe this is due to the latest i-tune software update.
    i called apple (since you can't simply e-mail them) today, 2/21.
    the tech said my telephone support had expired (yeah, i know)
    but that he would report the problem. i insisted that he make some noise about this to the appropriate dept, as i haven't installed any other programs on my computers in quite some time. PLEASE REPORT THIS TO APPLE AND LET THEM KNOW WE'RE NOT ALONE! both of my computers seem to work without a hitch, but the message- "first aid cannot connect to the disk management tool"- is pretty spooky, and could cause other problems down the road.... thanks!!

  • Remove-Item & Program Files folder: permissions error

    I am attempting to use Remove-Item to delete a file in Program Files and getting a permissions error. But, I am a local admin, and I tried running the script as administrator. I have also tried -Force, to no avail. I hope I don't have to go back to the DOS
    kludge I used in VBScript.
    Any thoughts?
    Gordon

    Well, this is odd. I tried doing it in the ISE, super simple, just Remove-Item and the raw path. Errors. But I verified that the folder in question is set to read only. So in the ISE I added -Force. And it worked.
    So I went back to my code and added -Force back in. And it worked. I assume if I misspelled it or something I would get an error, and I can't imagine the order makes any difference. May be that midnight is just a bit late to be playing in this sandbox.
    EDIT: The plot thickens. I have another folder giving me grief, but this folder actually says in Explorer that I don't have permission to view the folders permissions. this is a lame leftover folder after a (typically incomplete) Windows uninstall. Is there
    perhaps a PowerShell way of taking ownership of a folder like this? In my VBScript version I actually used DOS commands to do the deletes, and they all worked. 
    Thanks!
    Gordon

  • Can't open gifs?!  I'm getting permissions errors even though I'm the admin.  Help!

    I assume this is new since upgrading to Mavericks.  I'm having all kinds of permissions errors where if I open a file (pdf, gif, jpg, etc) even though I'm logged in as myself, and I'm the admin.  I've repaired permissions, but no errors were found.  When I click Get Info on a file, it shows that I have permission to read & write.  What?!  I'm baffled!!!

    Back up all data.
    This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
    I've tested these instructions only with the Safari web browser. If you use another browser, they may not work as described.
    Step 1
    If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box markedAllow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
    Triple-click anywhere in the following line on this page to select it:
    { sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
    Copy the selected text to the Clipboard by pressing the key combination command-C.
    Launch the Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window (command-V). I've tested these instructions only with the Safari web browser. If you use  another browser, you may have to press the return key after pasting.
    You'll be prompted for your login password. Nothing will be displayed when you type it. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
    The command may take a few minutes to run, or perhaps longer if you have literally millions of files in your home folder. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
    Step 2 (optional)
    Take this step only if you have trouble with Step 1 or if it doesn't solve the problem.
    Boot into Recovery. When the OS X Utilities screen appears, select
    Utilities ▹ Terminal
    from the menu bar. A Terminal window will open.
    In the Terminal window, type this:
    res
    Press the tab key. The partial command you typed will automatically be completed to this:
    resetpassword
    Press return. A Reset Password window will open. You’re not going to reset a password.
    Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
    Select your username from the menu labeled Select the user account if not already selected.
    Under Reset Home Directory Permissions and ACLs, click the Reset button.
    Select
     ▹ Restart
    from the menu bar.

Maybe you are looking for