Internal buffers appear to be full - error (Analytics agent running fine)

[CommunityUser]

Hello,

I've seen other users have the same problem before so I followed their steps of making sure the Analytics agent was configured correctly and running, as well as the app server agent. But I still get the same error repeatedly in my logs. 

I had the Analytics running fine for a couple months until about a week ago, so I'm not sure what happened. 

Any idea how to fix this?

[Chitra_Lal]

Hello Leanna,

This error means that your app agent is not able to forward any events to the analytics agent(this can happen even if your agents are online, connected), so you might need to flush the queue in order to get this working. 

Please refer to the below article link for couple of ways how can we resolve this issue: 

https://community.appdynamics.com/t5/Knowledge-Base/How-to-verify-Analytics-Dynamic-Service-is-enabl...

Hope this helps. Do let me know in case you have questions. 

Thank You,

Chitra

[CommunityUser]

Hi Chitra, 

Thanks for getting back to me.

Going through the link that you attached, I tried to perform the curl test and curl tells me that the connection is refused. So, then I made sure the config file for the Analytics agent was all correct, and restarted the agent through the command line to make sure any config file changes were taken into account for. The Analytics agent is reported as up and running but when I try the curl test again, the connection (to port 9091-- unless my analytics agent is running on another port for some reason?) is still refused. 

Do you know how to fix this? 

Thanks, 
Leanna

[CommunityUser]

I also tried port 9090, a suggestion from another Discussion question, but connection was refused as well.

[Mohammed_Rayan]

Do you see if the port is in listen state for the analytic-agent using the below command

netstat -an | grep 9090 (Unix)
netstat -an | findstr 9090 (Windows)

Can you also check in the analytic-agent.log to validate if its indeed up and running or it refused to startup due to an stale pid file