I bfu'd a machine to daily.620 and had a bunch of services die.  The
interesting thing was the following message from svc.startd:

Jun 20 19:39:32 svc.startd[100004]: failed to abandon contract 50: Permission 
denied

This was well before any login prompt showed up.  After the login
prompt showed up 'ctstat -a | grep 50' didn't show anything.  Looking
at 'svcs -xv' the time of failure uniquely lines up with when
svc:/network/linkmgmtd:default was put into maintenance for "Restarting
too quickly".  Thats not completely suprising as I bfu'd from a project
specific gate that was a new service in certainly creating a bit of a
mess.

The thing that suprised me was the EPERM message.  svc.started created
it but couldn't destroy it?

Maybe I'm just too far out in the weeds given the mixed bits to expect
sanity.

Some info after my signature.

                mph

Rebooting with command: boot                                          
Boot device: /pci at 1c,600000/scsi at 2/disk at 0,0:a  File and args: 
SunOS Release 5.11 Version onnv-gate:2007-06-20 64-bit
Copyright 1983-2007 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
DEBUG enabled
misc/forthdebug (505824 bytes) loaded
Hardware watchdog enabled
Hostname: cag-v240a
Configuring devices.
Jun 20 19:39:17 svc.startd[100004]: svc:/network/physical:nwam: Method or 
service exit timed out.  Killing contract 9.
Jun 20 19:39:17 svc.startd[100004]: network/physical:nwam failed: transitioned 
to maintenance (see 'svcs -xv' for details)
NIS domain name is mpklab.sfbay.sun.com
Configuring devices.
Loading smf(5) service descriptions: 1/2Jun 20 19:39:32 svc.startd[100004]: 
network/linkmgmtd:default failed repeatedly: transitioned to maintenance (see 
'svcs -xv' for details)
Jun 20 19:39:32 svc.startd[100004]: failed to abandon contract 50: Permission 
denied
2/2
/dev/rdsk/c0t0d0s7 is clean

cag-v240a console login:

[...]

# grep abandon /var/adm/messages
# svcs -xv
svc:/network/physical:nwam (physical network interface autoconfiguration)
 State: maintenance since Wed Jun 20 19:39:17 2007
Reason: Method failed.
   See: http://sun.com/msg/SMF-8000-8Q
   See: man -M /usr/share/man -s 1M nwamd
   See: http://opensolaris.org/os/projects/nwam/
   See: http://opensolaris.org/os/projects/nwam/phase0/
   See: /etc/svc/volatile/network-physical:nwam.log
Impact: 5 dependent services are not running:
        svc:/milestone/network:default
        svc:/network/shares/group:default
        svc:/network/shares/group:zfs
        svc:/network/ipfilter:default
        svc:/network/ssh:default

svc:/network/physical:default (physical network interfaces)
 State: disabled since Wed Jun 20 19:37:52 2007
Reason: Disabled by an administrator.
   See: http://sun.com/msg/SMF-8000-05
   See: man -M /usr/share/man -s 1M ifconfig
Impact: 5 dependent services are not running:
        svc:/milestone/network:default
        svc:/network/shares/group:default
        svc:/network/shares/group:zfs
        svc:/network/ipfilter:default
        svc:/network/ssh:default

svc:/system/webconsole:console (java web console)
 State: maintenance since Wed Jun 20 19:44:56 2007
Reason: Start method died on Killed (9).
   See: http://sun.com/msg/SMF-8000-KS
   See: man -M /usr/share/man -s 1M smcwebserver
   See: /var/svc/log/system-webconsole:console.log
Impact: This service is not running.

svc:/network/linkmgmtd:default (data-link management daemon)
 State: maintenance since Wed Jun 20 19:39:32 2007
Reason: Restarting too quickly.
   See: http://sun.com/msg/SMF-8000-L5
   See: man -M /usr/share/man -s 1M linkmgmtd
   See: /etc/svc/volatile/network-linkmgmtd:default.log
   See: /var/svc/log/network-linkmgmtd:default.log
Impact: This service is not running.

svc:/application/cde-printinfo:default (CDE Print Viewer)
 State: offline since Wed Jun 20 19:39:56 2007
Reason: Start method is running.
   See: http://sun.com/msg/SMF-8000-C4
   See: man -M /usr/dt/share/man -s 1M dtprintinfo
   See: /var/svc/log/application-cde-printinfo:default.log
Impact: This service is not running.
# ctstat | grep 50





Reply via email to