You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by "Jack M. Nilles" <jn...@jala.com> on 2018/10/01 20:36:41 UTC
Re: [users@httpd] 403 error upon upgrade
/etc/apache2/conf.d/php5.conf is as follows:
<IfModule mod_php5.c>
<FilesMatch "\.ph(p[345]?|tml)$">
SetHandler application/x-httpd-php
</FilesMatch>
<FilesMatch "\.php[345]?s$">
SetHandler application/x-httpd-php-source
</FilesMatch>
DirectoryIndex index.php4
DirectoryIndex index.php5
DirectoryIndex index.php
</IfModule>
Why this doesn't work is a mystery to me. Especially since it is included as part of the vhosts.conf file. Should I put the 'Include /etc/apache2/conf.d/*.conf' directive earlier in the conf file? Does the order make a difference?
BTW, if I copy the current index.php file on site1 to index.html the latter displays without the ssl decorations. However, the site still won't display any php files.
Re: [users@httpd] 403 error upon upgrade
Posted by "Jack M. Nilles" <jn...@jala.com>.
Eureka!! I found a new or recently revised file: /etc/apache2/listen.conf. That had a pair of listen lines under NameVirtualHost that I commented out. Restarting apache then produced a running server.
Thanks, guys, for your patience and help! I will keep your emails in my Whatthehell? folder for future reference.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] 403 error upon upgrade
Posted by Frank Gingras <th...@apache.org>.
vhosts do not bind to ports - the Listen directive does.
On Thu, Oct 4, 2018 at 3:17 PM Filipe Cifali <ci...@gmail.com>
wrote:
> Because something else could be listening on those ports, preventing httpd
> from starting. This is not so uncommon to happen. httpd is complaining on
> listening to both IPv4 and IPv6, so maybe a greedy virtualhost is trying to
> map more addresses than it should?
>
> On Thu, Oct 4, 2018 at 3:59 PM Jack M. Nilles <jn...@jala.com> wrote:
>
>> Of course, since Apache isn't running -- failed to start -- why would I
>> get any LISTEN ports?
>>
>> On 4 Oct 2018, at 11:46, Jack M. Nilles <jn...@jala.com> wrote:
>>
>> Here's what I get for the first part of that:
>>
>> * #* netstat -napo | egrep "(:80|:443)"
>> tcp 0 0 1.2.3.4:43160 23.210.206.246*:443*
>> ESTABLISHED 1961/(squid-1) off (0.00/0/0)
>> tcp 0 0 1.2.3.4:59116 107.14.47.80*:80*
>> TIME_WAIT - timewait (45.97/0/0)
>> tcp 0 0 1.2.3.4:48181 52.20.156.66*:443*
>> ESTABLISHED 1961/(squid-1) off (0.00/0/0)
>> tcp 0 0 1.2.3.4:41114 17.248.129.179*:443*
>> TIME_WAIT - timewait (58.11/0/0)
>> tcp 0 0 1.2.3.4:55151 52.32.170.59*:443*
>> ESTABLISHED 1961/(squid-1) off (0.00/0/0)
>> tcp 0 0 1.2.3.4:59019 172.217.14.74*:443*
>> TIME_WAIT - timewait (33.72/0/0)
>> tcp 0 0 1.2.3.4:52752 216.17.8.47*:443*
>> ESTABLISHED 710/java keepalive (320.48/0/0)
>>
>>
>> and I get no return for *#* netstat -napo | egrep "(:80|:443)" | grep
>> LISTEN
>>
>> On 4 Oct 2018, at 11:13, Filipe Cifali <ci...@gmail.com> wrote:
>>
>> netstat -napo|egrep "(:80|:443) |grep LISTEN
>>
>>
>>
>>
>
> --
> [ ]'s
>
> Filipe Cifali Stangler
>
Re: [users@httpd] 403 error upon upgrade
Posted by Filipe Cifali <ci...@gmail.com>.
Because something else could be listening on those ports, preventing httpd
from starting. This is not so uncommon to happen. httpd is complaining on
listening to both IPv4 and IPv6, so maybe a greedy virtualhost is trying to
map more addresses than it should?
On Thu, Oct 4, 2018 at 3:59 PM Jack M. Nilles <jn...@jala.com> wrote:
> Of course, since Apache isn't running -- failed to start -- why would I
> get any LISTEN ports?
>
> On 4 Oct 2018, at 11:46, Jack M. Nilles <jn...@jala.com> wrote:
>
> Here's what I get for the first part of that:
>
> * #* netstat -napo | egrep "(:80|:443)"
> tcp 0 0 1.2.3.4:43160 23.210.206.246*:443*
> ESTABLISHED 1961/(squid-1) off (0.00/0/0)
> tcp 0 0 1.2.3.4:59116 107.14.47.80*:80* TIME_WAIT
> - timewait (45.97/0/0)
> tcp 0 0 1.2.3.4:48181 52.20.156.66*:443*
> ESTABLISHED 1961/(squid-1) off (0.00/0/0)
> tcp 0 0 1.2.3.4:41114 17.248.129.179*:443* TIME_WAIT
> - timewait (58.11/0/0)
> tcp 0 0 1.2.3.4:55151 52.32.170.59*:443*
> ESTABLISHED 1961/(squid-1) off (0.00/0/0)
> tcp 0 0 1.2.3.4:59019 172.217.14.74*:443* TIME_WAIT
> - timewait (33.72/0/0)
> tcp 0 0 1.2.3.4:52752 216.17.8.47*:443*
> ESTABLISHED 710/java keepalive (320.48/0/0)
>
>
> and I get no return for *#* netstat -napo | egrep "(:80|:443)" | grep
> LISTEN
>
> On 4 Oct 2018, at 11:13, Filipe Cifali <ci...@gmail.com> wrote:
>
> netstat -napo|egrep "(:80|:443) |grep LISTEN
>
>
>
>
--
[ ]'s
Filipe Cifali Stangler
Re: [users@httpd] 403 error upon upgrade
Posted by "Jack M. Nilles" <jn...@jala.com>.
Of course, since Apache isn't running -- failed to start -- why would I get any LISTEN ports?
> On 4 Oct 2018, at 11:46, Jack M. Nilles <jn...@jala.com> wrote:
>
> Here's what I get for the first part of that:
>
> # netstat -napo | egrep "(:80|:443)"
> tcp 0 0 1.2.3.4:43160 23.210.206.246:443 ESTABLISHED 1961/(squid-1) off (0.00/0/0)
> tcp 0 0 1.2.3.4:59116 107.14.47.80:80 TIME_WAIT - timewait (45.97/0/0)
> tcp 0 0 1.2.3.4:48181 52.20.156.66:443 ESTABLISHED 1961/(squid-1) off (0.00/0/0)
> tcp 0 0 1.2.3.4:41114 17.248.129.179:443 TIME_WAIT - timewait (58.11/0/0)
> tcp 0 0 1.2.3.4:55151 52.32.170.59:443 ESTABLISHED 1961/(squid-1) off (0.00/0/0)
> tcp 0 0 1.2.3.4:59019 172.217.14.74:443 TIME_WAIT - timewait (33.72/0/0)
> tcp 0 0 1.2.3.4:52752 216.17.8.47:443 ESTABLISHED 710/java keepalive (320.48/0/0)
>
> and I get no return for # netstat -napo | egrep "(:80|:443)" | grep LISTEN
>
>> On 4 Oct 2018, at 11:13, Filipe Cifali <cifali.filipe@gmail.com <ma...@gmail.com>> wrote:
>>
>> netstat -napo|egrep "(:80|:443) |grep LISTEN
>
Re: [users@httpd] 403 error upon upgrade
Posted by "Jack M. Nilles" <jn...@jala.com>.
Here's what I get for the first part of that:
# netstat -napo | egrep "(:80|:443)"
tcp 0 0 1.2.3.4:43160 23.210.206.246:443 ESTABLISHED 1961/(squid-1) off (0.00/0/0)
tcp 0 0 1.2.3.4:59116 107.14.47.80:80 TIME_WAIT - timewait (45.97/0/0)
tcp 0 0 1.2.3.4:48181 52.20.156.66:443 ESTABLISHED 1961/(squid-1) off (0.00/0/0)
tcp 0 0 1.2.3.4:41114 17.248.129.179:443 TIME_WAIT - timewait (58.11/0/0)
tcp 0 0 1.2.3.4:55151 52.32.170.59:443 ESTABLISHED 1961/(squid-1) off (0.00/0/0)
tcp 0 0 1.2.3.4:59019 172.217.14.74:443 TIME_WAIT - timewait (33.72/0/0)
tcp 0 0 67.52.184.146:52752 216.17.8.47:443 ESTABLISHED 710/java keepalive (320.48/0/0)
and I get no return for # netstat -napo | egrep "(:80|:443)" | grep LISTEN
> On 4 Oct 2018, at 11:13, Filipe Cifali <ci...@gmail.com> wrote:
>
> netstat -napo|egrep "(:80|:443) |grep LISTEN
Re: [users@httpd] 403 error upon upgrade
Posted by Filipe Cifali <ci...@gmail.com>.
Jack, don't confuse INCOMING/OUTGOING connections with LISTEN.
Seems this site is gathering some info from other sites, you can see the
commands running *Java* and *squid*, if you have netstat installed
(otherwise just install it because it's super flexible and easy to use?)
run a `netstat -napo|egrep "(:80|:443) |grep LISTEN`
On Thu, Oct 4, 2018 at 3:01 PM Jack M. Nilles <jn...@jala.com> wrote:
> Here's what I get:
>
> *#* lsof -i:443
> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
> java 710 root 245u IPv6 49204 0t0 TCP server.site1.com:52752
> ->central.crashplanpro.com:https (ESTABLISHED)
> squid 1961 squid 13u IPv4 19134 0t0 TCP server.site1.com
> 55151->ec2-52-32-170-59.us-west-2.compute.amazonaws.com:https
> (ESTABLISHED)
> squid 1961 squid 20u IPv4 164585 0t0 TCP server.site1.com
> 43093->a23-210-206-246.deploy.static.akamaitechnologies.com:https
> (ESTABLISHED)
> squid 1961 squid 26u IPv4 18354 0t0 TCP server.site1.com
> 48181->ec2-52-20-156-66.compute-1.amazonaws.com:https (ESTABLISHED)
>
> and
>
> *#* apache2ctl restart
> httpd not running, trying to start
> (98)Address already in use: AH00072: make_sock: could not bind to address
> [::]:443
> (98)Address already in use: AH00072: make_sock: could not bind to address
> 0.0.0.0:80
> no listening sockets available, shutting down
> AH00015: Unable to open logs
>
> So four established connections, one of which is IPV6 (a backup resource).
> Why am I limited to 4 connections?
>
--
[ ]'s
Filipe Cifali Stangler
Re: [users@httpd] 403 error upon upgrade
Posted by Eric Covener <co...@gmail.com>.
On Thu, Oct 4, 2018 at 2:01 PM Jack M. Nilles <jn...@jala.com> wrote:
>
> Here's what I get:
>
> # lsof -i:443
> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
> java 710 root 245u IPv6 49204 0t0 TCP server.site1.com:52752->central.crashplanpro.com:https (ESTABLISHED)
> squid 1961 squid 13u IPv4 19134 0t0 TCP server.site1.com 55151->ec2-52-32-170-59.us-west-2.compute.amazonaws.com:https (ESTABLISHED)
> squid 1961 squid 20u IPv4 164585 0t0 TCP server.site1.com 43093->a23-210-206-246.deploy.static.akamaitechnologies.com:https (ESTABLISHED)
> squid 1961 squid 26u IPv4 18354 0t0 TCP server.site1.com 48181->ec2-52-20-156-66.compute-1.amazonaws.com:https (ESTABLISHED)
>
> and
>
> # apache2ctl restart
> httpd not running, trying to start
> (98)Address already in use: AH00072: make_sock: could not bind to address [::]:443
> (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
> no listening sockets available, shutting down
> AH00015: Unable to open logs
>
> So four established connections, one of which is IPV6 (a backup resource). Why am I limited to 4 connections?
Those aren't listening sockets. Your problem is more likely
overlapping Listens in Apache config files, not processes outside of
Apache.
--
Eric Covener
covener@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] 403 error upon upgrade
Posted by "Jack M. Nilles" <jn...@jala.com>.
Here's what I get:
# lsof -i:443
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
java 710 root 245u IPv6 49204 0t0 TCP server.site1.com:52752->central.crashplanpro.com:https (ESTABLISHED)
squid 1961 squid 13u IPv4 19134 0t0 TCP server.site1.com 55151->ec2-52-32-170-59.us-west-2.compute.amazonaws.com:https (ESTABLISHED)
squid 1961 squid 20u IPv4 164585 0t0 TCP server.site1.com 43093->a23-210-206-246.deploy.static.akamaitechnologies.com:https (ESTABLISHED)
squid 1961 squid 26u IPv4 18354 0t0 TCP server.site1.com 48181->ec2-52-20-156-66.compute-1.amazonaws.com:https (ESTABLISHED)
and
# apache2ctl restart
httpd not running, trying to start
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:443
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
So four established connections, one of which is IPV6 (a backup resource). Why am I limited to 4 connections?
Re: [users@httpd] 403 error upon upgrade
Posted by Frank Gingras <th...@apache.org>.
http://wiki.apache.org/httpd/CouldNotBindToAddress will help you
troubleshoot that error.
On Wed, Oct 3, 2018 at 8:21 PM Filipe Cifali <ci...@gmail.com>
wrote:
> Jack, the logs saying you can't bind the addresses:
>
> Oct 03 14:44:01 donner start_apache2[3998]: (98)Address already in use:
> AH00072: make_sock: could not bind to address [::]:443
> Oct 03 14:44:01 donner start_apache2[3998]: (98)Address already in use:
> AH00072: make_sock: could not bind to address 0.0.0.0:80
> Oct 03 14:44:01 donner start_apache2[3998]: AH00015: Unable to open logs
>
> This are the important bits, also, you should set error_log and put debug
> level on it if you can't find out why.
>
> On Wed, Oct 3, 2018 at 7:15 PM Jack M. Nilles <jn...@jala.com> wrote:
>
>> A few minutes later I get:
>>
>> apache2.service - The Apache Webserver
>> Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled)
>> Active: *failed* (Result: exit-code) since Wed 2018-10-03 15:10:27
>> PDT; 38s ago
>> Process: 5147 ExecStop=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND
>> -k graceful-stop (code=exited, status=0/SUCCESS)
>> Process: 5140 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND
>> -k start *(code=exited, status=1/FAILURE)*
>> Main PID: 5140 (code=exited, status=1/FAILURE)
>>
>> This after I tracked down some port interference.
>>
>>
>>
>>
>
> --
> [ ]'s
>
> Filipe Cifali Stangler
>
Re: [users@httpd] 403 error upon upgrade
Posted by Filipe Cifali <ci...@gmail.com>.
Jack, the logs saying you can't bind the addresses:
Oct 03 14:44:01 donner start_apache2[3998]: (98)Address already in use:
AH00072: make_sock: could not bind to address [::]:443
Oct 03 14:44:01 donner start_apache2[3998]: (98)Address already in use:
AH00072: make_sock: could not bind to address 0.0.0.0:80
Oct 03 14:44:01 donner start_apache2[3998]: AH00015: Unable to open logs
This are the important bits, also, you should set error_log and put debug
level on it if you can't find out why.
On Wed, Oct 3, 2018 at 7:15 PM Jack M. Nilles <jn...@jala.com> wrote:
> A few minutes later I get:
>
> apache2.service - The Apache Webserver
> Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled)
> Active: *failed* (Result: exit-code) since Wed 2018-10-03 15:10:27
> PDT; 38s ago
> Process: 5147 ExecStop=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k
> graceful-stop (code=exited, status=0/SUCCESS)
> Process: 5140 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND
> -k start *(code=exited, status=1/FAILURE)*
> Main PID: 5140 (code=exited, status=1/FAILURE)
>
> This after I tracked down some port interference.
>
>
>
>
--
[ ]'s
Filipe Cifali Stangler
Re: [users@httpd] 403 error upon upgrade
Posted by "Jack M. Nilles" <jn...@jala.com>.
A few minutes later I get:
apache2.service - The Apache Webserver
Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled)
Active: failed (Result: exit-code) since Wed 2018-10-03 15:10:27 PDT; 38s ago
Process: 5147 ExecStop=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful-stop (code=exited, status=0/SUCCESS)
Process: 5140 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start (code=exited, status=1/FAILURE)
Main PID: 5140 (code=exited, status=1/FAILURE)
This after I tracked down some port interference.
Re: [users@httpd] 403 error upon upgrade
Posted by "Jack M. Nilles" <jn...@jala.com>.
Well, I have now set SuSE's YaST to reconfigure apache2 using the same vhosts.conf file while ensuring that php5 is running. Now apache won't start. I have moved from a 403 error to a site can't be reached error. I get the following output from systemctl status apache2.service:
apache2.service - The Apache Webserver
Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled)
Active: failed (Result: exit-code) since Wed 2018-10-03 14:44:01 PDT; 6min ago
Process: 4006 ExecStop=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful-stop (code=exited, status=0/SUCCESS)
Process: 3998 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start (code=exited, status=1/FAILURE)
Main PID: 3998 (code=exited, status=1/FAILURE)
Oct 03 14:44:01 donner start_apache2[3998]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:443
Oct 03 14:44:01 donner start_apache2[3998]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Oct 03 14:44:01 donner start_apache2[3998]: no listening sockets available, shutting down
Oct 03 14:44:01 donner start_apache2[3998]: AH00015: Unable to open logs
Oct 03 14:44:01 donner systemd[1]: apache2.service: main process exited, code=exited, status=1/FAILURE
Oct 03 14:44:01 donner start_apache2[4006]: httpd (no pid file) not running
Oct 03 14:44:01 donner systemd[1]: Failed to start The Apache Webserver.
Oct 03 14:44:01 donner systemd[1]: Unit apache2.service entered failed state.
Any hints?
Re: [users@httpd] 403 error upon upgrade
Posted by Frank Gingras <th...@apache.org>.
The main document root does not interfere with your vhosts. See:
http://httpd.apache.org/docs/current/vhosts/name-based.html#using (See note
about "Main host goes away")
On Wed, Oct 3, 2018 at 2:40 PM Jack M. Nilles <jn...@jala.com> wrote:
> I just noticed, upon running 'apache2ctl -S', that the server root is
> listed as "/srv/www" and the document root as "/srv/www/htdocs" while the
> actual document roots are elsewhere (such as /home/data/site1/htdocs). I'm
> assuming that the vhosts.conf file takes care of this linkage. If it
> doesn't might that be the problem?
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
Re: [users@httpd] 403 error upon upgrade
Posted by "Jack M. Nilles" <jn...@jala.com>.
I just noticed, upon running 'apache2ctl -S', that the server root is listed as "/srv/www" and the document root as "/srv/www/htdocs" while the actual document roots are elsewhere (such as /home/data/site1/htdocs). I'm assuming that the vhosts.conf file takes care of this linkage. If it doesn't might that be the problem?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] 403 error upon upgrade
Posted by Filipe Cifali <ci...@gmail.com>.
Jack, you have to either load mod_php (which comes from compiling /
installing PHP in a certain way) or change the way you are using PHP on the
overall with httpd. Searching for how to install mod_php on SUSE X (being X
the version you are running) should provide frutiferous info, but I'm a
debian/rhel user so I'm not sure how YaST does things its way.
On Tue, Oct 2, 2018 at 6:47 PM Jack M. Nilles <jn...@jala.com> wrote:
> Frank,
>
> My main concern is to get apache to run with php at all, never mind
> scalability issues. So far everything looks fine except that it doesn't
> work. Maybe somewhere in the bowels of SuSE 42.1 there is an error.
>
> Jack
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
--
[ ]'s
Filipe Cifali Stangler
Re: [users@httpd] 403 error upon upgrade
Posted by "Jack M. Nilles" <jn...@jala.com>.
Frank,
My main concern is to get apache to run with php at all, never mind scalability issues. So far everything looks fine except that it doesn't work. Maybe somewhere in the bowels of SuSE 42.1 there is an error.
Jack
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] 403 error upon upgrade
Posted by Frank Gingras <th...@apache.org>.
Jack,
The point is not to use non-threaded to increase your performance and
scalability. The event mpm has the ability to run many threads per process,
which in turn can drastically increase the number of simultaneous clients
you can serve.
On Tue, Oct 2, 2018 at 4:34 PM Jack M. Nilles <jn...@jala.com> wrote:
> mpm_prefork_module is/was loaded.
>
> On 2 Oct 2018, at 8:24, Frank Gingras <th...@apache.org> wrote:
>
> http://wiki.apache.org/httpd/php is a good starting point - I would
> recommend not using mod_php, unless you have a good reason to use it.
>
> Nowadays, mod_proxy_fcgi and php-fpm is trivial to set up, and allow you
> to use a threaded mpm, such as event.
>
> On Tue, Oct 2, 2018 at 11:21 AM Jack M. Nilles <jn...@jala.com> wrote:
>
>> Sure enough, there seems to be no php module loaded:
>>
>> Loaded Modules:
>> core_module (static)
>> so_module (static)
>> http_module (static)
>> mpm_prefork_module (static)
>> unixd_module (static)
>> systemd_module (static)
>> actions_module (shared)
>> alias_module (shared)
>> auth_basic_module (shared)
>> authn_file_module (shared)
>> authz_host_module (shared)
>> authz_groupfile_module (shared)
>> authz_user_module (shared)
>> autoindex_module (shared)
>> cgi_module (shared)
>> dir_module (shared)
>> env_module (shared)
>> expires_module (shared)
>> include_module (shared)
>> log_config_module (shared)
>> mime_module (shared)
>> negotiation_module (shared)
>> setenvif_module (shared)
>> ssl_module (shared)
>> userdir_module (shared)
>> reqtimeout_module (shared)
>> authn_core_module (shared)
>> authz_core_module (shared)
>> rewrite_module (shared)
>> version_module (shared)
>>
>> How do I get it on board?
>>
>>
>>
>
Re: [users@httpd] 403 error upon upgrade
Posted by "Jack M. Nilles" <jn...@jala.com>.
mpm_prefork_module is/was loaded.
> On 2 Oct 2018, at 8:24, Frank Gingras <th...@apache.org> wrote:
>
> http://wiki.apache.org/httpd/php <http://wiki.apache.org/httpd/php> is a good starting point - I would recommend not using mod_php, unless you have a good reason to use it.
>
> Nowadays, mod_proxy_fcgi and php-fpm is trivial to set up, and allow you to use a threaded mpm, such as event.
>
> On Tue, Oct 2, 2018 at 11:21 AM Jack M. Nilles <jnilles@jala.com <ma...@jala.com>> wrote:
> Sure enough, there seems to be no php module loaded:
>
> Loaded Modules:
> core_module (static)
> so_module (static)
> http_module (static)
> mpm_prefork_module (static)
> unixd_module (static)
> systemd_module (static)
> actions_module (shared)
> alias_module (shared)
> auth_basic_module (shared)
> authn_file_module (shared)
> authz_host_module (shared)
> authz_groupfile_module (shared)
> authz_user_module (shared)
> autoindex_module (shared)
> cgi_module (shared)
> dir_module (shared)
> env_module (shared)
> expires_module (shared)
> include_module (shared)
> log_config_module (shared)
> mime_module (shared)
> negotiation_module (shared)
> setenvif_module (shared)
> ssl_module (shared)
> userdir_module (shared)
> reqtimeout_module (shared)
> authn_core_module (shared)
> authz_core_module (shared)
> rewrite_module (shared)
> version_module (shared)
>
> How do I get it on board?
>
>
Re: [users@httpd] 403 error upon upgrade
Posted by "Jack M. Nilles" <jn...@jala.com>.
The package manager (YaST) shows php5.5 as installed so it should have php-fpm in its code base.
I notice that /etc/php5/apache2/php.ini at present has short_open_tag = Off which might be the clue to its ignoring all the code in these sites that use <?php and ?> -- or not. The commented text is a tad ambiguous.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] 403 error upon upgrade
Posted by Filipe Cifali <ci...@gmail.com>.
Also double check what version of PHP SUSE server pkg manager is providing
now, this seems like a change of version where the pkg manager gone rogue
(maybe missing dependency on tree?)
On Tue, Oct 2, 2018 at 12:24 PM Frank Gingras <th...@apache.org> wrote:
> http://wiki.apache.org/httpd/php is a good starting point - I would
> recommend not using mod_php, unless you have a good reason to use it.
>
> Nowadays, mod_proxy_fcgi and php-fpm is trivial to set up, and allow you
> to use a threaded mpm, such as event.
>
> On Tue, Oct 2, 2018 at 11:21 AM Jack M. Nilles <jn...@jala.com> wrote:
>
>> Sure enough, there seems to be no php module loaded:
>>
>> Loaded Modules:
>> core_module (static)
>> so_module (static)
>> http_module (static)
>> mpm_prefork_module (static)
>> unixd_module (static)
>> systemd_module (static)
>> actions_module (shared)
>> alias_module (shared)
>> auth_basic_module (shared)
>> authn_file_module (shared)
>> authz_host_module (shared)
>> authz_groupfile_module (shared)
>> authz_user_module (shared)
>> autoindex_module (shared)
>> cgi_module (shared)
>> dir_module (shared)
>> env_module (shared)
>> expires_module (shared)
>> include_module (shared)
>> log_config_module (shared)
>> mime_module (shared)
>> negotiation_module (shared)
>> setenvif_module (shared)
>> ssl_module (shared)
>> userdir_module (shared)
>> reqtimeout_module (shared)
>> authn_core_module (shared)
>> authz_core_module (shared)
>> rewrite_module (shared)
>> version_module (shared)
>>
>> How do I get it on board?
>>
>>
>>
--
[ ]'s
Filipe Cifali Stangler
Re: [users@httpd] 403 error upon upgrade
Posted by Frank Gingras <th...@apache.org>.
http://wiki.apache.org/httpd/php is a good starting point - I would
recommend not using mod_php, unless you have a good reason to use it.
Nowadays, mod_proxy_fcgi and php-fpm is trivial to set up, and allow you to
use a threaded mpm, such as event.
On Tue, Oct 2, 2018 at 11:21 AM Jack M. Nilles <jn...@jala.com> wrote:
> Sure enough, there seems to be no php module loaded:
>
> Loaded Modules:
> core_module (static)
> so_module (static)
> http_module (static)
> mpm_prefork_module (static)
> unixd_module (static)
> systemd_module (static)
> actions_module (shared)
> alias_module (shared)
> auth_basic_module (shared)
> authn_file_module (shared)
> authz_host_module (shared)
> authz_groupfile_module (shared)
> authz_user_module (shared)
> autoindex_module (shared)
> cgi_module (shared)
> dir_module (shared)
> env_module (shared)
> expires_module (shared)
> include_module (shared)
> log_config_module (shared)
> mime_module (shared)
> negotiation_module (shared)
> setenvif_module (shared)
> ssl_module (shared)
> userdir_module (shared)
> reqtimeout_module (shared)
> authn_core_module (shared)
> authz_core_module (shared)
> rewrite_module (shared)
> version_module (shared)
>
> How do I get it on board?
>
>
>
Re: [users@httpd] 403 error upon upgrade
Posted by "Jack M. Nilles" <jn...@jala.com>.
Sure enough, there seems to be no php module loaded:
Loaded Modules:
core_module (static)
so_module (static)
http_module (static)
mpm_prefork_module (static)
unixd_module (static)
systemd_module (static)
actions_module (shared)
alias_module (shared)
auth_basic_module (shared)
authn_file_module (shared)
authz_host_module (shared)
authz_groupfile_module (shared)
authz_user_module (shared)
autoindex_module (shared)
cgi_module (shared)
dir_module (shared)
env_module (shared)
expires_module (shared)
include_module (shared)
log_config_module (shared)
mime_module (shared)
negotiation_module (shared)
setenvif_module (shared)
ssl_module (shared)
userdir_module (shared)
reqtimeout_module (shared)
authn_core_module (shared)
authz_core_module (shared)
rewrite_module (shared)
version_module (shared)
How do I get it on board?
Re: [users@httpd] 403 error upon upgrade
Posted by Frank Gingras <th...@apache.org>.
It is indeed recommended *not* to use <IfModule> for that very reason. If
the module isn't loaded, then those directives will not be evaluated. Run
apachectl -M to see loaded modules.
On Mon, Oct 1, 2018 at 5:27 PM Filipe Cifali <ci...@gmail.com>
wrote:
> Are you sure you have mod_php installed and active? This would explain the
> failing DirIndex and all of this sudden change
>
> On Mon, 1 Oct 2018 at 17:36 Jack M. Nilles <jn...@jala.com> wrote:
>
>> /etc/apache2/conf.d/php5.conf is as follows:
>>
>> <IfModule mod_php5.c>
>> <FilesMatch "\.ph(p[345]?|tml)$">
>> SetHandler application/x-httpd-php
>> </FilesMatch>
>> <FilesMatch "\.php[345]?s$">
>> SetHandler application/x-httpd-php-source
>> </FilesMatch>
>> DirectoryIndex index.php4
>> DirectoryIndex index.php5
>> DirectoryIndex index.php
>> </IfModule>
>>
>> Why this doesn't work is a mystery to me. Especially since it is included
>> as part of the vhosts.conf file. Should I put the '*Include
>> /etc/apache2/conf.d/*.conf*' directive earlier in the conf file? Does
>> the order make a difference?
>>
>> BTW, if I copy the current index.php file on site1 to index.html the
>> latter displays without the ssl decorations. However, the site still won't
>> display any php files.
>>
>>
>> --
> [ ]'s
>
> Filipe Cifali Stangler
>
Re: [users@httpd] 403 error upon upgrade
Posted by Filipe Cifali <ci...@gmail.com>.
Are you sure you have mod_php installed and active? This would explain the
failing DirIndex and all of this sudden change
On Mon, 1 Oct 2018 at 17:36 Jack M. Nilles <jn...@jala.com> wrote:
> /etc/apache2/conf.d/php5.conf is as follows:
>
> <IfModule mod_php5.c>
> <FilesMatch "\.ph(p[345]?|tml)$">
> SetHandler application/x-httpd-php
> </FilesMatch>
> <FilesMatch "\.php[345]?s$">
> SetHandler application/x-httpd-php-source
> </FilesMatch>
> DirectoryIndex index.php4
> DirectoryIndex index.php5
> DirectoryIndex index.php
> </IfModule>
>
> Why this doesn't work is a mystery to me. Especially since it is included
> as part of the vhosts.conf file. Should I put the '*Include
> /etc/apache2/conf.d/*.conf*' directive earlier in the conf file? Does the
> order make a difference?
>
> BTW, if I copy the current index.php file on site1 to index.html the
> latter displays without the ssl decorations. However, the site still won't
> display any php files.
>
>
> --
[ ]'s
Filipe Cifali Stangler