Sunil Subrahmanyam wrote:
Hi,
I installed solaris 10 and everything ran fine for a month. I recently upgraded
memory on the server and when I rebooted, some of the services were put in the
maintenance mode.
Here is the solaris 10 release info:
bash-3.00# cat /etc/release
Solaris 10 1/06 s10s_u1wos_19a SPARC
Copyright 2005 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 07 December 2005
Here is the error during boot up
irvsun12 console login: Mar 2 11:20:42 inetd[230]: Property 'name' of instance
svc:/network/rpc/rstat:default is missing, inconsistent or invalid
Mar 2 11:20:42 inetd[230]: Invalid configuration for instance
svc:/network/rpc/rstat:default, placing in maintenance
Mar 2 11:20:42 inetd[230]: Property 'name' of instance
svc:/network/rpc/rusers:default is missing, inconsistent or invalid
Mar 2 11:20:42 inetd[230]: Invalid configuration for instance
svc:/network/rpc/rusers:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance
svc:/network/telnet:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance
svc:/network/telnet:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'name' of instance
svc:/network/nfs/rquota:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance
svc:/network/nfs/rquota:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance
svc:/network/ftp:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance
svc:/network/ftp:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance
svc:/network/finger:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance
svc:/network/finger:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance
svc:/network/login:rlogin is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance
svc:/network/login:rlogin, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance
svc:/network/shell:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance
svc:/network/shell:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance
svc:/application/x11/xfs:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance
svc:/application/x11/xfs:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance
svc:/application/print/rfc1179:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance
svc:/application/print/rfc1179:default, placing in maintenance
Any help on getting this resolved is appreciated.
Sorry, no help, just another 'me too': I observe the very same symptoms
after applying recently a bunch of patches to S10U1/SPARC, only in my
case just one service is affected (it certainly was OK and running fine
before the upgrade/reboot):
Feb 19 18:12:10 obender inetd[265]: [ID 702911 daemon.error] Property
'name' of instance svc:/site/swat:default is missing, inconsistent or
invalid
Feb 19 18:12:10 obender inetd[265]: [ID 702911 daemon.error] Property
'proto' of instance svc:/site/swat:default is missing, inconsistent or
invalid
Feb 19 18:12:10 obender inetd[265]: [ID 702911 daemon.error] Invalid
configuration for instance svc:/site/swat:default, placing in maintenance
$ inetadm -l swat
SCOPE NAME=VALUE
name="swat"
endpoint_type="stream"
proto="tcp"
isrpc=FALSE
wait=FALSE
exec="/usr/sfw/sbin/swat -d 1 -l /var/log/swatlog"
user="root"
default bind_addr=""
default bind_fail_max=-1
default bind_fail_interval=-1
default max_con_rate=-1
default max_copies=-1
default con_rate_offline=-1
default failrate_cnt=10
default failrate_interval=60
default inherit_env=TRUE
default tcp_trace=FALSE
default tcp_wrappers=FALSE
Nobody here actually uses SWAT, so the service failure is sorta totally
unimportant, but I'd like to know what's the reason for such an oddity.
--
/ynp
_______________________________________________
opensolaris-discuss mailing list
[email protected]
