Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue running ngx-leaked-pools #14

Open
ghost opened this issue Feb 14, 2014 · 2 comments
Open

Issue running ngx-leaked-pools #14

ghost opened this issue Feb 14, 2014 · 2 comments

Comments

@ghost
Copy link

ghost commented Feb 14, 2014

Hi, I have been getting issues with running leaked pools:

sudo ./ngx-leaked-pools -p 7390
semantic error: while resolving probe point: identifier 'process' at :9:7
source: probe process("/usr/local/nginx/sbin/nginx").provider("nginx").mark("create-pool-done")

This has something to do with not able to find the marker in the symbols. Is this a known issue ? is there any pre-requisite ?

@agentzh
Copy link
Member

agentzh commented Feb 16, 2014

@avninagraj To quote the documentation for this tool:

This script requires Nginx instances that have applied the latest dtrace patch. See the
dtrace-nginx project for more details.

The bundle ngx_openresty 1.2.3.3+ includes the right dtrace patch by default. And you just need to build it with the --with-dtrace-probes configure option.

See https://github.com/agentzh/nginx-systemtap-toolkit#ngx-leaked-pools for more details.

@cjhust
Copy link

cjhust commented May 13, 2016

Systemtap not installed or its "stap" utility is not visible to the PATH environment:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants