Re: [users@httpd] 403 error upon upgrade

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 fo

Re: [users@httpd] 403 error upon upgrade

vhosts do not bind to ports - the Listen directive does. On Thu, Oct 4, 2018 at 3:17 PM Filipe Cifali 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,

Re: [users@httpd] 403 error upon upgrade

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.

Re: [users@httpd] 403 error upon upgrade

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 wrote: > > Here's what I get for the first part of that: > > # netstat -napo | egrep "(:80|:443)" > tcp0 0 1.2.3.4:43160 23.210.206.246:443

Re: [users@httpd] 403 error upon upgrade

Here's what I get for the first part of that: # netstat -napo | egrep "(:80|:443)" tcp0 0 1.2.3.4:43160 23.210.206.246:443 ESTABLISHED 1961/(squid-1) off (0.00/0/0) tcp0 0 1.2.3.4:59116 107.14.47.80:80 TIME_WAIT - timewait

Re: [users@httpd] 403 error upon upgrade

On Thu, Oct 4, 2018 at 2:01 PM Jack M. Nilles 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 squi

Re: [users@httpd] 403 error upon upgrade

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|e

Re: [users@httpd] 403 error upon upgrade

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

Re: [users@httpd] 403 error upon upgrade

http://wiki.apache.org/httpd/CouldNotBindToAddress will help you troubleshoot that error. On Wed, Oct 3, 2018 at 8:21 PM Filipe Cifali 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: co

Re: [users@httpd] 403 error upon upgrade

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

Re: [users@httpd] 403 error upon upgrade

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 gracef

Re: [users@httpd] 403 error upon upgrade

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

Re: [users@httpd] 403 error upon upgrade

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 wrote: > I just noticed, upon running 'apache2ctl -S', that the server root is

Re: [users@httpd] 403 error upon upgrade

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

Re: [users@httpd] 403 error upon upgrade

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/

Re: [users@httpd] 403 error upon upgrade

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

Re: [users@httpd] 403 error upon upgrade

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 wrote: >

Re: [users@httpd] 403 error upon upgrade

mpm_prefork_module is/was loaded. > On 2 Oct 2018, at 8:24, Frank Gingras 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 an

Re: [users@httpd] 403 error upon upgrade

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 -- or not. The commented text is a tad amb

Re: [users@httpd] 403 error upon upgrade

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 wrote: > http://wiki.apache.org/httpd/php is a good starting poin

Re: [users@httpd] 403 error upon upgrade

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

Re: [users@httpd] 403 error upon upgrade

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_

Re: [users@httpd] 403 error upon upgrade

It is indeed recommended *not* to use 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 wrote: > Are you sure you have mod_php installed and active? This would expla

Re: [users@httpd] 403 error upon upgrade

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 wrote: > /etc/apache2/conf.d/php5.conf is as follows: > > > >SetHandler application/x-httpd-php > >

Re: [users@httpd] 403 error upon upgrade

/etc/apache2/conf.d/php5.conf is as follows: SetHandler application/x-httpd-php SetHandler application/x-httpd-php-source DirectoryIndex index.php4 DirectoryIndex index.php5 DirectoryIndex index.php Why this doesn't w

Re: [users@httpd] 403 error upon upgrade

It worked before because you had other DirectoryIndex directives (mostly unaware of that fact). Now, you need DIrectoryIndex index.html index.php or just DirectoryIndex index.php On Sun, Sep 30, 2018 at 4:36 PM Jack M. Nilles wrote: > I don't have an index.html in that directory -- only index.p

Re: [users@httpd] 403 error upon upgrade

I don't have an index.html in that directory -- only index.php. I suppose I could put in an html file that immediately switches to the php page. That site has always worked before with no index.html file. Why not now? - To uns

Re: [users@httpd] 403 error upon upgrade

> Jerry Martinez > Owner & Lead Developer > > JM Web Services, Inc > 786.412.1660 | www.jmweb.net > > > -Original Message- > From: Jerry Martinez [mailto:je...@jmweb.net] > Sent: Sunday, September 30, 2018 2:47 PM > To: 'users@httpd.apache.org'

RE: [users@httpd] 403 error upon upgrade

worked flawlessly. Jerry Martinez Owner & Lead Developer JM Web Services, Inc 786.412.1660 | www.jmweb.net -Original Message- From: Jerry Martinez [mailto:je...@jmweb.net] Sent: Sunday, September 30, 2018 2:47 PM To: 'users@httpd.apache.org' Subject: RE: [users@httpd] 403 erro

RE: [users@httpd] 403 error upon upgrade

:14 PM To: users@httpd.apache.org Subject: Re: [users@httpd] 403 error upon upgrade > Date: Sunday, September 30, 2018 10:44:28 -0700 > From: "Jack M. Nilles" > > Basically the same as before: > > [Sun Sep 30 10:29:05.708882 2018] [autoindex:error] [pid 3663] [cl

Re: [users@httpd] 403 error upon upgrade

> Date: Sunday, September 30, 2018 10:44:28 -0700 > From: "Jack M. Nilles" > > Basically the same as before: > > [Sun Sep 30 10:29:05.708882 2018] [autoindex:error] [pid 3663] > [client 220.181.51.119:50416] AH01276: Cannot serve directory > /home/data/site1/htdocs/: No matching DirectoryIndex

Re: [users@httpd] 403 error upon upgrade

Basically the same as before: [Sun Sep 30 10:29:05.708882 2018] [autoindex:error] [pid 3663] [client 220.181.51.119:50416] AH01276: Cannot serve directory /home/data/site1/htdocs/: No matching DirectoryIndex (index.html,index.html.var) found, and server-generated directory index forbidden by Op

Re: [users@httpd] 403 error upon upgrade

What does the error log say now? On Sat, Sep 29, 2018 at 5:01 PM Jack M. Nilles wrote: > I have found another DirectoryIndex directive in > /etc/apache2/conf.d/gitweb.conf. Since this is higher up the chain than the > vhosts.d directory that might be what's producing the file download > behavior

Re: [users@httpd] 403 error upon upgrade

I have found another DirectoryIndex directive in /etc/apache2/conf.d/gitweb.conf. Since this is higher up the chain than the vhosts.d directory that might be what's producing the file download behavior. If I omit the DirectoryIndex line and restart apache then I at least just get the 403 error

Re: [users@httpd] 403 error upon upgrade

You still need to set AllowOverride none in the block to prevent .htaccess files from interfering. As for the index file being downloaded, if it's static content, see: http://httpd.apache.org/docs/current/mod/mod_mime.html#addtype If it's a php file, see: http://wiki.apache.org/httpd/php Last

Re: [users@httpd] 403 error upon upgrade

Frank, Sorry for the typos. I've corrected the code below to be consistent. The error message was, and is (I am anonymizing the directory details): [Fri Sep 28 15:15:39.301689 2018] [autoindex:error] [pid 17591] [client 1.2.3.4:45731] AH01276: Cannot serve directory /home/data/site1/htdocs/: No

Re: [users@httpd] 403 error upon upgrade

There is no reference to "webdir" anywhere in your configuration, so you effectively munged it to the point that we cannot help you. Further, I would recommend setting AllowOverride none in every single block - the last thing you want is for a rogue .htaccess file to interfere. If the sole purpos