[gentoo-user] Oddities in apache2 update, other init bizarrity.

[gentoo-user] Oddities in apache2 update, other init bizarrity.

[Kevin O'Gorman]

[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]

Stable x86 just got a new apache server, and it's puzzling me.

For one thing, /etc/conf.d/apache2 now ends with this

# Environment variables to keep
# All environment variables are cleared from apache
# Use this to preserve some of them
# NOTE!!! It's very important that this contains PATH
# TODO: Phase this out in favor of /etc/conf.d/env_whitelist
#KEEPENV="PATH"

It has said all along that it's important to have PATH, but now it's
commented out without any replacement in env_whitelist.
Moreover, there's no example in env_whitelist to show the syntax.  I just
put PATH in there on  a line of its own, and hoped for the best.

The bigger puzzle is this one:  I can't stop apache because it can't be
found, but I also can't start it because it's already running.  It is in
fact running and serving web pages.  But I'd like the init stuff to be a lot
more consistent.

The confusion about cupsd and vmware is a separate issue I've been meaning
to ask about for months; I don't think it has anything to do with apache2.

treat ~ # cd /etc/init.d
treat init.d # ./apache2 stop
 * Stopping apache2 ...
No /usr/sbin/apache2 found running; none
killed.
[ !! ]
treat init.d # ./apache2 start
 * WARNING:  apache2 has already been started.
treat init.d # ./apache2 status
 * Caching service dependencies ...
 *  Service 'cupsd' should be AFTER service 'vmware', but one of
 *  the services 'vmware' depends on, depends on
'cupsd'!
[ ok ]
 * status:  started
treat init.d #
-- 
Kevin O'Gorman, PhD

[-- Attachment #2: Type: text/html, Size: 3133 bytes --]

Re: [gentoo-user] Oddities in apache2 update, other init bizarrity.

[Dan Farrell]

On Tue, 4 Sep 2007 19:55:44 -0700
"Kevin O'Gorman" <kogorman@gmail.com> wrote:

> treat ~ # cd /etc/init.d
> treat init.d # ./apache2 stop
>  * Stopping apache2 ...
> No /usr/sbin/apache2 found running; none
> killed.
> [ !! ]
> treat init.d # ./apache2 start
>  * WARNING:  apache2 has already been started.
Have you tried 	# /etc/init.d/apache2 zap
		# killall apache2
		# /etc/init.d/apache2 start	
?

> treat init.d # ./apache2 status
>  * Caching service dependencies ...
>  *  Service 'cupsd' should be AFTER service 'vmware', but one of
>  *  the services 'vmware' depends on, depends on
> 'cupsd'!
the dependancies are pretty easy to find and even adjust
in /etc/init.d; in fact, for cups, head does a really nice job of
clipping the whole thing as an example: 
|dan@pascal ~ $ head /etc/init.d/cupsd 
|#!/sbin/runscript
|
|depend() {
|        use net
|        after logger
|        before nfs
|        use hotplug
|        after vmware
|}
you can list for vmware too, and see which of those depends on cups,
and fix this circular dependency issue; if you do so, you might want to
consider filing a bug report so others can fix it automatically on next
update.  
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Oddities in apache2 update, other init bizarrity.

[Grant]

> Stable x86 just got a new apache server, and it's puzzling me.
>
> For one thing, /etc/conf.d/apache2 now ends with this
>
> # Environment variables to keep
> # All environment variables are cleared from apache
>  # Use this to preserve some of them
> # NOTE!!! It's very important that this contains PATH
> # TODO: Phase this out in favor of /etc/conf.d/env_whitelist
> #KEEPENV="PATH"
>
> It has said all along that it's important to have PATH, but now it's
> commented out without any replacement in env_whitelist.
> Moreover, there's no example in env_whitelist to show the syntax.  I just
> put PATH in there on  a line of its own, and hoped for the best.
>
> The bigger puzzle is this one:  I can't stop apache because it can't be
> found, but I also can't start it because it's already running.  It is in
> fact running and serving web pages.  But I'd like the init stuff to be a lot
> more consistent.

I had the same problem yesterday, but rebooting the machine fixed it.
As for the KEEPENV, I was puzzled by that too but I didn't add
anything to env_whitelist and I left KEEPENV commented.  Everything
seems to be fine.

Today apache2 wants to upgrade to 2.2.4-r12.  I've got cold feet.
Anyone tried this yet?

- Grant
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Oddities in apache2 update, other init bizarrity.

[Dan Farrell]

On Wed, 5 Sep 2007 09:27:32 -0700
Grant <emailgrant@gmail.com> wrote:

> I had the same problem yesterday, but rebooting the machine fixed it.
> As for the KEEPENV, I was puzzled by that too but I didn't add
> anything to env_whitelist and I left KEEPENV commented.  Everything
> seems to be fine.

Possibly the commented out setting is meant to show the default, as is
common in config files.  The warning is to make sure that if you change
it you don't remove PATH.  
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Oddities in apache2 update, other init bizarrity.

[Dan Farrell]

On Wed, 5 Sep 2007 09:27:32 -0700
Grant <emailgrant@gmail.com> wrote:

> Today apache2 wants to upgrade to 2.2.4-r12.  I've got cold feet.
> Anyone tried this yet?

I just started it out, to see what happens.  

I turned off the AC today, my feet aren't very cold ; )
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Apache2 2.0 -> 2.2 upgrade

[Dan Farrell]

On Wed, 5 Sep 2007 13:02:16 -0500
"Marzan, Richard non Unisys" <Richard.Marzan@unisys.com> wrote:

> Goodluck friend
> 

Thanks,  I needed it.  I finally found a nice list of the information I
need here: 

http://httpd.apache.org/docs/2.2/upgrading.html

there's a message en route that covers all the majority of things, but
other stuff worth knowing that I haven't yet mentioned is :

The default setting of UseCanonicalName is now Off. If you did not have
this directive in your config file, you can add UseCanonicalName On to
retain the old behavior.

The directive AuthDigestFile  from mod_auth_digest has been
merged with AuthUserFile and is now part of mod_authn_file.

Many third-party modules designed for version 2.0 will work unchanged
with the the Apache HTTP Server version 2.2. But all modules must be
recompiled before being loaded.

The module mod_userdir will no longer act on requests unless a UserDir
directive specifying a directory name is present in the config file. To
restore the old default behavior, place the directive UserDir
public_html in your config file.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Apache2 2.0 -> 2.2 upgrade

[Dan Farrell]

I have discovered a really fun error message: 

>zeus dan # /etc/init.d/apache2 restart
> * Starting apache2 ...
>(98)Address already in use: make_sock: could not bind to address
>0.0.0.0:80 no listening sockets available, shutting down
>Unable to open
>logs                                                       [ !! ]

unless somebody has a good suggestion at this point (i've already
restarted), I guess I'll have to downgrade.  
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Apache2 2.0 -> 2.2 upgrade

[Christian Heim]

[-- Attachment #1: Type: text/plain, Size: 579 bytes --]

On Wednesday 05 September 2007 20:12:40 Dan Farrell wrote:
> On Wed, 5 Sep 2007 13:02:16 -0500

> The module mod_userdir will no longer act on requests unless a UserDir
> directive specifying a directory name is present in the config file. To
> restore the old default behavior, place the directive UserDir
> public_html in your config file.

Or just add -D PUBLIC_HTML to APACHE2_OPTS in /etc/conf.d/apache2.

Regards,

   Christian

-- 
Christian Heim <phreak at gentoo.org>
GPG key ID: 9A9F68E6
Fingerprint: AEC4 87B8 32B8 4922 B3A9 DF79 CAE3 556F 9A9F 68E6

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Apache2 2.0 -> 2.2 upgrade

[Christian Heim]

[-- Attachment #1: Type: text/plain, Size: 776 bytes --]

On Wednesday 05 September 2007 20:39:46 Dan Farrell wrote:
> I have discovered a really fun error message:
> >zeus dan # /etc/init.d/apache2 restart
> > * Starting apache2 ...
> >(98)Address already in use: make_sock: could not bind to address
> >0.0.0.0:80 no listening sockets available, shutting down
> >Unable to open
> >logs                                                       [ !! ]
>
> unless somebody has a good suggestion at this point (i've already
> restarted), I guess I'll have to downgrade.

You have another Listen somewhere it doesn't belong. Either remove that or -D 
DEFAULT_VHOST.

Regards,

   Christian

-- 
Christian Heim <phreak at gentoo.org>
GPG key ID: 9A9F68E6
Fingerprint: AEC4 87B8 32B8 4922 B3A9 DF79 CAE3 556F 9A9F 68E6

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Apache2 2.0 -> 2.2 upgrade

[Dan Farrell]

I have tracked down what appears to be the source of the difficulty
with restarting apache 2.2 after an upgrade.  

to recap, here's the error: 
>zeus ~ # /etc/init.d/apache2 restart
> * Starting apache2 ...
>(98)Address already in use: make_sock: could not bind to address
>0.0.0.0:80 no listening sockets available, shutting down
>Unable to open logs  

and the command 
>zeus apache2 # while /bin/true ; do ps -eaf | grep http; done /
>	|grep -v grep
shows that the threads are most likely causing the problem, somehow:
here is the output:
>  root      9695  9694  0 13:54 pts/3    00:00:00 /usr/sbin/apache2 -D
>  DEFAULT_VHOST -D PHP5 -D USERDIR -D SSL -D SSL_DEFAULT_HOST
>  -d /usr/lib/apache2 -f /etc/apache2/httpd.conf -t
( repeated many times) 


so if anyone has any idea how I might figure out how to properly
configure this part of apache2, i would certainly appreciate the
advice.  

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Apache2 2.0 -> 2.2 upgrade [solved]

[Dan Farrell]

well, if anyone has this problem, to fix it I commented out the 
Listen address in httpd.conf (defined for the default vhost anyway)

I also had to comment out this section here.  the comments said it was
the default only if compiled with USE="-threads" but nevertheless it
seemed to interfere.  

#<IfModule prefork.c>
#    StartServers         2 
#    MinSpareServers      2
#    MaxSpareServers      5
#    MaxClients         150
#    MaxRequestsPerChild  0
#</IfModule>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Apache2 2.0 -> 2.2 upgrade

[Dan Farrell]

On Wed, 5 Sep 2007 20:57:16 +0200
Christian Heim <phreak@gentoo.org> wrote:

> Regards,
> 
>    Christian
> 
> -- 

Thank you very much.  that was indeed a mistake I made.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Oddities in apache2 update, other init bizarrity.

[Grant]

> > Today apache2 wants to upgrade to 2.2.4-r12.  I've got cold feet.
> > Anyone tried this yet?
>
> a few minutes, 8 config file updates (i didn't let it
> update /etc/conf.d/apache2 or /etc/apache2/httpd.conf),
> and apache2 didn't restart.
>
> modules appear to have changed names.  Working on fixing now.  Kindly,
> apache2 didn't stop working before it checked config, so my site hasn't
> even gone down yet ; )
>
> However any advice would be appreciated as far as tracking down what I
> should have saved from the new httpd.conf

Any luck?  Can you just re-emerge the package and go through
etc-update properly?

- Grant
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Oddities in apache2 update, other init bizarrity.

[Dan Farrell]

On Wed, 5 Sep 2007 13:23:25 -0700
Grant <emailgrant@gmail.com> wrote:

> Any luck?  Can you just re-emerge the package and go through
> etc-update properly?
> 
> - Grant

You will have to accept some of the changes to /etc/apache2/httpd.conf.

some of the module names and files have changed; I also had to take out
part of my httpd.conf file to get it working properly.  

so the answer is yes, if you manually merge httpd.conf.  

You will also have to rebuild php module if you use it.  
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Oddities in apache2 update, other init bizarrity.

[kashani]

Dan Farrell wrote:
> 
> You will have to accept some of the changes to /etc/apache2/httpd.conf.
> 
> some of the module names and files have changed; I also had to take out
> part of my httpd.conf file to get it working properly.  
> 
> so the answer is yes, if you manually merge httpd.conf.  

It's always a good idea to make any custom changes in your own config 
files. I generally do not modify the Gentoo provided httpd.conf at all 
and then load in my own configs to make changes afterwards. Makes 
merging changes from Gentoo easier.

I usually put mine in /etc/apache2/vhosts.d/

000_httpd_tweaks.conf
00_default_vhost.conf
www.badapple.net.conf
and so on.

At first it seems like Gentoo is forcing you to jump through hoops and 
making your life complex. In some ways it is. However I've found that 
creating specific config files keeps you from losing settings when you 
migrate to new servers or update your server in just about any distro of 
Linux. It's a good habit to get into.

kashani
-- 
gentoo-user@gentoo.org mailing list