DB2 Agent does not not in Foglight 5.6.4
Hi all
We have configured DB2 agent for the follow-up of the Forum of one of our DBs. we put the necessary settings in the properties of the Agent, but we are unable to obtain the measurements taken for this instance. When we check the dashboard, it shows some errors in there.
We are unable to check the logs of the apllication since we do not have access to it. The same officer agent logs.
Please provide your inputs and we share the steps to solve this problem...
Thanks & best regards,
Guenoun.
Additional accessories:
I suspect that the error is in Foglight (not the agent logs) server logs.
I suspect that you have more of a problem.
The agent log indicate a problem with the agent and the screen you have attached the problems that appear in the log file of the Foglight Server.
I recommend to view the logs of the Foglight Server too, BUT to also open a case of pension as soon as POSSIBLE because it seems you have more of a problem.
Golan
Tags: Dell Tech
Similar Questions
-
12 c on the repository server management agent does not start due to a failure of the system
My environment architecture for 12 c Cloud Control (used for the purpose of personal practice) can be explained as follows:
@DBSERVER: (OEL6.5, x 86-64)
-12 c Enterprise Manager Cloud Control (EMCC)
-Database 11.2.0.4 which acts as a repository for 12 c EMCC
Monitored host is on a virtual machine (VM12) which is currently in the DBSERVER:
VM12: (OEL6.5, x 86-64)
-12 c Management Agent which monitors host and database (12.1.0.1)
The server worked fine for months until recently when the computer has restarted abruptly. Abrupt restart has occurred several times in the past, but this time, he had a problem when restarting. The DBSERVER when a startup starts the SGC and the AGENT. WHO starts perfectly, but the AGENT does not start. On trying to start the agent, it displays the following error message:
[orcl11204g@dbserver bin] $. / emctl start agent
Oracle Enterprise Manager Cloud control 12 c Release 3
Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved.
Starting Agent... failed.
Manager of target failed to startup: targets.xml was rejected: loaded with a token incorrect agent
See emctl.log and emagent.nohup in: / home/u01/oemrel3/agent/agent_inst/sysman/log
[orcl11204g@dbserver bin] $
The targets.xml file contains the following information, which do not seem to be of any help:
[orcl11204g@dbserver emd] $ cat targets.xml
<? XML version = "1.0"? >
<>targets
< / objectives >
[orcl11204g@dbserver emd] $
Anyone can provide assistance in such circumstances?
The DBSERVER repository database, the auditor and the who are running, while the agent is down. VM12, listener and agent database is running. Is there another file that should be checked for more information?
--> $/ AGENT_INST/bin/emctl stop agent
If the agent does not stop is free then kill all the background process agent first grepping for agent perl and java process only
--> Move your existing target.xml file
MV target.xml target.xml.old
--> Create an empty file targets.xml under/AGENT_INST/sysman/MDTs with the below content
--> Start the agent of
$AGENT_INST/bin/emctl start agent
That starts agent but without all the targets in targets.xml
To the discovery of targets saw agent console resynchronization
Concerning
Krishnan
-
Hello
I have 4.0 running with Labmanager to 75VM. Recently, I changed the pwd of the ESX host root. Today, when I rebooted my server VC, (hosts & VM) evrything work properly via the server Vsphere.
But I found that the hosts are not connected in the Labmanager. His watch the X symbol in the resource-> tab-> column available hosts. All my VM in the labmanger showing not available States.
I got the following error in LAbmanager
"The vCenter Lab Manager agent on the host is not responding. Each prepared host running an agent application. This request of the agent does not respond. This may be due to the breakdown of the network, failure of the host or agent failure. "
Someone at did you encounter this problem, please provide the solution. We strive to resolve the issue as soon as POSSIBLE.
Thank you
Yohanna.
See the attached file.
-
Install the new FDMEE 11.1.2.4 - ODI Agent does not start
After the installation and configuration of EMP 11.1.2.4, components (including the FDMEE) on a Windows 2008 (single-server installation), I ran diagnosis of EPM system and found the only test that failed was to the Agent of ODI.
ODI Agent availability check: http://server1:6550 / oraclediagent
Error: com.hyperion.cis.utils.BadResponseCodeException: bad response with the GET method code: 404
Recommended action: check the application of the FDM Enterprise Edition is started and the database schemas exist.
FDMEE and all the other components of the EMP seem to work and open in the workspace. The only problem is that ODI Agent will not start. Re-installation and configuration of FDMEE has not fixed this problem. I also tried to start manually in the WebLogic administration server, but it has not started and I found the following error in ErpIntegrator0.log.
# < 18 June 2015 3:47:13 AM PDT > < error > < hats > < server1 > < ErpIntegrator0 > < ExecuteThread [ASSET]: '9' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1434624433908 > < BEA-149265 > < error has occurred in the execution of the request for deployment with the ID ' 1434624127664 'for task ' 0'. Error is: "weblogic.application.ModuleException: [HTTP:101216] Servlet: 'AgentServlet' failed by preloading at startup in a Web application: 'oraclediagent'."
com.tangosol.net.RequestTimeoutException: timeout during the startup of the service: ServiceInfo (Id = 0, name is Cluster, Type = Cluster
Set of members = MasterMemberSet)
ThisMember = null
OldestMember = null
ActualMemberSet = MemberSet (Size = 0
)
Member ID | ServiceVersion | ServiceJoined | Member State
RecycleMillis = 1200000
RecycleSet = MemberSet (Size = 0
)
)
)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:3)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:58)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:4)
at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:10)
at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:26)
at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:2)
at com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:427)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureServiceInternal(DefaultConfigurableCacheFactory.java:968)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureService(DefaultConfigurableCacheFactory.java:937)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:919)
at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:1296)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:297)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:204)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:181)
to oracle.odi.runtime.agent.coherence.OdiAgentCoherenceCache. < init > (OdiAgentCoherenceCache.java:52)
at oracle.odi.runtime.agent.servlet.AgentServlet.initCoherence(AgentServlet.java:812)
at oracle.odi.runtime.agent.servlet.AgentServlet.initializeClusterCache(AgentServlet.java:762)
at oracle.odi.runtime.agent.servlet.AgentServlet.startup(AgentServlet.java:437)
at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:250)
at javax.servlet.GenericServlet.init(GenericServlet.java:242)
to weblogic.servlet.internal.StubSecurityHelper$ ServletInitAction.run (StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
to weblogic.servlet.internal.StubLifecycleHelper. < init > (StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3155)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:487)
to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
to weblogic.application.internal.BaseDeployment$ 2.next(BaseDeployment.java:672)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:149)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
in weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$ 100 (DeploymentReceiverCallbackDeliverer.java:13)
to weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$ 2.run(DeploymentReceiverCallbackDeliverer.java:69)
to weblogic.work.SelfTuningWorkManagerImpl$ WorkAdapterImpl.run (SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
'
weblogic.application.ModuleException: [HTTP:101216] Servlet: 'AgentServlet' failed by preloading at startup in a Web application: "oraclediagent."
com.tangosol.net.RequestTimeoutException: timeout during the startup of the service: ServiceInfo (Id = 0, name is Cluster, Type = Cluster
Set of members = MasterMemberSet)
ThisMember = null
OldestMember = null
ActualMemberSet = MemberSet (Size = 0
)
Member ID | ServiceVersion | ServiceJoined | Member State
RecycleMillis = 1200000
RecycleSet = MemberSet (Size = 0
)
)
)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:3)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:58)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:4)
at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:10)
at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:26)
at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:2)
at com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:427)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureServiceInternal(DefaultConfigurableCacheFactory.java:968)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureService(DefaultConfigurableCacheFactory.java:937)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:919)
at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:1296)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:297)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:204)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:181)
to oracle.odi.runtime.agent.coherence.OdiAgentCoherenceCache. < init > (OdiAgentCoherenceCache.java:52)
at oracle.odi.runtime.agent.servlet.AgentServlet.initCoherence(AgentServlet.java:812)
at oracle.odi.runtime.agent.servlet.AgentServlet.initializeClusterCache(AgentServlet.java:762)
at oracle.odi.runtime.agent.servlet.AgentServlet.startup(AgentServlet.java:437)
at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:250)
at javax.servlet.GenericServlet.init(GenericServlet.java:242)
to weblogic.servlet.internal.StubSecurityHelper$ ServletInitAction.run (StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
to weblogic.servlet.internal.StubLifecycleHelper. < init > (StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3155)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:487)
to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
to weblogic.application.internal.BaseDeployment$ 2.next(BaseDeployment.java:672)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:149)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
in weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$ 100 (DeploymentReceiverCallbackDeliverer.java:13)
to weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$ 2.run(DeploymentReceiverCallbackDeliverer.java:69)
to weblogic.work.SelfTuningWorkManagerImpl$ WorkAdapterImpl.run (SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1520)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)
to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
to weblogic.application.internal.BaseDeployment$ 2.next(BaseDeployment.java:672)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:149)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
in weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$ 100 (DeploymentReceiverCallbackDeliverer.java:13)
to weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$ 2.run(DeploymentReceiverCallbackDeliverer.java:69)
to weblogic.work.SelfTuningWorkManagerImpl$ WorkAdapterImpl.run (SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: com.tangosol.net.RequestTimeoutException: timeout during the startup of the service: ServiceInfo (Id = 0, name is Cluster, Type = Cluster
Set of members = MasterMemberSet)
ThisMember = null
OldestMember = null
ActualMemberSet = MemberSet (Size = 0
)
Member ID | ServiceVersion | ServiceJoined | Member State
RecycleMillis = 1200000
RecycleSet = MemberSet (Size = 0
)
)
)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:3)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:58)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:4)
at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:10)
at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:26)
at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:2)
at com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:427)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureServiceInternal(DefaultConfigurableCacheFactory.java:968)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureService(DefaultConfigurableCacheFactory.java:937)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:919)
at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:1296)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:297)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:204)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:181)
to oracle.odi.runtime.agent.coherence.OdiAgentCoherenceCache. < init > (OdiAgentCoherenceCache.java:52)
at oracle.odi.runtime.agent.servlet.AgentServlet.initCoherence(AgentServlet.java:812)
at oracle.odi.runtime.agent.servlet.AgentServlet.initializeClusterCache(AgentServlet.java:762)
at oracle.odi.runtime.agent.servlet.AgentServlet.startup(AgentServlet.java:437)
at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:250)
at javax.servlet.GenericServlet.init(GenericServlet.java:242)
to weblogic.servlet.internal.StubSecurityHelper$ ServletInitAction.run (StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
to weblogic.servlet.internal.StubLifecycleHelper. < init > (StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3155)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:487)
to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
to weblogic.application.internal.BaseDeployment$ 2.next(BaseDeployment.java:672)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:149)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
in weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$ 100 (DeploymentReceiverCallbackDeliverer.java:13)
to weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$ 2.run(DeploymentReceiverCallbackDeliverer.java:69)
to weblogic.work.SelfTuningWorkManagerImpl$ WorkAdapterImpl.run (SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>
# < 18 June 2015 3:47:13 AM PDT > < error > < hats > < server1 > < ErpIntegrator0 > < ExecuteThread [ASSET]: '9' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1434624433916 > < BEA-149202 > < encountered an exception while trying to commit Task 7 for the application "oraclediagent". >
During my research of these errors, I found results indicating the problem could be related to multiple NIC cards or enforceable, but I don't know if this is the reason of my problem and how to check it. Any help would be appreciated!
In your case, it seems that the list of the WKA is formed using the IP 127.0.0.1 loopback address but consistency has bound to the IP address of 10 points. Finally, make sure that they match so that ODI Agent can start, but given that it's a DHCP box you well then that tends to add another layer of complication.
What we tend to do in support with DHCP boxes to avoid problems with name resolution is to simulate a static IP address by adding a loopback adapter (google, you can add a loopback adapter Server 2008 for instructions) with a static IP address (I often use smth like setting IPv4 10.10.10.10 (, netmask 255.255.255.0 & no gateway) then add an entry to the hosts file to map the IP address for the host name of the host name for example, 10.10.10.10
You must make sure that the host name resolution works as expected in Java according to this link as well (which I think is why we go to the "loopback hack" first place in support): https://docs.oracle.com/cd/E40248_01/epm.1112/epm_install/frameset.htm?ch06s02s01.html
I would start by looping config tbh as I remember seeing someone with a box of AWS, earlier when helping a colleague where host name resolution was not working with that tool and they had problems with the Agent of ODI.
Concerning
Craig
-
The officer declined, and now it won't start. That's what I
***************************************************************
emctl start agent
Oracle Enterprise Manager 10g Grid Control 10.2.0.4.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Starts the service of Oracleagent10gAgent...
The Oracleagent10gAgent service could not be started.
A service specific error: 2.
More help is available by typing NET HELPMSG 3547.
***************************************************************
NET HELP does not what it is.
Help, please...Remove all files from AGENT_HOME\sysman\emd\state $
$AGENT_HOME\sysman\emd\upload
Sysman\emd\log $AGENT_HOME]and to try to restart the agent. Let us know.
-
ESX does not error - Host Server Agent does not start
Hello
I got an error on one of my ESX host in VC. The message "did not".
7 VM are currently connected to this host and they seem to all run normally.
I was able to connect to the host command line, but was a bit of difficulty in processing orders, they seem to cling. (ex: vmware-cmd - l does not give me an answer...)
So I tried to restart the service mgmt-vmware:
VMware ESX Server Host Agent Watchdog
VMware ESX Server host agent
This is where to stop.
I also tried just stop the service (mgmt-vmware stop) and he still gets that far.
Are their other commands that I might be able to run to retrieve this host in the VC?
I will not re-start rather host it running production servers.
Thank you
I had this problem today with one of our ESX host. If you are running:
ps - ef | grep vmware - pass
You should see something like:
root 3545 3504 1 11:40? 00:00:12 / usr/lib/vmware/hostd/vmware-hostd /etc/vmware/hostd/config.xml u
You can kill the process of:
Kill - 9 < PID > (e.g. kill 3545-9)
Then you should be able to restart the service mgmt-vmware . In fact, if you are already trying to restart the service, he will suddenly hit by action. I do not know what causes this, but it will not affect your running virtual machines.
I hope this helps.
Ray
-
Agent does not appear in Enterprise Manager GC after having redeployed
Hello
We run Control 11g Grid.
One of my team members deployed a screening Officer Grid out on a server using the 'Installer Agent' feature in Enterprise Manager GC.
The deployment of the agent worked successfully. The host name of the target server appeared under the screen "Hosts" in the tab target GC Enterprise Manager.
Shortly after my team member has deployed the agent, he realizes that he had installed the Grid Control Agent in a home misspelled agent on the target server. He then tried to remove the agent. He did it by closing the agent and by removing the home directory of the agent on the target server. He realizes then that the removal operation was not complete, so he took the host via Enterprise Manager user interface. He did on the hosts screen tab target. He has selected the host and then choose 'delete '. There are no databases or headphones on the server target, so he could not remove these first.
He then tried to redeploy the agent. Agent deployment operation said it has successfully completed, however the host name does not appear under the screen of 'targets' em. In addition to the "history of deployment" section of EM, there is no trace of the host in the console business at all.
The agent is running on the target server. The expected ports are in use.
On the target server, I tried running
$. / emctl status agent
Oracle Enterprise Manager 11 g Release 1 control Grid 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent version: 11.1.0.1.0
Version of the WHO: 11.1.0.1.0
Protocol version: 11.1.0.0.0
Home Agent: / sv/app/oracle/gcagent/agent11g
File binary agent: / sv/app/oracle/gcagent/agent11g
Agent process ID: 15613
Parent process ID: 15583
Agent URL: http://xxxxxx:xxxx/emd/main /.
URL of repository: http://xxxxxxxxxxx:xxxxx/em/upload /.
Started at the: 2011-05-11 13:40:52
Started by user: sv_ora
Last reload: 2011-05-11 13:40:52
Last download successful: (none)
Last attempt to download: (none)
Total megabytes of XML files uploaded so far: 0.00
Number of XML, files awaiting download: 44
Size of the XML files in the upload wait (MB): 2.42
Available disk space on the file upload system: 86,33%
Last attempt heartbeat to WHO: 2011-05-11 14:05
Last pulse in SGD: unknown
These two lines are a few concerns:
"Total megabytes of XML downloaded so far: 0.00.
"Last pulse in SGD: unknown.
I was worried that no XML files have been downloaded, so I ran
* < AGENT_HOME >/bin/emctl charge agent
EMD charging completed successfully
The 'status emctl agent' reports still 0.00 MB
* I also ran < AGENT_HOME >/bin/agentca d
* We restarted < AGENT_HOME > root.sh on the target server and restart the target server.
Also, I restarted the entire SGD on our server of the grid control.
I suspect that moving original host of the marked grid host somewhere as being "removed from grid control. I think that the redeployment of the agent has not updated this record, so there is always a place marked as deleted. I just do not where it is.
Does anyone have any ideas on how to proceed from here? I am happy to download all the log files who think can be useful.Hello
Please see the article-ID "grid Agent resynchronization translates ORA-20206: target does not exist: agentmachine.domain:host" [1273737.1 ID]
MOS...The reason may be that the agent has been reinstalled on the node and that the target.xml file is not correct. You can find the file target.xml
in the directory $AGENT_HOME/sysman/emd. It might be useful to check this file because it contains all the discovered targets.But try to follow the instructions in the article mentioned ID...
Published by: VivaLaVida on 11.05.2011 08:12
-
NAC agent does not parameter of customization of the CAM download
Hello
I would use the option of additional NAC 4.8.0 Agnet.
Based on the 'Clean Access Manager Configuration Guide' is the branding.tar.gz of neccesery containing the custom nac_logo.gif, the nac_login.xml, the nac_Srings_xx.xml (in our case here in Hungary: nac_Srings_HU.xml). The package updet the cam has been successful.
However, Agents do not update themselves.
Other related settings on cam:
Option: "the current NAC Agent is a mandatory upgrade" is checked in.
I tried to put the files customized to the customer appropriate on a machine mannualy folder. After the next startup of the Agent, the changes are busy.
What could be the couse that customers don't refresh themeself automatically by the CAM/CAS.
Thank you very much
Csaba
Hi Csaba,
I confirm that the document is false, so that personalization information are only after a (re) installation of the Agent.
Allow me to connect to a documentation bug to fix this...
Thank you for this comment.
Kind regards
Federico
-
Net monitor agent works does not in Foglight
Hi all
We use 5.6.4 foglight to monitor our environment. We have the Net monitor agent for the availability of the server configured and added a few set of servers in the properties of the agent, but we do not get alerts if the server goes down even after activation of the rule "unavailability of the aircraft".
Please let us know if there anything we missed and help us solve this problem.
Thanks & best regards,
Guenoun
Do you see anything in the log file?
The last time I saw a similar problem was a looooooong time ago and it was fixed in 5.2.1
https://support.software.Dell.com/Foglight/KB/42692
See also if the AIDS article
https://support.software.Dell.com/Foglight/KB/47272
Golan
-
PS_Scheduler agent does not collect not data in Foglight 5.6.4
Hi all
We are schedular areas of NT surveillance for Peoplesoft applications. For this, we Monitor PS_Sched agent and given necessary properties in it and created PS_Schedular and PS_SchedServer agents to monitor instructions SQL and use resources.
We are facing some problems in PS_Schedular agent because it collects no data and throwing an error like "there is no way the home of Peoplesoft.
Please suggest some troubleshooting steps to resolve this problem...
Thank you best regards &,.
Guenoun
This error has to do with the database connection setting is the PS_Scheduler agent properties. Check the settings and make sure that the settings are correct. Don't know what DB platform this PS environment use, but make sure that the settings are correct by accessing the Agent status-> and change the properties of the agent for DB connection settings.
The f
-
Cisco Secure ACS 5.3 SNMP agent does not
Hello
I have problems with the SNMP on Cisco Secure ACS 5.3 agent (patch level 5) stop, is there a quick way to restart the SNMP daemon via the command line?
Robert,
I understand where you come, I encountered the following bug:
The process of the SNMP agent in demon device ACS stops.
and reboot the box will bring him back to the top and after about 3 days, he'd stop. I just want to see if it's the same bug that could be back in patch 5. The best thing to do at this stage is to plan a quick down and restart the box to see if the snmp process starts again. If this then gives IT a week to see if the snmp Protocol falls down. If it does then make reference to this bug and open a new case of tac for repair. If not, then you should be in the clear.
Thank you
Tarik Admani
-
All,
I just downloaded and deployed the following script agent. Everything seemed to be going perfect. If I navigate to the fglam > State > agent > myagent > scripts folder and run the .sh script he things seem to work as I want. I let the agent walk for an hour while I went to lunch and I still don't see anything in the model. No idea where I was wrong?
Solaris with 5.5.8.2, FMS1 5.6.5 on centOS fglam.,.
[code]
#
#! / bin/bash
#somestuff
variable #define
EIMJobStartTimeUTCTimeStampString = 0
EIMJobStartTimeDate = 0
EIMJobStartTimeTime = 0
CurrentDate = 0
#Scrape file for journal information and format it in vars
EIMJobStartTimeUTCTimeStampString = $(tête-n 1)< `ls="" -t="" pt/myawesomeapp/enterprises/prod/prod_app1/log/eim*.log="" |="" head="" -n="" 1`|="" cut="" -f="" 2,3="" -d="" '="">
EIMJobStartTimeDate = $(echo $EIMJobStartTimeUTCTimeStampString | awk '{print substr ($0, 0, 10)} ")
EIMJobStartTimeTime = $(echo $EIMJobStartTimeUTCTimeStampString | awk '{print substr ($0, 12)} ")
CurrentDate = "date".
#echo our results for the test, do not include in the cartridge
#echo $EIMJobStartTimeUTCTimeStampString
#echo $EIMJobStartTimeDate
#echo $EIMJobStartTimeTime
#Echo results in format Foglight
echo "TABLE EIM_JOB_STARTTIME"
echo 'START_SAMPLE_PERIOD '.
echo "StartTime.StringObservation.obs is"$EIMJobStartTimeUTCTimeStampString ".
echo "StartTimeDate.StringObservation.obs is"$EIMJobStartTimeDate ".
echo "StartTimeTime.StringObservation.obs is"$EIMJobStartTimeTime ".
echo "SystemDate.StringObservation.obs is"$CurrentDate ".
echo 'END_SAMPLE_PERIOD '.
echo "END_TABLE.
[/ code]
Here is the result, it "seems" be correct
-bash-3,00$./EIMJobStartTime.sh
TABLE EIM_JOB_STARTTIME
START_SAMPLE_PERIOD
StartTime.StringObservation.obs = 2013-03-15 21:09:52
StartTimeDate.StringObservation.obs = 2013-03-15
StartTimeTime.StringObservation.obs = 21: 09:52
SystemDate.StringObservation.obs = Friday, March 15, 2013 21:11:26 UTC
END_SAMPLE_PERIOD
END_TABLE
-bash-3, $ 00
When I "get log" on the agent, that nothing ever happens for this agent.
5.6.5 seems to have a bug regarding the agent data of custom script that appears in the data browser.
Try to restart the FMS service, others have seen it solve the problem in topology view.
-
Hey guys! My school uses the Cisco NAC Agent for security on our network, but it gives me problems at the moment. My Windows is fully updated, a mandatory requirement. However, I have done some Windows updates automatically for a while now, and I spent the last few hours manually, download, installation, System Restore to a date in the past and then redownloading, etc..
I'm in my third year on that campus, and I always had minor problems, which none has caused me a problem until now. I'm not sure what the underlying problem is, and I don't know if this is a common problem for this stage, but I was hoping that I could receive aid better here that guys in the student technology services desk. I am working from my laptop on campus wireless, but this isn't helping me get my Office Online
I have attached the newspaper report of Cisco of the packer.
Hello
We can see the agent to tell you:
"Your computer is missing one or more critical updates. Run Windows Update and check that you have all critical patches installed. »
And it's true that Agent to do some checks which is a failure.
Now these controls check some registry keys related to Internet Explorer and a few other internal items.
Unfortunately, it is that your network administrator which should help you to solve this problem, because the application of the NAC Manager will have a detailed report of what exactly a failure in your machine and then the requirements are changed to allow you to access or your machine must comply with the requirements.
HTH,
Tiago--
If this helps you or answers to your question if it you please mark it as 'responded' or write it down, if other users can easily find it.
-
Essbase Agent does not run, crashes immediately
Hello
In a first step to connect to the administration console, I am trying start the agent - essbase.exe
But, it opens and crashes in a second. How can I solve this... ?
Thank youHello
Although essbase starts without any problem.
Do you run essbase as a windows service, if so you don't have to start in the start menu.
If it's a link just essbase.exe initially will make open and close because it is already running.If you go to an essbase prompt and type cmd, if essbase is already running, you should get:-fatal error: Essbase is already loaded
I'm not sure what you mean that it crashes.
You can connect to via maxl essbase?for example start > run > cmd > essmsh
login password admin on localhost.
See you soon
John
http://John-Goodwin.blogspot.com/ -
My WUA has stopped working (cannot connect, cannot download, impossible to install) with the error code 80072EFD several days ago. I have completed all suggested ways to fix, but can not fix. I am running Win Vista Home Premium x 64 on my x 64 PC.
Hello
More details here:
Try this, as it's the same for SP1 and SP2
http://www.walkernews.NET/2009/05/14/how-to-fix-Windows-Update-error-80072efd-in-Vista-SP1/and here:
http://trevinchow.com/blog/2006/08/09/Windows-Update-and-Error-0x80072EFD/
And hereWindows Update error 80072efd
http://Windows.Microsoft.com/en-us/Windows-Vista/Windows-Update-error-80072efdI hope this helps. Rob - bicycle - Mark Twain said it is good.
Maybe you are looking for
-
Failure of the Airport Extreme and Airport Express
Airport Extreme not to talk to the device POE from the antenna of radio after a thunderstorm (lightning). Plug the POE ethernet cable directly into Mac works. Airport Express lights. Airport Extreme appears, but there is no internet connection. A
-
different noise on playback of music
I get different sound plans with songs on a playlist of songs I purchased on iTunes store. I use an iPhone 6 to store all my music. I spent / or I have to put something to improve the sound quality? any help much appreciated.
-
Everyone was able to use the 7813R LV 2010 SP1? I can't compile the screws for this card that contains an old model of FPGA Xilinx, which only is not supported by the new version of the compiler, but I begin to suspect that the so-called 'automatic'
-
I just download the Sansa firmware update, and when I go to run it, an error message appears saying "the Installation failed. Please try again later. "I started again and received the same error message. Then I waited about 30 min. and sure enough, s
-
I get the error code 80246008 when you try to update.
I get the error code 80246008 when you try to update. I tried everything to repair windows at the attempt of essential security analysis of windows. Yet its does not work and I can install updates or download microsoft windows. can anyone help?