Skip to Main Content

Infrastructure Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

inetd-upgrade times out during first boot after live upgrade to Solaris 10

807559May 10 2005 — edited Apr 12 2007
[previously posted to Solaris 10 general, but then i realised this forum was more appropriate]
i've used live upgrade to update two sun servers from Solaris 9 to Solaris 10 3/05:
- a V1280; this went about as smoothly as anything. very easy. mind you, it doesn't run many services.

- a SunBlade 1000 which is our file/mail/NIS+/sunray server. this doesn't go well, stopping partway through the initial (re)boot process (with a few messages about inetd-upgrade timing out 3 times). after rebooting back to the old image and looking at the logs in /.alt.X/var/svc/log, this is what is in the most recently changed files:
svc.startd.log:
May 7 13:38:55/9: Ignoring svc:/TEMP/network/dns/server:default because its enabled property is misconfigured.
May 7 13:38:57/5 ERROR: Restarter: Ignoring REMOVE_INSTANCE command for unknown service svc:/TEMP/network/dns/server:default.
May 7 13:44:51/9: Ignoring svc:/TEMP/network/smtp:sendmail because its enabled property is misconfigured.
May 7 13:44:55/5 ERROR: Restarter: Ignoring REMOVE_INSTANCE command for unknown service svc:/TEMP/network/smtp:sendmail.
May 7 13:47:12/9: Ignoring svc:/system/sysidtool:net because its enabled property is misconfigured.
May 7 13:47:12/10: Ignoring svc:/system/sysidtool:net because its enabled property is misconfigured.
May 7 13:48:15/9: Ignoring svc:/TEMP/network/dns/server:default because its enabled property is misconfigured.
May 7 13:48:15/5 ERROR: Restarter: Ignoring REMOVE_INSTANCE command for unknown service svc:/TEMP/network/dns/server:default.
May 7 13:52:33/4: svc:/network/inetd-upgrade:default: Method or service exit timed out. Killing contract 36.
May 7 13:52:33/214 ERROR: svc:/network/inetd-upgrade:default: Method "/lib/svc/method/inetd-upgrade start" failed due to signal KILL.
May 7 13:52:33/214: svc:/network/inetd-upgrade:default: Increasing fault count to 1
May 7 13:56:33/4: svc:/network/inetd-upgrade:default: Method or service exit timed out. Killing contract 38.
May 7 13:56:33/214 ERROR: svc:/network/inetd-upgrade:default: Method "/lib/svc/method/inetd-upgrade start" failed due to signal KILL.
May 7 13:56:33/214: svc:/network/inetd-upgrade:default: Increasing fault count to 2
May 7 14:00:34/4: svc:/network/inetd-upgrade:default: Method or service exit timed out. Killing contract 40.
May 7 14:00:34/214 ERROR: svc:/network/inetd-upgrade:default: Method "/lib/svc/method/inetd-upgrade start" failed due to signal KILL.
May 7 14:00:34/214: svc:/network/inetd-upgrade:default: Increasing fault count to 3
i got the same first few errors in the svc.startd.log on the v1280 so i'm ignoring them; it's the inetd-upgrade timing out that i suspect is the problem.

network-inetd-upgrade:default.log
[ May 7 13:40:27 Rereading configuration. ]
[ May 7 13:48:32 Executing start method ("/lib/svc/method/inetd-upgrade start") ]
svcprop: Pattern 'network/nfs/rquota:ticlts' doesn't match any entities
svcprop: Pattern 'network/nfs/rquota:udp' doesn't match any entities
svcprop: Pattern 'network/rexec:tcp' doesn't match any entities
svcprop: Pattern 'network/rexec:tcp6' doesn't match any entities
svcprop: Pattern 'network/rpc/gss:ticotsord' doesn't match any entities
svcprop: Pattern 'network/rpc/mdcomm:tcp' doesn't match any entities
svcprop: Pattern 'network/rpc/mdcomm:tcp6' doesn't match any entities
svcprop: Pattern 'network/rpc/meta:tcp' doesn't match any entities
svcprop: Pattern 'network/rpc/meta:tcp6' doesn't match any entities
svcprop: Pattern 'network/rpc/metamed:tcp' doesn't match any entities
svcprop: Pattern 'network/rpc/metamed:tcp6' doesn't match any entities
svcprop: Pattern 'network/rpc/metamh:tcp' doesn't match any entities
svcprop: Pattern 'network/rpc/metamh:tcp6' doesn't match any entities
svcprop: Pattern 'network/rpc/rex:tcp' doesn't match any entities
svcprop: Pattern 'network/rpc/rstat:ticlts' doesn't match any entities
svcprop: Pattern 'network/rpc/rstat:udp' doesn't match any entities
svcprop: Pattern 'network/rpc/rstat:udp6' doesn't match any entities
svcprop: Pattern 'network/rpc/rusers:udp' doesn't match any entities
svcprop: Pattern 'network/rpc/rusers:udp6' doesn't match any entities
svcprop: Pattern 'network/rpc/rusers:ticlts' doesn't match any entities
svcprop: Pattern 'network/rpc/rusers:tcp' doesn't match any entities
svcprop: Pattern 'network/rpc/rusers:tcp6' doesn't match any entities
svcprop: Pattern 'network/rpc/rusers:ticotsord' doesn't match any entities
svcprop: Pattern 'network/rpc/rusers:ticots' doesn't match any entities
svcprop: Pattern 'network/rpc/spray:ticlts' doesn't match any entities
svcprop: Pattern 'network/rpc/spray:udp' doesn't match any entities
svcprop: Pattern 'network/rpc/spray:udp6' doesn't match any entities
svcprop: Pattern 'network/rpc/wall:ticlts' doesn't match any entities
svcprop: Pattern 'network/rpc/wall:udp' doesn't match any entities
svcprop: Pattern 'network/rpc/wall:udp6' doesn't match any entities
svcprop: Pattern 'network/security/krb5_prop:tcp' doesn't match any entities
svcprop: Pattern 'network/security/ktkt_warn:ticotsord' doesn't match any entities
svcprop: Pattern 'network/shell:tcp' doesn't match any entities
svcprop: Pattern 'network/shell:tcp6only' doesn't match any entities
svcprop: Pattern 'platform/sun4u/dcs:tcp' doesn't match any entities
svcprop: Pattern 'platform/sun4u/dcs:tcp6' doesn't match any entities
svc:/network/time:stream enabled
svc:/network/time:dgram enabled
svc:/network/echo:stream enabled
svc:/network/daytime:stream enabled
svc:/network/nfs/rquota:default enabled
svc:/application/x11/xfs:default will exec /usr/openwin/lib/fs.auto
svc:/application/x11/xfs:default will have an arg0 of fs
svc:/application/x11/xfs:default enabled
svc:/application/print/rfc1179:default enabled
svc:/network/rpc/gss:default enabled
svc:/network/rpc/smserver:default enabled
svc:/network/rpc/mdcomm:default enabled
tftp -> /var/svc/manifest/network/tftp-udp6.xml
Importing tftp-udp6.xml ...Done
[ May 7 13:52:33 Method or service exit timed out. Killing contract 36 ]
[ May 7 13:52:33 Method "start" failed due to signal KILL ]
[ May 7 13:52:33 Executing start method ("/lib/svc/method/inetd-upgrade start") ]
[[truncated, the rest is not interesting]]
note: the timeout for inetd-upgrade is longer (240 seconds) than usual (120 seconds) since i manually increased it; this was the third attempt at an upgrade). however, comparing the inetd-upgrade log on the v1280 it should only take a couple of seconds.

is inetd-upgrade required by some other service to complete? any ideas what could be causing it to time out?

cheers,
/lib
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on May 10 2007
Added on May 10 2005
2 comments
837 views