AppD Archive

PHP Agent Non Responsive

CommunityUser
Splunk Employee
Splunk Employee

Hello All, 

  My boss gave me the honor of setting up and getting appdynamics working on our system but i am running into some serious issues that i hope the community can assist with.  

We have a 3 tier application that includes :

tier 1 : 2 php nodes

tier 2 : 2 java nodes

tier 3 : 2 java nodes

the current issue is that on tier 1 i have 1 node up and responding but i cannot get the second node to respond at all.

I have checked to make sure there are no connections issues (in fact the now non responsive node was working at one point) and no changes have been made to the system since installing java 8 before the agents were installed.

my agent.log shows the following over and over 

[config.ConfigChannel] could not send config request
[config.ConfigChannel] sending config request with version -1

and after restarting the apache server for that node 


2016-04-04 22:27:02.066 GMT INFO 14306 [agent.AgentKernel] starting up agent kernel [4.2.0.2GA.9829.xxxxxxxxxx]
2016-04-04 22:27:02.067 GMT INFO entwexprd02 14306 [config.ConfigChannel] sending config request with version -1
2016-04-04 22:27:03.068 GMT ERROR entwexprd02 14306 [config.ConfigChannel] could not send config request
2016-04-04 22:27:03.799 GMT INFO entwexprd02 3706 [config.ConfigChannel] sending config request with version -1
2016-04-04 22:27:04.799 GMT ERROR entwexprd02 3706 [config.ConfigChannel] could not send config request
2016-04-04 22:27:06.031 GMT INFO entwexprd02 26965 [config.ConfigChannel] sending config request with version -1
2016-04-04 22:27:07.031 GMT ERROR entwexprd02 26965 [config.ConfigChannel] could not send config request
2016-04-04 22:27:08.155 GMT INFO entwexprd02 8326 [agent] module shutdown start
2016-04-04 22:27:08.155 GMT INFO entwexprd02 8326 [agent] module shutdown end

I have been through the conf files the ini files and permissions for the entire system matching them up to the other node that works and i find absolutely no differences.  Every forum post i find on this says check permissions or make sure the config is the same.  

Anyone have some ideas or seen this before.  

my next step is to have our unix admis delete the agent and reinstall 

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

resolved: Uninstall and reinstall the agent fixed the issue.

0 Karma
Get Updates on the Splunk Community!

Splunk Observability Cloud's AI Assistant in Action Series: Auditing Compliance and ...

This is the third post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how to ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

What You Read The Most: Splunk Lantern’s Most Popular Articles!

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...