Bug#223810:

[Fabio Massimo Di Nitto]

Sorry but i fail to see which is the problem here. /usr/local/bin is in
the path and it is a valid path as described in the FHS documentation. We
make no use of it since we do not store any data in it (debian Policy).

Thanks
Fabio

On Sat, 13 Dec 2003, Saku Ytti wrote:

> Uhh, even I don't understand what I'm trying to say in above line, probably
> s/ not//.
>
> Should be this:
> [EMAIL PROTECTED] /usr/lib/apache]# ./suexec.disabled -V
> -D DOC_ROOT="/var/www"
> -D GID_MIN=100
> -D HTTPD_USER="www-data"
> -D LOG_EXEC="/var/log/apache/suexec.log"
> -D SAFE_PATH="/usr/local/bin:/usr/bin:/bin"
> -D UID_MIN=100
> -D USERDIR_SUFFIX="public_html"
>
> But since yesterday it's not. HTTP_USER is 'www'. DOC_ROOT is
> '/usr/local...' etc.
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#223829: apache-perl: PerlRequire is reported as an Invalid command; due to modules.conf?

[Fabio Massimo Di Nitto]

Hi Adam,
thanks for reporting, I spotted the problem and I am working on a
proper fix. In the meanwhile it should be enough to run
modules-config apache-perl and re-enable mod_perl (that would make use of
the statically compiled in and not the dso).

Thanks
Fabio

On Sat, 13 Dec 2003, Adam Sjøgren wrote:

> Package: apache-perl
> Version: 1.3.29.0.1-1
> Severity: normal
> Tags: sid
>
> Upgrading apache-perl on my systems fails when Apache is to be
> restarted:
>
>  Syntax error on line 1006 of /etc/apache-perl/httpd.conf:
>  Invalid command 'PerlRequire', perhaps mis-spelled or defined by a module 
> not included in the server configuration
>
> This seems to be related to the three first lines of the generated
> /etc/apache-perl/modules.conf:
>
>  ClearModuleList
>  AddModule mod_so.c
>  AddModule mod_macro.c
>
> because if I comment them out, I can start Apache.
>
> (Until the next upgrade of an Apache-related package when modules.conf
> is overwritten with the lines again).
>
> Could it be thath ClearModuleList "clears" mod_perl, even when it's
> included in Apache? Just guessing, I'm just a user.
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux virgil 2.4.22-asjo-xfs-p4 #1 Thu Oct 23 21:28:18 CEST 2003 i686
> Locale: LANG=C, LC_CTYPE=da_DK
>
> Versions of packages apache-perl depends on:
> ii  apache-common   1.3.29.0.1-1 Support files for all Apache 
> webse
> ii  debconf 1.3.22   Debian configuration management 
> sy
> ii  dpkg1.10.18  Package maintenance system for 
> Deb
> ii  libapache-mod-perl  1.29.0.1-1   Integration of perl with the 
> Apach
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-10Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  libmagic1   4.06-1   File type determination library 
> us
> ii  libpam0g0.76-14  Pluggable Authentication Modules 
> l
> ii  libperl5.8  5.8.2-2  Shared Perl library.
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
>
> -- debconf information:
>   apache-perl/old-pidfile-set:
>   apache-perl/server-port: 80
>   apache-perl/init: true
> * apache-perl/enable-suexec: false
>   apache-perl/document-root: /var/www
> * apache-perl/upgrade-from-apache-conflict:
>   apache-perl/server-name: localhost
>   apache-perl/server-admin: [EMAIL PROTECTED]
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#224035: apache: suexec compiled with uid>=1000, breaks internal systems

[Fabio Massimo Di Nitto]

tags 224035 pending
merge 224035 223810 223902
stop
quit

Hi Joergen,
no it is a bug and it is already fixed in cvs. It will be ok in
the next upload.

Sorry for the mess but i simply messed up the CFLAGS for suexec in the
attempt to enable PAM limit supports and i didn't noticed.

Fabio

On Mon, 15 Dec 2003, Joergen Haegg wrote:

> Package: apache
> Version: 1.3.29.0.1-1
> Severity: normal
>
>
> Apache's suexec is compiled with min uid 1000 as of 1.3.27.0-2.
>
> This is of course as it should be, however, there are existing
> environments where it is difficult to change all user uids above 1000.
> (Most of these have been active for more than 10 years when
> system uids was below 100. :-)
> Also some of my internal packages (not in Debian) depends on being
> able to suexec and still have a system account.
>
> Because of this, would you consider adding an extra suexec, compiled
> with the old uidmin?
> The select mechanism is already in place, it's just an extra question
> that's needed.
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux zev 2.4.23-zev #1 Fri Dec 12 12:58:22 CET 2003 i686
> Locale: LANG=C, LC_CTYPE=en_US.ISO-8859-1
>
> Versions of packages apache depends on:
> ii  apache-common   1.3.29.0.1-1 Support files for all Apache 
> webse
> ii  debconf 1.3.22   Debian configuration management 
> sy
> ii  dpkg1.10.18  Package maintenance system for 
> Deb
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-10Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  libmagic1   4.06-1   File type determination library 
> us
> ii  libpam0g0.76-14  Pluggable Authentication Modules 
> l
> ii  logrotate   3.6.5-2  Log rotation utility
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
> ii  perl [perl5]5.8.2-2  Larry Wall's Practical Extraction
>
> -- debconf information:
> * apache/enable-suexec: true
> * apache/server-name: zev.se.axis.com
> * apache/document-root: /var/www
> * apache/server-port: 80
> * apache/init: true
> * apache/server-admin: [EMAIL PROTECTED]
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#223902: apache: suexec is built with www instead of www-data as user

[Fabio Massimo Di Nitto]

Hi Brian,
thanks for reporting. I have the fix ready in CVS. I expect to
upload a new version within today or tomorrow.

Fabio

On Sat, 13 Dec 2003, Brian McGroarty wrote:

> Package: apache
> Version: 1.3.29.0.1-1
> Severity: normal
> Tags: sid
>
> suexec is broken.
>
> /usr/lib/apache/suexec -V reports:
>  -D DOC_ROOT="/usr/local/apache/htdocs"
>  -D GID_MIN=100
>  -D HTTPD_USER="www"
>  -D LOG_EXEC="/var/log/apache/cgi.log"
>  -D SAFE_PATH="/usr/local/bin:/usr/bin:/bin"
>  -D UID_MIN=1000
>  -D USERDIR_SUFFIX="public_html"
>
> The HTTPD_USER option should be www-data.
>
> This prevents the su mechanism from properly working, making all
> relevant cgi scripts fail with an internal server error.
>
> /var/log/apache/cgi.log shows for each:
> crit: calling user mismatch (www-data instead of www)
>
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux eastbits 2.4.23-rc3-djc3-6um #2 Fri Nov 21 22:48:44 EST 2003 
> i686
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages apache depends on:
> ii  apache-common   1.3.29.0.1-1 Support files for all Apache 
> webse
> ii  debconf 1.3.22   Debian configuration management 
> sy
> ii  dpkg1.10.18  Package maintenance system for 
> Deb
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-10Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  libmagic1   4.06-1   File type determination library 
> us
> ii  libpam0g0.76-14  Pluggable Authentication Modules 
> l
> ii  logrotate   3.6.5-2  Log rotation utility
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
> ii  perl [perl5]5.8.2-2  Larry Wall's Practical Extraction
>
> -- debconf information:
> * apache/server-name: www.skittlebrau.org
> * apache/document-root: /var/www
> * apache/server-port: 80
> * apache/enable-suexec: true
> * apache/init: true
> * apache/server-admin: [EMAIL PROTECTED]
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#223780: apache-common: 'modules.conf' included twice

[Fabio Massimo Di Nitto]

Hi Marc,
can you send me your config files please?? I have been trying to
reproduce this problem with no success.

Thanks
Fabio

On Fri, 12 Dec 2003, [utf-8] Marc Dequènes wrote:

> Package: apache-common
> Version: 1.3.29.0.1-1
> Severity: normal
>
> After upgrade the following line is included even if already present,
> just above the other, thus breaking apache start.
> 
> Include /etc/apache/modules.conf
> 
>
> Duck
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#224128: Apache1.3.29+PHP+mod_includes BUG

[Fabio Massimo Di Nitto]

Hi Jordan,
sorry but i cannot reproduce this problem. Which debian version of
apache and php are you running??

On Mon, 15 Dec 2003, Jordan Trask wrote:

> When I add ?LoadModule includes_module /usr/lib/apache/1.3/mod_include.so?
> manually, to modules.conf. and do

why manually?? please use modules-config

> %apachectl restart
>
> The script will say it restarted, but it hasn?t and just quits.

it restarts fine here.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Re: Bug#224049: libapache-mod-perl: Segmentaion fault when starting apache

[Fabio Massimo Di Nitto]

On Wed, 17 Dec 2003, Michael D Schleif wrote:

> Fabio Massimo Di Nitto <[EMAIL PROTECTED]> [2003:12:17:06:29:51+0100] scribed:
> >
> > This problem has been already fixed in more recent versions of apache.
> >
> > Fabio
>
> What does this mean?  Is this only an issue of apache DEB version?

no the problem is in perl that broke the ABI. apache is not guilty in this
case. The problem has been fixed recompiling apache in version 1.3.28-1 so
any version from that one to 1.3.29.0.1-2 are working.

>
> By using the plural word, versions, do you mean that I have some other
> choice than 1.3.29.0.1-1?

yes since you can grab packages from snapshot.debian.net or something
similar but i highly unsuggest to get older versions than the latest one.

> I have searched bugs for mod_perl, libapache-mod-perl and apache itself,
> and I find no reference to this problem.

The bugs have been archived.

> Please, clarify.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=213974&archive=yes

is one of them (as reference)

Fabio

As workaround you can recompile apache locally on your machine from the
debian sources and it will work.

Bug#224233: apache: upgrade bombs with sed errors

[Fabio Massimo Di Nitto]

Hi Paul,
which version of sed are you using? For what i can see here you
have a mixed environment with woody/sid packages. When i test apache i
almost always test a full upgrade from woody to sid and i have never seen
this problem. If you can track the problem down to a specific version of
sed than we can simply add it as a versioned dependency.

Thanks
Fabio

On Tue, 16 Dec 2003, Paul Telford wrote:

> Package: apache
> Version: 1.3.29.0.1-2
> Severity: normal
>
>
> Apache gave me a "sed" error during upgrade.  Log pasted in below.
>
>
> [EMAIL PROTECTED]:/etc/apache$ dpkg -l apache
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
> uppercase=bad)
> ||/ Name Version  Description
> +++---
> 
> ii  apache   1.3.26-1 Versatile,
> high-performance HTTP server
> [EMAIL PROTECTED]:/etc/apache$ sudo apt-get install php4
> Reading Package Lists... Done
> Building Dependency Tree... Done
> The following extra packages will be installed:
>apache apache-common apache-utils file libkeynote0 libmagic1 libmm13
> zlib1g zlib1g-dev
> Suggested packages:
>apache-perl libapache-mod-auth-mysql php4-pear
> The following NEW packages will be installed:
>apache-utils libkeynote0 libmagic1 libmm13 php4
> The following packages will be upgraded
>apache apache-common file zlib1g zlib1g-dev
> 5 upgraded, 5 newly installed, 0 to remove and 668 not upgraded.
> 1 not fully installed or removed.
> Need to get 2954kB of archives.
> After unpacking 3025kB of additional disk space will be used.
> Do you want to continue? [Y/n]
> Get:1 http://http.us.debian.org unstable/main zlib1g-dev 1:1.2.1-2
> [405kB]
> Get:2 http://http.us.debian.org unstable/main zlib1g 1:1.2.1-2 [61.1kB]
> Get:3 http://http.us.debian.org unstable/main file 4.06-2 [25.5kB]
> Get:4 http://http.us.debian.org unstable/main libmagic1 4.06-2 [212kB]
> Get:5 http://http.us.debian.org unstable/main libkeynote0 2.3-10
> [28.2kB]
> Get:6 http://http.us.debian.org unstable/main apache 1.3.29.0.1-2
> [365kB]
> Get:7 http://http.us.debian.org unstable/main apache-common
> 1.3.29.0.1-2 [811kB]
> Get:8 http://http.us.debian.org unstable/main apache-utils 1.3.29.0.1-2
> [252kB]
> Get:9 http://http.us.debian.org unstable/main libmm13 1.3.0-1 [15.4kB]
> Get:10 http://http.us.debian.org unstable/main php4 4:4.3.3-4 [778kB]
> Fetched 2954kB in 23s (127kB/s)
> Reading changelogs... Done
> apt-listchanges: Do you want to continue? [Y/n]?
> Preconfiguring packages ...
> (Reading database ... 103786 files and directories currently installed.)
> Preparing to replace zlib1g-dev 1:1.1.4-3 (using
> .../zlib1g-dev_1%3a1.2.1-2_i386.deb) ...
> Unpacking replacement zlib1g-dev ...
> Preparing to replace zlib1g 1:1.1.4-3 (using
> .../zlib1g_1%3a1.2.1-2_i386.deb) ...
> Unpacking replacement zlib1g ...
> Preparing to replace file 3.37-3.1.woody.1 (using
> .../archives/file_4.06-2_i386.deb) ...
> Unpacking replacement file ...
> Selecting previously deselected package libmagic1.
> Unpacking libmagic1 (from .../libmagic1_4.06-2_i386.deb) ...
> Selecting previously deselected package libkeynote0.
> Unpacking libkeynote0 (from .../libkeynote0_2.3-10_i386.deb) ...
> Preparing to replace apache 1.3.26-1 (using
> .../apache_1.3.29.0.1-2_i386.deb) ...
> Unpacking replacement apache ...
> Preparing to replace apache-common 1.3.26-1 (using
> .../apache-common_1.3.29.0.1-2_i386.deb) ...
> Unpacking replacement apache-common ...
> Selecting previously deselected package apache-utils.
> Unpacking apache-utils (from .../apache-utils_1.3.29.0.1-2_i386.deb) ...
> Selecting previously deselected package libmm13.
> Unpacking libmm13 (from .../libmm13_1.3.0-1_i386.deb) ...
> Selecting previously deselected package php4.
> Unpacking php4 (from .../php4_4%3a4.3.3-4_i386.deb) ...
> Setting up netenv (0.94.3-1) ...
>
> Setting up zlib1g (1.2.1-2) ...
>
> Setting up zlib1g-dev (1.2.1-2) ...
> Setting up libmagic1 (4.06-2) ...
>
> Setting up file (4.06-2) ...
> Setting up libkeynote0 (2.3-10) ...
>
> Setting up apache-utils (1.3.29.0.1-2) ...
> Setting up apache-common (1.3.29.0.1-2) ...
>
> Setting up apache (1.3.29.0.1-2) ...
> Installing new version of config file /etc/init.d/apache ...
> Installing new version of config file /etc/logrotate.d/apache ...
> sed: invalid option -- s
> Usage: sed [OPTION]... {script-only-if-no-other-script} [input-file]...
>
>-n, --quiet, --silent
>   suppress automatic printing of pattern space
>-e script, --expression=script
>   add the script to the commands to be executed
>-f script-file, --file=script-file
>   add the contents of script-file to the commands to be
> executed
>--help

Bug#224233: apache: upgrade bombs with sed errors

[Fabio Massimo Di Nitto]

tags 224233 + pending
stop
quit


Ok it is a sed problem.. i could reproduce the bug easily. When i answered
back before i totally forgot i had a chroot handy ;)

Thanks
Fabio

On Tue, 16 Dec 2003, Paul Telford wrote:

> Package: apache
> Version: 1.3.29.0.1-2
> Severity: normal
>
>
> Apache gave me a "sed" error during upgrade.  Log pasted in below.
>
>
> [EMAIL PROTECTED]:/etc/apache$ dpkg -l apache
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
> uppercase=bad)
> ||/ Name Version  Description
> +++---
> 
> ii  apache   1.3.26-1 Versatile,
> high-performance HTTP server
> [EMAIL PROTECTED]:/etc/apache$ sudo apt-get install php4
> Reading Package Lists... Done
> Building Dependency Tree... Done
> The following extra packages will be installed:
>apache apache-common apache-utils file libkeynote0 libmagic1 libmm13
> zlib1g zlib1g-dev
> Suggested packages:
>apache-perl libapache-mod-auth-mysql php4-pear
> The following NEW packages will be installed:
>apache-utils libkeynote0 libmagic1 libmm13 php4
> The following packages will be upgraded
>apache apache-common file zlib1g zlib1g-dev
> 5 upgraded, 5 newly installed, 0 to remove and 668 not upgraded.
> 1 not fully installed or removed.
> Need to get 2954kB of archives.
> After unpacking 3025kB of additional disk space will be used.
> Do you want to continue? [Y/n]
> Get:1 http://http.us.debian.org unstable/main zlib1g-dev 1:1.2.1-2
> [405kB]
> Get:2 http://http.us.debian.org unstable/main zlib1g 1:1.2.1-2 [61.1kB]
> Get:3 http://http.us.debian.org unstable/main file 4.06-2 [25.5kB]
> Get:4 http://http.us.debian.org unstable/main libmagic1 4.06-2 [212kB]
> Get:5 http://http.us.debian.org unstable/main libkeynote0 2.3-10
> [28.2kB]
> Get:6 http://http.us.debian.org unstable/main apache 1.3.29.0.1-2
> [365kB]
> Get:7 http://http.us.debian.org unstable/main apache-common
> 1.3.29.0.1-2 [811kB]
> Get:8 http://http.us.debian.org unstable/main apache-utils 1.3.29.0.1-2
> [252kB]
> Get:9 http://http.us.debian.org unstable/main libmm13 1.3.0-1 [15.4kB]
> Get:10 http://http.us.debian.org unstable/main php4 4:4.3.3-4 [778kB]
> Fetched 2954kB in 23s (127kB/s)
> Reading changelogs... Done
> apt-listchanges: Do you want to continue? [Y/n]?
> Preconfiguring packages ...
> (Reading database ... 103786 files and directories currently installed.)
> Preparing to replace zlib1g-dev 1:1.1.4-3 (using
> .../zlib1g-dev_1%3a1.2.1-2_i386.deb) ...
> Unpacking replacement zlib1g-dev ...
> Preparing to replace zlib1g 1:1.1.4-3 (using
> .../zlib1g_1%3a1.2.1-2_i386.deb) ...
> Unpacking replacement zlib1g ...
> Preparing to replace file 3.37-3.1.woody.1 (using
> .../archives/file_4.06-2_i386.deb) ...
> Unpacking replacement file ...
> Selecting previously deselected package libmagic1.
> Unpacking libmagic1 (from .../libmagic1_4.06-2_i386.deb) ...
> Selecting previously deselected package libkeynote0.
> Unpacking libkeynote0 (from .../libkeynote0_2.3-10_i386.deb) ...
> Preparing to replace apache 1.3.26-1 (using
> .../apache_1.3.29.0.1-2_i386.deb) ...
> Unpacking replacement apache ...
> Preparing to replace apache-common 1.3.26-1 (using
> .../apache-common_1.3.29.0.1-2_i386.deb) ...
> Unpacking replacement apache-common ...
> Selecting previously deselected package apache-utils.
> Unpacking apache-utils (from .../apache-utils_1.3.29.0.1-2_i386.deb) ...
> Selecting previously deselected package libmm13.
> Unpacking libmm13 (from .../libmm13_1.3.0-1_i386.deb) ...
> Selecting previously deselected package php4.
> Unpacking php4 (from .../php4_4%3a4.3.3-4_i386.deb) ...
> Setting up netenv (0.94.3-1) ...
>
> Setting up zlib1g (1.2.1-2) ...
>
> Setting up zlib1g-dev (1.2.1-2) ...
> Setting up libmagic1 (4.06-2) ...
>
> Setting up file (4.06-2) ...
> Setting up libkeynote0 (2.3-10) ...
>
> Setting up apache-utils (1.3.29.0.1-2) ...
> Setting up apache-common (1.3.29.0.1-2) ...
>
> Setting up apache (1.3.29.0.1-2) ...
> Installing new version of config file /etc/init.d/apache ...
> Installing new version of config file /etc/logrotate.d/apache ...
> sed: invalid option -- s
> Usage: sed [OPTION]... {script-only-if-no-other-script} [input-file]...
>
>-n, --quiet, --silent
>   suppress automatic printing of pattern space
>-e script, --expression=script
>   add the script to the commands to be executed
>-f script-file, --file=script-file
>   add the contents of script-file to the commands to be
> executed
>--help display this help and exit
>-V, --version  output version information and exit
>
> If no -e, --expression, -f, or --file option is given, then the first
> non-option argument is taken as

Bug#223902: Bug#223810: Info received (was Bug#223810)

[Fabio Massimo Di Nitto]

Hi Saku,
thanks for tracking down the problem. I will upload a new version
today without the pam_limits support.

If you can be so kind to leave the bug closed we will avoid the usual
couple of tons of mails going around.

Fabio

On Wed, 17 Dec 2003, Saku Ytti wrote:

> The bug still persists, now the paths are correct but cgi's are still broken.
>
> [2003-12-17 08:37:07]: info: (target/actual) uid: (ytti/ytti) gid:
> (guru/guru) cmd: fortune.cgi
> [2003-12-17 08:37:07]: error: pam_open_session(): [6] Permission denied
>
> Changing to old suexec.disabled and it works a-ok.
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#224260: apache-common: error converting module information

[Fabio Massimo Di Nitto]

tags 224260 + pending
stop
quit

OK fixed in CVS. thanks for spotting it. In my tests i never got an error
message and it was working. Which version of sed are you using?

Thanks
Fabio

On Wed, 17 Dec 2003, Matt Jackson wrote:

> Package: apache-common
> Version: 1.3.29.0.1-2
> Severity: important
> Tags: sid
>
> When running /usr/sbin/modules-config to create the modules.conf it
> fails with a sed error. Line 138 of modules-config has a sed -s command.
> It appears that this should be sed -e. Changing it as suggested works
> for me.
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux clotho 2.4.21 #2 Mon Jun 16 22:12:52 EST 2003 i586
> Locale: LANG=en_AU, LC_CTYPE=en_AU
>
> Versions of packages apache-common depends on:
> ii  apache-utils1.3.29.0.1-2 Utility programs for webservers
> ii  debconf 1.3.22   Debian configuration management 
> sy
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-10Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
> ii  perl [perl5]5.8.2-2  Larry Wall's Practical Extraction
>
> -- debconf information:
> * apache-common/confignotes:
>   apache-common/old-logrotate-exists:
>   apache-common/logs:
>   apache-shared/debconf-modules: mod_userdir, mod_status, mod_setenvif, 
> mod_rewrite, mod_negotiation, mod_mime, mod_log_config, mod_expires, mod_dir, 
> mod_cgi, mod_autoindex, mod_auth, mod_alias, mod_access
>   apache-shared/restart: false
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#224259: apache: user not found in Basic authentication

[Fabio Massimo Di Nitto]

Hi Garamszegi,
this is mostlikely an error in your configuration. Please
use modules-config and remove all the auth modules that you do not need
and leave only mod_auth. This should make it working. Let me know asap if
it does or not.

Thanks
Fabio


On Wed, 17 Dec 2003, Garamszegi Karoly wrote:

> Package: apache
> Version: 1.3.29.0.1-1
> Severity: important
>
>
> Hello,
>
>  I have encountered the following problem: I set up Basic authentication
>  in access.conf:
>
>  
>  AuthType Basic
>  AuthName "Passwor Required"
>  AuthUserFile /etc/apache/pwd
>  Require valid-user
>
>  
>
> /etc/apache/pwd contains:
>
> addmin:J/HrQ7c/b6bNQ
> jerry:jerry
>
> Symptom: the browser pops up the authentication window, I enter the
> details, but after a few tries I got an Authorization required.
>
> In the logs:
>
> [Wed Dec 17 13:43:26 2003] [error] user jerry not found: /dev/admin
> [Wed Dec 17 13:43:27 2003] [error] user jerry not found: /dev/admin
> [Wed Dec 17 13:43:27 2003] [error] user jerry not found: /dev/admin
>
>
> Apache does not complain, if the /etc/apache/pwd file is missing, and
> according to strace, it does not even touch it.
>
>
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux glas 2.4.23 #1 Tue Dec 2 08:46:20 CET 2003 i686
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages apache depends on:
> ii  apache-common   1.3.29.0.1-1 Support files for all Apache 
> webse
> ii  debconf 1.3.22   Debian configuration management 
> sy
> ii  dpkg1.10.18  Package maintenance system for 
> Deb
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-10Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  libmagic1   4.06-2   File type determination library 
> us
> ii  libpam0g0.76-14  Pluggable Authentication Modules 
> l
> ii  logrotate   3.6.5-2  Log rotation utility
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
> ii  perl [perl5]5.8.2-2  Larry Wall's Practical Extraction
>
> -- debconf information excluded
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Re: Bug#224049: libapache-mod-perl: Segmentaion fault when starting apache

[Fabio Massimo Di Nitto]

On Wed, 17 Dec 2003, Michael D Schleif wrote:

> However, the problem persists!
>
> # COLUMNS=110 dpkg -l '*apache*' | grep ^i
> ii  apache1.3.29.0.1-2  Versatile, high-performance 
> HTTP server
> ii  apache-common 1.3.29.0.1-2  Support files for all Apache 
> webservers
> ii  apache-utils  1.3.29.0.1-2  Utility programs for 
> webservers
> ii  libapache-mod-jk  3.3a-4woody1  Apache connector for Tomcat 
> servlet engine
> ii  libapache-mod-perl1.27-4Integration of perl with the 
> Apache web server
^^^ upgrade libapache-mod-perl

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#224259: apache: user not found in Basic authentication

[Fabio Massimo Di Nitto]

Hi Garamszegi,

On Wed, 17 Dec 2003 [EMAIL PROTECTED] wrote:

>
> Hi Fabio,
>
>  my current modules.conf:
>
>

[SNIP]

>
> Shall be any of these modules removed? Is there other places to
> allow/disallow modules?

No this looks fine but i just noticed:

> >> addmin:J/HrQ7c/b6bNQ
> >> jerry:jerry

   ^

can you login as addmin?? in order to add a username/password to pwd you
should use htpasswd.

> >> [Wed Dec 17 13:43:26 2003] [error] user jerry not found: /dev/admin

this happen to me as well if i use a wrong password but otherwise
everything work just fine.

> >>
> >> Apache does not complain, if the /etc/apache/pwd file is missing, and
> >> according to strace, it does not even touch it.

the passwd files are read on the flies by detached processes so perhaps
you might have missed it.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

libapache-mod-perl dependencies

[Fabio Massimo Di Nitto]

I removed the bug from the CC since it is closed and we are going a bit
off topic.

On Wed, 17 Dec 2003, Michael D Schleif wrote:

> OK, now apache starts while mod_perl is enabled.  Thank you.

no problem.

>
> Is it a _bug_ that apt did *not* warn me about a dependency issue for
> libapache-mod-perl v1.27-4?

no, it's not a bug because apache does not depends on libapache-mod-perl
or "knows" about it.

>
> When I did this:
>
>apt-get install apache=1.3.29.0.1-2
>
> then, apt warned me about also upgrading apache-common.

that's correct.

>
> What do you think?

this is the normal behaviour. you asked apt-get to update only apache.
libapache-mod-perl is a package on "its own".

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#224233: apache-common: sed error

[Fabio Massimo Di Nitto]

Hi Paul,
-s was a typo, reported in another bug and fixed. I already
uploaded -3 with both the -s to -e correction and the version dependency.

Fabio

On Wed, 17 Dec 2003, Paul Telford wrote:

> I know you already marked this pending, but here's some more
> information just in case it helps you.
>
>
> After some more digging I found that this is caused by modules-config
> which is not compatible with older versions of sed.
>
>
> [EMAIL PROTECTED]:/usr/share/apache$ dpkg -l apache-common
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
> uppercase=bad)
> ||/ Name Version  Description
> +++---
> 
> ii  apache-common1.3.29.0.1-2 Support files for
> all Apache webservers
> [EMAIL PROTECTED]:/usr/share/apache$ grep "sed -s"
> /usr/sbin/modules-config
>  sed -s 's/AddModule mod_perl.c/LoadModule perl_module
> \/usr\/lib\/apache\/1.3\/mod_perl.so/g' | \
> [EMAIL PROTECTED]:/usr/share/apache$ dpkg -l sed
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
> uppercase=bad)
> ||/ Name Version  Description
> +++---
> 
> ii  sed  3.02-8   The GNU sed
> stream editor.
>
>
> After upgrading sed this particular error goes away.
>
> [EMAIL PROTECTED]:/usr/share/apache$ dpkg -l sed
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
> uppercase=bad)
> ||/ Name Version  Description
> +++---
> 
> ii  sed  4.0.7-3  The GNU sed
> stream editor
>
>
> Looks like a versioned depends is needed.  Older versions of sed can't
> use the "-s" option.
>
> Thanks,
>
> --
> Paul Telford | 1024D/431B38BA | [EMAIL PROTECTED] | [EMAIL PROTECTED]
> C903 0E85 9AF5 1B80 6A5F  F169 D7E9 4363 431B 38BA
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#224128: (no subject)

[Fabio Massimo Di Nitto]

Hi Jordan,
here you have a bit of a messed up system but i think the problem
you have is due to:

> ii  php4-imap  4.3.3-3IMAP module for php4
> ii  php4-pgsql 4.3.2+rc3-3PostgreSQL module for php4

php4 is broken and crashes apache when these 2 extensions are used
togehter. Please remove one of them and try again.

Thanks
Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Re: libapache-mod-perl install stuck in dpkg

[Fabio Massimo Di Nitto]

Hi Nori,
please upgrade apache and libapache-mod-perl to the latest
versions. the one you are using has an error (if not more.. i can't
remember on the fly) in the postinst script that depends from another
bunch of bug fixes in apache-common.

Fabio

On Wed, 17 Dec 2003, Nori Heikkinen wrote:

> for some time now, whenever i apt-get install anything, dpkg has been
> trying to configure libapache-mod-perl, and failing.  it'll present me
> with the config screen:
>
> Setting up libapache-mod-perl (1.28-1) ...
> Configuring
> 
>
>   1. mod_vhost_alias  22. mod_access43. mod_auth_digest
>   2. mod_env  23. mod_auth  44. mod_auth_external
>   3. mod_log_config   24. mod_auth_anon 45. mod_auth_inst
>   4. mod_log_agent25. mod_auth_dbm  46. mod_auth_system
>   5. mod_log_referer  26. mod_auth_db   47. mod_bandwidth
>   6. mod_mime_magic   27. libproxy  48. mod_cgisock
>   7. mod_mime 28. mod_digest49. mod_disallow_id
>   8. mod_negotiation  29. mod_cern_meta 50. mod_eaccess
>   9. mod_status   30. mod_expires   51. mod_ip_forwarding
>   10. mod_info31. mod_headers   52. mod_lock
>   11. mod_include 32. mod_usertrack 53. mod_macro
>   12. mod_autoindex   33. mod_unique_id 54. mod_peephole
>   13. mod_dir 34. mod_setenvif  55. mod_php4
>   14. mod_cgi 35. mod_auth_sys  56. mod_qs2ssi
>   15. mod_asis36. mod_perl  57. mod_roaming
>   16. mod_imap37. mod_put   58. mod_session
>   17. mod_actions 38. libcache  59. mod_ticket
>   18. mod_speling 39. mod_allowdev  60. mod_urlcount
>   19. mod_userdir 40. mod_auth_cache61. mod_mp3
>   20. mod_alias   41. mod_auth_cookie_file
>   21. mod_rewrite 42. mod_auth_cookie
>
> (Enter the items you want to select, separated by spaces.)
>
> :-) Please select the modules that apache will load
>
>
> and then, no matter which modules i enter, i get the following error:
>
> expr: syntax error
> dpkg: error processing libapache-mod-perl (--configure):
>  subprocess post-installation script returned error exit status 2
>  Errors were encountered while processing:
>   libapache-mod-perl
>
> i've tried apt-get removing this package, i've tried dpkg
> --configuring it ... nothing works.
>
> now i actually want libapache-mod-mp3, and its concomitant packages.
> i need libapache-mod-perl for this, if i read everything correctly ...
> and anyhow, i'd like to make it stop giving me this obnoxious error
> message every time i use apt.
>
> a friend suggested that this was a problem intergrating with my
> version of perl (i was running 5.8.1-2), and that i try installing the
> libapache-mod-perl in unstable instead.  having done so, i'm now
> running perl 5.8.2-2, but libapache is still stuck in the confuigure
> queue somehow.
>
> any hints?
>
> thanks,
>
> 
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#224390: apache-ssl: SSLCacheServerPort: httpd.conf not updated

[Fabio Massimo Di Nitto]

tags 224390 - patch
tags 224390 + wontfix
severity 224390 wishlist
stop
quit
thanks

Hi Thomas,
this is simply not possible. neither now or in the future so it is
wontfix. There is no patch in the message.. did you forget to attach one?

It is simply impossible to change a set back since there might be users
that are using that setup. The previous bug has been fixed meaning that
upgrading from woody to the actual release creates no breackage.

If you can provide a safe patch and way to determine which setup is there
for a mistake and which one for a user choise i will be happy to add it to
the postinst.

Thanks
Fabio


On Thu, 18 Dec 2003, Thomas R. Shemanske wrote:

> Package: apache-ssl
> Version: 1.3.29.0.1-3
> Severity: important
> Tags: patch sid
>
> In some sense this could be a reopening of bug 215011.
>
> I have been running apache-ssl for some time.  At some point I started
> getting the errors (as reported in 215011) in my error log:
>
> SSL23_GET_CLIENT_HELLO:unknown protocol
> gcachecommon.c:108: ReadThing: Assertion `nRead == sizeof usLength' failed.
>
> The fix, for apache-ssl version 1.3.28-2 (which was supposedly
> implemented in a later version) was to change the following entry in
> httpd.conf:
>
> SSLCacheServerPort 443 to
> SSLCacheServerPort /var/run/gcache_port
>
> This fix *does* work, but it never gets written to the httpd.conf file
> even if you dpkg-reconfigure apache-ssl
>
> I purged apache-ssl and reinstalled and the httpd.conf file is now
> correct, but of course one then has to remerge old modifications and
> users have to handle the new certificate.
>
> This really needs to be done in postinstall.
>
> Cheers!
>
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux hecke 2.4.23 #1 Tue Dec 2 11:41:35 EST 2003 i686
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages apache-ssl depends on:
> ii  apache-common   1.3.29.0.1-3 Support files for all Apache 
> webse
> ii  debconf 1.3.22   Debian configuration management 
> sy
> ii  dpkg1.10.18  Package maintenance system for 
> Deb
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-10Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  libkeynote0 2.3-10   Decentralized Trust-Management 
> sys
> ii  libmagic1   4.06-2   File type determination library 
> us
> ii  libpam0g0.76-14  Pluggable Authentication Modules 
> l
> ii  libssl0.9.7 0.9.7c-5 SSL shared libraries
> ii  logrotate   3.6.5-2  Log rotation utility
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
> ii  openssl 0.9.7c-5 Secure Socket Layer (SSL) binary 
> a
> ii  perl [perl5]5.8.2-2  Larry Wall's Practical Extraction
> ii  ssl-cert1.0-6Simple debconf wrapper for 
> openssl
>
> -- debconf information:
> * apache-ssl/server-name: hecke.dartmouth.edu
> * apache-ssl/server-admin: [EMAIL PROTECTED]
> * apache-ssl/enable-suexec: false
> * apache-ssl/init: true
> * apache-ssl/document-root: /var/www
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#224454: apache: upgrade fails because /var/www already exists

[Fabio Massimo Di Nitto]

Hi Sean,
this is really strange. From the postinst:

if [ ! -d /var/www ]; then
mkdir -p /var/www
chown root:root /var/www
chmod 755 /var/www
cp -f /usr/share/doc/$pkg/intro.html /var/www/index.html
chown www-data:www-data /var/www/index.html
chmod 644 /var/www/index.html
fi

we are already doing it. But hold on...

On Thu, 18 Dec 2003, Sean Finney wrote:

> Setting up apache (1.3.29.0.1-3) ...
> mkdir: cannot create directory `/var/www': File exists

 file???

I think you had something wrong in your system here..

Please let me know asap what was your /var/www.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#224390: apache-ssl: SSLCacheServerPort: httpd.conf not updated

[Fabio Massimo Di Nitto]

On Thu, 18 Dec 2003, Thomas R. Shemanske wrote:

> Fabio Massimo Di Nitto wrote:
> |
> |
> | Hi Thomas,
> | this is simply not possible. neither now or in the future so it is
> | wontfix. There is no patch in the message.. did you forget to attach one?
> |
> | It is simply impossible to change a set back since there might be users
> | that are using that setup. The previous bug has been fixed meaning that
> | upgrading from woody to the actual release creates no breackage.
> |
> | If you can provide a safe patch and way to determine which setup is there
> | for a mistake and which one for a user choise i will be happy to add it to
> | the postinst.
> |
> | Thanks
> | Fabio
>
>
> Well I admit I am a bit confused.  The machine on which this happened
> was setup about 6 months ago, and has been sid from day 1.  The
> httpd.conf file I had listed SSLCacheServerPort 443
>

Well if you want to stay with sid you have to expect that sometimes things
goes wrong. It was a bug and it has been fixed.

> So at first glance it seems that
> SSLCacheServerPort /var/run/gcache_port
>
> is correct for all versions of apache-ssl

Yes that's correct.

> How I got the other httpd.conf entry is a bit of a mystery, but I surely
> can't be alone in this.

It was a bug in the postinst script for 1.3.28

>
> The "patch" was just to make sure the config file listed the correct
> option, but as you suggest this may present a problem.

It does now. "patch" means that you are including a real patch to solve
the bug.

> Perhaps you could pop up a debconf dialog box at least alerting people
> to a potential problem in configuration?

debconf is not meant to popup for every single bit of configuration. I
might add a note in suggested_correction.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#224454: possibly more info

[Fabio Massimo Di Nitto]

On Fri, 19 Dec 2003, Sean Finney wrote:

> having another problem too, think it's related:
>
> mini-me[/var]18:01:24# /etc/init.d/apache start
> Configuration syntax error detected. Not reloading.
>
> Syntax error on line 281 of /etc/apache/httpd.conf:
> DocumentRoot must be a directory
>
>
> mini-me[/var]18:04:02# ls -ld /var/www
> lrwxrwxrwx1 root root   13 2003-08-05 08:49 www -> somewhere
>
>
> maybe this is all because my /var/www is a symlink elsewhere?

That would explain the error you get from the postinst.. but is somewhere
a directory??

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#224553: apache segfaults on startup

[Fabio Massimo Di Nitto]

reassign 224553 php4
stop
quit

Hi Birzan,
this is a php4 problem and i am reassigning it. From one of the
file included i can see you are loading php4-imap extension that is
broken. It is enough to disable that extension to make apache starting,
but it is not an apache fault.

Thanks
Fabio

On Sat, 20 Dec 2003, Birzan George Cristian wrote:

> Package: apache
> Version: 1.3.29.0.1-3
> Severity: grave
> Tags: sid
> Justification: renders package unusable
>
> Apache segfaults when starting, started happening after the latest
> apt-get dist-upgrade. I've attached both the output from
> catchsegv apache -X and gbd's backtrace, on my non-stripped build of
> apache.
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux heimdall 2.6.0-test11 #1 Thu Nov 27 03:17:51 EET 2003 i686
> Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15
>
> Versions of packages apache depends on:
> ii  apache-common   1.3.29.0.1-3 Support files for all Apache 
> webse
> ii  debconf 1.3.22   Debian configuration management 
> sy
> ii  dpkg1.10.18  Package maintenance system for 
> Deb
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-10Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  libmagic1   4.06-2   File type determination library 
> us
> ii  libpam0g0.76-14  Pluggable Authentication Modules 
> l
> ii  logrotate   3.6.5-2  Log rotation utility
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
> ii  perl [perl5]5.8.2-2  Larry Wall's Practical Extraction
>
> -- debconf information:
> * apache/enable-suexec: false
>   apache/server-name: localhost
>   apache/document-root: /var/www
>   apache/server-port: 80
>   apache/init: true
>   apache/server-admin: [EMAIL PROTECTED]
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#219378: still having this problem

[Fabio Massimo Di Nitto]

Hi Dave,
thanks for the information but I still cannot reproduce this
problem and it makes debug quite difficult. I will see if i can dedicate a
machine to reproduce your setup sometimes when i will be back from
holidays.

Fabio

On Thu, 25 Dec 2003, Dave O wrote:

>
> I again tried to upgrade to 1.3.29 and this is still happening.
>
> I tried setting MaxClients down to 50 so as not to use a ridiculous number
> of resources, and found that after all 50 children had been spawned and
> used, no pages could be served.  Browsers could connect, but just waited
> for the request to be processed forever until the server is restarted.  It
> seems as if something is tying up each child and will not let it process a
> new request under 1.3.29.  This server runs mod_perl and mod_php, and did
> not have this problem under 1.3.28
>
> Apache is completely unusable in this state.
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#224128: apache: I can repeat this behaviour and can supply a strace -f

[Fabio Massimo Di Nitto]

Hi Thomas,
thanks for your effort but the bug is well known to the php
maintainers. It is not an apache problem. Therefor this bug has been
closed. php4 has already 5 or more bugs opened for the same problem
already.

Thanks
Fabio


On Sun, 28 Dec 2003, Thomas Reifferscheid wrote:

> Package: apache
> Version: 1.3.29.0.1-3
> Severity: normal
> Followup-For: Bug #224128
>
> I can repeat Jordan Trasks Problem over and over again. Here is what I
> did:
>
> apachectl stop
>
> ps auxw |grep apache shows: no running apaches anymore.
> no /var/run/apache.pid.
>
> bash-2.05b# apachectl configtest
> Processing config directory: /etc/apache/conf.d
>  Processing config file: /etc/apache/conf.d/phpmyadmin
>  Syntax OK
>
> bash-2.05b# ps auxw |grep apa
> root 23992  0.0  0.0  1532  456 pts/2R01:44   0:00 grep apa
> bash-2.05b#
>
> bash-2.05b# modules-config apache disable mod_php4
> bash-2.05b# grep php /etc/apache/modules.conf
> bash-2.05b# apachectl start
> Processing config directory: /etc/apache/conf.d
>  Processing config file: /etc/apache/conf.d/phpmyadmin
>  /usr/sbin/apachectl start: httpd started
>  bash-2.05b# ps auxw |grep apache |wc -l
>  17
>
> bash-2.05b# modules-config apache enable mod_php4
> bash-2.05b# grep php /etc/apache/modules.conf
> LoadModule php4_module /usr/lib/apache/1.3/libphp4.so
>
> 
>
> bash-2.05b# apachectl graceful
> /usr/sbin/apachectl graceful: httpd gracefully restarted
> bash-2.05b# ps auxw |grep apache |wc -l
> 17
>
>   _with_ php4>
>
>  and apache is back online with php4
>
>
> you can find a strace -f of a startattempt here:
> http://student.physik.uni-mainz.de/~reiffert/out.gz
>
>
> Any questions?
>
>
>
>
>
>
>
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux one.webersheim.de 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 
> i686
> Locale: LANG=POSIX, LC_CTYPE=POSIX (ignored: LC_ALL set to POSIX)
>
> Versions of packages apache depends on:
> ii  apache-common   1.3.29.0.1-3 Support files for all Apache 
> webse
> ii  debconf 1.3.22   Debian configuration management 
> sy
> ii  dpkg1.10.18  Package maintenance system for 
> Deb
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-10Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  libmagic1   4.06-2   File type determination library 
> us
> ii  libpam0g0.76-14.1Pluggable Authentication Modules 
> l
> ii  logrotate   3.6.5-2  Log rotation utility
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
> ii  perl [perl5]5.8.2-2  Larry Wall's Practical Extraction
>
> -- debconf information:
> * apache/server-name: one.webersheim.de
> * apache/document-root: /var/www
> * apache/server-port: 80
> * apache/enable-suexec: false
> * apache/init: true
> * apache/server-admin: [EMAIL PROTECTED]
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Re: Bug#225352: apache: install fails because of missing (?) or incomplete .info files

[Fabio Massimo Di Nitto]

On Mon, 29 Dec 2003, simon raven wrote:

> Le Mon, Dec 29, 2003 at 08:31:35 +0100, Fabio Massimo Di Nitto a ïcrit:
> >
> > Hi Simon,
> > clearly you did not read entirely the error message in the first
> > place since for that error you are not supposed to open bugs against
> > apache. info files as shipped by the mentioned modules, in this case
> > mod_tsunami, mod_accouting and mod_dynvhost. Please file bugs against
> > them.
>
> yeh no problem.
>
> oh so it's to the debian-apache@lists.debian.org list instead of BTS? i
> saw that address when i was using reportbug, so i thought it would get
> forwarded there... doh!

that is the mailing list address and the "virtual maintainer" for apache
since we are a team behind it. The reason why we do not want bugs for that
error is that apache is "clean" and it has been fixed all at once. So the
only reason why you can see that error is that another debian modules has
not been cleaned up properly or a manual installed modules did not follow
the debian rules (of course when installed in the debian way). So
virtually we are "this bug" free.

> i'm too tired right now to think straight, but i think that's what you
> mean, right?

No .. it would have been enough to read the other 2 lines of the error ;)

>
> good night/day/whatever :)

ehehe

> no problems with that.


good.

Ciao
fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

sarge package transition (was Re: Bug#224049: libapache-mod-perl: Works with perl 5.8.0; Segfaults against 5.8.2)

[Fabio Massimo Di Nitto]

reassign 224959 libapache-mod-perl
reassign 225287 libapache-mod-perl
merge 225287 224959
severity 224959 normal
tags 224959 + sarge
stop
quit

I hope to reach all the people having this problem with this mail.

Recently sarge has received a new version of perl but apache and mod-perl
packages in sarge are old. Until the sid packages will not enter sarge
there is no way for us to "fix" this problem since it is already fixed
since a while in sid. We have no control over the package flow from sid to
sarge, the only way is to wait. Please be patience. There are 2 work
arounds that you can temporary use. One is to roll back perl and one
(extremely unsuggested!) is to pull apache and all its modules from sid.

Thanks
fabio

PS I will close these bugs as soon as apache will enter sarge.

On Thu, 25 Dec 2003, Jeremy Avnet wrote:

> Package: libapache-mod-perl
> Version: 1.27-4
> Severity: normal
> Followup-For: Bug #224049
>
>
> A the subject said, this problem started occuring when I updated the
> system and perl 5.8.2-2 packages were installed. After downgrading to
> 5.8.0-18 packages:
>
>   libperl-dev_5.8.0-18_i386.deb
>   libperl5.8_5.8.0-18_i386.deb
>   perl-base_5.8.0-18_i386.deb
>   perl-doc_5.8.0-18_all.deb
>   perl-modules_5.8.0-18_all.deb
>   perl-suid_5.8.0-18_i386.deb
>   perl_5.8.0-18_i386.deb
>
> Apache starts fine.
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux in 2.4.22 #1 Sat Dec 20 21:29:08 PST 2003 i686
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages libapache-mod-perl depends on:
> ii  apache-common   1.3.27.0-2   Support files for all Apache 
> webse
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdevel-symdump-perl   2.03-3   Perl module for inspecting perl's
> ii  libperl5.8  5.8.2-2  Shared Perl library.
> ii  liburi-perl 1.23-1   Manipulates and accesses URI 
> strin
> ii  libwww-perl 5.69-4   WWW client/server library for 
> Perl
> ii  perl [libmime-base64-perl]  5.8.2-2  Larry Wall's Practical Extraction
> ii  perl-base [perlapi-5.8.0]   5.8.2-2  The Pathologically Eclectic 
> Rubbis
>
> -- no debconf information
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#225056: apache: Segmentation fault on startup with virtual hosts

[Fabio Massimo Di Nitto]

Can you show me your modules.conf?? if you are using php4, do you have the
php4-imap extension enabled?? in that case please disable it and restart
apache (php4 is broken and maintainers know about it).

thanks
Fabio

On Mon, 29 Dec 2003, Jeremy Lunn wrote:

> On Mon, Dec 29, 2003 at 08:43:35AM +0100, Fabio Massimo Di Nitto wrote:
> > Hi Jeremy,
> > if you are using mod_perl would you be so kind to try to upgrade
> > perl as well and tell if that segfault still happens? Please also upgrade
> > to the latest apache packages.
>
> Didn't realise that there is a newer package, though it seems my mirror
> may be a little outdated there.  Just tried the newest one
> (1.3.29.0.1-3) though and the symptoms are the same.  Not using
> mod_perl, nor is it installed at all.
>
> Thanks,
>
> Jeremy
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#225056: apache: Segmentation fault on startup with virtual hosts

[Fabio Massimo Di Nitto]

Hi Jeremy,
if you are using mod_perl would you be so kind to try to upgrade
perl as well and tell if that segfault still happens? Please also upgrade
to the latest apache packages.

Fabio


On Thu, 25 Dec 2003, Jeremy Lunn wrote:

> Package: apache
> Version: 1.3.29-1
> Severity: normal
>
>
> Using NameVirtualHosts, though since 1.3.29 I am getting a segmentation
> fault on startup if more than one virtual host is specified (obviously
> it defeats the purpose of virtual hosts if you can only list one).  To
> add to the strangeness, starting without the virtual hosts then
> reloading seems to work fine (also 'apachectlt configtest' shows up as
> OK).
>
> I don't know how to get any verbosity out of apache other than this:
> europa:/home/jeremy# /usr/sbin/apache -X
> Segmentation fault
>
> Strange is all I can say, though I'm guessing it's an upstream bug in
> 1.3.29.
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux europa 2.4.23-xfs #2 Fri Dec 19 18:49:08 EST 2003 i686
> Locale: LANG=en_AU, LC_CTYPE=en_AU
>
> Versions of packages apache depends on:
> ii  apache-common   1.3.29-1 Support files for all Apache 
> webse
> ii  debconf 1.3.20   Debian configuration management 
> sy
> ii  dpkg1.10.18  Package maintenance system for 
> Deb
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-10Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  libmagic1   4.06-1   File type determination library 
> us
> ii  logrotate   3.6.5-2  Log rotation utility
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
> ii  perl [perl5]5.8.0-18 Larry Wall's Practical Extraction
>
> -- debconf information excluded
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Re: Segmentation Fault after apache-ssl upgrade

[Fabio Massimo Di Nitto]

Hi Felipe,
this seems to be a problem with perl that has been recently
updated in sarge. Soon a new version of apache should enter sarge as well
to fix this problem.


Fabio

On Mon, 29 Dec 2003, Felipe Martínez Hermo wrote:

>
>   Hi!
>
>   I have just apt-get upgrade'd my system (Debian testing) and seems like
> apache-* upgraded to version 1.3.27.0-2
>   Apache restarted just right, but apache-ssl responds with segmentation 
> fault:
> max:/home/felipe/apache# /etc/init.d/apache-ssl start
> Starting web server: apache-ssl/etc/init.d/apache-ssl: line 65:  2207
> Segmentation fault  start-stop-daemon --start --pidfile $PIDFILE --exec
> $DAEMON
> failed
>
>   There is one difference between apache and apache-ssl in this particular
> system: ssl is configured to interact with an Oracle database through Oracle
> client 8.1.7 and perl-dbi but it had been working fine for 2 years
>   There's also something wrong with logs:
> I found this at /var/log/apache-ssl/error.log.1:
> [Sun Dec 28 06:25:21 2003] [notice] SIGUSR1 received.  Doing graceful restart
>
> However, it doesn't seem to have restarted "gracefully" and both access.log
> and error.log are empty
>
>
>   What else can I try? Sorry if I seem a little bit lost, but is the 
> first time
> that apt-get is not going right.
>
>   Thank you
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#225287: found solution

[Fabio Massimo Di Nitto]

On Sun, 28 Dec 2003, Kevin Renskers wrote:

> Okay, after even more searching through all the bug reports, I came
> across http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=224049 (in
> section libapache-mod-perl).
>
> And indeed, after disabling mod_perl, apache is working again. When will
> this be fixed? And why wasn't this bug posted in the Apache section?

As i wrote in the bug report and to the mailing list a new apache needs to
flow from sid to sarge. when it is difficult to say. The problem has been
fixed in sid long time ago.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#225487: apache-ssl: Postinstall fails with a "sed" error

[Fabio Massimo Di Nitto]

Hi Doug,
can you be so kind to add set -x to
/var/lib/dpkg/info/apache-ssl.postinst
and send me the output?

thanks
Fabio

On Mon, 29 Dec 2003, Doug Maxwell wrote:

> Package: apache-ssl
> Version: 1.3.29.0.1-3
> Severity: grave
> Tags: sid
> Justification: renders package unusable
>
> Error occurs immediately after entering information needed for creation
> of self-signed certificate:
>
> [EMAIL PROTECTED]:~$ sudo apt-get -f install
> Reading Package Lists... Done
> Building Dependency Tree... Done
> 0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
> 1 not fully installed or removed.
> Need to get 0B of archives.
> After unpacking 0B of additional disk space will be used.
> Setting up apache-ssl (1.3.29.0.1-3) ...
> sed: -e expression #4, char 42: Unknown option to `s'
> dpkg: error processing apache-ssl (--configure):
> subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
> apache-ssl
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> [EMAIL PROTECTED]:~$
>
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux hades 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages apache-ssl depends on:
> ii  apache-common   1.3.29.0.1-3 Support files for all Apache 
> webse
> ii  debconf 1.3.22   Debian configuration management 
> sy
> ii  dpkg1.10.18  Package maintenance system for 
> Deb
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-10Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  libkeynote0 2.3-10   Decentralized Trust-Management 
> sys
> ii  libmagic1   4.06-2   File type determination library 
> us
> ii  libpam0g0.76-14  Pluggable Authentication Modules 
> l
> ii  libssl0.9.7 0.9.7c-5 SSL shared libraries
> ii  logrotate   3.6.5-2  Log rotation utility
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
> ii  openssl 0.9.7c-5 Secure Socket Layer (SSL) binary 
> a
> ii  perl [perl5]5.8.2-2  Larry Wall's Practical Extraction
> ii  ssl-cert1.0-6Simple debconf wrapper for 
> openssl
>
> -- debconf information:
>   apache-ssl/server-admin: [EMAIL PROTECTED]
> * apache-ssl/enable-suexec: false
>   apache-ssl/init: true
>   apache-ssl/server-name: localhost
>   apache-ssl/document-root: /var/www
>
> My version of sed:
>   
>   ii sed 4.0.7-3
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#225430: Apache segfaults when starting - either by usign the startup script in /etc/init.d or by apachectl

[Fabio Massimo Di Nitto]

severity 225430 normal
reassign 225430 libapache-mod-perl
tags 225430 sarge
merge 225430 224959
stop
quit

Hi Michelle,
this bug has been fixed already in sid since a long time. Please
check the BTS and debian-apache mailing list for reference next time.

Thanks
Fabio


On Mon, 29 Dec 2003, Michelle Murrain wrote:

> Package: apache
> Version: 1.3.27.0-2
> Severity: grave
> Justification: renders package unusable
>
>
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux sloth 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages apache depends on:
> ii  apache-common   1.3.27.0-2   Support files for all Apache 
> webse
> ii  debconf 1.3.22   Debian configuration management 
> sy
> ii  dpkg1.10.18  Package maintenance system for 
> Deb
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-10Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  libmagic1   4.06-2   File type determination library 
> us
> ii  logrotate   3.6.5-2  Log rotation utility
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
> ii  perl [perl5]5.8.2-2  Larry Wall's Practical Extraction
>
> -- debconf information:
>   apache/enable-suexec: false
>
>   I get the following error:
>   Starting web server: apache/etc/init.d/apache: line 70:  2305
>   Segmentation fault  start-stop-daemon --start --pidfile $PIDFILE
>   --exec $DAEMON
>   failed
>
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#225287: libapache-mod-perl: Lovely theory, but my Apache still won't run.

[Fabio Massimo Di Nitto]

Hi Robin,
I could close this bug straight ahead since it has been fixed
already in sid. Instead you should have checked the BTS where there are
already several explanation and workaround.

Fabio

On Mon, 29 Dec 2003, Robin Lee Powell wrote:

> Package: libapache-mod-perl
> Version: 1.27-4
> Severity: normal
> Followup-For: Bug #225287
>
> This bug is *NOT* 'normal' severity.  The package is unusable, that
> makes it grave.
>
> While downgrading the perl packages is a lovely theory, the 5.8.0
> packages are no longer available, so mod_perl is, in fact, completely
> unusable.  This renders my Apache unusable as well, as I have several
> things that require mod_perl.
>
> If there *is* a workaround that does not involve taking packages from
> unstable, I would very much appreciate specific instructions on how to
> take advantage of it.
>
> -Robin
>
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux chain.digitalkingdom.org 2.4.22-1-k7-smp #5 SMP Sat Oct 4 
> 14:42:01 EST 2003 i686
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages libapache-mod-perl depends on:
> ii  apache-common   1.3.27.0-2   Support files for all Apache 
> webse
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdevel-symdump-perl   2.03-3   Perl module for inspecting perl's
> ii  libperl5.8  5.8.2-2  Shared Perl library.
> ii  liburi-perl 1.23-1   Manipulates and accesses URI 
> strin
> ii  libwww-perl 5.69-4   WWW client/server library for 
> Perl
> ii  perl [libmime-base64-perl]  5.8.2-2  Larry Wall's Practical Extraction
> ii  perl-base [perlapi-5.8.0]   5.8.2-2  The Pathologically Eclectic 
> Rubbis
>
> -- no debconf information
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#225056: apache: Segmentation fault on startup with virtual hosts

[Fabio Massimo Di Nitto]

reassign 225056 php4
severity 225056 grave
stop
quit

Hi Jeremy,
thanks for the report, I am reassigning this bug to php4.

Fabio

On Mon, 29 Dec 2003, Jeremy Lunn wrote:

> On Mon, Dec 29, 2003 at 09:04:02AM +0100, Fabio Massimo Di Nitto wrote:
> > Can you show me your modules.conf?? if you are using php4, do you have the
> > php4-imap extension enabled?? in that case please disable it and restart
> > apache (php4 is broken and maintainers know about it).
>
> Interesting, that looks like it's the problem them (strange the way it
> affected virtual hosts).
>
> Thanks,
>
> Jeremy
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#225634: Apache no longer runs from inetd.

[Fabio Massimo Di Nitto]

On Wed, 31 Dec 2003, Norbert Veber wrote:

> Package: apache
> Version: 1.3.29.0.1-3
> Severity: important
>
> Hello,
>
> I just noticed that my web page no longer works.  I run apache with
> mod-ssl from inetd.
>
> Aparently this is caused by conf.d support:
>
> [EMAIL PROTECTED]:~]$ telnet localhost https
> Trying 127.0.0.1...
> Connected to localhost.

here you are connected.. in order to get a page you need to send a
request.

Try to use a normal browser and see what happens.. is that reproducible
also on non-SSL connection?? it could be a mod-ssl problem.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Re: Need some help to package apache-lingerd

[Fabio Massimo Di Nitto]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexis Sukrieh wrote:
| Hello there.
|
| I'm pretty interested in trying to package apache-lingerd, which has
| been requested for more than 500 days now :
| http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=187460
|
| Could someone point me to some piece of docs on how the Debian Apache
| Maintainers team bild their package ?
eheh the truth is that our documentation is our debian/rules file.
|
| The fact is that lignerd needs the following steps to be packaged :
|
| First step : building lingerd :
|
| - tuning of config.h file
| - user creation : 'lingerd'
| - directory creation for hosting pidfile and unix domain socket
|   (/var/run/lingerd).
| - compilation of lingerd binary and installation of it.
This can be done easily afaict.
|
| Second step : patching Apache.
|
| - add some files to the apache src source tree
| - patch some apache native files
| - compile apache
Amen.. this is a pain. I really suggest you to look at how we build
apache. Take as example the fact that from the same source we create
binaries for apache, apache-perl and apache-ssl, but if you really
really need to create a patched apache i sugget to prepare everything
carefully and coordinate with us. It is easier to build a new apache
flavour from the same sources than having to upload a new one.
The security team would have serious problems to handle (again) more
than one apache source.
|
| Third step :
|
| - update the init.d startup script for apache : lingerd must be launched
|   before apache to work properly.
if you start from the apache package check debian/pkgtemplates and the
script that creates the final scripts.
|
| I'm sure that the team has a lot of guidelines to build such a package
| but I cannont find any docs about this.
as above.. read the source luke ;)
|
| Help will be welcome :)
|
|
Fabio
- --
 fajita: step one
 Whatever the problem, step one is always to look in the error log.
 fajita: step two
 When in danger or in doubt, step two is to scream and shout.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBYYiRhCzbekR3nhgRAn9kAKCV8jPp0iU20wmuEvipphiOQeZIjQCdGDOT
qJXBQPpDRJnmyzN8+9REP/A=
=ktLr
-END PGP SIGNATURE-

Re: Problem with segfaulting Apache 1.3.31-6 on Debian Sarge

[Fabio Massimo Di Nitto]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adrian Neumaier wrote:
| Hi,
|
| with the latest apache update i get an segmentation fault in apache
| while reading /usr/share/misc/file/magic/mime.
|
| If i do an 'strace apache -F' i get the following output:
|
| open("/usr/share/misc/file/magic.mime", O_RDONLY) = 4
| fstat64(4, {st_mode=S_IFREG|0644, st_size=26861, ...}) = 0
| mmap2(NULL, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
| 0) = 0x48997000
| read(4, "# Magic data for KMimeMagic (ori"..., 131072) = 26861
| read(4, "", 131072) = 0
| close(4)= 0
| munmap(0x48997000, 131072)  = 0
| --- SIGSEGV (Segmentation fault) @ 0 (0) ---
| +++ killed by SIGSEGV +++
|
| If i run it with 'gdb --args apache -F' i get this:
|
| Program received signal SIGSEGV, Segmentation fault.
| [Switching to Thread 1076565824 (LWP 23328)]
| 0x401f0568 in strcmp () from /lib/tls/i686/cmov/libc.so.6
|
| This even happens with when i run apache with -X...
|
| I've no clue why this happens - nor why it happend only last sunday
| morning when apache was restarted during the logrotate. Apache-ssl is
| not affected by this behavior.
|
| Some Package informations:
|
| ii  apache 1.3.31-6   Versatile, high-performance HTTP server
| ii  apache-common  1.3.31-6   Support files for all Apache webservers
| ii  libc6  2.3.2.ds1-16   GNU C Library: Shared libraries and
| Timezone
| ii  libc6-i686 2.3.2.ds1-16   GNU C Library: Shared libraries [i686
| optimized]
|
| Kernel is a 2.6.7
|
| Has anyone any hint for me how to get rid of this? Sadly using apache2
| is not a solution for me...
Are you running php4? In this case it is a know problem and either you
install libapache-mod-ssl (even unconfigured) or you remove php4.
The real problem is located down in the lic6 elf loader but there is not
much to do about it until there will be a fix for it.
Fabio
- --
 fajita: step one
 Whatever the problem, step one is always to look in the error log.
 fajita: step two
 When in danger or in doubt, step two is to scream and shout.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBY9ZphCzbekR3nhgRAo/MAJ47XLCrzbWivkLzMiOMo9oKqCkwgwCfcxHh
sTsoWIoCuMIwphUDUXFFRd8=
=K+Aa
-END PGP SIGNATURE-

Re: help

[Fabio Massimo Di Nitto]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Priya Ranjan wrote:
| Hi I am not a member of this list but I need some help. I was trying to
| install libapache-mod-perl and uninstall also but it was giving me grief
| as shown below.
| Any solutions?
| thanks,
| -priya
|
|
| (Reading database ... 97252 files and directories currently installed.)
| Removing libapache-mod-perl ...
| Error: libphp4.so does not have a corresponding .info file.
| The above errors might cause apache to not work properly or start
| Please refer to the documentation on how to fix it or report it to
| Debian Apache Mailing List  if in doubt
| on how to proceed
For some reasons your php4 installation is broken or not complete.
This causes an error in the sanity checks we perform in order to handle
the apache configuration properly.
Fabio
- --
 fajita: step one
 Whatever the problem, step one is always to look in the error log.
 fajita: step two
 When in danger or in doubt, step two is to scream and shout.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBa3sihCzbekR3nhgRAoG/AJkBoXJ8R1spimvZqSwRq0b68KEP/gCggx66
kHl8VtwVmdqe+3NS6K9WHXo=
=jtzq
-END PGP SIGNATURE-

Bug#277124: apache-common: /var/lib/apache/mod-bandwidth permissions

[Fabio Massimo Di Nitto]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Lammerts wrote:
| Thom May wrote:
|
|> Thank you so much, we hadn't noticed we were deliberately creating a
|> directory with 777 permissions.
|> (yes, it is necessary, and yes, it is really necessary, and yes it's
|> absolutely necessary).
|
|
| Well, maybe you can explain why? This directory is not gonna be accessed
| by anyone except apache, right?
|
| I would read the RTFM you know, if there was any...
There is one copied in several locations:
zless \
/usr/share/doc/apache{,-ssl,-perl,-dbg,-utils,-common}/README.Debian.gz\
| head -n 20
Fabio
- --
 fajita: step one
 Whatever the problem, step one is always to look in the error log.
 fajita: step two
 When in danger or in doubt, step two is to scream and shout.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBdK1phCzbekR3nhgRAlPlAJ48k2OFDNbq1p3fLiPaKBkV2Yr67wCfSZ6T
Sy5XayLIY+aK6z7bzwRvtkg=
=ZmZP
-END PGP SIGNATURE-

Bug#225487: apache-ssl: Postinstall fails with a "sed" error

[Fabio Massimo Di Nitto]

Hi Douglas,
thanks for the information. I think that the fact that apache does
not start is related to the wrong certificate. Just to be sure 100% please
remove /etc/apache-ssl/apache.pem and try to reinstall apache-ssl with
your patch applied to make-ssl-cert. This should generate a new and clean
certificate and hopefully apache-ssl will start.

Thanks
fabio

On Wed, 31 Dec 2003, Douglas Maxwell wrote:

> Hi Fabio-
>
> This patch fixes the problem and allows me to generate the cert.
>
> [EMAIL PROTECTED]:~$ diff -ur make-ssl-cert.orig make-ssl-cert
> --- make-ssl-cert.orig  2003-12-31 12:51:49.0 -0500
> +++ make-ssl-cert   2003-12-31 12:52:18.0 -0500
> @@ -97,13 +97,13 @@
>  Email="$RET"
>  db_fset make-ssl-cert/email seen false
>
> -sed -e s,@CountryName@,"$CountryName", \
> --e s,@StateName@,"$StateName", \
> --e s,@LocalityName@,"$LocalityName", \
> --e s,@OrganisationName@,"$OrganisationName", \
> --e s,@OUName@,"$OUName", \
> --e s,@HostName@,"$HostName", \
> --e s,@Email@,"$Email", \
> +sed -e s/@CountryName@/"$CountryName"/ \
> +-e s/@StateName@/"$StateName"/ \
> +-e s/@LocalityName@/"$LocalityName"/ \
> +-e s/@OrganisationName@/"$OrganisationName"/ \
> +-e s/@OUName@/"$OUName"/ \
> +-e s/@HostName@/"$HostName"/ \
> +-e s/@Email@/"$Email"/ \
>  $template > /tmp/$$.req
>
>  export RANDFILE=/dev/random
>
> ...but I now get an error regarding the cert request:
>
> hades:/etc/apache-ssl# apt-get -f install
> Reading Package Lists... Done
> Building Dependency Tree... Done
> 0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
> 1 not fully installed or removed.
> Need to get 0B of archives.
> After unpacking 0B of additional disk space will be used.
> Setting up apache-ssl (1.3.29.0.1-3) ...
> + make_selfsigned_cert
> + '[' '!' -f /etc/apache-ssl/apache.pem ']'
> + /usr/sbin/make-ssl-cert /usr/share/ssl-cert/ssleay.cnf
> /etc/apache-ssl/apache.pem
> Generating a 1024 bit RSA private key
> .++
> ...++
> writing new private key to '/etc/apache-ssl/apache.pem'
> -
> problems making Certificate Request
> 5332:error:0D07A098:asn1 encoding routines:ASN1_mbstring_copy:string too
> short:a_mbstr.c:147:minsize=1
> dpkg: error processing apache-ssl (--configure):
>  subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
>  apache-ssl
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> ...and when I run 'apt-get -f install' again:
>
> Starting web server: apache-sslProcessing config directory:
> /etc/apache-ssl/conf.d
>  failed
> invoke-rc.d: initscript apache-ssl, action "start" failed.
> dpkg: error processing apache-ssl (--configure):
>  subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
>  apache-ssl
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> hades:/etc/apache-ssl#
>
> I attached the output with 'set -x' in the postinstall script, as it was
> rather large - this is with the above patch applied.
>
> Regards,
>
> Doug
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#225487: apache-ssl: Postinstall fails with a "sed" error

[Fabio Massimo Di Nitto]

Hi Doug,

On Thu, 1 Jan 2004, Douglas Maxwell wrote:

> On Thu, Jan 01, 2004 at 10:01:23AM +0100, Fabio Massimo Di Nitto wrote:
> >
> > Hi Douglas,
> > thanks for the information. I think that the fact that apache does
> > not start is related to the wrong certificate. Just to be sure 100% please
> > remove /etc/apache-ssl/apache.pem and try to reinstall apache-ssl with
> > your patch applied to make-ssl-cert. This should generate a new and clean
> > certificate and hopefully apache-ssl will start.
>
> No luck - I get the same error after removing the cert and regenerating
> it. I also tried a clean installation after purging the existing one -
> with the same results.

Sorry I need to ask you to do the last test. What happens if you create
the certificate with default values?? just for testing of course. If this
work there might be something wrong in the data you pass to make-ssl-cert
via debconf or a bug in it that make the certificate wrong.

Thanks a lot
Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#226498: Apache (php) crashes with PHP4 and GD2.

[Fabio Massimo Di Nitto]

reassign 226498 php4
stop
quit

Clearly this is a php4 problem. I am reassigning the bug.

Fabio

On Tue, 6 Jan 2004, Rasmus Aveskogh wrote:

>
> Package: apache, apache-common, php4, php4-gd2
> Version: apache 1.3.29.0.1-3, php4 4.3.3-4, php4-gd2 4.3.2+rc3-2
>
> Apache starts off as normal and is able to handle normal non-PHP pages.
> When a PHP page (regardless of using GD2 or not) is requested the (child)
> server crashes with the following error in the error log:
>
> /usr/sbin/apache: relocation error: /usr/lib/php4/20020429/gd.so:
> undefined symbol: gdFreeFontCache
>
> The network socket to the client is terminated non-gracefully.
>
> I've tryed it on two different machines both using unstable, and it
> doesn't seem to get to work at all.
>
> I'm using Debian unstable and Linux 2.6.0.
>
> -ra
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#225634: Apache no longer runs from inetd.

[Fabio Massimo Di Nitto]

tags 225634 upstream
retitle 225634 apache, apache-perl, apache-ssl cannot run from inetd when 
including a directory as config source.
stop
quit

hi Norbert,
as you can see I just managed to reproduce the problem. Using
non-ssl connection makes the error more evident since some extra junk is
added before sending the html. On the ssl side i suspect that this extra
junk would break the negotiation for encryption and so on.

Of course the only workaround until upstream will not fix this problem is
to run apache in standalone. I suspect an error in the vty detaching code.

Fabio

On Wed, 31 Dec 2003, Norbert Veber wrote:

> On Wed, Dec 31, 2003 at 12:20:07PM -0500, Norbert Veber wrote:
> > PS.  This is the inetd.conf line I use:
> >
> > https   stream tcp  nowait.180  root  /usr/sbin/tcpd 
> > /usr/sbin/apache
> >
> > It has worked fine for about a year.
> >
> > In httpd.conf I have:
> > # ServerType is either inetd, or standalone.
> >
> >
> > ServerType inetd
>
> Also, if you want to connect to it yourself, its https://pyre.virge.net.
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#226638: apachectl configtest segfault

[Fabio Massimo Di Nitto]

Hi John,
are you using sarge? In case please be sure to update
libapache-mod-perl too and check if this error still happens.

Thanks
Fabio

On Wed, 7 Jan 2004, John West wrote:

> Package: apache
> Version: 1.3.29.0.1-3
> Severity: normal
>
> Hi-
>
> When invoking apachectl configtest, I get a segfault.  See below:
>
> shoggoth:/home/jwest# apachectl stop
> /usr/sbin/apachectl stop: httpd (no pid file) not running
> shoggoth:/home/jwest# apachectl configtest
> [15361]SES:  Embperl Session management enabled ()
> Processing config directory: /etc/apache/conf.d
> Syntax OK
> /usr/sbin/apachectl: line 171: 15361 Segmentation fault  $HTTPD -t
>
> This also causes my upgrade to fail.
>
> Thanks!
>
> --John
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux shoggoth 2.4.20ctx #1 Mon Mar 17 11:44:18 EST 2003 i686
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages apache depends on:
> ii  apache-common   1.3.29.0.1-3 Support files for all Apache 
> webse
> ii  debconf 1.3.22   Debian configuration management 
> sy
> ii  dpkg1.10.18  Package maintenance system for 
> Deb
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-10Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  libmagic1   4.06-2   File type determination library 
> us
> ii  libpam0g0.76-14.1Pluggable Authentication Modules 
> l
> ii  logrotate   3.6.5-2  Log rotation utility
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
> ii  perl [perl5]5.8.2-2  Larry Wall's Practical Extraction
>
> -- debconf information:
>   apache/server-name: localhost
>   apache/document-root: /var/www
>   apache/server-port: 80
> * apache/enable-suexec: false
>   apache/init: true
>   apache/server-admin: [EMAIL PROTECTED]
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Re: Standard apache modules missing .info files. Apache package fails setup

[Fabio Massimo Di Nitto]

On Fri, 9 Jan 2004, Lindsay Haisley wrote:

> Apache version 1.3.29.0.1-3 fails on setup with the following errors re.
> standard apache modules:
>
>   Error: mod_example.so does not have a corresponding .info file.
>   Error: mod_mmap_static.so does not have a corresponding .info file.
>   Error: the above error list does not permit a safe use of modules-config.
>   Please refer to the documentation on how to fix it or report it to
>   Debian Apache Maling List  if in doubt
>   on how to proceed
>
> Since I was unable to find adequate (read "any") information in
> /usr/share/doc/apache/* on how to address this problem I am directing it
> this list, as requested.
>
> Packages apache-ssl is also blocked.

Since modules are generated using the apache-dev package all related
information are in there. Please install apache-dev and check:
/usr/share/doc/apache-dev/README.modules

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#226833: apache: modules-config fails on unrelated .so files

[Fabio Massimo Di Nitto]

Hi Simon,

On Thu, 8 Jan 2004, Simon Huggins wrote:

> Package: apache
> Version: 1.3.29.0.1-3
> Severity: normal
>
> modules-config is overzealous in its parsing of /usr/lib/apache/1.3 on
> upgrades.
>
> My previously working config caused it to die during configuration.
>
> I had an old libperl.so lying around in there (I'm still not sure why -
> I don't have mod_perl installed now).
>
> It didn't have a .info file so modules-config barfed.

The error is generated on purpuse. It doesn't barf.

> I don't think modules-config should just barf on such things.  I'm not
> sure if you're allowed to prompt during configuration I believe it's
> frowned upon but as you're going to barf anyway perhaps it would be
> permissible to prompt the user to override its choices.
>
> Otherwise perhaps it could limit itself to complaining about currently
> active modules or just discard modules from its own calculations which
> don't have an info file (and warn presumably).

There are reasons why we stop upgrading if the relation between .so and
.info is incosistent. The problem is simple, without info file we cannot
build the list on modules that needs to be loaded. If for example we
ignore a module, and some directives of this module are in the
configuration files, apache will complain at a later stage that the
configuration is broken (when we perform the restart) and it will not
attempt a restart. This can lead to a situation in which the user will
think that the upgrade was smooth when it wasn't, with an old apache
running and the new one not completely configured. Or that apache is not
running and it will not restart "without an explicit reason" that is not
the simplest to debug.

Fixing this problem would make user life more complex in terms of
understanding what is wrong.

>
> Either of these would have given me a nicer upgrade path.

In your specific case this is possibly true but not for common cases
therefor is much better to stop upgrading with an error and let the user
know that something is missing or broken and that the upgrade is not
complete other than just hide things from him.

The idea of giving the user the possibility to override is nice but
extremely dangerous for the same reasons as above.

In anycase i will close the bug in a few days if you do not have any more
comments.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#226638: (no subject)

[Fabio Massimo Di Nitto]

tags 226638 moreinfo
stop
quit

No answer back to my information request. I will close this bug in a
couple of days if the submitter will not answer back.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#224923: apache-ssl: error during post-installation script

[Fabio Massimo Di Nitto]

Hi Sylvain,
please upgrade to the latest packages and let me know if this is
still happening. I will close the bug in a couple of days if i will not
hear anything from you.

Thanks
Fabio

On Tue, 23 Dec 2003, Sylvain Ferriol wrote:

> Package: apache-ssl
> Version: 1.3.27.0-2
> Severity: normal
>
> apt-get install apache-ssl return an error:
> """
> Starting web server: apache-ssl/usr/sbin/apache-ssl already running.
> failed
> invoke-rc.d: initscript apache-ssl, action "start" failed.
> ...
> ...
> """
>
> and is it possible to use debconf for configuring ssl certificates
>
> sylvain
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: alpha
> Kernel: Linux dirac 2.4.18-1-generic #4 Sat Nov 29 10:19:17 EST 2003 alpha
> Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]
>
> Versions of packages apache-ssl depends on:
> ii  apache-common   1.3.27.0-2   Support files for all Apache 
> webse
> ii  debconf 1.3.20   Debian configuration management 
> sy
> ii  dpkg1.10.18  Package maintenance system for 
> Deb
> ii  libc6.1 2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-10Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  libmagic1   4.06-1   File type determination library 
> us
> ii  libssl0.9.7 0.9.7c-5 SSL shared libraries
> ii  logrotate   3.6.5-2  Log rotation utility
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
> ii  openssl 0.9.7c-5 Secure Socket Layer (SSL) binary 
> a
> ii  perl [perl5]5.8.0-18 Larry Wall's Practical Extraction
>
> -- debconf-show failed
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#226954: apache: mod_proxy; auth/basic; tomcat4: apache inserts blank line in header

[Fabio Massimo Di Nitto]

tags 226954 + woody
severity 226954 minor
stop
quit
thanks

Please do not abuse of severity. The bug is fixed and could be closed.

Fabio

On Fri, 9 Jan 2004, Marc SCHAEFER wrote:

> Package: apache
> Version: 1.3.26-0woody3
> Severity: important
> Tags: patch
>
> Hi,
>
> if using mod_proxy in Apache and the remote HTTP server returns
> a HTTP/1.1 401 (authentification required), but there is nothing
> after the 401 after the space, Apache adds a space and thus
> makes the additional header lines displayed in your WWW client.
>
> Bad case:
>HTTP/1.1 401
>Content-Type: text/html;charset=ISO-8859-1
>Connection: close
>Content-Language: en-US
>Date: Fri, 09 Jan 2004 15:19:57 GMT
>Server: Apache Tomcat/4.1 (HTTP/1.1 Connector)
>WWW-Authenticate: Basic realm="Authentication for bla platform."
>
> Good case:
>replace the first line with
>   HTTP/1.1 401 blaaa
>
> (you can easily reproduce this by typing by hand through a
> nc -l -p 4000)
>
> This was found by using tomcat4.1 with Apache and mod_proxy and
> an authentification module.
>
> References: (although this is Apache 2, it applies).
>http://bugzilla.redhat.com/bugzilla/long_list.cgi?buglist=89179
>
> Patch:
>Apparently the fix is already in testing/unstable, this is
>for documentation for people who wants to maintain stable
>packages.
>
> diff -urP apache_1.3.26/src/modules/proxy/proxy_util.c 
> apache_1.3.26/apache_1.3.26/src/modules/proxy/proxy_util.c
> --- build-tree/apache_1.3.26/src/modules/proxy/proxy_util.c   Tue Jun 18 
> 02:59:59 2002
> +++ build-tree/apache_1.3.26/src/modules/proxy/proxy_util.c   Mon Feb  3 
> 18:13:26 2003
> @@ -1,7 +1,7 @@
>  /* 
>   * The Apache Software License, Version 1.1
>   *
> - * Copyright (c) 2000-2002 The Apache Software Foundation.  All rights
> + * Copyright (c) 2000-2003 The Apache Software Foundation.  All rights
>   * reserved.
>   *
>   * Redistribution and use in source and binary forms, with or without
> @@ -1607,6 +1607,12 @@
>  }
>  *backasswards = 0;
>
> +/* there need not be a reason phrase in the response,
> +  * and ap_getline() already deleted trailing whitespace.
> +  * But RFC2616 requires a SP after the Status-Code. Add one:
> +  */
> + if (strlen(buffer) < sizeof("HTTP/1.x 200 ")-1)
> +   buffer = ap_pstrcat(r->pool, buffer, " ", NULL);
>  buffer[12] = '\0';
>  r->status = atoi(&buffer[9]);
>  buffer[12] = ' ';
>
>
> -- System Information
> Debian Release: 3.0
> Architecture: i386
> Kernel: Linux defian 2.4.21 #1 Fri Nov 7 18:54:07 MET 2003 i686
> Locale: LANG=C, LC_CTYPE=fr_CH
>
> Versions of packages apache depends on:
> ii  apache-common 1.3.26-0woody3 Support files for all Apache 
> webse
> ii  dpkg  1.9.21 Package maintenance system for 
> Deb
> ii  libc6 2.2.5-11.5 GNU C Library: Shared libraries 
> an
> ii  libdb22:2.7.7.0-7The Berkeley database routines 
> (ru
> ii  libexpat1 1.95.2-6   XML parsing C library - runtime 
> li
> ii  logrotate 3.5.9-8Log rotation utility
> ii  mime-support  3.18-1.3   MIME files 'mime.types' & 
> 'mailcap
> ii  perl  5.6.1-8.3  Larry Wall's Practical Extraction
> ii  perl [perl5]  5.6.1-8.3  Larry Wall's Practical Extraction
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#226131: $r->dir_config('foo') returns undef instead of 0 when PerlSetVar foo '0'

[Fabio Massimo Di Nitto]

Hi Don,
can you test the patch and come back to me?

Fabio

On Sat, 3 Jan 2004, Don Armstrong wrote:

> Package: libapache-mod-perl
> Version: 1.29.0.1-3
> Severity: important
> Tags: patch
>
> An apache configuration with:
>
> 
>  PerlSetVar foo '0';
> 
>
> Causes $r->dir_config('foo') to return undef unstead of zero. However,
> $r->dir_config returns a hashref with the appropriate values set.
>
> Apparently, the following patch[1] fixes this issue, but I have not yet
> tried it myself. (It looks reasonable though...)
>
> Index: src/modules/perl/Apache.xs
> ===
> RCS file: /home/cvspublic/modperl/src/modules/perl/Apache.xs,v
> retrieving revision 1.129
> diff -u -r1.129 Apache.xs
> --- src/modules/perl/Apache.xs 16 Sep 2003 19:51:06 - 1.129
> +++ src/modules/perl/Apache.xs 25 Nov 2003 20:39:41 -
> @@ -2084,7 +2084,7 @@
> &perl_module);
> TABLE_GET_SET(c->vars, FALSE);
> }
> - if (!SvTRUE(RETVAL)) {
> + if (!SvOK(RETVAL)) {
> s = r && r->server ? r->server : perl_get_startup_server();
> if (s && s->module_config) {
> SvREFCNT_dec(RETVAL); /* in case above did newSV(0) */
>
>
> Don Armstrong
>
> 1: 
> http://www.gossamer-threads.com/archive/mod_perl_C1/modperl_F7/PerlSetVar_with_0_value_P90608/
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#225015: apache: fails to upgrade

[Fabio Massimo Di Nitto]

Hi Martin,

On Tue, 23 Dec 2003, Martin Hans wrote:

> Package: apache
> Version: 1.3.29.0.1-3
> Severity: important
> Tags: sid
>
> The apache package fails to upgrade:
>
> Setting up apache (1.3.29.0.1-3) ...
> Starting web server: apache failed
> invoke-rc.d: initscript apache, action "start" failed.

Can you please check the logs for errors and see what is causing the
failure?

> dpkg: error processing apache (--configure):
>  subprocess post-installation script returned error exit status 1
>
> Afterwards the apache package is broken, but the apache itself
> is running.
> I got no "/var/www" like #224454 and my /var/www is just a directory.

I don't understand... do you have a /var/www or not?? /var/www is only
created on installation.. it is not touched across upgrades.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#227294: apache-perl: hangs reading files in conf.d blocking startup process

[Fabio Massimo Di Nitto]

reassign 227294 libapache-mod-ssl
stop
quit
thanks

Hi Streph,
as you have noticed apache doesn't write anything inside conf.d.
If a package writes a portion of config file in there breaking other stuff
there is nothing i can do as a apache maintainer other than reassigning
the bug to the appropriate package. In any case if conf.d is only
commented in the configuration it shouldn't be readded automatically.
(at least that's what the script is supposed to do)

Fabio

On Sun, 11 Jan 2004, Streph Treadway wrote:

> Package: apache-perl
> Version: 1.3.29.0.1-3
> Severity: normal
>
> I upgraded today from 1.3.29-1 to take advantage of the bugfix for #223829.
> Thanks, by the way.  I am running apache-perl with mod_ssl as a DSO.
> I use mod_ssl in a single virtual host.  The upgrade installed two files
> related to mod_ssl in conf.d, which was otherwise empty.  One of these
> appeared to contain global configuration directives and the other had
> vhost-specific directives.  Neither appered related to my particular
> configuration, which remains in http.conf.  When attempting to restart
> after the upgrade, apache-perl hung reading the files in conf.d and did
> again on attempts to restart.  This was particularly annoying as it
> blocked the startup process.  For now I have commented out the include
> directive in httpd.conf for conf.d, and all is well.  But I expect I will
> have to repeat the process on my next routine upgrade.  The apache-perl
> error.log has the following which suggests the problem is that my key is
> not where the default configuration expects it to be:
>
> [Sun Jan 11 17:46:02 2004] [error] mod_ssl: Init: Private key not found
> (OpenSSL library error follows)
> [Sun Jan 11 17:46:02 2004] [error] OpenSSL: error:0D094068:asn1 encoding
> routines:d2i_ASN1_SET:bad tag
> [Sun Jan 11 17:46:02 2004] [error] OpenSSL: error:0D0680A8:asn1 encoding
> routines:ASN1_CHECK_TLEN:wrong tag
> [Sun Jan 11 17:46:02 2004] [error] OpenSSL: error:0D07803A:asn1 encoding
> routines:ASN1_ITEM_EX_D2I:nested asn1 error
> [Sun Jan 11 17:46:02 2004] [error] OpenSSL: error:0D09A00D:asn1 encoding
> routines:d2i_PrivateKey:ASN1 lib
>
>
> Thanks again,
>
> Streph
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux janus 2.4.19 #4 SMP Wed Aug 20 19:54:38 EDT 2003 i586
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages apache-perl depends on:
> ii  apache-common   1.3.29.0.1-3 Support files for all Apache 
> webse
> ii  debconf 1.4.4Debian configuration management 
> sy
> ii  dpkg1.10.18  Package maintenance system for 
> Deb
> ii  libapache-mod-perl  1.29.0.1-3   Integration of perl with the 
> Apach
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-13Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  libmagic1   4.06-2   File type determination library 
> us
> ii  libpam0g0.76-14.1Pluggable Authentication Modules 
> l
> ii  libperl5.8  5.8.2-2  Shared Perl library.
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
>
> -- debconf information:
>   apache-perl/old-pidfile-set:
> * apache-perl/upgrade-from-apache-conflict:
>   apache-perl/server-port: 80
>   apache-perl/init: true
> * apache-perl/enable-suexec: false
>   apache-perl/server-name: www.ginkwunk.net
>   apache-perl/server-admin: [EMAIL PROTECTED]
>   apache-perl/document-root: /var/www
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Re: Thought: hell is going to break loose

[Fabio Massimo Di Nitto]

Hi David,

On Mon, 12 Jan 2004, David N. Welton wrote:

>
> ... when a stable release comes out and people's apache installations
> suddenly *stop working*.  Do some calculations based on how many
> people are making noise about this issue now and I think 'royal
> ruckus' doesn't begin to describe the situation.

Well you are welcome to help us in maintaing apache. We are an open team
and we really appreciate help since apache is such a wide and complex
package that it is impossible to verify any situation in advance.

> There has got to be a way that things can not just fall over like that.
> Debian to me is about providing stable upgrades, even if someone has
> done something we now consider to be trampling on Debian's territory.

we do all agree on this issue.. help us testing packages before release is
even better.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#225487: apache-ssl: Postinstall fails with a "sed" error

[Fabio Massimo Di Nitto]

On Mon, 12 Jan 2004, Douglas Maxwell wrote:

> Hi Fabio-
>
> On Mon, Jan 12, 2004 at 09:18:04PM +0100, Fabio Massimo Di Nitto wrote:
> > I am just going trough the bug again and i noticed that there is
> > stuff missing from the information required to generate the certificate
> > like Locality Name.
> >
> > All the fields are required to generate the certificate. Can you kindly
> > try again removing /etc/apache-ssl/apache.pem, create a certificate with
> > all the fields filled up?
>
> I tried this, and it now seems to work fine. The cert is generated without
> error, and apache-ssl starts as normal. This was definitely unexpected
> behavior, though. I have generated self-signed certificates before and have
> not had to fill in all the fields.

It is unexpected for me as well. From my experience i can tell that i have
been always providing all the data (also in the past) to be sure that
everything was ok.

> Did this change recently?

I have no idea.

> Would a warning
> in debconf be appropriate, or perhasps some logic to refuse to generate the
> cert if any fields are left blank?

I was thinking about the second option. The first one would not prevent
users from messing around ;) In any case it is all still a ssl-cert
problem (but no9 worry... we are still the same maintainers ;))

> Thanks for your time, it is much appreciated.

No problem at all.

Thanks to you for helping us
Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#226131: $r->dir_config('foo') returns undef instead of 0 when PerlSetVar foo '0'

[Fabio Massimo Di Nitto]

thanks. applied.

Fabio

On Mon, 12 Jan 2004, Don Armstrong wrote:

> On Mon, 12 Jan 2004, Don Armstrong wrote:
>
> > On Mon, 12 Jan 2004, Fabio Massimo Di Nitto wrote:
> > >   can you test the patch and come back to me?
> >
> > Yeah, lemme do that.
>
> Ok, I've gone through and tested this, and yes, the patch does work as
> advertised.
>
> Just for reference, upstream's patch is here:
>
> http://cvs.apache.org/viewcvs.cgi/modperl/src/modules/perl/Apache.xs?r1=1.129&r2=1.130
>
>
> Don Armstrong
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#225487: apache-ssl: Postinstall fails with a "sed" error

[Fabio Massimo Di Nitto]

reassign 225487 ssl-cert
stop
quit

Hi Douglas,
I am just going trough the bug again and i noticed that there is
stuff missing from the information required to generate the certificate
like Locality Name.

All the fields are required to generate the certificate. Can you kindly
try again removing /etc/apache-ssl/apache.pem, create a certificate with
all the fields filled up?

This would explain the error you get that some strings are empty and the
minimum size is 1. In any case i am reassining the bug to ssl-cert
regarding the sed stuff.

Thanks
Fabio

On Fri, 2 Jan 2004, Douglas Maxwell wrote:

> Hi Fabio-
>
> (forgot to CC debian-bugs, sorry for the dup)
> > Sorry I need to ask you to do the last test. What happens if you
> > create
> > the certificate with default values?? just for testing of course. If
> > this
> > work there might be something wrong in the data you pass to
> > make-ssl-cert
> > via debconf or a bug in it that make the certificate wrong.
>
> The thought had occurred to me, too. I don't recall what the original
> defaults were - debconf seems to remember my answers to the cert
> questions from one invocation to the next (normally a great
> feature...;-)).
>
> I did try to generate a new cert with very generic information - only
> "localhost" for hostname and "[EMAIL PROTECTED]" for email, with the
> other settings left blank (I think that was the default...).  I also
> tried with some generic settings for country/state/organization. Same
> results.
>
> I attached a script output where you can see my responses to debconf's
> questions, also with the output of "set -x" in the postinst shell
> script.
>
> This error doesn't seem to matter (/etc/apache-ssl/conf.d is empty):
>
> "Starting web server: apache-ssl
> Processing config directory: /etc/apache-ssl/conf.d failed"
>
> Just as a test, I commented out the "include" directive in
> /etc/apache-ssl/httpd.conf that included
> /etc/apache-ssl/conf.d/, and just got this, generic error:
>
> hades:/home/doug# apt-get -f install
> Reading Package Lists... Done
> Building Dependency Tree... Done
> 0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
> 1 not fully installed or removed.
> Need to get 0B of archives.
> After unpacking 0B of additional disk space will be used.
> Setting up apache-ssl (1.3.29.0.1-3) ...
> Starting web server: apache-ssl failed
> invoke-rc.d: initscript apache-ssl, action "start" failed.
> dpkg: error processing apache-ssl (--configure):
>  subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
>  apache-ssl
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> hades:/home/doug#
>
>
> Thanks,
>
> Doug
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Re: Apache module Loading problem

[Fabio Massimo Di Nitto]

Hi Cemil,

On Tue, 13 Jan 2004, Cemil Degirmenci wrote:

> A long time the missing info files was no problem, because Apache starts 
> anyway... but after doing some
> handicrafts it seems that i destroy my Apache. After /etc/init.apache start 
> now the following Error appears:
> [Tue Jan 13 15:36:23 2004] [warn] module setenvif_module is already 
> loaded, skipping
> [Tue Jan 13 15:36:23 2004] [warn] module perl_module is already loaded, 
> skipping
> [Tue Jan 13 15:36:23 2004] [warn] module php4_module is already loaded, 
> skipping
> Syntax error on line 370 of /etc/apache/httpd.conf:
> Invalid command 'Order', perhaps mis-spelled or defined by a module not 
> included in the server configuration
>
> /var/log/apache/error.log doesnt say something usefull, even in debug mode :/
> www:/etc/apache# tail -f /var/log/apache/error.log
> [Tue Jan 13 14:48:47 2004] [info] SQLInclude: Config specifies [EMAIL 
> PROTECTED]:Port = [EMAIL PROTECTED]:3306
> [Tue Jan 13 14:48:47 2004] [info] SQLInclude: Connection to '192.168.0.200' 
> established...
> [Tue Jan 13 14:48:47 2004] [info] SQLInclude: SQL query successed: 801 rows 
> fetched
> [Tue Jan 13 14:48:47 2004] [info] SQLInclude: Done.
> [Tue Jan 13 14:48:47 2004] [info] mod_unique_id: using ip addr 127.0.0.1
> [Tue Jan 13 14:48:48 2004] [notice] Apache/1.3.29 (Debian GNU/Linux) 
> mod_accounting/0.5 PHP/4.3.3 configured -- resuming normal operations
> [Tue Jan 13 14:48:48 2004] [info] Server built: Dec 17 2003 15:54:05
> [Tue Jan 13 14:48:48 2004] [notice] Accept mutex: sysvsem (Default: sysvsem)
> [Tue Jan 13 14:51:40 2004] [info] removed PID file /var/run/apache.pid 
> (pid=6942)
> [Tue Jan 13 14:51:40 2004] [notice] caught SIGTERM, shutting down
>

After we talked on irc and we fixed the .info problems, did you manage to
find the other problem for the multiple loadmodules and the "Order"
missing?

Fabio

PS sorry but it took me more than 2 hours to come back home

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#227589: apache: segmentation fault on start (not Perl's fault)

[Fabio Massimo Di Nitto]

Hi Tom,
are you using php4? please try to disable php4-imap extension in
case (it is a very well known problem). Otherwise please send me the
output of strace apache -X -F.

Thanks
Fabio

On Tue, 13 Jan 2004, Tom Goulet wrote:

> Package: apache
> Version: 1.3.29.0.1-3
> Severity: normal
>
>
> Apache crashes on start.
>
> Here is the command I ran:
> | strace -f apache -F
> Here is the last bit of output:
> | stat64("/etc/cram-md5.pwd", 0xb9dc) = -1 ENOENT (No such file or 
> directory)
> | stat64("/dev/urandom", {st_mode=S_IFCHR|0444, st_rdev=makedev(1, 9), ...}) 
> = 0
> | --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> | +++ killed by SIGSEGV +++
>
> Apache is not using Perl.
> | [EMAIL PROTECTED]:/etc/apache# grep -ir loadmodule . | grep -i perl
> | grep: warning: ./conf: recursive directory loop
> |
> | [EMAIL PROTECTED]:/etc/apache#
>
> Meanwhile my SSL-capable Apache seems to be doing fine.
>
> Apache shouldn't crash.
>
> I have no guesses as to what's wrong, except that I suspect that this
> was caused by a recent upgrade.
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux geek 2.4.23-1-k6 #1 Sun Nov 30 23:02:57 EST 2003 i586
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages apache depends on:
> ii  apache-common   1.3.29.0.1-3 Support files for all Apache 
> webse
> ii  debconf 1.3.22   Debian configuration management 
> sy
> ii  dpkg1.10.18  Package maintenance system for 
> Deb
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-10Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  libmagic1   4.06-2   File type determination library 
> us
> ii  libpam0g0.76-14.1Pluggable Authentication Modules 
> l
> ii  logrotate   3.6.5-2  Log rotation utility
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
> ii  perl [perl5]5.8.2-2  Larry Wall's Practical Extraction
>
> -- debconf information:
> * apache/server-name: geek.em.ca
> * apache/document-root: /var/www
> * apache/server-port: 80
> * apache/enable-suexec: true
> * apache/init: true
> * apache/server-admin: [EMAIL PROTECTED]
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#227589: apache: segmentation fault on start (not Perl's fault)

[Fabio Massimo Di Nitto]

reassign 227589 php4-imap
severity 227589 important
stop
quit

Hi Tom,
thanks.. i am reassigning the bug.


Fabio


On Tue, 13 Jan 2004, Tom Goulet wrote:

> On Wed, Jan 14, 2004 at 06:19:10AM +0100, Fabio Massimo Di Nitto wrote:
>
> > are you using php4? please try to disable php4-imap extension in
> > case (it is a very well known problem).
>
> I disabled the PHP module and Apache starts, so I'll assume it's the PHP
> IMAP thing.
>
> Thank you.
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#225015: apache: fails to upgrade

[Fabio Massimo Di Nitto]

Hi Martin,
are you using php4? in case please try to remove the php4-imap
extension and try again (it is a well known problem in php4). Otherwise
please send me the output of:

strace apache -X -F

Thanks
Fabio

PS keep the bug in CC. I am not the only maintainer that take care of
apache.

On Tue, 13 Jan 2004, Martin Hans wrote:

> Hi Fabio,
>
> first, the "/var/www" part of my bug report was very badly phrased, sorry.
> I only wanted to say, that my problem is not the same like the #224454 issue,
> although the dselect error message is the same. And yes I have a /var/www.
>
> I attached the dselect log. I hope it helps.
> I get no log messages in /var/log/apache/* or some other logs in /var/log.
>
> Cheers
>
> Martin
>
> On Monday 12 January 2004 21:28, you wrote:
> > Hi Martin,
> >
> > On Tue, 23 Dec 2003, Martin Hans wrote:
> > > Package: apache
> > > Version: 1.3.29.0.1-3
> > > Severity: important
> > > Tags: sid
> > >
> > > The apache package fails to upgrade:
> > >
> > > Setting up apache (1.3.29.0.1-3) ...
> > > Starting web server: apache failed
> > > invoke-rc.d: initscript apache, action "start" failed.
> >
> > Can you please check the logs for errors and see what is causing the
> > failure?
> >
> > > dpkg: error processing apache (--configure):
> > >  subprocess post-installation script returned error exit status 1
> > >
> > > Afterwards the apache package is broken, but the apache itself
> > > is running.
> > > I got no "/var/www" like #224454 and my /var/www is just a directory.
> >
> > I don't understand... do you have a /var/www or not?? /var/www is only
> > created on installation.. it is not touched across upgrades.
> >
> > Fabio
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#225015: apache: fails to upgrade

[Fabio Massimo Di Nitto]

Hi,
I think this is another problem compared to the one Martin is
talking about. Please open a bug towards php4 directly.

Thanks
Fabio

On Tue, 13 Jan 2004, P PRABHU wrote:

> Dear Fabio
>
> Iam getting the error when starting apache configured
> with PhP.
>
> t-servernew:/home/sysadm# /etc/init.d/apache start
> Starting web server: apache.
> Syntax error on line 240 of /etc/apache/httpd.conf:
> Cannot load /usr/lib/apache/1.3/libphp4.so into
> server: libpcre.so.2: cannot open shared object file:
> No such file or directory
> /usr/sbin/apachectl start: httpd could not be started
>
>
> Iam also attaching my apache configuration file.
>
>
> Regards
> P.Prabhu
>
> --- Fabio Massimo Di Nitto <[EMAIL PROTECTED]>
> wrote:
> >
> >
> > Hi Martin,
> > are you using php4? in case please try to remove
> > the php4-imap
> > extension and try again (it is a well known problem
> > in php4). Otherwise
> > please send me the output of:
> >
> > strace apache -X -F
> >
> > Thanks
> > Fabio
> >
> > PS keep the bug in CC. I am not the only maintainer
> > that take care of
> > apache.
> >
> > On Tue, 13 Jan 2004, Martin Hans wrote:
> >
> > > Hi Fabio,
> > >
> > > first, the "/var/www" part of my bug report was
> > very badly phrased, sorry.
> > > I only wanted to say, that my problem is not the
> > same like the #224454 issue,
> > > although the dselect error message is the same.
> > And yes I have a /var/www.
> > >
> > > I attached the dselect log. I hope it helps.
> > > I get no log messages in /var/log/apache/* or some
> > other logs in /var/log.
> > >
> > > Cheers
> > >
> > > Martin
> > >
> > > On Monday 12 January 2004 21:28, you wrote:
> > > > Hi Martin,
> > > >
> > > > On Tue, 23 Dec 2003, Martin Hans wrote:
> > > > > Package: apache
> > > > > Version: 1.3.29.0.1-3
> > > > > Severity: important
> > > > > Tags: sid
> > > > >
> > > > > The apache package fails to upgrade:
> > > > >
> > > > > Setting up apache (1.3.29.0.1-3) ...
> > > > > Starting web server: apache failed
> > > > > invoke-rc.d: initscript apache, action "start"
> > failed.
> > > >
> > > > Can you please check the logs for errors and see
> > what is causing the
> > > > failure?
> > > >
> > > > > dpkg: error processing apache (--configure):
> > > > >  subprocess post-installation script returned
> > error exit status 1
> > > > >
> > > > > Afterwards the apache package is broken, but
> > the apache itself
> > > > > is running.
> > > > > I got no "/var/www" like #224454 and my
> > /var/www is just a directory.
> > > >
> > > > I don't understand... do you have a /var/www or
> > not?? /var/www is only
> > > > created on installation.. it is not touched
> > across upgrades.
> > > >
> > > > Fabio
> > >
> >
> > --
> > Our mission: make IPv6 the default IP protocol
> > "We are on a mission from God" - Elwood Blues
> >
> >
> http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html
> >
> >
> > --
> > To UNSUBSCRIBE, email to
> > [EMAIL PROTECTED]
> > with a subject of "unsubscribe". Trouble? Contact
> > [EMAIL PROTECTED]
> >
>
> __
> Do you Yahoo!?
> Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
> http://hotjobs.sweepstakes.yahoo.com/signingbonus

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#225015: apache: fails to upgrade

[Fabio Massimo Di Nitto]

reassign 225015 php4
stop
quit

Hi Martin,
thanks i am reassigning the bug to php.

Fabio

On Wed, 14 Jan 2004, Martin Hans wrote:

> Hi Fabio,
>
> with your php4 hint I found the solution -
> if I remove the "php4-pgsql" package
> the apache upgrade succeeds without any problems.
>
> Cheers
>
> Martin
>
> On Wednesday 14 January 2004 06:36, Fabio Massimo Di Nitto wrote:
> > Hi Martin,
> > are you using php4? in case please try to remove the php4-imap
> > extension and try again (it is a well known problem in php4). Otherwise
> > please send me the output of:
> >
> > strace apache -X -F
> >
> > Thanks
> > Fabio
> >
> > PS keep the bug in CC. I am not the only maintainer that take care of
> > apache.
> >
> > On Tue, 13 Jan 2004, Martin Hans wrote:
> > > Hi Fabio,
> > >
> > > first, the "/var/www" part of my bug report was very badly phrased,
> > > sorry. I only wanted to say, that my problem is not the same like the
> > > #224454 issue, although the dselect error message is the same. And yes I
> > > have a /var/www.
> > >
> > > I attached the dselect log. I hope it helps.
> > > I get no log messages in /var/log/apache/* or some other logs in
> > > /var/log.
> > >
> > > Cheers
> > >
> > > Martin
> > >
> > > On Monday 12 January 2004 21:28, you wrote:
> > > > Hi Martin,
> > > >
> > > > On Tue, 23 Dec 2003, Martin Hans wrote:
> > > > > Package: apache
> > > > > Version: 1.3.29.0.1-3
> > > > > Severity: important
> > > > > Tags: sid
> > > > >
> > > > > The apache package fails to upgrade:
> > > > >
> > > > > Setting up apache (1.3.29.0.1-3) ...
> > > > > Starting web server: apache failed
> > > > > invoke-rc.d: initscript apache, action "start" failed.
> > > >
> > > > Can you please check the logs for errors and see what is causing the
> > > > failure?
> > > >
> > > > > dpkg: error processing apache (--configure):
> > > > >  subprocess post-installation script returned error exit status 1
> > > > >
> > > > > Afterwards the apache package is broken, but the apache itself
> > > > > is running.
> > > > > I got no "/var/www" like #224454 and my /var/www is just a directory.
> > > >
> > > > I don't understand... do you have a /var/www or not?? /var/www is only
> > > > created on installation.. it is not touched across upgrades.
> > > >
> > > > Fabio
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#227997: mod_usertrack causes segfault

[Fabio Massimo Di Nitto]

severity 227997 important
tags 227997 moreinfo
tags 227997 unreproducible
stop
quit

Hi Carl,
mod_usertrack is working fine. Please provide us with your
configurations and possibly strace apache -F -X to see where it actually
segfaults.

Thanks
Fabio

On Thu, 15 Jan 2004, Carl Johnstone wrote:

> Package: apache-common
> Version: 1.3.29.0.1-3
> Severity: grave
>
> Enabling mod_usertrack causes apache to Segfault.
>
> Carl
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Re: apache configure probs...

[Fabio Massimo Di Nitto]

Please check README.modules in the apache-dev package.

Fabio

On Fri, 16 Jan 2004, Greg Folkert wrote:

> The error told me to send the error here. I am subscribed...
>
> -begin
> knight:/etc/apache# dpkg --configure apache
> Setting up apache (1.3.29.0.1-3) ...
> Error: 220mod_auth_curdir.info does not have a valid LoadModule entry.
> Error: 240mod_auth_dbm_curdir.info does not have a valid LoadModule
> entry.
> Error: 250mod_auth_db_curdir.info does not have a valid LoadModule
> entry.
> Error: the above error list does not permit a safe use of
> modules-config.
> Please refer to the documentation on how to fix it or report it to
> Debian Apache Maling List  if in doubt
> on how to proceed
> dpkg: error processing apache (--configure):
>  subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
>  apache
> -end
>
> Here are the relevant lines from httpd.conf
>
> 
> #LoadModule auth_module /usr/lib/apache/1.3/mod_auth_curdir.so
> 
> #LoadModule dbm_auth_module /usr/lib/apache/1.3/mod_auth_dbm_curdir.so
> 
> #LoadModule db_auth_module /usr/lib/apache/1.3/mod_auth_db_curdir.so
> 
>
> Even when uncommented... it still produces the error
>
> I also look @ the 220mod_auth_curdir.info file and it had:
>
> LoadModule: db_auth_module /usr/lib/apache/modules/mod_auth_curdir.so
> LoadModule: db_auth_module /usr/lib/apache/1.3/mod_auth_curdir.so
>
> Similar occurred in the 240mod_auth_dbm_curdir.info and
> 250mod_auth_db_curdir.info
>
> I removed the incorrect lines... All is well. (the /u/l/a/modules/blah
> line)
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#228033: apache does not start

[Fabio Massimo Di Nitto]

severity 228033 normal
stop
quit

On Fri, 16 Jan 2004, Darius Zitkevicius wrote:

> after "apt-get install apache" using sarge mixed width unstable:

and how am i supposed to reproduce this? Please upgrade also php4 and all
the libapache-modules. apache runs fine on sid so I am sure that the
problem is in something that is not upgraded.

> I have this problem on serveral machines.
> "apt-get -t unstable install apache" gives the same result.
>
> so apache won't run on testing and on unstable.

it works perfectly fine on unstable.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Re: where has apache1.3 gone?

[Fabio Massimo Di Nitto]

It is still there... I have no idea why you cannot find it.

Fabio

On Sun, 18 Jan 2004, Chris wrote:

> Am I missing something? I recently did an upgrade but it seems I am no
> longer able to use apache1.3... In dselect the apache package is no
> longer there, although apache-common and apache-utils are still
> available. I have noticed that apache2-common and apache2-mpm-* are
> available, do I have to use apache2 now??
>
> My httpd.conf files still exist, so which packages do I still need if I
> now have to install apache2?
>
> This is my sources.list:
> deb ftp://ftp.uk.debian.org/debian/ testing main contrib
> deb-src ftp://ftp.uk.debian.org/debian/ testing main contrib
>
> deb http://non-us.debian.org/debian-non-US testing/non-US main contrib
> deb-src http://non-us.debian.org/debian-non-US testing/non-US main contrib
>
> deb http://security.debian.org/ stable/updates main
>
> Thanks.
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#228077: apache-dev: apxs doesn't work well with modules-config

[Fabio Massimo Di Nitto]

On Fri, 16 Jan 2004, Carl Johnstone wrote:

> Package: apache-dev
> Version: 1.3.29.0.1-3
> Severity: minor
>
> when installing 3rd party modules using apxs:
>
>   * no .info file is created in /usr/lib/apache breaking module-config

For this please read the documentation. It is not possible to create .info
files automatically otherwise there would be no need for them.

>   * a configuration line is added directly to the apache config, rather
> than using modules-config to enable the module

This is true and should be fixed.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#228309: apache 1.3.29 upgrade unables to load PHP pages

[Fabio Massimo Di Nitto]

reassign 228309 php4
stop
quit
thanks

As you can read from the group the problem is in php4. apache preserves
LoadModules across upgrades.

Fabio


On Sat, 17 Jan 2004, Rudy Godoy wrote:

> Package: apache
> Version: 1.3.29.0.1-3
> Severity: important
> Tags: sid
>
>
> After an apache update to 1.3.29.0.1-3 suddely PHP pages are not intepreted.
> I had to purge and reinstall both apache and php4* to have them finally 
> working.It seems other people had the same experience [0] i was diging into 
> config
> files to workaround this but i had no luck, my previous version was 1.3.26
> Seems that the new modules config structure of apache is messing PHP4 for
> some reason.
>
> 0- 
> http://groups.google.com.pe/groups?hl=es&lr=&ie=UTF-8&oe=UTF-8&threadm=btbghv%2456cpj%241%40ID-205474.news.uni-berlin.de&rnum=3&prev=/groups%3Fq%3Dphp%2B4.3%2Bapache%2B1.3.29%2Bdebian%26hl%3Des%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26selm%3Dbtbghv%252456cpj%25241%2540ID-205474.news.uni-berlin.de%26rnum%3D3
>
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux jane 2.4.22-1-686 #6 Sat Oct 4 14:09:08 EST 2003 i686
> Locale: LANG=en_US, LC_CTYPE=en_US (ignored: LC_ALL set to en_US)
>
> Versions of packages apache depends on:
> ii  apache-common   1.3.29.0.1-3 Support files for all Apache 
> webse
> ii  debconf 1.3.20   Debian configuration management 
> sy
> ii  dpkg1.10.18  Package maintenance system for 
> Deb
> ii  libc6   2.3.2.ds1-8  GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-10Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  libmagic1   4.06-1   File type determination library 
> us
> ii  libpam0g0.76-14  Pluggable Authentication Modules 
> l
> ii  logrotate   3.6.5-2  Log rotation utility
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
> ii  perl [perl5]5.8.2-2  Larry Wall's Practical Extraction
>
> -- debconf information:
> * apache/enable-suexec: false
>   apache/server-name: localhost
>   apache/document-root: /var/www/default
>   apache/server-port: 80
>   apache/init: true
>   apache/server-admin: [EMAIL PROTECTED]
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#228435: apache: does not start with the imap module

[Fabio Massimo Di Nitto]

reassign 228435 horde2
stop
quit

Hi franck,
I doubt this is in apache problem at all. apache does not know
anything about imap. I think this is a bug in horde that does not depend
on php4-imap (that is broken!).

Thanks
Fabio

On Mon, 19 Jan 2004, Franck Touboul wrote:

> Package: apache
> Version: 1.3.29.0.1-3
> Severity: normal
>
>
> Hi,
> this bug look like the php one (Bug #228033)
> I can't use the imap module (for horde) :
> "Auth_imap: Required IMAP functions were not found."
>
> I'm working with a Debian/Testing but this is the same with another
> computer on a Debian/Unstable.
>
> Thanks,
>
> Franck
>
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux rodriguez 2.4.20 #1 SMP mer jui 9 01:21:35 CEST 2003 i686
> Locale: LANG=fr_FR, LC_CTYPE=fr_FR (ignored: LC_ALL set to fr_FR)
>
> Versions of packages apache depends on:
> ii  apache-common   1.3.29.0.1-3 Support files for all Apache 
> webse
> ii  debconf 1.3.22   Debian configuration management 
> sy
> ii  dpkg1.10.18  Package maintenance system for 
> Deb
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-10Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  libmagic1   4.06-2   File type determination library 
> us
> ii  libpam0g0.76-14.1Pluggable Authentication Modules 
> l
> ii  logrotate   3.6.5-2  Log rotation utility
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
> ii  perl [perl5]5.8.2-2  Larry Wall's Practical Extraction
>
> -- debconf information excluded
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#228077: apache-dev: apxs doesn't work well with modules-config

[Fabio Massimo Di Nitto]

On Sun, 18 Jan 2004, Pawel Wiecek wrote:

> On Jan 18,  8:17pm, Fabio Massimo Di Nitto wrote:
> > >   * no .info file is created in /usr/lib/apache breaking module-config
> > For this please read the documentation. It is not possible to create .info
> > files automatically otherwise there would be no need for them.
>
> Actually isn't most (though not all) of information required to create a
> very basic .info file available on build time?
>
> .info file with LoadModule: line, empty description and default priority
> could easily by created as a part of module skeleton.

The skeleton is not an issue. The problem is fetching the information
about the module name inside the code and how the module will be called
after linking. Not all the modules become mod_foo.so, some of them ends up
in libfoo.so and so on.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#228451: apache-dev: could you upgrade to libdb4.2-dev dependency , 4.1 conflict with gnome-dev

[Fabio Massimo Di Nitto]

Hi Alban,
this is already in the TODO list, but it still needs testing and
coordination with apache2 and so on..

Fabio

On Mon, 19 Jan 2004, Alban Browaeys wrote:

> Package: apache-dev
> Severity: wishlist
>
> I need apache-dev to compile mod_mono
> (and gnome-dev too to use gtk#)
> I admit its still a small audience.
>
> Cheers
> Alban
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux argos 2.6.1 #2 Sun Jan 11 04:19:23 CET 2004 i686
> Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#228033: apache does not start

[Fabio Massimo Di Nitto]

Can you be a bit more specific? apache needs a valid hostname to work:

http://httpd.apache.org/docs/mod/core.html#servername

special note: "however this may not work reliably, or may not return the
preferred hostname."

Thanks
Fabio

On Sun, 18 Jan 2004, Darius [windows-1257] ?itkevicius wrote:

> Problem is hostname. If I have not legal hostname (for example my name) apache
> fails to start.
>
> Now I don't know is this a bug or feature.
>
> If I don't have real hostname only working solution is 'localhost'. But on
> woody I was able to specify any hostname that I like.
>
> Sorrt if this bug is invalid.
>
> Darius
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#227997: mod_usertrack causes segfault

[Fabio Massimo Di Nitto]

severity 227997 minor
tags 227997 - unreproducible
tags 227997 - moreinfo

Hi Carl,
the problem seems to be:

CookieTracking on

that cause the segfaults. Checking the documentation:

http://httpd.apache.org/docs/mod/mod_usertrack.html#cookietracking

it seems to me that this option can be used only when mod_usertrack is
statically compiled into apache (and in our case it is not since we make
use of DSO).

I am also dowgrading the bug since the apache still serves the pages
correctly and it does not die completly (only the child is killed but
respawned immediatly). Theoretically this is not even a bug since it is
documented but I want to discuss with the other apache maintainers before
closing it since there might be the option to compile in mod_usertrack.

Fabio

On Fri, 16 Jan 2004, Carl Johnstone wrote:

>
> Two separate apache installs both exhibit the same problem - one of
> which is a fairly clean re-install I did recently for testing purposes.
> I assumed it would be easy to reproduce :-)
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux gmgrd031pc 2.6.0-test11 #1 Mon Dec 22 17:25:10 GMT 2003 i586
> Locale: LANG=C, LC_CTYPE=C
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#224783: Bug#224782: DO NOT CLOSE THIS BUG

[Fabio Massimo Di Nitto]

retitle 224783 apache, -ssl, -perl will not build with shell other than 
/bin/bash
stop
quit

On Mon, 22 Dec 2003, Adam Majer wrote:

> This bug is NOT for the Apache maintainers - it is for Apache
> users that might want to rebuild Apache from source in
> woody (eg, to add a module like mod_security).

Ok i will just clean the things a bit since also apache-perl is affected
and 3 bugs for the same thing are useless.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#227997: mod_usertrack causes segfault

[Fabio Massimo Di Nitto]

tags 227997 - pending
stop
quit

I didn't apply anything to the debian tree therefor this bug is not
pending.


On Mon, 19 Jan 2004, Carl Johnstone wrote:

> Fabio:
> > I am also dowgrading the bug since the apache still serves the pages
> > correctly and it does not die completly (only the child is killed but
> > respawned immediatly).
>
> The child dies, but no content is returned on that child request. If you
> have the module turned on for all pages (as I have) then your http
> server effectively becomes useless.

It does return pages to me. I would have wrote that otherwise.

>
> For users whose setup depends on this module (as mine does) then the
> severity of the bug is effectively grave.
> I realise that there are a lot
> of users who don't use the module and are therefore not affected by the
> bug, the documentation for the BTS suggests to me that important is the
> correct severity for this type of bug.

>rant> As a user point of view every single bug in this world is grave.
No.. i do not agree but i will leave as is now since i am tired to play
ping-pong with the BTS. A single optional command for a module is only a
very small part of the entire apache package. it does not corrupt fs or it
doesn't introduce any security hole so grave is unacceptable. important is
still questionable. anyway  let's keep this stuff out of the BTS
since they are irrelevant to the bug.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#227232: apache: Overwrites own modules.conf on upgrade

[Fabio Massimo Di Nitto]

On Mon, 12 Jan 2004, Jeroen van Wolffelaar wrote:

> Package: apache
> Version: 1.3.29.0.1-3
> Severity: critical
> Justification: causes serious data loss
>
> (I consider by home-made configuration also data - webserver will not
> run without; and without backups I wouldn't have been able to recover
> per module the reasons why I enabled/disabled that module)

Yes that's correct. This problem was spotted in another bug that got
lost/forgotten/closed (for what i can recall at least).

> Amongst others, config files were already split up. For example, I had
> moved all LoadModules line to a file called /etc/apache/modules.conf
>
> After upgrade to this version, the postinst failed, because apache
> failed to start because some modules I enabled via modules.conf were
> missing.

If they were all debian modules it is kinda strange otherwise yes..

> I'm now going to clean up the mess and restore config from backup, and I
> will check out the postinst afterwards, if I find more problems, or a
> patch for this, I will add to this report and/or open another one.

No need to. I know where the problem is (unfortunatly).

> Above this, why modules-config? You cannot add comments next to the
> loadmodule line like this?!

sorry but i don't understand what you mean.

>
> apache2's approach of a mods-available, and mods-enabled containing
> symlinks to the former, MUCH cleaner, and easier, and more
> straightforward, and non-causing-data-loss! And, it's more consitent
> within Debian

The switch to modules-config and modules.conf is part of the transition.
There are several steps that needs to be done and cannot be done in one
shot.

the first one was to get rid of the old apacheconfig that was pretty much
broken, replacing it with modules-config forcing all the apache modules to
clean up the way they were configured. Providing a standard (and only one)
way to enable/disable modules. Once this is completed we can change
modules-config and the underlaying structure without the other modules
even noticing it. the advantage is that at that point we can make a clean
transition without having to upload 200 packages together with 200
different implementations to achieve the same task. For the disadvantegs
just check the BTS ;)

We can agree that the name modules.conf was not the best choise but (and i
accept my responsabilities for it) we endup in a urgent and broken upload
because of perl breaking the abi (at that time).

> --Jeroen
> (apologies for my insecure wordings, my mood is currently a bit... you
> can guess)

well you are still running a testing/unstable system. things can break for
mistakes... tho noone want it.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#228077: apache-dev: apxs doesn't work well with modules-config

[Fabio Massimo Di Nitto]

On Mon, 19 Jan 2004, Pawel Wiecek wrote:

> On Jan 19,  6:03am, Fabio Massimo Di Nitto wrote:
> > The skeleton is not an issue. The problem is fetching the information
> > about the module name inside the code and how the module will be called
>
> This still can be fetched from sources on module build time.
>
> In any case -- most of .info file could be generated on module build
> time, but not on module install time. I think the submitter wanted the
> latter.

Can you provide a patch for apxs to do so? I squashing other bugs...

Thanks
Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#228537: apache-common: listconffiles doesn't handle " characters very well

[Fabio Massimo Di Nitto]

Uh thanks for spotting this error! it is the same problem of another bug.

Fabio

On Mon, 19 Jan 2004, Allard Hoeve wrote:

> Package: apache-common
> Version: 1.3.29.0.1-3
> Severity: normal
> Tags: sid patch
>
> Hello All,
>
> While upgrading to apache 1.3.29.0.1-3 from 1.3.27 I ran into a bug in
> listconffiles. It seems it breaks when Include directives are written like so:
>
> Include "/etc/apache/local.conf"
>
> The Include gets detected as "/etc/apache/local.conf", not
> /etc/apache/local.conf, without the quotes. The same applies to ServerRoot
> directives.
>
> The result is listconffiles trying to open:
>
> "/etc/apache/"/"/etc/apache/local.conf"
>
> The following patch fixes the problem:
>
> __
> --- /usr/share/apache/listconffiles.old 2004-01-19 16:56:22.0 +0100
> +++ /usr/share/apache/listconffiles 2004-01-19 16:58:23.0 +0100
> @@ -52,6 +52,7 @@
>s/^\s*(.*)/$1/;
>(undef,$serverroot) = split;
>($serverroot .= "/") unless ($serverroot =~ m|/$|);
> +   $serverroot =~ s/"//g;
>  #  print "DEBUG: Found ServerRoot to be $serverroot\n";
>  }
>
> @@ -59,6 +60,8 @@
>s/^\s*(.*)/$1/;
>my (undef,$file) = split;
>
> +  $file =~ s/"//g;
> +
>if ($file !~ m|^/| ) {
> $file = $serverroot . $file;
>}
> --
>
> Simple, but effective. This now works on my system.
>
> Regards,
>
> Allard Hoeve
>
>
>
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: sparc
> Kernel: Linux baco 2.4.21 #4 Fri Aug 1 13:36:07 CEST 2003 sparc64
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages apache-common depends on:
> ii  apache-utils1.3.29.0.1-3 Utility programs for webservers
> ii  debconf 1.3.22   Debian configuration management 
> sy
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-16Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
> ii  perl [perl5]5.8.2-2  Larry Wall's Practical Extraction
> ii  sed 4.0.7-3.0.1  The GNU sed stream editor
>
> -- debconf information:
> * apache-common/confignotes:
>   apache-common/old-logrotate-exists:
>   apache-common/logs:
>   apache-shared/debconf-modules: mod_userdir, mod_status, mod_ssl, 
> mod_setenvif, mod_rewrite, mod_negotiation, mod_mime_magic, mod_mime, 
> mod_log_config, mod_env, mod_dir, mod_cgi, mod_autoindex, mod_auth, 
> mod_alias, mod_actions, mod_access, mod_php4
>   apache-shared/restart: false
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#228667: apache: fails to start after fresh install

[Fabio Massimo Di Nitto]

tags 228667 - experimental
stop
quit

Hi Russel,

On Mon, 19 Jan 2004, Russell Hires wrote:


>   The error message is:
>  Starting web server: apacheProcessing config directory:
>  /etc/apache/conf.d
>   failed
>   invoke-rc.d: initscript apache, action "start" failed.
>   dpkg: error processing apache (--configure):
>subprocess post-installation script returned error exit status 1
>Errors were encountered while processing:
> apache
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>

did you install only apache or also php4?

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#227357: /usr/lib/apache/1.3/mod_log_config.so undefined symbol: ap_popenf_ex (from log rotate?); but it obviously can...

[Fabio Massimo Di Nitto]

Hi Anthony,
apparently there was another case like this one but we are still
working on how to reproduce the problem.

Thanks
Fabio

On Mon, 12 Jan 2004, Anthony DeRobertis wrote:

> Package: apache
> Version: 1.3.29.0.1-3
> Severity: important
>
> This is a testing server which I only use every once and a while. I
> upgraded to the lastest version of apache yesterday, and that worked.
>
> This morning, I find my apache is not running. Looking in the error log,
> I see:
>
> [Mon Jan 12 02:38:13 2004] [error] [client 192.168.65.1] File does not exist: 
> /var/www/ITBC/include/menucode.php
> [Mon Jan 12 06:26:38 2004] [notice] SIGUSR1 received.  Doing graceful restart
> Syntax error on line 8 of /etc/apache/modules.conf:
> Cannot load /usr/lib/apache/1.3/mod_log_config.so into server: 
> /usr/lib/apache/1.3/mod_log_config.so: undefined symbol: ap_popenf_ex
>
> 02:38:13 was the last I touched the machine. I was asleep from around
> then until ~11:00:00 this morning. I think that must of come from
> logrotate rotating the logs. The postrotate there looks like this:
>
>postrotate
>if [ -f /var/run/apache.pid ]; then \
> /etc/init.d/apache reload > /dev/null; fi
>endscript
>
> (shouldn't that use invoke-rc.d, btw?)
>
> I just started apache again, and the config is fine:
> Processing config directory: /etc/apache/conf.d
> [Mon Jan 12 16:08:53 2004] [warn] pid file /var/run/apache.pid overwritten -- 
> Unclean shutdown of previous Apache run?
> [Mon Jan 12 16:08:54 2004] [notice] Apache/1.3.29 (Debian GNU/Linux) 
> PHP/4.3.3 configured -- resuming normal operations
> [Mon Jan 12 16:08:54 2004] [notice] Accept mutex: sysvsem (Default: sysvsem)
>
> I have not modified any apache config since installing the package
> (i.e., a while before either time stamp)
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux bohr 2.4.22-bohr #1 SMP Fri Dec 5 08:58:30 EST 2003 i686
> Locale: LANG=en_US, LC_CTYPE=en_US
>
> Versions of packages apache depends on:
> ii  apache-common   1.3.29.0.1-3 Support files for all Apache 
> webse
> ii  debconf 1.3.22   Debian configuration management 
> sy
> ii  dpkg1.10.18  Package maintenance system for 
> Deb
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-10Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  libmagic1   4.06-2   File type determination library 
> us
> ii  libpam0g0.76-14.1Pluggable Authentication Modules 
> l
> ii  logrotate   3.6.5-2  Log rotation utility
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
> ii  perl [perl5]5.8.2-2  Larry Wall's Practical Extraction
>
> -- debconf information:
> * apache/enable-suexec: false
> * apache/server-name: bohr.local
> * apache/document-root: /var/www
> * apache/server-port: 80
> * apache/init: true
> * apache/server-admin: [EMAIL PROTECTED]
>
>
>
>  Output from gpg 
> gpg: Signature made Mon Jan 12 22:23:44 2004 CET using DSA key ID 55EA59FE
> gpg: Good signature from "Anthony DeRobertis <[EMAIL PROTECTED]>"
> gpg: aka "Anthony DeRobertis <[EMAIL PROTECTED]>"
> gpg: aka "Anthony DeRobertis <[EMAIL PROTECTED]>"
> gpg: aka "Anthony DeRobertis <[EMAIL PROTECTED]>"
> gpg: aka "Anthony DeRobertis <[EMAIL PROTECTED]>"
> gpg: aka "Anthony DeRobertis (Work) <[EMAIL PROTECTED]>"
> gpg: aka "Anthony DeRobertis (Work) <[EMAIL PROTECTED]>"
> gpg: aka "Anthony DeRobertis (Pager) <[EMAIL PROTECTED]>"
> gpg: aka "Anthony DeRobertis (AnimeMusicVideos.org) <[EMAIL 
> PROTECTED]>"
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the owner.
> Primary key fingerprint: E501 CEE3 E030 2D48 D449  274C FB3F 88C2 55EA 59FE
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Re: Apache 1.3.29.0.1-3 Installation failed

[Fabio Massimo Di Nitto]

Sorry but did you upgrade only apache? or the entire machine?? in the
first case backport is not possible, in the second case be sure you
updated php4 as well.

Fabio

On Tue, 20 Jan 2004, B. Liu wrote:

> I updated apache from stable to unstable 1.3.29.0.1-3, and failed to
> install ths unstable version. The error message is:
>
> Setting up apache (1.3.29.0.1-3) ...
> Error: libphp4.so does not have a corresponding .info file.
> Error: the above error list does not permit a safe use of modules-config.
> Please refer to the documentation on how to fix it or report it to
> Debian Apache Maling List  if in doubt
> on how to proceed
> dpkg: error processing apache (--configure):
>  subprocess post-installation script returned error exit status 1
> Setting up libapache-mod-perl (1.29.0.1-3) ...
> Error: libphp4.so does not have a corresponding .info file.
> Error: the above error list does not permit a safe use of modules-config.
> Please refer to the documentation on how to fix it or report it to
> Debian Apache Maling List  if in doubt
> on how to proceed
> dpkg: error processing libapache-mod-perl (--configure):
>  subprocess post-installation script returned error exit status 1
> dpkg: dependency problems prevent configuration of apache-perl:
>  apache-perl depends on libapache-mod-perl (>= 1.29.0.1-3); however:
>   Package libapache-mod-perl is not configured yet.
>  apache-perl depends on libapache-mod-perl (<< 1.30); however:
>   Package libapache-mod-perl is not configured yet.
> dpkg: error processing apache-perl (--configure):
>  dependency problems - leaving unconfigured
> Errors were encountered while processing:
>  apache
>  libapache-mod-perl
>  apache-perl
>
> regards
>
> Bin
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Re: Apache 1.3.29.0.1-3 Installation failed

[Fabio Massimo Di Nitto]

Can you check /var/log/apache/error.log and apachectl configtest?

Thanks
Fabio

On Tue, 20 Jan 2004, B. Liu wrote:

>
> Hi, Thank you for quick response. I updated the entire machine, I have
> php43 installed at /usr/local/. But following your suggestion, I installed
> the php4 debian package as well, this time the error message is different.
> Here it is:
>
> Reading Package Lists... Done
> Building Dependency Tree... Done
> The following extra packages will be installed:
>   libmm13
> Suggested packages:
>   php4-pear
> The following NEW packages will be installed:
>   libmm13 php4
> 0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
> 3 not fully installed or removed.
> Need to get 794kB of archives.
> After unpacking 1831kB of additional disk space will be used.
> Do you want to continue? [Y/n] y
> Get:1 http://ftp.uk.debian.org testing/main libmm13 1.3.0-1 [15.4kB]
> Get:2 http://ftp.uk.debian.org testing/main php4 4:4.3.3-4 [778kB]
> Fetched 794kB in 9s (84.6kB/s)
> Preconfiguring packages ...
> Selecting previously deselected package libmm13.
> (Reading database ... 63872 files and directories currently installed.)
> Unpacking libmm13 (from .../libmm13_1.3.0-1_i386.deb) ...
> Selecting previously deselected package php4.
> Unpacking php4 (from .../php4_4%3a4.3.3-4_i386.deb) ...
> Setting up apache (1.3.29.0.1-3) ...
> Starting web server: apache failed
> invoke-rc.d: initscript apache, action "start" failed.
> dpkg: error processing apache (--configure):
>  subprocess post-installation script returned error exit status 1
> Setting up libapache-mod-perl (1.29.0.1-3) ...
>
> Setting up apache-perl (1.3.29.0.1-3) ...
> Starting web server: apache-perlProcessing config directory:
> /etc/apache-perl/conf.d
> .
>
> Setting up libmm13 (1.3.0-1) ...
>
> Setting up php4 (4.3.3-4) ...
>
> Errors were encountered while processing:
>  apache
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> Any suggestions?
>
> Bin
>
> On Tue, 20 Jan 2004, Fabio Massimo Di Nitto wrote:
>
> >
> > Sorry but did you upgrade only apache? or the entire machine?? in the
> > first case backport is not possible, in the second case be sure you
> > updated php4 as well.
> >
> > Fabio
> >
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Re: Apache 1.3.29.0.1-3 Installation failed

[Fabio Massimo Di Nitto]

Probably you have an instance of apache that is still running or something
in your system is using port 5656. Check with netstat or similar.

Fabio

On Tue, 20 Jan 2004, B. Liu wrote:

>
> The error.log file shows as following,
> [Tue Jan 20 06:26:26 2004] [notice] Apache/1.3.29 (Debian GNU/Linux)
> PHP/4.3.2 configured -- resuming normal operations
> [Tue Jan 20 06:26:26 2004] [notice] Accept mutex: sysvsem (Default:
> sysvsem)
> [Tue Jan 20 10:53:08 2004] [crit] (98)Address already in use: make_sock:
> could not bind to port 5656
>
> apachectl configtest runs:
>
> Processing config directory: /etc/apache/conf.d
> Syntax OK
>
> Bin
>
> On Tue, 20 Jan 2004, Fabio Massimo Di Nitto wrote:
>
> >
> > Can you check /var/log/apache/error.log and apachectl configtest?
> >
> > Thanks
> > Fabio
> >
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#228791: apache: modules-config name and/or location too general

[Fabio Massimo Di Nitto]

severity 228791 wishlist
tags 228781 wontfix
stop
quit

Hi Jeroen,

On Tue, 20 Jan 2004, Jeroen van Wolffelaar wrote:

> Since shortishly, apache uses /usr/sbin/modules-config for providing an
> interface to update the available and loaded modules in apache.
>
> First, the name seems a bit general to me: it has not the word 'apache'
> in it, and it is in no way at first sight clear that this is an
> apache-specific script (except when you look at source and manpage of
> course...).

The reason why there is no "apache" word in it is that we ship 3 flavours
of apache. After a big cleanup of name clashing around the 3 flavours
(apache, apache-ssl and apache-perl) if we have to ship an
apache-modules-whatvername than people would expect also the other 3 and
that won't be the case. Plus expandig modules-config in the future to
support for instance apache2 or other webservers is relatively simple.

>
> Second, I might be wrong about this, but I do not believe that there is
> an imminent reason to have this script in /usr/sbin. I think this script
> belongs better in /usr/share/apache-common/(bin/)modules-config or
> something like that. If done this way, the general name is not a problem
> anymore, since it isn't in global program namespace anymore.

No becuase modules-config is a tool that can be used anytime by the
administrator. /usr/sbin is the proper localtion.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#228667: apache: fails to start after fresh install

[Fabio Massimo Di Nitto]

Hi Russel,
please keep the bug in CC. Can you send me your modules.conf?

Thanks
Fabio

On Tue, 20 Jan 2004, Russell Hires wrote:

> Only apache. How does php4 work w/ apache?
>
> Russell
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#227232: apache: Overwrites own modules.conf on upgrade

[Fabio Massimo Di Nitto]

On Tue, 20 Jan 2004, Jeroen van Wolffelaar wrote:

> > > I'm now going to clean up the mess and restore config from backup, and I
> > > will check out the postinst afterwards, if I find more problems, or a
> > > patch for this, I will add to this report and/or open another one.
> >
> > No need to. I know where the problem is (unfortunatly).
>
> Ok, that's half of the reason I didn't yet do so (other reason: RL)
>
> I noticed the problem, IMHO is in the cp -f modules.conf
> modules.conf.old without any checking wether old exists, so only keeping
> one backup (and on postinst rerun original modules.conf is lost).

Yes i have this in mind as well. I am evaluating the possibility to
perform a full backup of the configs each time since now we have the tool
to do so.

> > > Above this, why modules-config? You cannot add comments next to the
> > > loadmodule line like this?!
> >
> > sorry but i don't understand what you mean.
>
> Without modules-config, you can maintain a configuration fragment with
> the LoadModule lines, and have comments above them, as a kind of
> reminder for yourself: what is it, what's it relevance to my own system,
> and why did I disable/enable this module.
>
> With modules-config, that is AFAICS impossible.

that's correct because it is generated automatically. Maintaing comments
inside isn't impossible just a lot more work for modules-config. I
consider this as a wishlist but i will see if i can find the time to fix
it after this bug that is more important.

> Okay, I agree & understand here :), thanks for the explaination.
>
> So I understand you will in the future mimic apache2's way of handling
> apache-modules? I believe that would greatly improve Debian's
> consistency.

Yes that's correct. As you might have noticed we already started
introducing conf.d as a testbed and several packages are using it. Next
steps will be to introduce the modules structure.

> ... indeed, I don't blame anyone, my goal is to provide an as useful as
> possible bugreport to assist apache-maintainers fixing it in order to
> prevent this bug slip into sarge :)
>
> Sorry if I was unclear about this, and thanks for all the good work.

Thanks to you!
Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Re: Processed: tagging the right bug

[Fabio Massimo Di Nitto]

Ops.. sorry.. thanks for fixing it.

Fabio

On Wed, 21 Jan 2004, Debian Bug Tracking System wrote:

> Processing commands for [EMAIL PROTECTED]:
>
> > tags 228791 wontfix
> Bug#228791: apache: modules-config name and/or location too general
> There were no tags set.
> Tags added: wontfix
>
> > tags 228781 - wontfix
> Bug#228781: unmet dependecies
> Tags were: wontfix
> Tags removed: wontfix
>
> > stop
> Stopping processing here.
>
> Please contact me if you need assistance.
>
> Debian bug tracking system administrator
> (administrator, Debian Bugs database)
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#228667: apache: fails to start after fresh install

[Fabio Massimo Di Nitto]

Hi Russel,
as suggested in another message on this bug please disable
mod_uniqe_id and see if apache starts. mod_unique_id requires a valid
hostname that can be resolvable.
Check the documentation at:
http://httpd.apache.org/docs/mod/mod_unique_id.html

Thanks
Fabio

On Wed, 21 Jan 2004, Russell Hires wrote:

> # Autogenerated file - do not edit!
> # This file is maintained by the apache package.
> # To update it, run the command:
> #/usr/sbin/modules-config apache
> ClearModuleList
> AddModule mod_so.c
> AddModule mod_macro.c
> LoadModule config_log_module /usr/lib/apache/1.3/mod_log_config.so
> LoadModule mime_magic_module /usr/lib/apache/1.3/mod_mime_magic.so
> LoadModule mime_module /usr/lib/apache/1.3/mod_mime.so
> LoadModule negotiation_module /usr/lib/apache/1.3/mod_negotiation.so
> LoadModule status_module /usr/lib/apache/1.3/mod_status.so
> LoadModule autoindex_module /usr/lib/apache/1.3/mod_autoindex.so
> LoadModule dir_module /usr/lib/apache/1.3/mod_dir.so
> LoadModule cgi_module /usr/lib/apache/1.3/mod_cgi.so
> LoadModule userdir_module /usr/lib/apache/1.3/mod_userdir.so
> LoadModule alias_module /usr/lib/apache/1.3/mod_alias.so
> LoadModule rewrite_module /usr/lib/apache/1.3/mod_rewrite.so
> LoadModule access_module /usr/lib/apache/1.3/mod_access.so
> LoadModule auth_module /usr/lib/apache/1.3/mod_auth.so
> LoadModule expires_module /usr/lib/apache/1.3/mod_expires.so
> LoadModule unique_id_module /usr/lib/apache/1.3/mod_unique_id.so
> LoadModule setenvif_module /usr/lib/apache/1.3/mod_setenvif.so
>
> On Wednesday 21 January 2004 01:29 am, Fabio Massimo Di Nitto wrote:
> > Hi Russel,
> > please keep the bug in CC. Can you send me your modules.conf?
> >
> > Thanks
> > Fabio
> >
> > On Tue, 20 Jan 2004, Russell Hires wrote:
> > > Only apache. How does php4 work w/ apache?
> > >
> > > Russell
>
> --
> Linux -- the OS for the Renaissance Man
>  Output from gpg 
> gpg: Signature made Wed Jan 21 13:28:37 2004 CET using DSA key ID F56C8494
> gpg: Good signature from "Russell Hires <[EMAIL PROTECTED]>"
> gpg: please do a --check-trustdb
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the owner.
> Primary key fingerprint: 26B8 98D5 1391 D9FA F4EA  43A7 02A2 86AE F56C 8494
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#227357: /usr/lib/apache/1.3/mod_log_config.so undefined symbol: ap_popenf_ex (from log rotate?); but it obviously can...

[Fabio Massimo Di Nitto]

tags 227357 pending
stop
quit

Ok found the problem and fixed for the next upload. You should never seen
this message again (also from now). According to my tests it happens only
when upgrading from woody (1.3.26) and testing (1.3.27) where one of the
mantainer scripts was broken.

The problem is that during the upgrade process usually apache is stopped,
upgraded and started again. The script in woody is broken and therefor
does NOT stop apache during the upgrade. so basically you were still
running 1.3.26 (or 1.3.27 from testing).
Doing a graceful restart, as it happens during logrotate, would spit out
that error. a stop and start of course fix the problem forever since all
apache is reloaded.

Of course now i perform the check to ensure that apache is stopped before
upgrading.

Thanks
Fabio

On Tue, 20 Jan 2004, Anthony DeRobertis wrote:

>
> On Jan 20, 2004, at 02:56, Fabio Massimo Di Nitto wrote:
>
> >
> > Hi Anthony,
> > apparently there was another case like this one but we are still
> > working on how to reproduce the problem.
>
> Wish I could help more, but so far, it hasn't recurred for me. Glad to
> hear I'm not just crazy, though.
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#228946: apache: apache 1.3.29.0.1-3 conflicts with libapache-mod-perl 1.27, causing coredumps

[Fabio Massimo Di Nitto]

tags 228946 + pending
stop
quit

Hi,
for some reason this bit was lost around apache 1.3.27. the fix is
ready to be uploaded.

Thanks
Fabio

On Wed, 21 Jan 2004 [EMAIL PROTECTED] wrote:

> Package: apache
> Version: 1.3.29.0.1-3
> Severity: normal
>
> I upgraded apache to 1.3.29.0.1-3 yesterday; no conflict was noted with
> the given version of libapache-mod-perl. After upgrading apache, however, it
> (and apache-ssl) both coredumped when run; backtrace below:
>
> #0  0x403f0fe2 in boot_Apache__Table () from /usr/lib/apache/1.3/mod_perl.so
> #1  0x403f1927 in boot_DynaLoader () from /usr/lib/apache/1.3/mod_perl.so
> #2  0x4048b739 in Perl_pp_entersub () from /usr/lib/libperl.so.5.8
> #3  0x40483fa9 in Perl_runops_standard () from /usr/lib/libperl.so.5.8
> #4  0x4041f319 in Perl_call_sv () from /usr/lib/libperl.so.5.8
> #5  0x4041f53b in Perl_eval_sv () from /usr/lib/libperl.so.5.8
> #6  0x403ba70a in perl_require_module () from /usr/lib/apache/1.3/mod_perl.so
> #7  0x403accf8 in perl_module_init () from /usr/lib/apache/1.3/mod_perl.so
> #8  0x404b3932 in Perl_leave_scope () from /usr/lib/libperl.so.5.8
> #9  0x404b180c in Perl_pop_scope () from /usr/lib/libperl.so.5.8
> #10 0x4041d939 in perl_parse () from /usr/lib/libperl.so.5.8
> #11 0x4041d2e2 in perl_parse () from /usr/lib/libperl.so.5.8
> #12 0x403ad2ea in perl_startup () from /usr/lib/apache/1.3/mod_perl.so
> #13 0x403b2afe in perl_cmd_handler_handlers () from 
> /usr/lib/apache/1.3/mod_perl.so
> #14 0x0805588d in ap_clear_module_list ()
> #15 0x080c1644 in ?? ()
> #16 0x080c1714 in ?? ()
> #17 0x0806a351 in ap_getword_conf ()
> #18 0x005f in ?? ()
>
> I'm not suggesting the two should be made to run together, but maybe some
> indication of a conflict should be given...?
>
> -- System Information
> Debian Release: testing/unstable
> Kernel Version: Linux nova 2.4.23 #6 Sun Dec 7 00:45:49 GMT 2003 i686 
> GNU/Linux
>
> Versions of the packages apache depends on:
> ii  apache-common  1.3.29.0.1-3   Support files for all Apache webservers
> ii  debconf1.4.7  Debian configuration management system
> ii  dpkg   1.10.18Package maintenance system for Debian
> ii  libc6  2.3.2.ds1-10   GNU C Library: Shared libraries and Timezone
> ii  libdb4.1   4.1.25-4   Berkeley v4.1 Database Libraries [runtime]
> ii  libexpat1  1.95.6-4   XML parsing C library - runtime library
> ii  libmagic1  4.02-4 File type determination library using "magic
> ii  libpam0g   0.76-9 Pluggable Authentication Modules library
> ii  logrotate  3.5.9-1Log rotation utility
> ii  mime-support   3.23-1 MIME files 'mime.types' & 'mailcap', and sup
> ii  perl   5.8.2-2Larry Wall's Practical Extraction and Report
> ii  perl   5.8.2-2Larry Wall's Practical Extraction and Report
>   ^^^ (Provides virtual package perl5)
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Re: Re: conf.d usage

[Fabio Massimo Di Nitto]

Hi Frederic,

On Thu, 22 Jan 2004, Frederic Schutz wrote:

> Michael Loftis wrote:
>
>  > Putting a file in a conf.d is equivalent to writing those directives
>  > in the httpd.conf file. There are no restrictions.
>
> A follow-up question, as a package maintainer: if my package wants to
> install a snippet of config (or a symlink) into conf.d and the file
> already exists (eg created by the user), what should the package do ?

You have to preserve the user file or symlink or directory.

> Or is there a naming scheme I could follow (eg name-of-package.conf),
> and assume that a user will not manually create such files ?

I would suggest pkgname.conf but you still have to check if it has been
created by you, modified by the user and so on before touching it.
You still have the option to prompt the user for a proper action to take
in case.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#229099: apache fails starting (no libapache-mod-perl installed)

[Fabio Massimo Di Nitto]

reassign 229099 php4
stop
quit
thanks

Hi Giuseppe,
you are using the php4-imap extension that is known to be broken
since long time and it causes apache to segafult. Reassigning the bug to
php4.

On Fri, 23 Jan 2004, Giuseppe Sacco wrote:

> I did an strace of apache an found that it segfaults just after opening
> /dev/urandom. When it hangs, there is a huge file in /tmp (more the 60Mb)
> created by apache (maybe this is normal.)

I am not sure about the 60MB file. afaik it's part of the shared memory
but i have never noticed one so big.

> I attach to this message an archive with tmp/log beign the output of
> strace -o /tmp/log -f -s256 apache -F

thanks. This one clearly shows the php4-imap installation problem.

Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#229099: Apache fails starting, php4-imap is one cause.

[Fabio Massimo Di Nitto]

Hi Andy,
yes that's correct. it is a very well known problem in php4. The
bug has been reassigned.

On Fri, 23 Jan 2004, Andy Baillie wrote:

> I have essentially the same problem occuring at the same time 22.01.2004.
>
> apache versions
> ii  apache 1.3.29.0.1-3   Versatile, high-performance HTTP server
> ii  apache-common  1.3.29.0.1-3   Support files for all Apache webservers
> ii  apache-doc 1.3.29.0.1-3   Apache webserver docs
> ii  apache-ssl 1.3.29.0.1-3   Versatile, high-performance HTTP server with
> ii  apache-utils   1.3.29.0.1-3   Utility programs for webservers
>
> In my case the gdb output looks like
>
> stargate:/etc/apache# gdb /usr/sbin/apache
> GNU gdb 5.3-debian
> Copyright 2002 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i386-linux"...(no debugging symbols found)...
> (gdb) set args -X
> (gdb) run
> Starting program: /usr/sbin/apache -X
> (no debugging symbols found)...(no debugging symbols found)...[New Thread
> 16384 (LWP 9779)]
>
> (no debugging symbols found)...(no debugging symbols found)...
>--- snipped repeated lines ---
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 16384 (LWP 9779)]
> 0x40212700 in strcmp () from /lib/libc.so.6
> (gdb) bt
> #0  0x40212700 in strcmp () from /lib/libc.so.6
>
> An strace resulted in
>
> getpid()= 9751
> gettimeofday({1074828666, 541580}, NULL) = 0
> getpid()= 9751
> getpid()= 9751
> open("/etc/krb5.keytab", O_RDONLY)  = -1 ENOENT (No such file or 
> directory)
> stat64("/dev/urandom", {st_mode=S_IFCHR|0444, st_rdev=makedev(1, 9), ...}) = 0
> --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> +++ killed by SIGSEGV +++
>
> much the same as before
>
> A web scan showed that php can be problematic and I have a second machine on
> which the same version of apache is installed and it works without problems.
> Comparing the two shows I have php-imap as an active extension on the
> failing setup. Commenting this out from /etc/php/apache/php.ini allowed my
> apache server to start normally.
>
> PHP packages installed
> ii  php4   4.3.3-4A server-side, HTML-embedded scripting langu
> ii  php4-cgi   4.3.3-4A server-side, HTML-embedded scripting langu
> ii  php4-imap  4.3.3-4IMAP module for php4
> ii  php4-mysql 4.3.3-4MySQL module for php4
> ii  php4-pear  4.3.3-4PEAR - PHP Extension and Application Reposit
>
> For me the segfault clearly happens while I have php4-imap installed and
> active. If you don't have php-imap on your machine then its an equivalent
> failure but if you do have php installed it may be worth checking each
> extension in turn.
>
> Regards
> Andy
>
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#225015: apache: fails to upgrade

[Fabio Massimo Di Nitto]

tags 225015 pending
merge 225015 227357
stop
quit
thanks

On Fri, 23 Jan 2004, Steve Langasek wrote:

> reassign 225015 apache
> thanks
>
> After discussing with Fabio, I am reassigning this bug back to apache,
> as it appears to be a known bug in the apache prerm script from woody.
>
> Cheers,
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#229027: apache-common: Notes changed config file format on fresh install

[Fabio Massimo Di Nitto]

tags 229027 pending
stop
quit
thanks

Hi Mark,
thanks for noticing it. it is now fixed in CVS and it will be
included in -4.

Fabio

On Thu, 22 Jan 2004, Mark Brown wrote:

> Package: apache-common
> Version: 1.3.29.0.1-3
> Severity: minor
>
> A fresh install of apache-common causes the apache-common/confignotes
> template to be displayed.  Given that this is documenting a change in
> the configuration scheme it would seem sensible to only display this
> note while upgrading from a version that had the old scheme.
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux loki 2.4.22-1-686 #6 Sat Oct 4 14:09:08 EST 2003 i686
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages apache-common depends on:
> ii  apache-utils1.3.29.0.1-3 Utility programs for webservers
> ii  debconf 1.3.22   Debian configuration management 
> sy
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-16Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  mime-support3.23-1   MIME files 'mime.types' & 
> 'mailcap
> ii  perl [perl5]5.8.2-2  Larry Wall's Practical Extraction
> ii  sed 4.0.7-3  The GNU sed stream editor
>
> -- debconf information excluded
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#229553: debconf note spam

[Fabio Massimo Di Nitto]

severity 229553 minor
tags 229553 + pending
merge 229553 229027
stop
quit

Fabio

On Sat, 24 Jan 2004, Matt Zimmerman wrote:

> Package: apache-common
> Version: 1.3.29.0.1-3
> Severity: normal
>
> This package displays a priority 'high' debconf note
> (apache-common/confignotes) on every installation, containing information
> which is irrelevant except when upgrading from certain older versions.
> This message should only be displayed in situations where it actually
> applies.
>
> -- System Information:
> Debian Release: unstable
> Architecture: i386
> Kernel: Linux mizar 2.4.24-deb1-skas3-1 #1 Thu Jan 8 11:19:59 PST 2004 i686
> Locale: LANG=en_US, LC_CTYPE=en_US
>
> Versions of packages apache-common depends on:
> ii  apache-utils1.3.29.0.1-3 Utility programs for webservers
> ii  debconf 1.4.7Debian configuration management 
> sy
> ii  libc6   2.3.2.ds1-11 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-16Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  mime-support3.24-1   MIME files 'mime.types' & 
> 'mailcap
> ii  perl [perl5]5.8.2-2  Larry Wall's Practical Extraction
> ii  sed 4.0.7-3  The GNU sed stream editor
>
> -- debconf information excluded
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#229505: apache-ssl: post-installation script fails

[Fabio Massimo Di Nitto]

Hi,
are you running testing? is this a fresh installation or an
upgrade?

Please provide me more information asap.

Fabio

On Sun, 18 Jan 2004, Michael Kebe wrote:

> Package: apache-ssl
> Version: 1.3.29.0.1-3
> Severity: normal
>
> After apt-get install apache-ssl I get:
> > Setting up apache-ssl (1.3.29.0.1-3) ...
> > Starting web server: apache-sslProcessing config directory:
> > /etc/apache-ssl/conf.d
> >  failed
> > invoke-rc.d: initscript apache-ssl, action "start" failed.
> > dpkg: error processing apache-ssl (--configure):
> >  subprocess post-installation script returned error exit status 1
> > Errors were encountered while processing:
> >  apache-ssl
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux missmuh 2.4.20 #8 Tue Jun 3 23:51:20 CEST 2003 i686
> Locale: LANG=C, [EMAIL PROTECTED]
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Bug#219973: apache dies only if php4 module loaded

[Fabio Massimo Di Nitto]

I don't understand why you are following up on this bug. In any case it is
a well known php4 problem (see BTS) and please do not mix bugs.

Thanks
Fabio

On Sun, 25 Jan 2004, Marko Mrdjenovic wrote:

> Package: apache
> Version: 1.3.29.0.1-3
> Severity: normal
> Followup-For: Bug #219973
>
> After some testing I figured that apache dies only when php4 module is
> loaded (php version: 4:4.3.3-4). At first it worked fine but then it just 
> started
> crashing, don't know why. Yet.
>
> -- System Information:
> Debian Release: 3.x
> Architecture: i386
> Kernel: Linux blue 2.4.21-3-586tsc #1 Sun Jul 20 15:03:47 EST 2003 i586
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages apache depends on:
> ii  apache-common   1.3.29.0.1-3 Support files for all Apache 
> webse
> ii  debconf 1.3.22   Debian configuration management 
> sy
> ii  dpkg1.10.18  Package maintenance system for 
> Deb
> ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries 
> an
> ii  libdb4.14.1.25-16Berkeley v4.1 Database Libraries 
> [
> ii  libexpat1   1.95.6-6 XML parsing C library - runtime 
> li
> ii  libmagic1   4.06-2   File type determination library 
> us
> ii  libpam0g0.76-15  Pluggable Authentication Modules 
> l
> ii  logrotate   3.6.5-2  Log rotation utility
> ii  mime-support3.24-1   MIME files 'mime.types' & 
> 'mailcap
> ii  perl [perl5]5.8.2-2  Larry Wall's Practical Extraction
>
> -- debconf information excluded
>
>
>
>

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html

Re: Policy regarding apache modules

[Fabio Massimo Di Nitto]

On Sun, 25 Jan 2004, Sebastian Ley wrote:

> Hi,
>
> I am packaging OpenGroupware.org [1] which comes with an apache module
> that enables the webserver to handle the HTTP requests for the
> application server.
>
> 1) Is there a policy regarding naming, location in the filesystem etc.
> for apache modules?

Yes, please read carefully README.modules shipped with apache-dev.

> 2) The module needs some entries in httpd.conf. How do I handles this
> best? I could output a note which tells the user to update his
> httpd.conf but I would prefer something more automatic.

you can use /etc/apache/conf.d without mangling httpd.conf

Regards
Fabio

-- 
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues

http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html