Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports

[2012-01-26 14:57 UTC] ml at fatbsd dot com

for security reason and by design it's not possible to make the master process to
listen to those requests.
The only possibility is to fork another process only to handle this. And this is
quite a a big change. It's on my todo list but no ETA yet.
++ fat

Here is the first revision of the patch (it needs some verifications and there should be some missing free(), but it works
on my side). It can be applied on the last 5.3 snapshot (not sure it will applies correctly on older version/revision).
Here's what's new:
- new FPM configuration item for pool: pm.status_allow which is unset by default. Add the names of the other pool you want
to access from this pool (use a comma (,) as a separator). If one of the element is the char '*', then all pool are
available from this pool status page
- call the status page of this pool adding a pool=xxx in the query string and there it's supposed to work
Exemple: for having a dedicated pool which only respond to the /status page and permit to see all pools status : add the
following pool to your php-fpm.conf
[status]
listen=/tmp/status.sock
user = nobody ;use a low privilege user, nothing is needed here
group = nogroup
pm = ondemand
pm.max_children = 1 ;set a higher value if you need parallal requesting to the status page
pm.status_path = /status
pm.status_allow = * ; allow to see all pool status
chroot = /var/empty ; chroot to un empty directory for security reason
security.limit_extensions = .nonexistantextesionxxxxx ; limit to only one neverused extension
it'll only respond to the /status page (because of the pseudo random security.limit_extensions) and it's possible to see all
pool status page:
http://xxx/status?pool=pool1http://xxx/status?pool=pool2&fullhttp://xxx/status?pool=pool3&json&full
Waiting to here from you on this.
++ fat

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.