general/entity_stability astring Evolving general/single_instance boolean true start/exec astring /opt/SUNWappserver/sbin/asadmin\ start-domain\ --user\ admin\ --passwordfile\ /opt/SUNWappserver/domain1_passwd\ --domaindir\ /var/opt/SUNWappserver/domains\ domain1 start/group astring :default start/limit_privileges astring :default start/privileges astring basic start/project astring :default start/resource_pool astring :default start/stability astring Evolving start/supp_groups astring :default start/type astring method start/use_profile boolean false start/user astring appservd start/working_directory astring :default start/timeout_seconds count 0 stop/exec astring /opt/SUNWappserver/sbin/asadmin\ stop-domain\ --domaindir\ /var/opt/SUNWappserver/domains\ domain1 stop/group astring :default stop/limit_privileges astring :default stop/privileges astring :default stop/project astring :default stop/resource_pool astring :default stop/stability astring Evolving stop/supp_groups astring :default stop/type astring method stop/use_profile boolean false stop/user astring appservd stop/working_directory astring :default stop/timeout_seconds count 0 tm_common_name/C ustring Appserver\ Domain\ Administration\ Server tm_man_Appserver/manpath astring /opt/SUNWappserver/appserver/man tm_man_Appserver/section astring 1 tm_man_Appserver/title astring Appserver
Thanks, Greg Tony Nguyen wrote: > Greg Asselin wrote: >> Hi, >> >> I have an SMF manifest to start / stop the DAS (Sun Application >> Server 8.1 EE). >> >> The DAS is quite large, and as a result takes ~43 min to start. >> The SMF manifest is attached below. Executing "svcadm enable das" >> result in the service going into maintenance after 20 min, but the >> DAS does still starts after 43min. >> So even though the DAS does get started successfully in 43 min, SMF >> shows the following. # svcs | grep das >> # maintenance 1:40:10 svc:/application/das:default >> >> I have also tried "svcadm enable -s das" with the same result. In >> addition I have tried -1 in the manifest instead of 0 for >> timeout_seconds. >> >> The service log is also attached below. (Note: stop gets called by >> SMF after 20 (It seems to timeout) but the das is still starting) >> >> What is needed to correct this? >> > Interesting since setting timeout_seconds should do it. Did you > re-import the service after changing timeout_seconds value? What does > 'svcprop application/das' report when you change timeout_seconds? > > -tony >
