7 Replies Latest reply: Feb 20, 2007 5:04 PM by 807559 RSS

    some services in maintenance state after reboot

    807559
      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.

      Thanks
        • 1. Re: some services in maintenance state after reboot
          807559
          What does "svcprop rpc/rstat:default" report?


          David
          • 2. Re: some services in maintenance state after reboot
            807559
            Hi David,

            Sorry for the delay in response. ldap was turned on and ldap did not have the rpc and protocol settings. I have disabled ldap for now and have to figure out how to add them.

            Thanks,
            Sunil
            • 3. Re: some services in maintenance state after reboot
              807559
              I have run into the same problem and cannot figure out how to resolve it.

              Here is what I saw during the boot process:

              May 11 21:37:59 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc/gss:default is invalid
              May 11 21:37:59 inetd[202]: Invalid configuration for instance svc:/network/rpc/gss:default, placing in maintenance
              May 11 21:38:01 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc/mdcomm:default is invalid
              May 11 21:38:01 inetd[202]: Invalid configuration for instance svc:/network/rpc/mdcomm:default, placing in maintenance
              May 11 21:38:01 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc/meta:default is invalid
              May 11 21:38:01 inetd[202]: Invalid configuration for instance svc:/network/rpc/meta:default, placing in maintenance
              May 11 21:38:02 svc.startd[7]: svc:/system/mdmonitor:default: Method "/lib/svc/method/svc-mdmonitor" failed with exit status 1.
              May 11 21:38:02 svc.startd[7]: svc:/system/mdmonitor:default: Method "/lib/svc/method/svc-mdmonitor" failed with exit status 1.
              May 11 21:38:02 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc/metamed:default is invalid
              May 11 21:38:02 svc.startd[7]: svc:/system/mdmonitor:default: Method "/lib/svc/method/svc-mdmonitor" failed with exit status 1.
              May 11 21:38:02 inetd[202]: Invalid configuration for instance svc:/network/rpc/metamed:default, placing in maintenance
              May 11 21:38:02 svc.startd[7]: system/mdmonitor:default failed
              May 11 21:38:03 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc/metamh:default is invalid
              May 11 21:38:04 inetd[202]: Invalid configuration for instance svc:/network/rpc/metamh:default, placing in maintenance
              May 11 21:38:04 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc/rstat:default is invalid
              May 11 21:38:04 inetd[202]: Invalid configuration for instance svc:/network/rpc/rstat:default, placing in maintenance
              May 11 21:38:05 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc/rusers:default is invalid
              May 11 21:38:05 louise2 inetd[202]: Invalid configuration for instance svc:/network/rpc/rusers:default, placing in maintenance
              May 11 21:38:06 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/security/ktkt_warn:default is invalid
              May 11 21:38:06 louise2 inetd[202]: Invalid configuration for instance svc:/network/security/ktkt_warn:default, placing in maintenance
              May 11 21:38:06 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/telnet:default is invalid
              May 11 21:38:06 louise2 inetd[202]: Invalid configuration for instance svc:/network/telnet:default, placing in maintenance
              May 11 21:38:07 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/nfs/rquota:default is invalid
              May 11 21:38:07 louise2 inetd[202]: Invalid configuration for instance svc:/network/nfs/rquota:default, placing in maintenance
              May 11 21:38:08 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/ftp:default is invalid
              May 11 21:38:08 louise2 inetd[202]: Invalid configuration for instance svc:/network/ftp:default, placing in maintenance
              May 11 21:38:08 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/finger:default is invalid
              May 11 21:38:08 louise2 inetd[202]: Invalid configuration for instance svc:/network/finger:default, placing in maintenance
              May 11 21:38:09 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/login:rlogin is invalid
              May 11 21:38:09 louise2 inetd[202]: Invalid configuration for instance svc:/network/login:rlogin, placing in maintenance
              May 11 21:38:09 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/shell:default is invalid
              May 11 21:38:09 louise2 inetd[202]: Invalid configuration for instance svc:/network/shell:default, placing in maintenance
              May 11 21:38:09 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/application/font/stfsloader:default is invalid
              May 11 21:38:09 louise2 inetd[202]: Invalid configuration for instance svc:/application/font/stfsloader:default, placing in maintenance
              May 11 21:38:09 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/application/x11/xfs:default is invalid
              May 11 21:38:09 louise2 inetd[202]: Invalid configuration for instance svc:/application/x11/xfs:default, placing in maintenance
              May 11 21:38:10 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc/smserver:default is invalid
              May 11 21:38:10 louise2 inetd[202]: Invalid configuration for instance svc:/network/rpc/smserver:default, placing in maintenance
              May 11 21:38:10 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/application/print/rfc1179:default is invalid
              May 11 21:38:10 louise2 inetd[202]: Invalid configuration for instance svc:/application/print/rfc1179:default, placing in maintenance
              May 11 21:38:10 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc-100235_1/rpc_ticotsord:default is invalid
              May 11 21:38:10 louise2 inetd[202]: Invalid configuration for instance svc:/network/rpc-100235_1/rpc_ticotsord:default, placing in maintenance
              May 11 21:38:11 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc-100083_1/rpc_tcp:default is invalid
              May 11 21:38:11 louise2 inetd[202]: Invalid configuration for instance svc:/network/rpc-100083_1/rpc_tcp:default, placing in maintenance
              May 11 21:38:11 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc-100068_2-5/rpc_udp:default is invalid
              May 11 21:38:11 louise2 inetd[202]: Invalid configuration for instance svc:/network/rpc-100068_2-5/rpc_udp:default, placing in maintenance
              May 11 21:38:11 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/tftp/udp6:default is invalid
              May 11 21:38:11 louise2 inetd[202]: Invalid configuration for instance svc:/network/tftp/udp6:default, placing in maintenance



              And if I run: svcprop rpc/gss:default

              #
              general/enabled boolean true
              general/entity_stability astring Unstable
              general/restarter fmri svc:/network/inetd:default
              rpcbind/entities fmri svc:/network/rpc/bind
              rpcbind/grouping astring require_all
              rpcbind/restart_on astring restart
              rpcbind/type astring service
              keyserv/entities fmri svc:/network/rpc/keyserv
              keyserv/grouping astring optional_all
              keyserv/restart_on astring none
              keyserv/type astring service
              inetd/endpoint_type astring tli
              inetd/isrpc boolean true
              inetd/name astring 100234
              inetd/proto astring ticotsord
              inetd/rpc_high_version integer 1
              inetd/rpc_low_version integer 1
              inetd/stability astring Evolving
              inetd/wait boolean true
              inetd_start/exec astring /usr/lib/gss/gssd
              inetd_start/group astring root
              inetd_start/limit_privileges astring :default
              inetd_start/privileges astring basic,!file_link_any,!proc_info,!proc_session,net_privaddr,file_chown,file_dac_read,file_dac_write
              inetd_start/project astring :default
              inetd_start/resource_pool astring :default
              inetd_start/supp_groups astring :default
              inetd_start/timeout_seconds count 0
              inetd_start/type astring method
              inetd_start/use_profile boolean false
              inetd_start/user astring root
              inetd_start/working_directory astring :default
              inetd_offline/exec astring :kill_process
              inetd_offline/timeout_seconds count 0
              inetd_offline/type astring method
              inetd_disable/exec astring :kill
              inetd_disable/timeout_seconds count 0
              inetd_disable/type astring method
              tm_common_name/C ustring Generic\ Security\ Service
              tm_man_gssd/manpath astring /usr/share/man
              tm_man_gssd/section astring 1M
              tm_man_gssd/title astring gssd
              restarter/auxiliary_state astring none
              restarter/next_state astring none
              restarter/state astring maintenance
              restarter/state_timestamp time 1147397880.430382000
              inetd_state/cur_state integer 8
              inetd_state/next_state integer 13
              #
              • 4. Re: some services in maintenance state after reboot
                807559
                What if you run "svcprop -c -p inetd_start/exec rpc/gss"?
                • 5. Re: some services in maintenance state after reboot
                  807559
                  Hi

                  I have run into the same problem and cannot figure out how to resolve it :(
                  Here is what I saw during the boot process in emergency mode..

                  WARNING: semsys:seminfo_semmni is set more than once in /etc/system. "set semsys
                  :seminfo_semmni = 5024" applied as the current setting.

                  sorry, variable 'tcp_time_wait_interval' is not defined in the 'tcp' module
                  sorry, variable 'tcp_xmit_hiwat' is not defined in the 'tcp' module
                  sorry, variable 'tcp_recv_hiwat' is not defined in the 'tcp' module

                  Feb 15 10:49:06 server01 inetd[201]: Invalid configuration for instance svc:/network/rpc/smserver:default, placing in maintenance
                  Feb 15 10:49:06 server01 inetd[201]: Property 'user' of instance svc:/application/print/rfc1179:default is missing, inconsistent or invalid
                  Feb 15 10:49:06 server01 inetd[201]: Invalid configuration for instance svc:/application/print/rfc1179:default, placing in maintenance
                  Feb 15 10:49:06 server01 automountd[416]: svc_create: cannot register 100099 vers 4 on ticotsord
                  Feb 15 10:49:06 server01 automountd[416]: unable to create service
                  Feb 15 10:49:06 server01 inetd[201]: Property 'user' of instance svc:/network/rpc-100235_1/rpc_ticotsord:default is missing, inconsistent or invalid
                  Feb 15 10:49:06 server01 inetd[201]: Invalid configuration for instance svc:/network/rpc-100235_1/rpc_ticotsord:default, placing in maintenance
                  Feb 15 10:49:07 server01 inetd[201]: Property 'user' of instance svc:/network/rpc-100083_1/rpc_tcp:default is missing, inconsistent or invalid
                  Feb 15 10:49:07 server01 inetd[201]: Invalid configuration for instance svc:/network/rpc-100083_1/rpc_tcp:default, placing in maintenance
                  Feb 15 10:49:07 server01 inetd[201]: Property 'user' of instance svc:/network/rpc-100068_2-5/rpc_udp:default is missing, inconsistent or invalid
                  Feb 15 10:49:07 server01 inetd[201]: Invalid configuration for instance svc:/network/rpc-100068_2-5/rpc_udp:default, placing in maintenance
                  Feb 15 10:49:07 server01 automountd[432]: svc_create: cannot register 100099 vers 4 on ticotsord
                  Feb 15 10:49:07 server01 automountd[432]: unable to create serviceFeb 15 10:49:07 server01 automountd[445]: svc_create: cannot register 100099 v
                  ers 4 on ticotsord
                  Feb 15 10:49:07 server01 automountd[445]: unable to create service
                  Feb 15 10:49:08 server01 automountd[458]: svc_create: cannot register 100099 vers 4 on ticotsord
                  Feb 15 10:49:08 server01 automountd[458]: unable to create service
                  Feb 15 10:49:09 server01 svc.startd[7]: system/filesystem/autofs:default failed repeatedly
                  Feb 15 10:49:12 server01 snmpXdmid: svc_tp_create: Could not register prog 100249 vers 1 on udp
                  Feb 15 10:49:12 server01 snmpXdmid: svc_tp_create: Could not register prog 100249 vers 1 on tcp
                  Feb 15 10:49:12 server01 snmpXdmid: svc_tp_create: Could not register prog 100249 vers 1 on ticlts
                  Feb 15 10:49:12 server01 snmpXdmid: svc_tp_create: Could not register prog 100249 vers 1 on ticotsord
                  Feb 15 10:49:12 server01 snmpXdmid: svc_tp_create: Could not register prog 100249 vers 1 on ticots
                  Feb 15 10:49:12 server01 snmpXdmid: Failed to register callback error = 9
                  Feb 15 10:49:12 server01 snmpXdmid: Initialization failed. Return code = 90.
                  Thu Feb 15 10:49:12 2007 fatal: Must have the "nobody" user defined
                  Feb 15 10:49:12 server01 /usr/sbin/vold[525]: Must have the "nobody" user defined

                  Thanks
                  Bala
                  • 6. Re: some services in maintenance state after reboot
                    807559
                    i have fixed the eariler problem after i got this message

                    I faced this problem after appying patch in solris 10..
                    how to fix this issue?

                    The / file system (/dev/md/rdsk/d0) is being checked.

                    WARNING - Unable to repair the / filesystem. Run fsck
                    manually (fsck -F ufs /dev/md/rdsk/d0).

                    Feb 17 12:36:00 svc.startd[7]: svc:/system/filesystem/usr:default: Method "/lib/
                    svc/method/fs-usr" failed with exit status 95.
                    [ system/filesystem/usr:default failed fatally (see 'svcs -x' for details) ]
                    Requesting System Maintenance Mode
                    (See /lib/svc/share/README for more information.)
                    Console login service(s) cannot run


                    Regards
                    Bala
                    • 7. Re: some services in maintenance state after reboot
                      807559
                      Run "fsck -F ufs /dev/md/rdsk/d0" and fix any problems.