Loading Profile...
RPM not working with Rails 2.3 edge
It seems RPM is not working with Rails edge 2.3.
When I uncomment STDOUT in init.rb it gives the following output:
"RPM detected environment: LocalEnvironment[unknown:], RAILS_ENV: development"
Nothing can be find in logs too.
Is RPM still do not support the latest Rails edge?
When I uncomment STDOUT in init.rb it gives the following output:
"RPM detected environment: LocalEnvironment[unknown:], RAILS_ENV: development"
Nothing can be find in logs too.
Is RPM still do not support the latest Rails edge?
I’m anxious
3
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The best answer from the company
-
This should work in the latest agent release, 2.8.9. Please try and let me know. If it's still not working, can you try rails 2.3.2?
Please follow-up to support@newrelic.com. We aren't monitoring getsatisfaction anymore.
The company says
this answers the question
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi laktek,
For some reason it appears we are not detecting your http frontend. What are you using (ie mongrel/passenger/thin/webbrick/etc)?
- Jim -
Inappropriate?Hi Jim,
Thanks for your quick reply. I'm using Mongrel. I also tried with webrick but still no luck
-
Inappropriate?Laktek we've filed a bug on this. Meanwhile, if you want to experiment with a workaround, look at local_environment.rb and see if you can figure out why mongrel detection is not working in 2.3, or try hardwiring mongrel.
-
Inappropriate?Thank you very much for your support. Hardwiring mongrel made it work.
Also I needed to change the following line to get the Developer Mode view render correctly.
In rpm/ui/controllers/newrelic_controller.rb, line 154:
- response.headers['Last-Modified'] = last_modified
+ response.last_modified = last_modified
I’m thankful
-
Inappropriate?Any progress on this bug. I'm using 2.3.0 and mongrel/passenger neither seem to picked up.
I took a look at the check_for_mongrel method, it returns the ports 3000 and 1.
I’m anxious
-
Inappropriate?I'm afraid there's no progress to report. It's scheduled for the next major release of the agent 2.9.0, due in 4-6 weeks.1 Comment Add a comment
This answers the question
-
Any updates? -
Inappropriate?This should work in the latest agent release, 2.8.9. Please try and let me know. If it's still not working, can you try rails 2.3.2?
Please follow-up to support@newrelic.com. We aren't monitoring getsatisfaction anymore.
The company says
this answers the question
EMPLOYEE
EMPLOYEE
