Error Fail To Start Cacao Agent. Scn-agent
Contents |
Allen-Oracle on Aug 14, 2012 Sometimes, through network or configuration problems, you can
Instance Name Not Found: [scn-agent]
end up with an OS where you're not sure if warning: unable to connect to java instance of the cacao agent! it has a properly configured Agent. There are a few simple things you can do to
Error: The Cacao Smf Service Config Is Not In Sync With The Cacao Config
see if an asset has an Agent, and if it does, to see if it's correctly configured to talk to a Proxy Controller. One way unable to check smf status to check is to look for the "scn-agent" SMF service. If it exists, there's an Agent on the system that has been configured. If the service is disabled, the agent isn't running, but it has been installed and configured. # svcs scn-agent STATE STIME FMRI online Aug_14 svc:/application/management/common-agent-container-1:scn-agent Another way is to run "sc-console list-connections". If the Agent is configured, this will show you the connection to the Proxy Controller. # sc-console list-connections scn-agenthttps://10.163.209.70:21165 urn:scn:clregid:
SMF service By ejannett on avr. 21, 2008 On solaris 1x the Common Agent Container is registered under SMF. Sometimes (mainly dueto user violent/wrong https://blogs.oracle.com/opscenter/entry/checking_an_agent_s_status usage of packaging) the service configuration is corrupted and trying to start CAC messages like the following ones may appear.#cacaoadm startsvcs: Pattern'svc:/application/management/common-agent-container-1:default' doesn'tmatch any instancesError when reseting SMF service maintenance https://blogs.oracle.com/ejannett/entry/problem_about_corrupt_cacao_smf state:[svc:/application/management/common-agent-container-1:default].Error when trying to start SMF service:[svc:/application/management/common-agent-container-1:default].One way to recover from that is to uninstall the package and to cleanup the repository if needed.Note that CAC configuration remains on the host across installations. Also note that operation will notsolve all possible corruptions but I hope this will help most of people facing that issueuninstall the package#pkgrm SUNWcacaortremove any stale service registrationsBe careful to only remove FMRI relative to your installation#svcs svc:/application/management/common-agent-container\\\*disabled Dec_03 svc:/application/management/common-agent-container-4:defaultdisabled Dec_03 svc:/application/management/common-agent-container-6:defaultdisabled Dec_03 svc:/application/management/common-agent-container-7:defaultdisabled Dec_03 svc:/application/management/common-agent-container-8:defaultonline Apr_02 svc:/application/management/common-agent-container-9:default#svcprop -p common-agent-container/basedir svc:/application/management/common-agent-container\\\*svc:/application/management/common-agent-container-9:default/:properties/common-agent-container/basedir astring /svc:/application/management/common-agent-container-8:default/:properties/common-agent-container/basedir astring /svc:/application/management/common-agent-container-7:default/:properties/common-agent-container/basedir astring /var/tmp/root/cac
for Nagios, Zabbix and other network monitoring and management tools. Search Forums Show Threads Show Posts Tag Search http://www.unix.com/infrastructure-monitoring/213627-agent-installation-issue-ops-center.html Advanced Search Unanswered Threads Find All Thanked Posts Go to Page... http://unix.derkeiler.com/Mailing-Lists/SunManagers/2009-04/msg00076.html linux operating commands and unix operating commands Agent Installation Issue on Ops Center Infrastructure Monitoring Thread Tools Search this Thread Display Modes #1 01-21-2013 Junaid Subhani Registered User Join Date: Aug 2012 unable to Last Activity: 3 October 2016, 10:14 PM EDT Posts: 181 Thanks: 50 Thanked 2 Times in 2 Posts Agent Installation Issue on Ops Center Hi guys . While installing the agent on an asset Solaris system: Code: root@system: /var/tmp/OC $ /opt/SUNWxvmoc/bin/agentadm configure -u root -p /var/tmp/OC/mypasswd -x 172.21.16.65 agentadm: Version 12.1.2.2161 launched with args: configure error fail to -u root -p /var/tmp/OC/mypasswd -x 172.21.16.65 Validating step : workarounds configure -u root -p /var/tmp/OC/mypasswd -x 172.21.16.65 Validating step : db configure -u root -p /var/tmp/OC/mypasswd -x 172.21.16.65 /var/run/cacao/instances/scn-agent/run/*.pid: No such file or directory Validating step : sc_console configure -u root -p /var/tmp/OC/mypasswd -x 172.21.16.65 verified sc_console command is OK Validating step : setup_hmp configure -u root -p /var/tmp/OC/mypasswd Validating step : scn_agent configure scn_agent Common Agent Container environment is OK Validating step : setup_net configure skipping setup_net step for zone VC. Validating step : uce_agent configure Validating step : config_sysconfig configure Validating step : final configure End of validation executing step : workarounds workaround configuration done. executing step : db /var/run/cacao/instances/scn-agent/run/*.pid: No such file or directory configuring db INFO: hd_domain_vc_agent_db.sh decrypted the password. Java DB creation and initialization for Domain Model successful configuring jobs db INFO: hd_jobs_vc_agent_db.sh decrypted the password. Java DB creation and initialization for job manager successful INFO: db decrypted the password. executing step : sc_console verified sc_c
that I9ve a 3communication problem2 when I try to run the web interface. Here some info and errors: -bash-3.00# uname -a SunOS node02 5.10 Generic_138888-08 sun4v sparc SUNW,SPARC-Enterprise-T5220 Sun cluster 3.2 installed Last recommended patch-cluster installed Last java patch-cluster installed -bash-3.00# /usr/cluster/bin/scstat ------------------------------------------------------------------ -- Cluster Nodes -- Node name Status --------- ------ Cluster node: node-02 Online Cluster node: node-01 Online ------------------------------------------------------------------ -- Cluster Transport Paths -- Endpoint Endpoint Status -------- -------- ------ Transport path: node-02:e1000g3 node-01:e1000g3 Path online Transport path: node-02:e1000g0 node-01:e1000g0 Path online ------------------------------------------------------------------ -- Quorum Summary -- Quorum votes possible: 1 Quorum votes needed: 1 Quorum votes present: 1 -- Quorum Votes by Node -- Node Name Present Possible Status --------- ------- -------- ------ Node votes: node-02 1 1 Online Node votes: node-01 0 0 Online -- Quorum Votes by Device -- Device Name Present Possible Status ----------- ------- -------- ------ ------------------------------------------------------------------ -- Device Group Servers -- Device Group Primary Secondary ------------ ------- --------- -- Device Group Status -- Device Group Status ------------ ------ -- Multi-owner Device Groups -- Device Group Online Status ------------ ------------- ------------------------------------------------------------------ ------------------------------------------------------------------ -- IPMP Groups -- Node Name Group Status Adapter Status --------- ----- ------ ------- ------ IPMP Group: node-02 sc_ipmp0 Online nxge3 Online IPMP Group: node-01 sc_ipmp0 Online nxge3 Online ------------------------------------------------------------------ Here the errors: -bash-3.00# svcs -xv svc:/application/print/server:default (LP print server) State: disabled since Thu Apr 23 12:36:21 2009 Reason: Disabled by an administrator. See: http://sun.com/msg/SMF-8000-05 See: man -M /usr/share/man -s 1M lpsched Impact: 2 dependent services are not running: svc:/application/print/rfc1179:default svc:/application/print/ipp-listener:default svc:/application/management/common-agent-container-1:default (Cacao, a common Java container for JDMK/JMX based management solution) State: maintenance since Thu Apr 23 14:11:48 2009 Reason: Start method failed repeatedly, last exited with status 1. See: http://sun.com/msg/SMF-8000-KS See: man -M /usr/share/ma