Page 1 of 1

/proc/‹pid›/ directory not readable?

Posted: Mon Jan 06, 2014 5:44 am
by gaia
I've noticed that NewRelic doesn't show up any processes under the CPU consumption section. Their support pointed me to this answer:

Missing processes
Why can't I see any processes other than nrsysmond?


Often this is caused by running in a heightened security mode using tools such as grsecurity, SELinux "strict" or AppArmor. The New Relic system monitor runs as an unprivileged process and is unable to read information about other processes if the /proc/‹pid›/ directory is not readable. If you are not sure what is going on, send a support ticket with details about your environment, and include your nrsysmond.log.

Is there a setting for ASL I can change to allow nrsysmond to see the other processes?

Re: /proc/‹pid›/ directory not readable?

Posted: Mon Jan 06, 2014 7:51 am
by prupert
You can add the user who you want to have access to reading process information to the procread group.
usermod -a -G procread username

Re: /proc/‹pid›/ directory not readable?

Posted: Tue Jan 07, 2014 6:35 am
by gaia
prupert wrote:You can add the user who you want to have access to reading process information to the procread group.
usermod -a -G procread username

"usermod -a -G procread newrelic" solved the problem.

thanks