Apache HTTP Server 2.4 Problem Diagnosis
Apache HTTP Server 2.4 Problem Diagnosis
Apache HTTP Server 2.4 Problem Diagnosis
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
nginx — DTrace-ing<br />
<strong>Apache</strong> <strong>HTTP</strong><br />
<strong>Server</strong> <strong>2.4</strong><br />
<strong>Problem</strong><br />
<strong>Diagnosis</strong><br />
Jeff Trawick<br />
Introduction<br />
What kinds of<br />
issues<br />
encountered<br />
Using tools<br />
inside the web<br />
server<br />
Looking from<br />
the outside<br />
What if you<br />
build the code<br />
differently<br />
There’s a fork of nginx 1.2.1 (slightly out of date) that<br />
includes DTrace probes (and System Tap too). (unclear<br />
how experimental this is)<br />
The pid provider needs to be provided the pid to trace,<br />
which is not a burden with nginx. This is the provider that<br />
allows instrumentation of arbitrary functions in the<br />
process. The nginx docs have some minimal information<br />
about using the pid provider with it.<br />
Compare with<br />
httpd 2.2 and<br />
nginx<br />
References<br />
and further<br />
reading