Your New Relic Java agent is not generating log files.
Ensure your New Relic Java agent is configured to generate
newrelic_agent.log files by checking the following:
- Log file directory
New Relic's Java agent stores log files in the
logsdirectory. The Java agent creates this directory in the same location used for the
-javaagentswitch. If you can't find
newrelic_agent.log, ensure the JVM process has permissions to write to the
Permissions management varies greatly by environment, so work with your system administrator to verify that this is not an issue. If permissions are not the issue, check that you did not customize the location of the
- Config file
Ensure that the YAML format in
newrelic.ymlis valid by using a YAML validator. This tool verifies that your YAML is valid. It also gives you an interpreted version uncluttered by comments.
If your YAML is not valid, use a whitespace-aware editor such as Sublime Text. This will help you make changes to your
newrelic.ymlwith the correct whitespace.
- Boot log
You can start up your app server so that it prints to the console. Here are some examples of where this is stored:
catalina.out(if specified in
When booting your JVM, the generated logs should show that the
newrelic.jarfile opens and the agent interprets the
newrelic.ymlconfiguration file. Failures to find either file or open them correctly will show here.
Successfully loading the agent will look something like this:
Aug 29, 2013 15:02:49 -0700 NewRelic 1 INFO: Agent is using Logback Aug 29, 2013 15:02:49 -0700 NewRelic 1 INFO: Loading configuration file "/path/on/your/host/newrelic/.newrelic.yml"
For more help
Additional documentation resources include:
- Generating logs for troubleshooting (collecting log file data and verifying your Java app's name and location to help identify and resolve the problem).