Splunk AppDynamics

Internal server error 500

CommunityUser
Splunk Employee
Splunk Employee

when trying to trigger some events in app dynamice server, server throws internal server error 500. while for other events it works fine.

For example when i go for Http Action Template Test and i select event type as "Custom Action Failed" or "Http Action Failed" or "Custom Email Action Failed" and when i click on Run Test button i get the following error popup:

Error

500 Internal Server Error


Exception Id:b290cc57-a776-4515-a15f-dced7c151b90
 
Can you please help me debugging this issue. Also i want to know is this the issue with App Dynamics or somthing else?
Labels (3)
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Dheeraj,

Please provide the server logs from <ControllerHome>/logs/server.log to see what application exceptions are causing this.

Please perform the sequence of the actions you mentioned below so that your latest server logs capture these exceptions.

Thanks,

Asha.

CommunityUser
Splunk Employee
Splunk Employee

Hi Asha,

Please find the  attached server logs from
Thanks & Regards,

Dheeraj

^Log file removed as attachment and from the post for security reasons by @Ryan.Paredez 

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Dheeraj,

These logs are not sufficient and I do not see any severe exceptions below. Would you please upload the complete log file. And it is not related to the 500 error mentioned. It would help us to the context in which program has thrown the 500. Please upload the latest logs after performing the actions that cause the 500 error.

Thanks,

Asha.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...