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.

El Capitan Losing Sharing Permissions Between Reboots

I am having an issue that when I reboot the my 2010 Mac Pro, and log back in as my user the 3 permission check boxes I have selected under the sharing panel in system preferences become unchecked. They are: Screen Sharing, File Sharing, and Remote Login. They stay checked if I just log off and back on.

This behavior started to occurred when I had to manually restore the data on the system hard drive when it had some unfixable sectors. Since the repair, everything else appears to be working okay now except this last issue. Since then I have upgraded to the newer versions of El Capitan as released, and I am currently on the latest release.

I have checked the file permissions in my user folder and as far as I can tell everything looks correct.

All the other preferences like firewall for example are sticking just fine.

I also have the latest release of OS X server installed. There is a file sharing preference there as well that ties into the same file sharing setting under the preference panel.

If anyone has a suggestion please let me know.

Thanks.

-Jeff-

Posted on Apr 7, 2016 3:12 PM

32 replies

cdhw

Level 4

3,588 points

Apr 9, 2016 4:35 AM in response to jeff_farandwidesw

I'm not seeing anything particularly unusual there, except:

WARNING Found KDC certificate (O=System Identity,CN=com.apple.kerberos.kdc)is missing the PK-INIT KDC EKU, this is bad for interoperability.

, which I think means you either need to get a properly signed certificate from your Kerberos admin or renew and/or change the trust settings on the one you have. Linc Davis's advice to reinstall the OS and Server may well have fixed this issue as a side-effect.

Am I correct to believe that enabling/disabling the services seems to work, e.g. you can switch on and off the file sharing service and it works as expected and the problem is that after a reboot some unseen hand has switched them off? If so, the finger of suspicion points at the launchagents/daemons failing after a restart.

Start by checking that the files in these directories:

/System/Library/LaunchDaemons/

/System/Library/LaunchAgents/

Have correct owners and permissions, i.e.:

-rw-r--r-- 1 root wheel

Then have a look at the system logs for entries relevant to sharing when you restart the server.

Linc Davis

Level 10

209,547 points

Apr 9, 2016 5:45 AM in response to jeff_farandwidesw

1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.

The test works on OS X 10.8 ("Mountain Lion") and later. I don't recommend running it on older versions of OS X. It will do no harm, but it won't do much good either.

Don't be put off by the complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.

2. If you don't already have a current backup, please back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.

There are ways to back up a computer that isn't fully functional. Ask if you need guidance.

3. Below are instructions to run a UNIX shell script, a type of program. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.

You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.

In this case, however, there are ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone who understands the code can verify what it does.

You may not be able to understand the script yourself. But variations of it have been posted on this website many times over a period of years. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message. See, for example, this discussion.

Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.

4. Here's a general summary of what you need to do, if you choose to proceed:

☞ Copy the text of a particular web page (not this one) to the Clipboard.

☞ Paste into the window of another application.

☞ Wait for the test to run. It usually takes a few minutes.

☞ Paste the results, which will have been copied automatically, back into a reply on this page.

These are not specific instructions; just an overview. The details are in parts 7 and 8 of this comment. The sequence is: copy, paste, wait, paste again. You don't need to copy a second time.

5. Try to test under conditions that reproduce the problem, as far as possible. For example, if the computer is intermittently slow, run the test during a slowdown.

You may have started up in safe mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual before running it. If you can only test in safe mode, do that.

6. If you have more than one user, and only one user is affected by the problem,, and the affected user is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.

7. Load this linked web page (on the website "Pastebin.") Press the key combination command-A to select all the text, then copy it to the Clipboard by pressing command-C.

8. Launch the built-in Terminal application in any one of the following ways:

☞ Enter the first few letters of its name ("Terminal") 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 and start typing the name.

Click anywhere in the Terminal window to activate it. Paste from the Clipboard into the window by pressing command-V, then press return. The text you pasted should vanish immediately.

9. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. If you don't know the password, or if you prefer not to enter it, just press return three times at the password prompt. Again, the script will still run.

If the test is taking much longer than usual to run because the computer is very slow, you might be prompted for your password a second time. The authorization that you grant by entering it expires automatically after five minutes.

If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.

10. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, a series of lines will appear in the Terminal window like this:

Test started

Part 1 of 4 done at: … sec
…
Part 4 of 4 done at: … sec

The test results are on the Clipboard.

Please close this window.

The intervals between parts won't be exactly equal, but they give a rough indication of progress.

Wait for the final message "Please close this window" to appear—again, usually within a few minutes. If you don't see that message within about 30 minutes, the test probably won't complete in a reasonable time. In that case, press the key combination control-C or command-period to stop it. Then go to the next step. You'll have incomplete results, but still something.

In order to get results, the test must either be allowed to complete or else manually stopped as above. If you close the Terminal window while the test is still running, the partial results won't be saved.

11. When the test is complete, or if you stopped it manually, quit Terminal. The results will have been saved to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.

At the top of the results, there will be a line that begins with the words "Start time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "close this window" message. Please wait for it and try again.

If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.

12. When you post the results, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the software that runs this website. Please post the test results on Pastebin, then post a link here to the page you created.

If you have an account on Pastebin, please don't select Private from the Paste Exposure menu on the page, because then no one but you will be able to see it.

13. When you're done with the test, it's gone. There is nothing to uninstall or clean up.

14. This is a public forum, and others may give you advice based on the results of the test. They speak for themselves, not for me. The test itself is harmless, but whatever else you do may not be. For others who choose to run it, I don't recommend that you post the test results on this website unless I asked you to.

15. The linked UNIX shell script bears a notice of copyright. Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

Apr 9, 2016 5:24 PM in response to Linc Davis

Thanks for the use of the script. Here are some of the more interesting results that:

Note: This was run with the shared settings turned on.

Kernel log

97 Apr 9 18:45:39 0x<ptr>, 0x03b205ea Intel82574L::rxFrame - mbuf allocation failed

98 Apr 9 18:45:39 0x<ptr>, 0x006205ea Intel82574L::rxFrame - mbuf allocation failed

99 Apr 9 18:45:39 0x<ptr>, 0x011805ea Intel82574L::rxFrame - mbuf allocation failed

100 Apr 9 18:45:40 0x<ptr>, 0x01c405ea Intel82574L::rxFrame - mbuf allocation failed

101 Apr 9 18:45:41 Process systemmigrationd [362] disabling system-wide I/O Throttling

102 Apr 9 18:45:41 Process systemmigrationd [362] disabling system-wide CPU Throttling

103 Apr 9 18:46:01 Process systemmigrationd [362] disabling system-wide I/O Throttling

104 Apr 9 18:46:01 Process systemmigrationd [362] disabling system-wide CPU Throttling

105 Apr 9 18:46:21 Process systemmigrationd [362] disabling system-wide I/O Throttling

106 Apr 9 18:46:21 Process systemmigrationd [362] disabling system-wide CPU Throttling

107 Apr 9 18:46:41 Process systemmigrationd [362] disabling system-wide I/O Throttling

108 Apr 9 18:46:41 Process systemmigrationd [362] disabling system-wide CPU Throttling

109 Apr 9 18:47:01 Process systemmigrationd [362] disabling system-wide I/O Throttling

110 Apr 9 18:47:01 Process systemmigrationd [362] disabling system-wide CPU Throttling

111 Apr 9 18:47:21 Process systemmigrationd [362] disabling system-wide I/O Throttling

112 Apr 9 18:47:21 Process systemmigrationd [362] disabling system-wide CPU Throttling

113 Apr 9 18:47:41 Process systemmigrationd [362] disabling system-wide I/O Throttling

114 Apr 9 18:47:41 Process systemmigrationd [362] disabling system-wide CPU Throttling

115 Apr 9 18:51:58 Process launchd [1] disabling system-wide I/O Throttling

116 Apr 9 18:51:58 Process launchd [1] disabling system-wide CPU Throttling

117 Apr 9 18:55:32 IO80211ControllerMonitor::configureSubscriptions() failed to add subscriptionIO80211Controller::start _controller is 0x5a9dfeae95c3066d, provider is 0x5a9dfeae95ae906d

118 Apr 9 18:55:34 ** GPU Hardware VM is disabled (multispace: disabled, page table updates with DMA: disabled, non-contiguous VRAM: disabled)

119 Apr 9 18:55:47 0x1face000, 0x00000000 Intel82574L::timeoutOccurred - no link - reset the chipset once

120 Apr 9 19:12:03 hfs_clonefile: cluster_read failed - 34

121 Apr 9 19:20:12 hfs_clonefile: cluster_read failed - 34

122

123 System log

124

125 4 SystemConfiguration 0x00007fff9a3d0faf rlsPerform + 184

126 5 SystemConfiguration 0x00007fff9a3e43ab __SCDynamicStoreSetDispatchQueue_block_invoke_2 + 52

127 6 libdispatch.dylib 0x00007fff9c02693d _dispatch_call_block_and_release + 12

128 7 libdispatch.dylib 0x00007fff9c01b40b _dispatch_client_callout + 8

129 8 libdispatch.dylib 0x00007fff9c02003b _dispatch_queue_drain + 754

130 9 libdispatch.dylib 0x00007fff9c026707 _dispatch_queue_invoke + 549

131 10 libdispatch.dylib 0x00007fff9c01ed53 _dispatch_root_queue_drain + 538

132 11 libdispatch.dylib 0x00007fff9c01eb00 _dispatch_worker_thread3 + 91

133 12 libsystem_pthread.dylib 0x00007fff92ad74de _pthread_wqthread + 1129

134 13 libsystem_pthread.dylib 0x00007fff92ad5341 start_wqthread + 13

135 Apr 9 19:21:46 symptomsd: -[NWInterface initWithInterfaceName:] nw_interface_create_with_name(iptap0) failed, dumping backtrace:

136 [x86_64] libnetcore-583.50.1

137 0 libsystem_network.dylib 0x00007fff9746dde9 __nw_create_backtrace_string + 123

138 1 Network 0x00007fff9f734f46 -[NWInterface initWithInterfaceName:] + 226

139 2 SymptomEvaluator 0x00007fff9db0f2fc config_callback + 874

140 3 SystemConfiguration 0x00007fff9a3d0faf rlsPerform + 184

141 4 SystemConfiguration 0x00007fff9a3e43ab __SCDynamicStoreSetDispatchQueue_block_invoke_2 + 52

142 5 libdispatch.dylib 0x00007fff9c02693d _dispatch_call_block_and_release + 12

143 6 libdispatch.dylib 0x00007fff9c01b40b _dispatch_client_callout + 8

144 7 libdispatch.dylib 0x00007fff9c02003b _dispatch_queue_drain + 754

145 8 libdispatch.dylib 0x00007fff9c026707 _dispatch_queue_invoke + 549

146 9 libdispatch.dylib 0x00007fff9c01ed53 _dispatch_root_queue_drain + 538

147 10 libdispatch.dylib 0x00007fff9c01eb00 _dispatch_worker_thread3 + 91

148 11 libsystem_pthread.dylib 0x00007fff92ad74de _pthread_wqthread + 1129

149 12 libsystem_pthread.dylib 0x00007fff92ad5341 start_wqthread + 13

150

151 launchd log

152

153 Apr 9 18:38:08 com.apple.airplaydiagnostics.server: Unrecognized MachService property: ResetAtClose

154 Apr 9 18:39:31 com.apple.xpc.launchd.user.domain.501.100011.Aqua: Could not import service from caller: path = /System/Library/LaunchAgents/com.apple.CommCenter-osx.plist, caller = loginwindow.116, error = 138: Service cannot be loaded on this hardware

155 Apr 9 18:39:31 com.apple.xpc.launchd.user.domain.501.100011.Aqua: Could not import service from caller: path = /System/Library/LaunchAgents/com.apple.FirmwareUpdateHelper.plist, caller = loginwindow.116, error = 138: Service cannot be loaded on this hardware

156 Apr 9 18:40:18 com.apple.xpc.launchd.user.domain.501.100011.Aqua: Could not import service from caller: caller = otherbsd.469, service = com.apple.photostream-agent, error = 119: Service is disabled

157 Apr 9 18:40:38 com.apple.xpc.launchd.user.domain.264.100018.Aqua: Could not import service from caller: path = /System/Library/LaunchAgents/com.apple.CommCenter-osx.plist, caller = loginwindow.577, error = 138: Service cannot be loaded on this hardware

158 Apr 9 18:40:38 com.apple.xpc.launchd.user.domain.264.100018.Aqua: Could not import service from caller: path = /System/Library/LaunchAgents/com.apple.FirmwareUpdateHelper.plist, caller = loginwindow.577, error = 138: Service cannot be loaded on this hardware

159 Apr 9 18:40:41 com.apple.xpc.launchd.user.domain.264.100018.Aqua: Could not import service from caller: caller = otherbsd.654, service = com.apple.photostream-agent, error = 119: Service is disabled

160 Apr 9 18:41:33 com.apple.xpc.launchd.user.domain.264.100024.Aqua: Could not import service from caller: path = /System/Library/LaunchAgents/com.apple.CommCenter-osx.plist, caller = loginwindow.761, error = 138: Service cannot be loaded on this hardware

161 Apr 9 18:41:33 com.apple.xpc.launchd.user.domain.264.100024.Aqua: Could not import service from caller: path = /System/Library/LaunchAgents/com.apple.FirmwareUpdateHelper.plist, caller = loginwindow.761, error = 138: Service cannot be loaded on this hardware

162 Apr 9 18:41:34 com.apple.xpc.launchd.user.domain.264.100024.Aqua: Could not import service from caller: caller = otherbsd.779, service = com.apple.photostream-agent, error = 119: Service is disabled

163 Apr 9 18:49:47 com.apple.xpc.launchd.domain.system: Could not read path: path = //System/Library/LaunchAgents/com.apple.mrt.uiagent.plist, error = 2: No such file or directory

164 Apr 9 18:49:47 com.apple.xpc.launchd.domain.system: Could not read path: path = //System/Library/LaunchDaemons/com.apple.mrt.plist, error = 2: No such file or directory

165 Apr 9 18:51:47 com.apple.xpc.launchd.domain.system: Could not read path: path = //System/Library/LaunchDaemons/com.apple.stackshot.plist, error = 2: No such file or directory

166 Apr 9 18:55:30 com.apple.airplaydiagnostics.server: Unrecognized MachService property: ResetAtClose

167 Apr 9 19:02:58 com.apple.xpc.launchd.user.domain.501.100032.Aqua: Could not import service from caller: path = /System/Library/LaunchAgents/com.apple.CommCenter-osx.plist, caller = loginwindow.703, error = 138: Service cannot be loaded on this hardware

168 Apr 9 19:02:58 com.apple.xpc.launchd.user.domain.501.100032.Aqua: Could not import service from caller: path = /System/Library/LaunchAgents/com.apple.FirmwareUpdateHelper.plist, caller = loginwindow.703, error = 138: Service cannot be loaded on this hardware

169 Apr 9 19:03:13 com.apple.xpc.launchd.user.domain.264.100036.Aqua: Could not import service from caller: path = /System/Library/LaunchAgents/com.apple.CommCenter-osx.plist, caller = loginwindow.794, error = 138: Service cannot be loaded on this hardware

170 Apr 9 19:03:13 com.apple.xpc.launchd.user.domain.264.100036.Aqua: Could not import service from caller: path = /System/Library/LaunchAgents/com.apple.FirmwareUpdateHelper.plist, caller = loginwindow.794, error = 138: Service cannot be loaded on this hardware

171 Apr 9 19:03:14 com.apple.xpc.launchd.user.domain.264.100036.Aqua: Could not import service from caller: caller = otherbsd.815, service = com.apple.photostream-agent, error = 119: Service is disabled

172 Apr 9 19:03:50 com.apple.xpc.launchd.user.domain.501.100032.Aqua: Could not import service from caller: caller = otherbsd.759, service = com.apple.photostream-agent, error = 119: Service is disabled

173 Apr 9 19:12:56 com.apple.xpc.launchd.domain.system: Could not read path: path = //System/Library/LaunchDaemons/com.apple.rpmuxd.plist, error = 2: No such file or directory

Thanks.

-Jeff-

Linc Davis

Level 10

209,547 points

Apr 9, 2016 5:47 PM in response to jeff_farandwidesw

You're free to do as you wish with the report, of course, but I can't comment on it unless I see the whole thing.

Apr 10, 2016 2:18 AM in response to cdhw

The folders you mentioned had the correct permissions.

I did clean up a bunch of permissions under the /private folder, but this also has not changed the behavior. For whatever reason the system seems come to life faster now after I login.

I have not seen any sharing errors in the log.

Thanks.

-Jeff-

cdhw

Level 4

3,588 points

Apr 10, 2016 3:34 AM in response to jeff_farandwidesw

My guess is that your attempt to repair the bad disk and then 'manually restore' your files hasn't gone as well as you thought. In your position I would replace the disk and perform a clean install from scratch and making sure not to reimport bad data or settings.

If you want to continue playing whack-a-mole, you could try starting and stopping file sharing with these commands:

sudo serveradmin start smb

sudo serveradmin start afp

sudo serveradmin stop smb

sudo serveradmin stop afp

and see whether the state persists across reboots. If it doesn't then my guess is that something is interfering with the the autolaunch process at startup. If you have an installation with random wrong ownership and permissions all over the place, however, you're wasting your time and a clean installation is going to be the way to go.

Apr 10, 2016 3:45 AM in response to cdhw

I'm pretty confident that all the permissions are good now, I did a very thorough comparison with one of my other machines. Other than this 1 issue, everything else is working fine, so I don't see myself do a clean install for this. I rarely restart the machine anyway so this issue is not that big of a deal. However with that said, I am still going to put a little more effort into troubleshooting. I'll try your suggestion. I find when dealing with problems you end up learning a bunch of things a long the way so I don't see it as a waste of time.

Thanks.

-Jeff-

Apr 10, 2016 4:02 AM in response to Linc Davis

I did a fresh run. Here is the link: http://pastebin.com/2stQzGhh

Thanks.

-Jeff-

Apr 10, 2016 4:36 AM in response to cdhw

After making sure smb and afp were running before reboot, they were stopped when the system came back up. When I manually enabled sharing through the preferences pane, the 2 services started.

Thanks.

-Jeff-

Linc Davis

Level 10

209,547 points

Apr 10, 2016 5:14 AM in response to jeff_farandwidesw

I'm sorry, but you're running pre-release software intended only for testing, not for production, and also breaking the non-disclosure agreement that you accepted as a condition of receiving that software. Please report your results through the channel that was provided to you when you registered as a beta tester.

If you want stability and good performance, use the release version of OS X.

Apr 10, 2016 5:17 AM in response to Linc Davis

This was happening under 10.11.4 as well. And I had reverted back since with the same issue.

Thanks.

-Jeff-

Linc Davis

Level 10

209,547 points

Apr 10, 2016 6:01 AM in response to jeff_farandwidesw

The only safe way to revert is to erase the startup volume and restore everything from a backup that predates the beta installation. If that's what you did, please do it again now and then run the test. Otherwise, you'll have to wait until 10.11.5 is released, and I don't know when that will be.

Apr 10, 2016 8:14 PM in response to jeff_farandwidesw

I have resolved the issue. I found some more permissions that were not correct. After scanning through what I believe to be ALL the files now and fixing the permissions, the 3 shared settings are now kept on during reboots.

cdhw was onto the issue where the launchd service was not apparently starting for those particular functions.

Thank you cdhw and Linc Davis for assisting in my problem.

-Jeff-

Mxi

Level 1

8 points

Apr 10, 2016 11:41 PM in response to jeff_farandwidesw

Hi,

Could you please tell me what you did to fix it?

Thanks

Mat

Apr 11, 2016 2:31 PM in response to Mxi

The key to solving my issue were making sure the file owner permissions were correct. All the read and write permissions were okay, it was the actual owner permissions of the files. A lot of find by owner and change owner commands. Luckily I have another Mac I was able to use as a comparison for the correct values. I am not sure which file(s) was the key to my issue, but I believe it was related to something under the /private/var folder. For me it was a good exercise since I corrected all of the file owner settings, not just the ones related to my problem. Hope this helps you some.

-Jeff-

El Capitan Losing Sharing Permissions Between Reboots