Support for FCGIWrapper? about cachetool HOT 6 CLOSED

I'm not sure if it is possible, but if you submit a PR, i see no reason not to accept it.

from cachetool.

@gordalina I'd happily make a PR if I had an idea how to solve this. With this setup there is no way to cross the boundary of the CLI SAPI.

So I guess the only option here is the usual workaround where a random file is created in the web root with a opcache_reset() call and request this file from CLI via HTTP.

Unless you have a better idea I'll close this one.

from cachetool.

what's your exact use case? apache2 with mod_fcgi?
maybe if you expose fcgiwrapper through a socket, you can pass the path to cachetool so it connects as a regular fcgi client

from cachetool.

@gordalina Unfortunately I'm not sure about how this setup was made. It looks like mod_fcgid (mind the d) is currently used and I'm not sure where to find the socket in use. With lsof I can find this:

php5-cgi  32581       <ssh-username>    0u     unix 0xffff88023555a440       0t0    5271086 /var/lib/apache2/fcgid/sock/57741.60

However, the permissions of that socket file are rather strict:

srwx------ 1 www-data www-data 0 Jan 26 08:39 /var/lib/apache2/fcgid/sock/57741.60

It this setup messed up (not unlikely) or am I missing something?

from cachetool.

if you run cachetool as www-data you'd be able to access the socket, can you try that?
php cachetool.phar opcache:status --fcgi=/var/lib/apache2/fcgid/sock/57741.60

from cachetool.

This works indeed but requires sudo. And the socket file apparently changes from time to time so I'd have to detect it as mentioned with lsof.

All in all not really a useful solution from my POV for this setup. It'll most likely be switched to regular PHP-FPM soon so this shouldn't be an issue anymore.

But I'll keep the solution in my head in case I encounter it again, thanks a lot!

from cachetool.