/var/run/name_service_door - zones stuck in single user mode
I have two Sol10 boxes - e4500 & x86. Both have multiple zones configured which have been working for quite a while. I was enabling audit logging on these machines (perzone) which required a reboot.
After a reboot, the zones won't come out of the singleuser milestone. Trying to ping the global zone by name (nsswitch is files, dns), it hangs. A truss reveals:
open64("/var/run/name_service_door", O_RDONLY) = 3
fcntl(3, F_SETFD, 0x00000001) = 0
door_info(3, 0xFF16F7A8) = 0
door_call(3, 0xFFBFD790) (sleeping...)
and hangs forever.
I threw the latest patch cluster at both and it had no effect.
Each zone has a /etc/sysidcfg, /etc/.NFS4inst_state.domain, and proper nsswitch.conf/resolv.conf that had been working (rebooting) until I tried to enable auditing. This happened a while ago and a total uninstall/reinstall of the zones fixed the issue.
offline 13:11:49 svc:/network/nfs/client:default
offline 13:11:49 svc:/system/filesystem/autofs:default
offline 13:11:49 svc:/system/system-log:default
offline 13:11:49 svc:/network/smtp:sendmail
offline 13:11:49 svc:/milestone/multi-user:default
offline 13:11:49 svc:/milestone/multi-user-server:default
offline 13:11:50 svc:/application/print/ipp-listener:default
offline 13:11:53 svc:/network/ssh:default
#svcadm milestone svc:/milestone/multi-user:default
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Root password for system maintenance (control-d to bypass):
At this point I'm not sure how to debug this issue. Any ideas?
Your panic log cites a page fault:
panic(cpu1 caller 0x001A3135): Unresolved kernel trap (CPU 1, Type 14=page fault)…
This is a common fault type, indicating the processor could not access either data memory or the next instruction to be executed. Potential causes include RAM problems, hard disk corruption, and programming errors.
The panic log you posted is incomplete, so there's not much else to say based on what you've posted. I do note some messages prior to the panic indicating M-Audio devices: you might want to check with those folks re: Mac Pro compatibility, any necessary updates, etc.
I suggest following the full set of troubleshooting steps cited in my "Resolving Kernel Panics" FAQ. The FAQ includes step-by-step instructions for identifying and resolving some of the most common causes of kernel panics. The FAQ is a roadmap: start at the beginning and work systematically through the end, i.e. the "If all else fails..." section.
Author: Troubleshooting Mac® OS X
I may receive some form of compensation, financial or otherwise, from my recommendation or link.