Loading Profile...
Mongrel instances disappearing from configured application
We have 12 Mongrel instances which are running without problem, however as time goes on instances start disappearing from our configured application in New Relic. For example, right now the dashboard only says '9 instances'. Last week it went down to zero until I restarted our Mongrel cluster at which point all 12 appeared in RPM again.
This has only started happening since we upgraded to the latest agent. Is this a known issue and can anyone help? We're paying for a Silver account.
This has only started happening since we upgraded to the latest agent. Is this a known issue and can anyone help? We're paying for a Silver account.
I’m a bit fed up
3
people have 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.
The company marked this problem solved.
The best solution from the company
-
Anyone who has this problem should contact support@newrelic.com. There are several possible causes for this.
It appears one cause of this problem is using SSL in the agent. If you have the use_ssl flag set to true, and you see mongrels that stop reporting, try setting it to false. We haven't isolated the exact cause for this because there has only been one reproducible incident, but in that case there were some plugins with suspicious patches to the Net:HTTP libraries.
The company says
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi Olly,
This should be easy to troubleshoot because we have pretty decent logging in the Agent. The best thing to do is look at RPM and find a Mongrel you think is reporting but isn't showing up in RPM. Grab the newrelic.log file for that mongrel (each mongrel has a separate log file). Take a look at the bottom of the log file to see if there are any errors. If so, then email us the log file (support@newrelic.com). If there are no errors, then change our Agent's log level to "debug" from "info" (in config/newrelic.yml). At debug logging, all communication with RPM is logged and we'll be able to find out what's wrong for sure.
Thanks,
Jim -
Inappropriate?Hi Jim,
We have three Mongrel's missing from RPM (8005, 8006, 8007) and the RPM log files for these instances are blank.
However, the RPM log files for all the instances contains these errors:
[12/15/08 08:31:19 (13405)] ERROR : Error running task in Agent Worker Loop: end of file reached
[12/15/08 09:53:24 (13405)] ERROR : Error running task in Agent Worker Loop: end of file reached
[12/15/08 15:42:27 (13405)] ERROR : Error running task in Agent Worker Loop:
[12/15/08 15:59:28 (13405)] ERROR : Error running task in Agent Worker Loop:
Does this mean anything to you?
I will move the log level to debug but before I do can you tell me what impact this will have on application performance?
I’m confused
-
Inappropriate?Olly changing the debug level of the agent won't affect the application's performance. Thanks for your help.
-
Inappropriate?Hi
Just to let you know I've sent through the debug-level log file for a Mongrel which has disappeared from RPM since the last restart.
-
Inappropriate?Anyone who has this problem should contact support@newrelic.com. There are several possible causes for this.
It appears one cause of this problem is using SSL in the agent. If you have the use_ssl flag set to true, and you see mongrels that stop reporting, try setting it to false. We haven't isolated the exact cause for this because there has only been one reproducible incident, but in that case there were some plugins with suspicious patches to the Net:HTTP libraries.
The company says
this solves the problem
-
Inappropriate?Olly and everyone else, we believe we have fixed the problem. The fix is available in beta right now. Please try it out. With ssl on you should no longer see mongrels disappearing.
http://rpmstatus.newrelic.com/2009/03...
Please let us know if you have the opportunity to try this out.
1 person says
this solves the problem
-
Inappropriate?Thanks Bill. It's not a problem for us any more since we're now using Passenger :)
I’m happy
EMPLOYEE
EMPLOYEE
