Bug#228791: apache: modules-config name and/or location too general
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
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#228840: apache2-prefork-dev has identity crisis
Package: apache2-prefork-dev
Version: 2.0.48-4
Severity: normal
lucifer:~/build/php4/4.3.5/php-4.3.5RC1/ /usr/bin/apxs2 -q MPM_NAME
worker
lucifer:~/build/php4/4.3.5/php-4.3.5RC1/ dpkg -S /usr/bin/apxs2
apache2-prefork-dev: /usr/bin/apxs2
'nuff said. This is breaking PHP builds, forcing thread-safety when
we don't need it.
... Adam
-- System Information:
Debian Release: testing/unstable
Architecture: powerpc
Kernel: Linux lucifer 2.4.24 #1 Mon Jan 19 06:46:33 MST 2004 ppc
Locale: LANG=C, LC_CTYPE=C
Versions of packages apache2-prefork-dev depends on:
ii apache2-common2.0.48-4 Next generation, scalable, extenda
ii autoconf 2.59-1 automatic configure script builder
ii autotools-dev 20040105.1 Update infrastructure for config.{
ii bzip2 1.0.2-1A high-quality block-sorting file
ii libapr0-dev 2.0.48-4 Development headers for libapr
ii libdb4.1-dev 4.1.25-16 Berkeley v4.1 Database Libraries [
ii libpcre3-dev 4.3-4 Development stuff for libpcre
ii libssl-dev0.9.7c-5 SSL development libraries, header
ii libtool 1.5-8 Generic library support script
ii openssl 0.9.7c-5 Secure Socket Layer (SSL) binary a
ii zlib1g-dev1:1.2.1-3 compression library - development
-- no debconf information
Bug#227232: apache: Overwrites own modules.conf on upgrade
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
Processed: tagging the right bug
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)
Re: Processed: tagging the right bug
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
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 # 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 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFADnB1AqKGrvVshJQRAuJVAJ9QD4uCg28SVzJVVOsjvqXidzK4MgCgo7ct jwy2djePHOUjr0SUgqdYdqc= =2ZzJ -END PGP SIGNATURE-
Processed: your mail
Processing commands for [EMAIL PROTECTED]: severity 228033 normal Bug#228033: apache does not start Severity set to `normal'. severity 228667 normal Bug#228667: apache: fails to start after fresh install Severity set to `normal'. merge 228033 228667 Bug#228033: apache does not start Bug#228667: apache: fails to start after fresh install Merged 228033 228667. tags 228033 pending Bug#228033: apache does not start There were no tags set. Bug#228667: apache: fails to start after fresh install Tags added: pending tags 228667 pending Bug#228667: apache: fails to start after fresh install Tags were: pending Bug#228033: apache does not start Tags added: pending stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: Perfect webdesign
Hello: We are proud to offer you high quality custom web design, logo and stationery design, e-commerce and custom programming. Please, check our portfolio at http://www.luxwebdev.com/portfolioweb.html What can we do for your business? - Unique custom high quality design - Unique logo design - Stationery development (letterhead, business cards, envelope designs) - Custom programming - Content managment systems - E-commerce systems with payment processings - Java development - Search engine marketing - Flash and Multmedia development - Business presentations - Hight quality 3D Video creation - Desktop programming Please write me to [EMAIL PROTECTED] only. (PLEASE USE THIS EMAIL ONLY AND DO NOT TRY TO 'REPLY' TO THE MESSAGE). Thank you for your attention! Best, Alex Moyer LuxWebDev.com [EMAIL PROTECTED] * Private, Confidential and Privileged. This email and any files and attachments transmitted with it are confidential and/or privileged. They are intended solely for the use of the intended recipient. The content of this email and any file or attachment transmitted with it may have been changed or altered without the consent of the author. If you are not the intended recipient, please note that any review, dissemination, disclosure, alteration, printing, circulation or transmission of this email and/or any file or attachment transmitted with it, is prohibited and may be unlawful. *
Bug#227357: /usr/lib/apache/1.3/mod_log_config.so undefined symbol: ap_popenf_ex (from log rotate?); but it obviously can...
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
Processed: Re: Bug#227357: /usr/lib/apache/1.3/mod_log_config.so undefined symbol: ap_popenf_ex (from log rotate?); but it obviously can...
Processing commands for [EMAIL PROTECTED]: tags 227357 pending Bug#227357: /usr/lib/apache/1.3/mod_log_config.so undefined symbol: ap_popenf_ex (from log rotate?); but it obviously can... There were no tags set. Tags added: pending stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#228946: apache: apache 1.3.29.0.1-3 conflicts with libapache-mod-perl 1.27, causing coredumps
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)
Bug#228946: apache: apache 1.3.29.0.1-3 conflicts with libapache-mod-perl 1.27, causing coredumps
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
Processed: submitter
Processing commands for [EMAIL PROTECTED]: submitter 228946 ! Bug#228946: apache: apache 1.3.29.0.1-3 conflicts with libapache-mod-perl 1.27, causing coredumps Changed Bug submitter from [EMAIL PROTECTED] to Paul Walker [EMAIL PROTECTED]. -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: Re: Bug#228946: apache: apache 1.3.29.0.1-3 conflicts with libapache-mod-perl 1.27, causing coredumps
Processing commands for [EMAIL PROTECTED]: tags 228946 + pending Bug#228946: apache: apache 1.3.29.0.1-3 conflicts with libapache-mod-perl 1.27, causing coredumps There were no tags set. Tags added: pending stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: Re: conf.d usage
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 ? 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 ? Frederic
Re: Re: conf.d usage
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
