Welcome! Log In Create A New Profile

Advanced

[PHP] PHP-FPM fails to start scripts

Posted by John Iliffe 
John Iliffe
[PHP] PHP-FPM fails to start scripts
May 23, 2017 03:40AM
PHP-7.1.3 compiled from source, running on Fedora 25 with Apache-2.4.25

php-fpm is running but reports all scripts as "No Input File Specified" on
the browser and "ERROR: Unable to open primary script:
/httpd/iliffe//i_phpinfo.php (No such file or directory)" on the error log.
[ This script is actually phpinfo() ].

I have been working with the Apache list to try and resolve this but have
now been referred to the PHP list as not an Apache problem.

Environment: the requested script is in the document root at /httpd/iliffe
and does exist and is world readable.
------------------------
namei /httpd/iliffe/i_phpinfo.php
f: /httpd/iliffe/i_phpinfo.php
d /
d httpd
d iliffe
- i_phpinfo.php
---------------------------

The Apache directive invoking this script is:

ProxyPassMatch "^/.*\.php(/.*)?$" fcgi://127.0.0.1:9015/httpd/iliffe/

php-fpm is running on a TCP socket at 127.0.0.1:9015 It is in pool www.

Running strace on php-fpm yields the following info: (relevant bit
extracted from a 24,000 line trace report)

----------------------------
9223 12:25:52 lstat("/httpd/iliffe//i_phpinfo.php", {st_mode=S_IFREG|0644,
st_size=213, ...}) = 0
9223 12:25:52 lstat("/httpd/iliffe", {st_mode=S_IFDIR|0755, st_size=4096,
....}) = 0
9223 12:25:52 lstat("/httpd", {st_mode=S_IFDIR|0755, st_size=141, ...}) =
0
9223 12:25:52 lstat("/httpd/iliffe/.user.ini", 0x7ffe0e20ae80) = -1 ENOENT
(No such file or directory)
-------------------------------

and then about 30 lines further down the report:

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

9223 12:25:52 lstat("/httpd/i_phpinfo.php", 0x7ffe0e208f30) = -1 ENOENT (No
such file or directory)
9223 12:25:52 write(2, "ERROR: Unable to open primary sc"..., 95) = 95
9223 12:25:52 times( <unfinished ...>
9222 12:25:52 <... epoll_wait resumed> [{EPOLLIN, {u32=27169440,
u64=27169440}}], 11, 1000) = 1
9223 12:25:52 <... times resumed> {tms_utime=0, tms_stime=0, tms_cutime=0,
tms_cstime=0}) = 486185773
9223 12:25:52 setitimer(ITIMER_PROF, {it_interval={tv_sec=0, tv_usec=0},
it_value={tv_sec=0, tv_usec=0}}, <unfinished ...>
9222 12:25:52 read(10, <unfinished ...>
9223 12:25:52 <... setitimer resumed> NULL) = 0
9222 12:25:52 <... read resumed> "ERROR: Unable to open primary sc"...,
1023) = 95
9223 12:25:52 write(3, "\1\7\0\1\0X\0\0Unable to open primary s"..., 240
<unfinished ...>
9222 12:25:52 write(3, "[20-May-2017 12:25:52] WARNING: "..., 169
<unfinished ...>
-------------------------------------

Error logging starts AFTER the second attempt to open the file on the wrong
path.

Note that the first lstat has the file (return code = 0) and it is a readable
regular file {st_mode=S_IFREG|0644, st_size=213, ...}

The second attempt doesn't get the file:

9223 12:25:52 lstat("/httpd/i_phpinfo.php", 0x7ffe0e208f30) = -1 ENOENT (No
such file or directory)

because php-fpm is looking on the wrong path. (missing second
subdirectory).

So, my questions:

1. why am I getting not found responses when php-fpm can find the script
file and is permitted to open it?

2. why, when php-fpm has found the file already does it continue to descend
the directory structure?

3. why is the second attempt on the wrong directory?

4. if this is a configuration problem on my part, where should I be looking
to correct it?

I have also downloaded and tried php-fpm from the PHP-7.1.5 and it has the
same problem.

Please let me know if any other information is required.

Thanks in advance.

John
=====================================






--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Lester Caine
Re: [PHP] PHP-FPM fails to start scripts
May 23, 2017 08:50AM
On 23/05/17 02:41, John Iliffe wrote:
> The Apache directive invoking this script is:
>
> ProxyPassMatch "^/.*\.php(/.*)?$" fcgi://127.0.0.1:9015/httpd/iliffe/

ProxyPassMatch ^/(.*\.php(/.*)?)$ fcgi://127.0.0.1:9015/httpd/iliffe/$1
was your original line, and this should have resulted in the right
trimming of slashes while I think you are currently getting the double
slash because of the trailing one in your current string.

ProxyPassMatch ^/info$ fcgi://127.0.0.1:9015/httpd/iliffe/i_phpinfo.php
and http://localhost/info should work ... but is /httpd REALLY a root
folder? I'm getting /srv/www/htdocs as the default root, and I switch to
/srv/website/test.com for each website ...

I'm still running Apache2.4 with mod_php5.so as I was having a similar
problem 'converting'. I've got nginx running php-fpm and even different
versions which I can pick up, but I could do with having another go with
the old Apache machines if only to allow PHP7 to run with the PHP5 setup ;)

--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
John Iliffe
Re: [PHP] PHP-FPM fails to start scripts
May 23, 2017 07:10PM
On Tuesday 23 May 2017 02:40:03 Lester Caine wrote:
> On 23/05/17 02:41, John Iliffe wrote:
> > The Apache directive invoking this script is:
> > ProxyPassMatch "^/.*\.php(/.*)?$" fcgi://127.0.0.1:9015/httpd/iliffe/
>
> ProxyPassMatch ^/(.*\.php(/.*)?)$ fcgi://127.0.0.1:9015/httpd/iliffe/$1
> was your original line, and this should have resulted in the right
> trimming of slashes while I think you are currently getting the double
> slash because of the trailing one in your current string.
>
> ProxyPassMatch ^/info$ fcgi://127.0.0.1:9015/httpd/iliffe/i_phpinfo.php
> and http://localhost/info should work ... but is /httpd REALLY a root
> folder? I'm getting /srv/www/htdocs as the default root, and I switch to
> /srv/website/test.com for each website ...
>
> I'm still running Apache2.4 with mod_php5.so as I was having a similar
> problem 'converting'. I've got nginx running php-fpm and even different
> versions which I can pick up, but I could do with having another go with
> the old Apache machines if only to allow PHP7 to run with the PHP5 setup
> ;)
Thanks Lester.

Now that was interesting. My original line didn't have the $1 on the end
of the match, so I added it. Now I get "File Not Found" as a browser
response and the trace doesn't show all those lstats. Only one now and it
is a stat (not lstat).

3156 12:41:52 stat("/httpd/iliffe", {st_mode=S_IFDIR|0755, st_size=4096,
....}) = 0

Note that the requested script is no longer there. It still gets the
correct path from somewhere. The log entries are:

-----------------------
php-fpm.log
[23-May-2017 12:42:16] ERROR: unable to read what child say: Bad file
descriptor (9)
[23-May-2017 12:42:16] ERROR: unable to read what child say: Bad file
descriptor (9)
-----------------------

httpd log
[Tue May 23 12:43:15.441179 2017] [proxy:error] [pid 2980:tid
140444876887808] (111)Connection refused: AH00957: FCGI: attempt to connect
to 127.0.0.1:9015 (*) failed
[Tue May 23 12:43:15.441237 2017] [proxy_fcgi:error] [pid 2980:tid
140444876887808] [client 206.248.138.118:43231] AH01079: failed to make
connection to backend: 127.0.0.1
[Tue May 23 12:43:18.797290 2017] [proxy_fcgi:error] [pid 2981:tid
140444935636736] [client 206.248.138.118:43232] AH01071: Got error 'Primary
script unknown\n'
---------------------------------

ss -a shows socket 127.0.0.1:9015 is active:
tcp LISTEN 0 128 127.0.0.1:9015 *:*
tcp LISTEN 0 0 127.0.0.1:9015 *:*

Any other ideas?

FYI, buried in the php-fpm source code there are a number of comments about
the problem of getting the correct directory path from Apache calls. Looks
like the PHP folks haven't solved the problem for PHP 7 yet. While I was
Googling this problem I noticed piles of reports of problems with nginx
running php-fpm so maybe they resolved that first. One other point is the
big section in the man pages for lstat for Fedora 25 showing changes in the
macros. I'm not a good enough programmer to understand a lot of it.

John (VA3JI/VE3CES)
=================================

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
John Iliffe
Re: [PHP] PHP-FPM fails to start scripts
May 24, 2017 03:00AM
On Tuesday 23 May 2017 02:40:03 Lester Caine wrote:
> On 23/05/17 02:41, John Iliffe wrote:
> > The Apache directive invoking this script is:
> > ProxyPassMatch "^/.*\.php(/.*)?$" fcgi://127.0.0.1:9015/httpd/iliffe/
>
> ProxyPassMatch ^/(.*\.php(/.*)?)$ fcgi://127.0.0.1:9015/httpd/iliffe/$1
> was your original line, and this should have resulted in the right
> trimming of slashes while I think you are currently getting the double
> slash because of the trailing one in your current string.
>
Please ignore this following paragraph. It was an attempt at a minimalist
ProxyPassMatch that would bypass any regex errors. It isn't useful in the
real world so I dropped trying it. I think you got that info from the
Apache mailing list.
> ProxyPassMatch ^/info$ fcgi://127.0.0.1:9015/httpd/iliffe/i_phpinfo.php
> and http://localhost/info should work ... but is /httpd REALLY a root
> folder? I'm getting /srv/www/htdocs as the default root, and I switch to
> /srv/website/test.com for each website ...
>
Some further info:

Yes, /httpd is the root directory for the web pages. The production server
has a lot of named virtual hosts on it and each one has a document root of
/httpd/<server name>/ and the test server is set up the same way. The
test server is www.iliffe.ca and its document root thus becomes /httpd/iliffe
plus a few subs below that where needed. In this case, there are no
additional subs.

When I tried the $1 extension as you suggested it didn't work, see previous
memo; so I removed the $1 and also the last '/' in the ProxyPassMatch
directive and now php-fpm has the correct path and file but without the
double '//'. So, this is one case where a trailing / on a directory does
not work/isn't required. Here is the strace record:

-------------------------------
5254 20:14:55 lstat("/httpd/iliffe/i_phpinfo.php", {st_mode=S_IFREG|0644,
st_size=213, ...}) = 0
--------------------------------

php-fpm received a 0 from lstat (file exists), is a regular file (S_IFREG)
and is readable (0644). So that makes no difference to the result. php-fpm
still backs down the directory tree and then tries to stat the wrong file
name. Just for completeness, here is the php-fpm log entry:

----------------------------------
[23-May-2017 20:14:55] WARNING: [pool www] child 5254 said into stderr:
"ERROR: Unable to open primary script: /httpd/iliffe/i_phpinfo.php (No such
file or directory)"
---------------------------------

I haven't been able to find out yet if the parameter data is picked up when
the Apache directive is coded this way. (eg: i_phpinfo.php?a=b&c=d)

I seem to be getting a good argument here for backing off to PHP5!

Regards,

John
===============================

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Lester Caine
Re: [PHP] PHP-FPM fails to start scripts
May 24, 2017 09:50AM
On 24/05/17 02:05, John Iliffe wrote:
> On Tuesday 23 May 2017 02:40:03 Lester Caine wrote:
>> On 23/05/17 02:41, John Iliffe wrote:
>>> The Apache directive invoking this script is:
>>> ProxyPassMatch "^/.*\.php(/.*)?$" fcgi://127.0.0.1:9015/httpd/iliffe/
>>
>> ProxyPassMatch ^/(.*\.php(/.*)?)$ fcgi://127.0.0.1:9015/httpd/iliffe/$1
>> was your original line, and this should have resulted in the right
>> trimming of slashes while I think you are currently getting the double
>> slash because of the trailing one in your current string.
>>
> Please ignore this following paragraph. It was an attempt at a minimalist
> ProxyPassMatch that would bypass any regex errors. It isn't useful in the
> real world so I dropped trying it. I think you got that info from the
> Apache mailing list.

I suggested it simply because it would bypass some errors ;)

>> ProxyPassMatch ^/info$ fcgi://127.0.0.1:9015/httpd/iliffe/i_phpinfo.php
>> and http://localhost/info should work ... but is /httpd REALLY a root
>> folder? I'm getting /srv/www/htdocs as the default root, and I switch to
>> /srv/website/test.com for each website ...
>>
> Some further info:
>
> Yes, /httpd is the root directory for the web pages. The production server
> has a lot of named virtual hosts on it and each one has a document root of
> /httpd/<server name>/ and the test server is set up the same way. The
> test server is www.iliffe.ca and its document root thus becomes /httpd/iliffe
> plus a few subs below that where needed. In this case, there are no
> additional subs.

One of the major problems with Linux is the way each distribution
modifies just where it installs key applications and how it manages
them. I'm on SUSE myself and apart from a couple of attempts at other
distros when the SUSE guys just totally lost the plot, I've been with
that since version 6. My problem is installing later APACHE/PHP builds
while maintaining the stable SUSE installs ... and getting paths right
teds to be the problem.

> When I tried the $1 extension as you suggested it didn't work, see previous
> memo; so I removed the $1 and also the last '/' in the ProxyPassMatch
> directive and now php-fpm has the correct path and file but without the
> double '//'. So, this is one case where a trailing / on a directory does
> not work/isn't required. Here is the strace record:
>
> -------------------------------
> 5254 20:14:55 lstat("/httpd/iliffe/i_phpinfo.php", {st_mode=S_IFREG|0644,
> st_size=213, ...}) = 0
> --------------------------------
>
> php-fpm received a 0 from lstat (file exists), is a regular file (S_IFREG)
> and is readable (0644). So that makes no difference to the result. php-fpm
> still backs down the directory tree and then tries to stat the wrong file
> name. Just for completeness, here is the php-fpm log entry:
>
> ----------------------------------
> [23-May-2017 20:14:55] WARNING: [pool www] child 5254 said into stderr:
> "ERROR: Unable to open primary script: /httpd/iliffe/i_phpinfo.php (No such
> file or directory)"
> ---------------------------------

THAT is telling me that /httpd/iliffe/i_phpinfo.php is not the path to
the file. Bit like one gets with windows where it hides the real
physical location and only gives you a 'user' view of the path. My copy
of Apache is using wwwrun:www user when it is running, so all of the
/<server name> folders and files have that user name and group, but even
with that php should be able still to read the file so I'm still
thinking the path is wrong in some way. A quick search on Fedora give
/var/www/html/ as the default where SUSE gives me /srv/www/htdocs ...

> I haven't been able to find out yet if the parameter data is picked up when
> the Apache directive is coded this way. (eg: i_phpinfo.php?a=b&c=d)
>
> I seem to be getting a good argument here for backing off to PHP5!

If there was a good security reason for changing the PHP5.4 machines I'm
still running then I'd move, and eaccelerator still provides all the
speed improvement I need, so I'm not surprised three quarters the world
has yet to even move to a higher version of PHP5 ... and less that 5%
are using PHP7 front facing.

--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
John Iliffe
Re: [PHP] PHP-FPM fails to start scripts
May 24, 2017 07:20PM
On Wednesday 24 May 2017 03:40:54 Lester Caine wrote:
> On 24/05/17 02:05, John Iliffe wrote:
> > On Tuesday 23 May 2017 02:40:03 Lester Caine wrote:
> >> On 23/05/17 02:41, John Iliffe wrote:
> >>> The Apache directive invoking this script is:
> >>> ProxyPassMatch "^/.*\.php(/.*)?$"
> >>> fcgi://127.0.0.1:9015/httpd/iliffe/
> >>
> >> ProxyPassMatch ^/(.*\.php(/.*)?)$
> >
> > Some further info:
> >
> > Yes, /httpd is the root directory for the web pages. The production
> > server has a lot of named virtual hosts on it and each one has a
> > document root of /httpd/<server name>/ and the test server is set up
> > the same way. The test server is www.iliffe.ca and its document root
> > thus becomes /httpd/iliffe plus a few subs below that where needed.
> > In this case, there are no additional subs.
>
> One of the major problems with Linux is the way each distribution
> modifies just where it installs key applications and how it manages
> them. I'm on SUSE myself and apart from a couple of attempts at other
> distros when the SUSE guys just totally lost the plot, I've been with
> that since version 6. My problem is installing later APACHE/PHP builds
> while maintaining the stable SUSE installs ... and getting paths right
> teds to be the problem.
>
I used to do disk management in a very large data centre in the 1970's and
so I have developed ways of keeping track of the data. For one thing, I
never intersperse the data with the system stuff and I always keep the
application software (PHP, Apache, Pgsql, etc, separate too. At the very
least that allows me to have various versions of the software and bounce
around between them. Idiosyncratic, I have been told, but it makes
managing everything easier! Once you have the paths figured out once,
everything stays the same or moves in a predictable manner.

Also, downloads from repositories have a bad habit of installing
incompatible updates. For example, any attempt to upgrade from PHP5 to
PHP7 in a automatic install will cause great and unexpected grief for the
programmers. Read the change notice!
>
> THAT is telling me that /httpd/iliffe/i_phpinfo.php is not the path to
> the file.
Yes, it is for sure. lstat in the trace gets a 0 response code which
confirms existence and file type. namei also confirms the path.

Also, there is a major cron PHP batch component to the production server
that is replicated on the test server and all of it runs correctly from a
similar directory arrangement ( /batch/... ) I had to test all of these
CLI scripts to make sure they would run correctly on PHP7.

> Bit like one gets with windows where it hides the real
> physical location and only gives you a 'user' view of the path. My copy
> of Apache is using wwwrun:www user when it is running, so all of the
> /<server name> folders and files have that user name and group, but even
> with that php should be able still to read the file so I'm still
> thinking the path is wrong in some way. A quick search on Fedora give
> /var/www/html/ as the default where SUSE gives me /srv/www/htdocs ...
>
> >
> > I seem to be getting a good argument here for backing off to PHP5!
>
> If there was a good security reason for changing the PHP5.4 machines I'm
> still running then I'd move, and eaccelerator still provides all the
> speed improvement I need, so I'm not surprised three quarters the world
> has yet to even move to a higher version of PHP5 ... and less that 5%
> are using PHP7 front facing.
I've been playing with this since January with absolutely no useful results
so I think I will conclude that there is a serious unresolved problem with
PHP7 and back off to PHP5. I still have the unmodified versions of the
scripts that required changes (3 out of several hundred) and I suspect that
they would have run except that they were badly written in the first place.

Thanks for the help Lester.

John






--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
John Iliffe
Re: [PHP] PHP-FPM fails to start scripts
May 25, 2017 07:50PM
On Wednesday 24 May 2017 03:40:54 Lester Caine wrote:
> On 24/05/17 02:05, John Iliffe wrote:
> > On Tuesday 23 May 2017 02:40:03 Lester Caine wrote:
> >> On 23/05/17 02:41, John Iliffe wrote:
> >>> The Apache directive invoking this script is:
> >>> ProxyPassMatch "^/.*\.php(/.*)?$"
> >>> fcgi://127.0.0.1:9015/httpd/iliffe/
> >>
> >> ProxyPassMatch ^/(.*\.php(/.*)?)$
> >> fcgi://127.0.0.1:9015/httpd/iliffe/$1 was your original line, and
> >> this should have resulted in the right trimming of slashes while I
> >> think you are currently getting the double slash because of the
> >> trailing one in your current string.
> >
> > Please ignore this following paragraph. It was an attempt at a
> > minimalist ProxyPassMatch that would bypass any regex errors. It
> > isn't useful in the real world so I dropped trying it. I think you
> > got that info from the Apache mailing list.
>
> I suggested it simply because it would bypass some errors ;)
>
> >> ProxyPassMatch ^/info$
> >> fcgi://127.0.0.1:9015/httpd/iliffe/i_phpinfo.php and
> >> http://localhost/info should work ... but is /httpd REALLY a root
> >> folder? I'm getting /srv/www/htdocs as the default root, and I
> >> switch to /srv/website/test.com for each website ...
> >
> > Some further info:
> >
> > Yes, /httpd is the root directory for the web pages. The production
> > server has a lot of named virtual hosts on it and each one has a
> > document root of /httpd/<server name>/ and the test server is set up
> > the same way. The test server is www.iliffe.ca and its document root
> > thus becomes /httpd/iliffe plus a few subs below that where needed.
> > In this case, there are no additional subs.
>
> One of the major problems with Linux is the way each distribution
> modifies just where it installs key applications and how it manages
> them. I'm on SUSE myself and apart from a couple of attempts at other
> distros when the SUSE guys just totally lost the plot, I've been with
> that since version 6. My problem is installing later APACHE/PHP builds
> while maintaining the stable SUSE installs ... and getting paths right
> teds to be the problem.
>
> > When I tried the $1 extension as you suggested it didn't work, see
> > previous memo; so I removed the $1 and also the last '/' in the
> > ProxyPassMatch directive and now php-fpm has the correct path and
> > file but without the double '//'. So, this is one case where a
> > trailing / on a directory does not work/isn't required. Here is the
> > strace record:
> >
> > -------------------------------
> > 5254 20:14:55 lstat("/httpd/iliffe/i_phpinfo.php",
> > {st_mode=S_IFREG|0644, st_size=213, ...}) = 0
> > --------------------------------
> >
> > php-fpm received a 0 from lstat (file exists), is a regular file
> > (S_IFREG) and is readable (0644). So that makes no difference to the
> > result. php-fpm still backs down the directory tree and then tries
> > to stat the wrong file name. Just for completeness, here is the
> > php-fpm log entry:
> >
> > ----------------------------------
> > [23-May-2017 20:14:55] WARNING: [pool www] child 5254 said into
> > stderr: "ERROR: Unable to open primary script:
> > /httpd/iliffe/i_phpinfo.php (No such file or directory)"
> > ---------------------------------
>
> THAT is telling me that /httpd/iliffe/i_phpinfo.php is not the path to
> the file. Bit like one gets with windows where it hides the real
> physical location and only gives you a 'user' view of the path. My copy
> of Apache is using wwwrun:www user when it is running, so all of the
> /<server name> folders and files have that user name and group, but even
> with that php should be able still to read the file so I'm still
> thinking the path is wrong in some way. A quick search on Fedora give
> /var/www/html/ as the default where SUSE gives me /srv/www/htdocs ...
>
> > I haven't been able to find out yet if the parameter data is picked up
> > when the Apache directive is coded this way. (eg:
> > i_phpinfo.php?a=b&c=d)
> >
> > I seem to be getting a good argument here for backing off to PHP5!
>
> If there was a good security reason for changing the PHP5.4 machines I'm
> still running then I'd move, and eaccelerator still provides all the
> speed improvement I need, so I'm not surprised three quarters the world
> has yet to even move to a higher version of PHP5 ... and less that 5%
> are using PHP7 front facing.

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
John Iliffe
Re: [PHP] PHP-FPM fails to start scripts
May 25, 2017 07:50PM
On Wednesday 24 May 2017 03:40:54 Lester Caine wrote:
> On 24/05/17 02:05, John Iliffe wrote:
> > On Tuesday 23 May 2017 02:40:03 Lester Caine wrote:
> >> On 23/05/17 02:41, John Iliffe wrote:
> >>> The Apache directive invoking this script is:
> >>> ProxyPassMatch "^/.*\.php(/.*)?$"
> >>> fcgi://127.0.0.1:9015/httpd/iliffe/
> >>
Lester:

Just as an FYI, I installed PHP-5.6.30 and without any changes to the
Apache config files everything came up perfectly and works so far as I can
see.

So, the problem is PHP-7.

John

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Sorry, only registered users may post in this forum.

Click here to login