APMIA - missing sysedge data

Products

• CA Application Performance Management SaaS

Issue/Introduction

 

SystemEDGE is not being reported data for a IA host monitor.

There is this error in the agent startup log

 

[ERROR] [IntroscopeAgent.SnmpCollector] Unable to bind to address: 127.0.0.1/162
java.net.BindException: Permission denied (Bind failed)
        at java.net.PlainDatagramSocketImpl.bind0(Native Method)
        at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:93)
        at java.net.DatagramSocket.bind(DatagramSocket.java:392)
        at java.net.DatagramSocket.<init>(DatagramSocket.java:242)
        at java.net.DatagramSocket.<init>(DatagramSocket.java:299)
        at org.snmp4j.transport.DefaultUdpTransportMapping.<init>(DefaultUdpTransportMapping.java:99)
        at com.wily.introscope.agent.snmp.SnmpTrapReciever.startReceiver(SnmpTrapReciever.java:125)
        at com.wily.introscope.agent.snmp.SnmpTrapReciever.init(SnmpTrapReciever.java:117)
        at com.wily.introscope.agent.snmp.SNMPBridge.IAgentService_startService(SNMPBridge.java:75)
        at com.wily.introscope.agent.service.ServiceAdministrator$ServiceInitializer.startService(ServiceAdministrator.java:554)
        at com.wily.introscope.agent.service.ServiceAdministrator$ServiceInitializer.startServiceSafe(ServiceAdministrator.java:568)
        at com.wily.introscope.agent.service.ServiceAdministrator$ServiceInitializer.IExecutableItem_execute(ServiceAdministrator.java:432)
        at com.wily.util.task.AsynchExecutionQueue$WrapperItem.IExecutableItem_execute(AsynchExecutionQueue.java:414)
        at com.wily.util.task.AsynchExecutionQueue.doTask(AsynchExecutionQueue.java:205)
        at com.wily.util.task.ATask$CoreTask.run(ATask.java:132)
        at java.lang.Thread.run(Thread.java:748)

 

 

 

 

Environment

Release : SAAS

Component : Integration with APM

Cause

 

The agent was installed in one location where it was running for some time. Then this agent was put into a tar file and moved to a different machine.

The idea was to prepare a package that could be deployed to multiple machines.

The HostMonitor extension needs to be enabled on the first time the agent is started and does not accept being moved to a different machine after it has run on a first machine.

Resolution

Particularly for preparing a package to deploy to multiple machines, a clean package that has never been used needs to be configured.

In general make sure the HostMonitor option is enabled in the Extensions.profile before you try to run or install the APMIA. 

If not enabled when first run, the agent needs to be reinstalled with the HostMonitor option enabled.