AppD Archive

Unable to start the db-agent

CommunityUser
Splunk Employee
Splunk Employee

Hello,

I'm trying to use the db-agent with the Saas version. I downloaded the .zip generated by the wizzard but I get an exception when I start it. Here is the log :

Using Java Version [1.7.0_51] for Agent
Using Agent Version [Database Agent v4.0.4.0 GA Build Date 2015-03-31]
[Default Database Agent] Resolved install dir location :/opt/appdynamics/dbagent
log4j:WARN No appenders could be found for logger (com.singularity.ee.agent.dbagent.DBAgent).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
[Default Database Agent] Resolved install dir location :/opt/appdynamics/dbagent
Default Database Agent Install Directory :/opt/appdynamics/dbagent
Default Database Agent Temp Directory :/opt/appdynamics/dbagent/tmp
Tasks Root Directory :/opt/appdynamics/dbagent/controlchannel
Logger Configuration :/opt/appdynamics/dbagent/conf/logging/log4j.xml
Redirecting all logging statements to the configured logger
14:58:36,275  INFO [main] DBAgent:46 - ####################################################################################
14:58:36,278  INFO [main] DBAgent:46 - Agent Install Directory [/opt/appdynamics/dbagent]
14:58:36,278  INFO [main] DBAgent:46 - Using Agent Version [Database Agent v4.0.4.0 GA Build Date 2015-03-31]
14:58:36,279  INFO [main] DBAgent:46 - JVM Runtime: 
	java.home=/opt/java/jdk1.7.0_51/jre
	java.vm.vendor=Oracle Corporation
	java.vm.name=Java HotSpot(TM) 64-Bit Server VM
	java.runtime.version=1.7.0_51-b13
	java.io.tmpdir=/tmp
14:58:36,281  INFO [main] DBAgent:46 - OS Runtime: 
	os.name=Linux
	os.arch=amd64
	os.version=2.6.32-504.8.1.el6.x86_64
	user.name=postgres
	user.home=/var/lib/pgsql
	user.dir=/opt/appdynamics/dbagent
14:58:36,284  INFO [main] DBAgent:46 - JVM Args : 
14:58:36,290  INFO [main] DBAgent:46 - JVM Runtime Name: 3231@testperf-test-sql1.toto.net
14:58:36,290  INFO [main] DBAgent:46 - JVM PID: 3231
14:58:36,290  INFO [main] DBAgent:46 - Default Database Agent is resolving bootstrap info....
14:58:36,297  INFO [main] DBAgent:46 - Default Host Identifier Resolver using host name for unique host identifier [testperf-test-sql1.toto.net]
14:58:36,300  INFO [main] DBAgent:46 - Default IP Address Resolver found IP addresses [[10.0.0.28]]
14:58:36,300  INFO [main] DBAgent:46 - Full Agent Registration Info Resolver found system property [appdynamics.agent.applicationName] for application name [Database Monitoring]
14:58:36,300  INFO [main] DBAgent:46 - Full Agent Registration Info Resolver found system property [appdynamics.agent.tierName] for tier name [Database Monitoring]
14:58:36,300  INFO [main] DBAgent:46 - Full Agent Registration Info Resolver found system property [appdynamics.agent.nodeName] for node name [Database Monitoring]
14:58:36,304  INFO [main] DBAgent:46 - Full Agent Registration Info Resolver using selfService [false]
14:58:36,304  INFO [main] DBAgent:46 - Full Agent Registration Info Resolver using application name [Database Monitoring]
14:58:36,306  INFO [main] DBAgent:46 - Full Agent Registration Info Resolver using tier name [Database Monitoring]
14:58:36,307  INFO [main] DBAgent:46 - Full Agent Registration Info Resolver using node name [Database Monitoring]
14:58:36,313  INFO [main] DBAgent:46 - XML Controller Info Resolver found controller host [toto972.saas.appdynamics.com]
14:58:36,313  INFO [main] DBAgent:46 - XML Controller Info Resolver found controller port [443]
14:58:36,314  INFO [main] DBAgent:46 - XML Controller Info Resolver found valid config [Controller Host: toto972.saas.appdynamics.com; Controller Port: 443; ssl-enabled: true]
14:58:36,317  INFO [main] DBAgent:46 - XML Agent Account Info Resolver using account name [toto972]
14:58:36,317  INFO [main] DBAgent:46 - XML Agent Account Info Resolver using account access key [7qvpvjfispa1]
14:58:36,320  INFO [main] DBAgent:46 - Keystore file /opt/appdynamics/dbagent/conf/cacerts.jks was not found
14:58:36,500  INFO [main] DBAgent:46 - Trying secure protocol:TLSv1.2
14:58:36,601  INFO [main] DBAgent:46 - Default Database Agent resolved bootstrap info!
14:58:36,602  INFO [main] DBAgent:46 - Creating machine agent scheduler, pool size: 2
14:58:36,615  INFO [main] DBAgent:46 - Creating machine agent monitor scheduler, pool size: 4
14:58:36,619  INFO [main] DBAgent:46 - Started Agent Schedulers
14:58:36,619  INFO [main] DBAgent:46 - Scheduling Default Database Agent Registration ....
14:58:36,627  INFO [Agent-Scheduler-1] DBAgent:46 - using controller host [toto972.saas.appdynamics.com]; controller port [443]
14:58:36,636  INFO [Agent-Scheduler-1] DBAgent:46 - setting unique host information Host Name [testperf-test-sql1.toto.net]
14:58:36,636  INFO [Agent-Scheduler-1] DBAgent:46 - setting agent version [Database Agent v4.0.4.0 GA Build Date 2015-03-31]
14:58:36,637  INFO [Agent-Scheduler-1] DBAgent:46 - setting agent properties [{dbagent-name=Default Database Agent}]
14:58:36,637  INFO [Agent-Scheduler-1] DBAgent:46 - setting agent install dir [/opt/appdynamics/dbagent]
14:58:36,637  INFO [Agent-Scheduler-1] DBAgent:46 - setting agent type [DB_AGENT]
14:58:36,637  INFO [Agent-Scheduler-1] DBAgent:46 - setting agent application [Database Monitoring]
14:58:36,637  INFO [Agent-Scheduler-1] DBAgent:46 - setting agent tier name [Database Monitoring]
14:58:36,637  INFO [Agent-Scheduler-1] DBAgent:46 - setting agent node name [Database Monitoring]
14:58:36,638  INFO [Agent-Scheduler-1] DBAgent:46 - Sending Registration request
14:58:37,123  INFO [Agent-Scheduler-1] DBAgent:46 - Full certificate chain validation performed using default certificate file
14:58:37,760  INFO [Agent-Scheduler-1] DBAgent:46 - Auto agent registration attempted: Application Name [Database Monitoring] Component Name [Database Monitoring] Node Name [Database Monitoring]
14:58:37,760  INFO [Agent-Scheduler-1] DBAgent:46 - Auto agent registration SUCCEEDED!
14:58:37,761  INFO [Agent-Scheduler-1] DBAgent:46 - Registered Machine Agent with machine ID [51930]
14:58:37,761  INFO [Agent-Scheduler-1] DBAgent:46 - Starting Default Database Agent....
14:58:38,041  INFO [Agent-Scheduler-1] ManagedMonitorDelegate:110 - Started Agent Metric Generation Service
14:58:38,061  INFO [Agent-Scheduler-1] ManagedMonitorDelegate:131 - Started Agent Env Properties Service
14:58:38,062  INFO [Agent-Scheduler-1] ManagedMonitorDelegate:136 - Scheduled Continuous Task Monitor with frequency [30000]ms
14:58:38,071  INFO [Agent-Scheduler-1] MonitorConfigReader:45 - Reading monitor config file:/opt/appdynamics/dbagent/monitors/DatabaseMonitor/monitor.xml
14:58:38,075  INFO [Agent-Scheduler-1] MonitorConfigReader:117 - os name [linux] version [2.6.32-504.8.1.el6.x86_64]
14:58:38,080  INFO [Agent-Scheduler-1] NodeMonitorManager:132 - Initializing Managed Monitor [DatabaseMonitor]
14:58:38,081  INFO [Agent-Scheduler-1] ManagedMonitorDelegate:162 - Initializing managed monitor [DBMonitor]
14:58:38,081  INFO [Agent-Scheduler-1] ManagedMonitorDelegate:181 - Executing managed monitor [DBMonitor], task name [null]
14:58:38,081  INFO [Agent-Scheduler-1] ManagedMonitorDelegate:218 - Task [null] for monitor [DBMonitor] is SCHEDULED
14:58:38,085  INFO [Agent-Scheduler-1] JavaTaskCreator:48 - Task classpath not specified,System classpath will be used.
14:58:38,088  INFO [Agent-Scheduler-1] NodeMonitorManager:81 - No unmanaged Monitors installed for this Agent.
14:58:38,088  INFO [Agent-Scheduler-1] AgentMonitorManager:73 - Initialized System Monitor Manager with directory [/opt/appdynamics/dbagent/monitors]
14:58:38,088  INFO [Agent-Scheduler-1] DBAgent:46 - Set up agent monitor manager
14:58:38,089  INFO [Agent-Scheduler-1] DBAgent:46 - Orchestration is disabled - disabling one-way agent transport. The agent will not be able to execute workflow tasks.
14:58:38,090  INFO [Agent-Scheduler-1] DBAgent:46 - Set up agent re-registration task
14:58:38,095  INFO [Agent-Scheduler-1] DBAgentConfigManager:46 - Scheduling configuration refresh at an interval of 10 seconds
14:58:38,095  INFO [Agent-Scheduler-1] DBAgentConfigManager:46 - Configuration refresh task interval is 10 seconds
14:58:38,096  INFO [Agent-Scheduler-1] DBAgent:46 - Configuration manager successfully configured
14:58:38,097  INFO [Agent-Scheduler-1] DBMonitorService:94 - Initialized with maxInactiveTimeSlicesAllowed [30], maxPublishQueueLength [5], aggregationFrequencyInMillis [60000]
14:58:38,101  INFO [Agent-Scheduler-1] DBAgent:46 - Started AppDynamics Default Database Agent Successfully.
Started AppDynamics Default Database Agent Successfully.
14:58:43,328 ERROR [AD Thread Pool-Global0] DBAgentPollingForUpdate:30 - In DB Monitor Config Request error in reading data from servlet response reading byte[], size :139, error java.io.StreamCorruptedException: invalid stream header: 3C726573
14:58:43,328 ERROR [AD Thread Pool-Global0] DBAgentPollingForUpdate:34 - Error reading response from Controller
com.singularity.ee.rest.ResponseReadException: java.io.StreamCorruptedException: invalid stream header: 3C726573
	at com.singularity.ee.rest.controller.request.ABinaryControllerRequest.<init>(ABinaryControllerRequest.java:61)
	at com.singularity.ee.rest.controller.request.AgentPollingConfigurationRequest.<init>(AgentPollingConfigurationRequest.java:24)
	at com.singularity.ee.rest.controller.request.DBMonitorConfigRequest.<init>(DBMonitorConfigRequest.java:30)
	at com.singularity.ee.agent.dbagent.config.channel.DBAgentPollingForUpdate.getConfigurationResponse(DBAgentPollingForUpdate.java:29)
	at com.singularity.ee.agent.configuration.channel.PollingForUpdate.pollForConfigUpdate(PollingForUpdate.java:96)
	at com.singularity.ee.agent.configuration.channel.PollingForUpdate.nextTransition(PollingForUpdate.java:40)
	at com.singularity.ee.agent.configuration.channel.AgentConfigurationChannel.refreshConfiguration(AgentConfigurationChannel.java:48)
	at com.singularity.ee.agent.configuration.channel.AgentConfigurationRefreshTask.run(AgentConfigurationRefreshTask.java:32)
	at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:107)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335)
	at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152)
	at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:117)
	at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:204)
	at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:234)
	at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694)
	at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726)
	at java.lang.Thread.run(Thread.java:744)
Caused by: java.io.StreamCorruptedException: invalid stream header: 3C726573
	at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804)
	at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299)
	at com.singularity.ee.util.serialize.JavaSerializer.unmarshalObject(JavaSerializer.java:40)
	at com.singularity.ee.rest.controller.request.ABinaryControllerRequest.constructPaylodFromInputTracked(ABinaryControllerRequest.java:131)
	at com.singularity.ee.rest.controller.request.ABinaryControllerRequest.constructPaylodFromInput(ABinaryControllerRequest.java:123)
	at com.singularity.ee.rest.controller.request.ABinaryControllerRequest.<init>(ABinaryControllerRequest.java:56)
	... 17 more

Is it a bug ?

Thanks in advance.

[Edit]: I'm using Centos 6.5 x64 and JDK 1.7.0_51 Oracle's version

Regards,

Antoine Rouaze

0 Karma
1 Solution

CommunityUser
Splunk Employee
Splunk Employee

Ok I just found why it doesn't work. With the Saas we have to use the 4.0.3 version, not the 4.0.4.0 of the db-agent.

Regards,

Antoine Rouaze

View solution in original post

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Ok I just found why it doesn't work. With the Saas we have to use the 4.0.3 version, not the 4.0.4.0 of the db-agent.

Regards,

Antoine Rouaze

0 Karma

Tandava_Krishna
New Member

are you running both machine agnet and db agent on the same host?

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...