The infrastructure agent is not starting, and logs are not created.
Here are some troubleshooting options for non-root users if the infrastructure agent is not starting and there are no logs:
To see if
requiretty is causing logging issues:
/var/log/syslog, look for the message
sudo: sorry, you must have a tty to run sudo.
When using old Linux versions, sometimes the
nri-agentuser fails to execute a service because it does not have any TTY attached.
If you find this message, edit your
/etc/sudoersfile with the
visudocommand and comment or remove the following line:
Save and exit the file.
Check the agent's permission to open
log_file. It's possible that the log file you are using was created when the agent was running as root, and now the
nri-agent user does not have permissions to write it.
To solve this, try one of these options:
Change the owner of the log file.
log_fileentry in the
/etc/newrelic-infra.ymlconfiguration file. Our installation scripts create the
/var/log/newrelic-infra/folder for that purpose, so we recommend the following value:log_file: /var/log/newrelic-infra/newrelic-infra.log
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.