Bug#227357: /usr/lib/apache/1.3/mod_log_config.so undefined symbol: ap_popenf_ex (from log rotate?); but it obviously can...
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
Processed: now it's pending (and tested)
Processing commands for [EMAIL PROTECTED]: tags 227997 + pending Bug#227997: mod_usertrack causes segfault Tags were: upstream Tags added: pending stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Apache 1.3.29.0.1-3 Installation failed
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 debian-apache@lists.debian.org 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 debian-apache@lists.debian.org 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
Re: Apache 1.3.29.0.1-3 Installation failed
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 debian-apache@lists.debian.org 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 debian-apache@lists.debian.org 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
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
Bug#227357: /usr/lib/apache/1.3/mod_log_config.so undefined symbol: ap_popenf_ex (from log rotate?); but it obviously can...
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.
Re: Apache 1.3.29.0.1-3 Installation failed
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
Re: Apache 1.3.29.0.1-3 Installation failed
Hi, you are right, I had apache running, problem solved. Thank you very much. Bin On Tue, 20 Jan 2004, Fabio Massimo Di Nitto wrote: 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
Bug#228667: Re[2]: Bug#228667: apache: fails to start after fresh install
Hello, I had the same error message on i386. message in /var/log/apache/error.log (and .../apache-ssl/error.log, which i also tried): [Tue Jan 20 17:45:27 2004] [alert] mod_unique_id: unable to gethostbyname(debian) gone after disabling mod_unique_id in the modules selection dialog. php is not installed. bye .. carsten debconf-settings: Getting dependency information for apache... *** The following debconf settings were detected: * apache/server-name: www.bag-shi.de //not important * apache/document-root: /var/www * apache/server-port: 80 * apache/enable-suexec: false//not important * apache/init: true * apache/server-admin: [EMAIL PROTECTED] Tuesday, January 20, 2004, 6:20:13 AM, you wrote: ... 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 -- Best regards, Carstenmailto:[EMAIL PROTECTED]
Bug#227232: apache: Overwrites own modules.conf on upgrade
On Mon, Jan 19, 2004 at 01:02:07PM +0100, Fabio Massimo Di Nitto wrote: On Mon, 12 Jan 2004, Jeroen van Wolffelaar wrote: 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). 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). 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. 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 ;) 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. My second issue with modules-config is in a different bugreport now on its way. 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). I don't fully grasp perl's abi relevance here, but in fact, I disagree modules.conf is a bad name: _if_ it is decided to have a seperate file for the modules configuration, modules.conf seems very logical (this is emphasized by the fact that I personally had choosen that very name long time ago for this purpose). Unfortunately this clash caused this very problem to happen with me, but ... well you are still running a testing/unstable system. things can break for mistakes... tho noone want it. ... 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. --Jeroen -- Jeroen van Wolffelaar +31-30-253 4499 [EMAIL PROTECTED] http://Jeroen.A-Eskwadraat.nl
