One of my coworkers has a system with a service in an odd state: running, disabled, no contract ID, svcadm disable hung trying to shut it down.
Here's the svcadm: UID PID PPID C STIME TTY TIME CMD root 26616 26503 0 15:05:52 pts/2 0:01 /usr/sbin/svcadm disable -st svc:/application/management/common-agent-container Here's the service's process: UID PID PPID C STIME TTY TIME CMD root 25905 1 0 15:04:25 ? 0:00 /usr/lib/cacao/lib/tools/launch -w /var/run/cacao/instances/default/run -L 1638 root 25906 25905 0 15:04:25 ? 0:47 /usr/jdk/jdk1.6.0_06/bin/java -Dsun.security.pkcs11.enable-solaris=false -Xmx10 And here is the status of the service: $ svcs -l '*cont*' fmri svc:/application/management/common-agent-container-1:default name Cacao, a common Java container for JDMK/JMX based management solution enabled false state online next_state none state_time Thu Aug 21 15:06:29 2008 restarter svc:/system/svc/restarter:default dependency require_all/none svc:/system/filesystem/local (online) dependency require_all/none svc:/network/initial (online) dependency require_all/none svc:/milestone/multi-user (online) The last few entries in the /var/svc/log file indicate that the service was cleanly started: [ Aug 21 17:04:24 Executing start method ("/usr/lib/cacao/lib/tools/scripts/cacao_smf start default"). ] [ Aug 21 17:06:29 Method "start" exited with status 0. ] Got me. Any clues? He's going to need the system back soon.