OS X 10.9.4 clients won't shut down when connected to OS X Server SMB2 share

Question

Level 1

28 points

OS X 10.9.4 clients won't shut down when connected to OS X Server SMB2 share

Hi all!

I have setup a OS X 10.9 server and activated file sharing. The server hosts about 15 OS X 10.9.4 clients. The problem is, whenever the clients are connected to the server using SMB2 protocol, they do not properly shut down, they freeze forever on the grey screen that appears shortly before they (should) power off. Users must manually force power off by pressing and holding down the power button of their computers.

Console does not list any errors, the last entry prior to the forced power off is always "shutdowntime = xxxxx" which means the shutdown process actually completed successfully.

When I force the clients to connect via AFP protocol (by disabling SMB on the server or by connecting via "cmd + k" and then "afp://IP-Address" they shut down without any issue.

Can somebody help?

Thanks!

Mac mini, OS X Server

Posted on Aug 29, 2014 1:52 PM

Reply

Answer 1

Linc Davis

Level 10

209,739 points

Aug 29, 2014 2:37 PM in response to S-Tech

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

Launch the Console 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 Console in the icon grid.

Step 1

For this step, the title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES ▹ All Messages

from the log list on the left. If you don't see that list, select

View ▹ Show Log List

from the menu bar at the top of the screen.

In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter "BOOT_TIME" (without the quotes.)

Each message in the log begins with the date and time when it was entered. Note the timestamps of the BOOT_TIME log messages, which refer to the times when the system was started. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Select the messages logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.

If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.

When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Some private information, such as your name, may appear in the log. Anonymize before posting.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

Step 2

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select

View ▹ Show Log List

from the menu bar.

There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". A shutdown stall report has a name that ends in ".shutdownstall". Select the most recent of each, if any. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot. It's possible that none of these reports exists.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

Reply

Answer 2

S-Tech Author

Level 1

28 points

Aug 30, 2014 5:36 AM in response to Linc Davis

Thanks. Here is the log. Please note the last entry "SHUTDOWN_TIME" was written to the log before I manually forced power off.

30.08.14 14:22:23,000 bootlog[0]: BOOT_TIME 1409401343 0