unable to shutdown solaris 10

alienkidmj12 · February 25, 2010, 5:14pm

hi folks, i have a snag, when i attempt shutdown of solaris 10 on a sunfire v240 it seems to pause for ages, and goes no further, im busy learning my way around the system so please be patient.

/etc(R)-bash-3.00$ init 6
/etc(R)-bash-3.00$ svc.startd: The system is coming down.  Please wait.
svc.startd: 99 system services are now being stopped.

it has been like this for 10 minutes and im sure it should be faster, there are no big oracle databases or anything, although i have installed the latest patch cluster dated 12th feb without issues, not sure if its related, would think not since it went on fine.

i have also changed to bge0.conf so all my interfaces are running at 100fdx.

my system is connected via ethernet 0, although at the moment i am connected via 'console -f' as i dont think my ethernets are working correctly, i have

/(R)-bash-3.00$ ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000 
bge0: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 0.0.0.0 netmask 0 
        ether 0:14:4f:4d:d2:11 
bge1: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 3
        inet 192.168.0.34 netmask ffffff00 broadcast 192.168.0.255
        ether 0:14:4f:4d:d2:12 
bge2: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 4
        inet 192.168.0.35 netmask ffffff00 broadcast 192.168.0.255
        ether 0:14:4f:4d:d2:13 
bge3: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 5
        inet 192.168.0.36 netmask ffffff00 broadcast 192.168.0.255
        ether 0:14:4f:4d:d2:14 
/(R)-bash-3.00$

i can fix bge0 with ' ifconfig bge0 192.168.0.33 netmask 255.255.255.0 broadcast 192.168.0.255' but still does not sut down correctly.

i have recently updated wih OpenBoot 4.22.3 and alom 1.6 also, which also seemed to go smoothly.

can anyone shed any light please, i can provide logs or anyother info if required

---------- Post updated at 05:14 PM ---------- Previous update was at 05:10 PM ----------

Also, note sure if this is relevant but now im getting

 
Feb 25 21:45:01 midnight-sol inetd[3240]: Failed to bind to the port of service instance svc:/network/netbios-ssn/tcp:default, proto tcp: Address already in use
Feb 25 21:45:01 midnight-sol inetd[3240]: Too many bind failures for instance svc:/network/netbios-ssn/tcp:default, transitioning to maintenance
Feb 25 21:53:19 midnight-sol inetd[3240]: Failed to bind to the port of service instance svc:/network/netbios-ssn/tcp:default, proto tcp: Address already in use
Feb 25 21:53:19 midnight-sol inetd[3240]: Too many bind failures for instance svc:/network/netbios-ssn/tcp:default, transitioning to maintenance
Feb 25 21:54:30 midnight-sol inetd[3240]: The inetd_start method of instance svc:/network/netbios-ns/udp:default isn't a regular file
Feb 25 21:57:34 midnight-sol inetd[3240]: Failed to bind to the port of service instance svc:/network/netbios-ssn/tcp:default, proto tcp: Address already in use
Feb 25 21:57:34 midnight-sol inetd[3240]: Too many bind failures for instance svc:/network/netbios-ssn/tcp:default, transitioning to maintenance
Feb 25 21:58:17 midnight-sol inetd[3240]: Failed to bind to the port of service instance svc:/network/netbios-ssn/tcp:default, proto tcp: Address already in use
Feb 25 21:58:17 midnight-sol inetd[3240]: Too many bind failures for instance svc:/network/netbios-ssn/tcp:default, transitioning to maintenance
Feb 25 21:59:05 midnight-sol inetd[3240]: The inetd_start method of instance svc:/network/netbios-ns/udp:default isn't a regular file
Feb 25 22:02:28 midnight-sol su: 'su root' succeeded for mzqxps on /dev/pts/1
svc.startd: The system is coming down.  Please wait.
svc.startd: 98 system services are now being stopped.

DukeNuke2 · February 25, 2010, 5:22pm

cleanup your network configuration or "unplumb" all interfaces before shutdown and try again. if it works, you know it is a network issue.

alienkidmj12 · February 25, 2010, 5:30pm

can you be more descriptive on what i do here,maybe provide examples ? thanks

incredible · February 26, 2010, 4:32am

Are services commented using "#" in the /etc/services file?

alienkidmj12 · February 26, 2010, 2:33pm

hi, nothing commented out there, ive tidied up my ifconfig now, all that works, as my hostname.bge0 was not matching with the hosts file. i think the error in question started occuring when i ran inetadm -f against the inet.conf file, it seems to have changed other info which i cannot locate, im now getting

# Feb 26 19:04:23 midnight-sol inetd[348]: The inetd_start method of instance svc:/network/netbios-ns/udp:default isn't a regular file

and

 
Feb 26 19:00:23 midnight-sol /usr/lib/snmp/snmpdx: unable to get my IP address: gethostbyname(midnight-sol) failed [h_errno: host not found(1)]
Last login: Fri Feb 26 18:43:48 on console
Feb 26 19:00:24 midnight-sol last message repeated 9 times
Feb 26 19:00:24 midnight-sol svc.startd[7]: application/management/snmpdx:default failed repeatedly: transitioned to maintenance (see 'svcs -xv' for details)

my hosts file is as follows

#
# Internet host table
#
127.0.0.1       localhost loghost midnight-sol
::1     localhost
192.168.0.33    midnight-sol-net1 net1
192.168.0.34    midnight-sol-net2 net2
192.168.0.35    midnight-sol-net3 net3
192.168.0.36    midnight-sol-net4 net4

and my ifconfig now shows

lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000 
bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 192.168.0.33 netmask ffffff00 broadcast 192.168.0.255
        ether 0:14:4f:4d:d2:11 
bge1: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 3
        inet 192.168.0.34 netmask ffffff00 broadcast 192.168.0.255
        ether 0:14:4f:4d:d2:12 
bge2: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 4
        inet 192.168.0.35 netmask ffffff00 broadcast 192.168.0.255
        ether 0:14:4f:4d:d2:13 
bge3: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 5
        inet 192.168.0.36 netmask ffffff00 broadcast 192.168.0.255
        ether 0:14:4f:4d:d2:14

system still takes ages to shutdown, is there anything ican run to provide output which might help the situation ?? thanks

SysFe · February 26, 2010, 5:06pm

Can you check if there are applications active that during shutdown are stopped by "traditional" kill scripts (MQ, e.g.)?

ps -ef | grep K

Sometimes such a kill script can hang, causing the whole shutdown procedure to last forever.

DukeNuke2 · February 26, 2010, 5:08pm

don't set the hostname to the loopback adapter!

incredible · February 27, 2010, 5:48pm

2 types situations
Problem

system never respond to init 0 ,init 5 or init S
system "hangs" at some point and never seem to move

Solution
1)Use /usr/ucb/shutdown -h now to force the system to halt.
2)login via ssh, probably there will be some process or any agents like CA to hold the system from going down. Killing the process will solve it.