Bug #60891 [Fbk->NoF]: FPM status serving should be moved to the master process

From: Date: Mon, 18 Feb 2013 00:35:39 +0000
Subject: Bug #60891 [Fbk->NoF]: FPM status serving should be moved to the master process
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-177063@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=60891&edit=1

 ID:               60891
 Updated by:       php-bugs@lists.php.net
 Reported by:      erno dot kovacs at freemail dot hu
 Summary:          FPM status serving should be moved to the master
                   process
-Status:           Feedback
+Status:           No Feedback
 Type:             Bug
 Package:          FPM related
 Operating System: Any
 PHP Version:      5.3.9
 Assigned To:      fat

 New Comment:

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.


Previous Comments:
------------------------------------------------------------------------
[2012-12-19 17:01:11] aderumier at odiso dot com

Hello,
any news about pm.status_allow = *   patch ?

I'm really looking for this, monitoring status in one page (integration with 
nagios/cacti).

Regards,

Alexandre Derumier

------------------------------------------------------------------------
[2012-08-23 11:17:23] jasper at nerdsweide dot nl

Sounds good! I'm looking forward to these features.

> ... and there should be some missing free()
This means there is a memory-leak right?

------------------------------------------------------------------------
[2012-05-28 23:27:47] fat@php.net

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=pool1
http://xxx/status?pool=pool2&full
http://xxx/status?pool=pool3&json&full

Waiting to here from you on this.

++ fat

------------------------------------------------------------------------
[2012-05-28 23:08:16] fat@php.net

The following patch has been added/updated:

Patch Name: bug60891-v1.patch
Revision:   1338246496
URL:        https://bugs.php.net/patch-display.php?bug=60891&patch=bug60891-v1.patch&revision=1338246496

------------------------------------------------------------------------
[2012-01-26 14:57:22] 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

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=60891


-- 
Edit this bug report at https://bugs.php.net/bug.php?id=60891&edit=1


Thread (8 messages)

« previous php.bugs (#177063) next »