MacOS – Can anyone interpret verbose shutdown messages

macosshutdown

I almost always boot up in Verbose mode so I can see what's happening during boot up/shut down. Usually critical errors make themselves obvious, some lesser errors aren't so obvious but can be cleared up, and yet other errors aren't really errors at all and should be expected. I've fixed a bunch of things on startup, and now I'm trying to figure out messages I see on shutdown.

I'm basically just wondering if anyone can be an interpreter and tell me if any of this is bad or should not be happening, or if it all just looks normal.

Sorry for posting these messages as a photo. I'm not sure where to find a text log, if there is one:

enter image description here

It looks like there are a lot of processes that are staying alive until the system finally gives up on them and kills them all. If this is to be expected, that would be helpful to know. If not, how can I make the shut down run more smoothly?

Oh, and can anyone explain the anonymous.sudo processes? Is that okay? Where might that come from?

Thanks for any illumination you can offer!

Best Answer

It depends on each executable.

The closedown process sends a signal SIGTERM to each process and the process should then cleanup and shut itself down. This includes subprocesses and that appears to be most of the lines in your log - perhaps the parent does not shut its subprocesses down when it does, also see Unix zombie processes in wikipaedia

I would suggest that the original parent has not behaved 'properly' but probably does not matter unless there become many more zombie processes when the OS could run out of process handles.

Related Solutions

Shell or Applescript to delay shutdown

Why not just change your users' behavior on the shutdown process to make this a lot simpler (with minimal effort on scripting/programming the shutdown hook)?

Tell the users not to use the standard shutdown process (from the menu or through the keyboard shortcut) and instead use your backup AppleScript that's transformed into an app called something like SafeShutdown.app

Within the SafeShutdown app script, do the backup and then end it with a

tell application "Finder"
    shut down
end tell

or with this (will prompt for password)

do shell script "sudo shutdown -h now" with administrator privileges

or with a

tell application "System Events"
    shut down
end tell

MacOS – Mavericks Server – nothing enabled, but services still running and logging messages

Your list of active services mirrors mine on a server with only DNS running per the server app:

enabledServices =     (
    "com.apple.apspd",
    "com.apple.collabd",
    "com.apple.DeviceManagement.devicemgrd",
    "com.apple.DeviceManagement.postgres",
    "com.apple.DeviceManagement.SCEPHelper",
    "com.apple.opendirectorybackup",
    "com.apple.server.alertsd",
    "com.apple.server.eventsd",
    "com.apple.server.v2.stats",
    "com.apple.ServerEventAgent",
    "com.apple.servermgrd",
    "com.apple.disks.smart.status",
    "com.apple.xcscredd",
    "com.apple.xcscredhandler",
    "org.calendarserver.agent",
    "org.calendarserver.relocate",
    "org.isc.named"
);

In your case, the collabd should be running and it is complaining about the machine serial number. Check that your hardware serial number is in fact readable via software:

system_profiler SPHardwareDataType | grep 'Serial'

The best way to troubleshoot server when you don't trust the graphical server app (or want more details) is to use serveradmin command as opposed to the serverctl command. As you have noticed, serverctl is undocumented, so you'll want to stick with the stable serveradmin interface if at all possible.

Here's a short loop command that dumps just the running/stopped status of the various subsystems that serveradmin knows about:

for service in `sudo serveradmin list`
do
  sudo serveradmin status $service | egrep "RUNNING|STOPPED"
done

You could easily change that grep command to stop only the running services...

sudo serveradmin status $service | grep "RUNNING" && sudo serveradmin stop $service

Best Answer

Related Solutions

Shell or Applescript to delay shutdown

MacOS – Mavericks Server – nothing enabled, but services still running and logging messages

Related Question