Received: (qmail 1620 invoked by uid 2012); 5 Nov 1998 09:40:42 -0000 Message-Id: <19981105094042.1619.qmail@hyperreal.org> Date: 5 Nov 1998 09:40:42 -0000 From: Sven Anders Reply-To: anderss@fmi.uni-passau.de To: apbugs@hyperreal.org Subject: Apache compiled but did not start (shared modules) X-Send-Pr-Version: 3.2 >Number: 3345 >Category: os-linux >Synopsis: Apache compiled but did not start (shared modules) >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Thu Nov 5 01:50:00 PST 1998 >Last-Modified: Sun Nov 8 05:20:00 PST 1998 >Originator: anderss@fmi.uni-passau.de >Organization: >Release: 1.3.3 >Environment: Linux skeeve 2.0.35 #9 Mon Oct 19 19:42:36 GMT 1998 i586 unknown pgcc-2.90.29 980515 (egcs-1.0.3 release) glibc-2.0.6 K6-2-300 >Description: I do have problems running Apache 1.3.3. It compiled fine, but when I start it the following error message occures: # apachectl start Syntax error on line 26 of /etc/httpd/httpd.conf: Cannot load /usr/packages/daemons/apache-1.3.3/modules/mod_env.so into server: / usr/packages/daemons/apache-1.3.3/modules/mod_env.so: undefined symbol: env_modu le /usr/sbin/apachectl start: httpd could not be started Hallo ! I do have problems running Apache 1.3.3. It compiled fine, but when I start it the following error message occures: # apachectl start Syntax error on line 26 of /etc/httpd/httpd.conf: Cannot load /usr/packages/daemons/apache-1.3.3/modules/mod_env.so into server: / usr/packages/daemons/apache-1.3.3/modules/mod_env.so: undefined symbol: env_modu le /usr/sbin/apachectl start: httpd could not be started >How-To-Repeat: I already tried these: 1. ./configure --prefix=/usr/packages/daemons/apache-1.3.3 --sysconfdir=/etc/httpd/ --libexecdir=/usr/packages/daemons/apache-1.3.3/modules --localstatedir=/var -- runtimedir=/var/run --logfiledir=/var/log --proxycachedir=/var/proxy --enable-mo dule=most --enable-shared=max 2. ./configure --prefix=/usr/packages/daemons/apache-1.3.3 --sysconfdir=/etc/httpd/ --libexecdir=/usr/packages/daemons/apache-1.3.3/modules --localstatedir=/var -- runtimedir=/var/run --logfiledir=/var/log --proxycachedir=/var/proxy --enable-mo dule=most --enable-shared=max --enable-rule=SHARED_CORE 3. set the LD_LIBRARY_PATH to "/usr/packages/daemons/apache-1.3.3/modules" I already tried these: 1. ./configure --prefix=/usr/packages/daemons/apache-1.3.3 --sysconfdir=/etc/httpd/ --libexecdir=/usr/packages/daemons/apache-1.3.3/modules --localstatedir=/var -- runtimedir=/var/run --logfiledir=/var/log --proxycachedir=/var/proxy --enable-mo dule=most --enable-shared=max 2. ./configure --prefix=/usr/packages/daemons/apache-1.3.3 --sysconfdir=/etc/httpd/ --libexecdir=/usr/packages/daemons/apache-1.3.3/modules --localstatedir=/var -- runtimedir=/var/run --logfiledir=/var/log --proxycachedir=/var/proxy --enable-mo dule=most --enable-shared=max --enable-rule=SHARED_CORE 3. set the LD_LIBRARY_PATH to "/usr/packages/daemons/apache-1.3.3/modules" But nothing works... >Fix: No idea ? Is it a problem with the new glibc or with the c-compiler ? >Audit-Trail: State-Changed-From-To: open-feedback State-Changed-By: lars State-Changed-When: Thu Nov 5 15:10:09 PST 1998 State-Changed-Why: I'm not able to reproduce this problem on a Linux system with glibc 2.0.7, but I tested with gcc. Please check your compiler installation. Severity-Changed-From-To: serious-non-critical Severity-Changed-By: lars Severity-Changed-When: Thu Nov 5 15:10:09 PST 1998 State-Changed-From-To: feedback-closed State-Changed-By: marc State-Changed-When: Sun Nov 8 00:06:46 PST 1998 State-Changed-Why: User reports problem solved. From: Marc Slemko To: Apache bugs database Cc: Subject: Re: os-linux/3345: Apache compiled but did not start (shared modules) (fwd) Date: Sun, 8 Nov 1998 00:02:57 -0800 (PST) ---------- Forwarded message ---------- Date: Sun, 8 Nov 1998 03:09:16 +0100 (MET) From: Sven Anders To: lars@apache.org Cc: apache-bugdb@apache.org Subject: Re: os-linux/3345: Apache compiled but did not start (shared modules) On 5 Nov 1998 lars@apache.org wrote: > Synopsis: Apache compiled but did not start (shared modules) > > State-Changed-From-To: open-feedback > State-Changed-By: lars > State-Changed-When: Thu Nov 5 15:10:09 PST 1998 > State-Changed-Why: > > I'm not able to reproduce this problem on a > Linux system with glibc 2.0.7, but I tested > with gcc. > > Please check your compiler installation. > > Severity-Changed-From-To: serious-non-critical > Severity-Changed-By: lars > Severity-Changed-When: Thu Nov 5 15:10:09 PST 1998 The gcc was ok. It was the glibc. glibc-2.0.6 did NOT work ! I updated to 2.0.7 and now all runs smoothly! :-) Thanks for all! Greetings Sven -- >>> "I am the embodiment of modern medicine." <<<<<<< Der Dativ ist dem <<<<<<< >>>>>> The holographic doctor, USS-Voyager <<<<<<<<<< Genitiv sein Tod. <<<<<<< >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< >> http://www.fmi.uni-passau.de/~anderss >< email: anderss@fmi.uni-passau.de << From: Lars Eilebrecht To: (Apache GNATS) Cc: Subject: Re: os-linux/3345: Apache compiled but did not start (shared modules) Date: Sun, 08 Nov 1998 05:39:40 +0100 (CET) --------------Forwarded message---------------------------------- From: Sven Anders To: lars@apache.org Subject: Re: os-linux/3345: Apache compiled but did not start (shared modules) [...] The gcc was ok. It was the glibc. glibc-2.0.6 did NOT work ! I updated to 2.0.7 and now all runs smoothly! :-) Thanks for all! Greetings Sven -- >>> "I am the embodiment of modern medicine." <<<<<<< Der Dativ ist dem <<<<<<< >>>>>> The holographic doctor, USS-Voyager <<<<<<<<<< Genitiv sein Tod. <<<<<<< >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< >> http://www.fmi.uni-passau.de/~anderss >< email: anderss@fmi.uni-passau.de << --------------End of forwarded message------------------------- >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]