Loading Profile...
Should RPM be disabled for rake tasks?
Things like rake db:migrate, and many other custom rake tasks are not running in the context of a mongrel process, and throw a permission denied error because they are running as a different user than the log directory.
But I feel like they shouldn't run, unless that's expected data to gather for RPM. Anyone from New Relic want to opine on that?
But I feel like they shouldn't run, unless that's expected data to gather for RPM. Anyone from New Relic want to opine on that?
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?The current agent is disabled for rake tasks as well as the console.
Do you have the latest agent, version 2.1.6?
If so, then could you show me a stack trace from initialization? -
Inappropriate?I think I see what's happening. The newrelic.yml file gets parsed first, and in my case, the parsing fails because the permissions on the rake user are not the same as my mongrel user. Thus, an exception is raised, rescued, and spit to stdout in the global rescue of init.rb.
So I guess what I'm really asking is whether the rake/console disabling check can happen sooner in the workflow, so it doesn't throw exceptions on launch of the rails-env.
I’m curious
EMPLOYEE
