Loading Profile...
Error initializing New Relic plugin !
Hi, the plugin is not running, in my apache error log I get: "** [NewRelic] Error initializing New Relic plugin (Permission denied - /var/www/insms/log/newrelic_agent.passenger_My_Application.log)
Error initializing New Relic plugin (Permission denied - /var/www/insms/log/newrelic_agent.passenger_My_Application.log)
** [NewRelic] /usr/lib/ruby/1.8/logger.rb:518:in `initialize'
"
Apache user has write permissions to the log directory
Error initializing New Relic plugin (Permission denied - /var/www/insms/log/newrelic_agent.passenger_My_Application.log)
** [NewRelic] /usr/lib/ruby/1.8/logger.rb:518:in `initialize'
"
Apache user has write permissions to the log directory
I’m confused
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi Anas,
I am so sorry it has taken so long to get back to you. It is pretty unlikely that this is a newrelic agent issue. Is it possible that the passenger app is running under a different user? -
Inappropriate?i have the same problem and set the default user with passenger_default_user <user>; in the nginx config, but it still doesn't work.</user> -
Inappropriate?Well the issue is pretty clear. New Relic needs to be able to write to a log file in the rails logs directory. If it's not there, it needs to be able to create the file with write permissions for the directory. If it can't do that, there can only be a couple of causes: 1) The plugin is running as a UID that does not have the ability to create a log file in that directory, 2) the UID does not have permissions to modify the file that is already there, possibly because it is owned by another user, such as would happen when another rails app ran (like a rake task) as another user.
The best bet is to create the log file described in the error message manually, then set the permissions on it so it can be written by any user.
The company says
this solves the problem
EMPLOYEE
