Subject: pkg/18854: apache server not starting properly after upgrade
To: None <>
From: Andrew Brown <>
List: netbsd-bugs
Date: 10/29/2002 14:30:34
>Number:         18854
>Category:       pkg
>Synopsis:       apache server not starting properly after upgrade
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Oct 29 11:31:00 PST 2002
>Originator:     TheMan
>Release:        1.6F (though that's not related)


the apache startup script says this:

# "${apache_start}" is the subcommand sent to apachectl to control how
# httpd is started.  It's value may be overridden in:
#       /usr/pkg/etc/httpd/apache_start.conf
#       /etc/rc.conf
#       /etc/rc.conf.d/apache,
# in order of increasing precedence.  Its possible values are "start"
# and "startssl", and defaults to "start" unless it's already set.

yet this is false on two levels.

(1) rc.conf is only read once at startup, so when the apache script
runs, it overrides the settings there with the contents of
apache_start.conf and rc.conf.d/apache.  setting "apache_start" to
"start" in /etc/rc.conf has no effect.  unless you rerun the apache
startup script by hand.

(2) if you install mod_ssl (which includes a nice sh script for
signing certificates, this value appears to "default" to "startssl"
even though you might not want that.

aside: it's also confusing that there are so many ways to "enable" ssl
support (this setting, using -DSSL, just loading the modules in the
httpd.conf, etc).


upgrade apache and mod_ssl.  copy the rc.d script into /etc/rc.d.
read it.  note that apache_start can be set in rc.conf.  set it.
reboot.  lose.


maybe change apache_start.conf from