From nobody@FreeBSD.org  Sun Oct  6 09:56:53 2002
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9825837B401
	for <freebsd-gnats-submit@FreeBSD.org>; Sun,  6 Oct 2002 09:56:53 -0700 (PDT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5CB1043E81
	for <freebsd-gnats-submit@FreeBSD.org>; Sun,  6 Oct 2002 09:56:53 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.6/8.12.6) with ESMTP id g96Gur7R015274
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 6 Oct 2002 09:56:53 -0700 (PDT)
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.6/8.12.6/Submit) id g96Gur2o015273;
	Sun, 6 Oct 2002 09:56:53 -0700 (PDT)
Message-Id: <200210061656.g96Gur2o015273@www.freebsd.org>
Date: Sun, 6 Oct 2002 09:56:53 -0700 (PDT)
From: Alex <akruijff@dds.nl>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Apache2 port error
X-Send-Pr-Version: www-1.0

>Number:         43747
>Category:       misc
>Synopsis:       Apache2 port error
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Oct 06 10:00:24 PDT 2002
>Closed-Date:    Wed Oct 09 02:48:03 PDT 2002
>Last-Modified:  Wed Oct 09 02:48:03 PDT 2002
>Originator:     Alex
>Release:        4.6.2
>Organization:
>Environment:
FreeBSD Intranet.kruij557.speed.planet.nl 4.6.2-RELEASE-p2 FreeBSD 4.6.2-RELEASE-p2 #0: Wed Sep 18 13:45:18 CEST 2002     alex@Intranet.kruij557.speed.planet.nl:/disk1/obj/usr/src/sys/INTRANET  i386     
>Description:
     I updated the apache2 port with portupgrade. It was not posible to restart the webserver was afther that. Afther this i updated my sources againg and forced a install througth the port system. Same result.

Intranet# apachectl restart
httpd: module "sapi_apache2.c" is not compatible with this version of Apache (found 20020628, need 20020903).
Please contact the vendor for the correct version.
>How-To-Repeat:
     Update your sources and update a apache2 sw then try to restart the sw.
>Fix:
     
>Release-Note:
>Audit-Trail:

From: Harry Oosterman <hoosterman@cedron.com>
To: freebsd-gnats-submit@FreeBSD.org, akruijff@dds.nl
Cc:  
Subject: Re: misc/43747: Apache2 port error
Date: Mon, 07 Oct 2002 10:28:42 +0200

 After the portupgrade of apache2, I upgraded mod_php4.
 That fixed the problem. So check all modules installed
 separate from apache2.
 
 A portupgrade -r will probabely fix this problem.
 
 

From: Alex <freebsd-reply@akruijff.dds.nl>
To: Harry Oosterman <hoosterman@cedron.com>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re[2]: misc/43747: Apache2 port error
Date: Tue, 8 Oct 2002 11:37:31 +0200

 Hello/Beste Harry,
 
 Monday, October 07, 2002, 10:28:42 AM, you wrote:
 
 HO> After the portupgrade of apache2, I upgraded mod_php4.
 HO> That fixed the problem. So check all modules installed
 HO> separate from apache2.
 
 HO> A portupgrade -r will probabely fix this problem.
 
 Tanks for you help, but i still have the problem.
 I made the following two aliases which i use for updating.
 pv = portversion | grep -v '='
 pu = potupgrade -Rr
 
 Intranet# pv
 XFree86-Server              <
 XFree86-clients             <
 cups-base                   <
 pkg_tarup                   ?
 samba                       <
 
 Intranet# apachectl restart
 httpd: module "sapi_apache2.c" is not compatible with this version of Apache (found 20020628, need 20020903).
 Please contact the vendor for the correct version.
 
 
 
 -- 
 Best regards/Met vriendelijke groet,
 Alex
 

From: Peter Pentchev <roam@ringlet.net>
To: Alex <freebsd-reply@akruijff.dds.nl>
Cc: bug-followup@FreeBSD.org
Subject: Re: misc/43747: Apache2 port error
Date: Tue, 8 Oct 2002 14:23:54 +0300

 On Tue, Oct 08, 2002 at 02:40:02AM -0700, Alex wrote:
 > The following reply was made to PR misc/43747; it has been noted by GNATS.
 > 
 >  Hello/Beste Harry,
 >  
 >  Monday, October 07, 2002, 10:28:42 AM, you wrote:
 >  
 >  HO> After the portupgrade of apache2, I upgraded mod_php4.
 >  HO> That fixed the problem. So check all modules installed
 >  HO> separate from apache2.
 >  
 >  HO> A portupgrade -r will probabely fix this problem.
 >  
 >  Tanks for you help, but i still have the problem.
 >  I made the following two aliases which i use for updating.
 >  pv = portversion | grep -v '='
 >  pu = potupgrade -Rr
 >  
 >  Intranet# pv
 >  XFree86-Server              <
 >  XFree86-clients             <
 >  cups-base                   <
 >  pkg_tarup                   ?
 >  samba                       <
 >  
 >  Intranet# apachectl restart
 >  httpd: module "sapi_apache2.c" is not compatible with this version of Apache (found 20020628, need 20020903).
 >  Please contact the vendor for the correct version.
 
 I think Harry is not saying that your mod_php4 port is out-of-date with
 respect to the FreeBSD Ports Collection.  Its version has not been
 changed, so portversion would not report it as being out-of-date.
 
 What has changed, though, is the Apache 2 code itself.  The PHP module
 uses some functions and library calls from the Apache server source;
 whenever the Apache code changes, there is a chance that some of the API
 calls would change - either become invalid, or do something else, with
 bad, unintended consequences either way.  Thus, there is a version check
 at module loading time: the Apache binary queries the module, obtains
 the Apache API version for which it was built, and compares it with its
 own.
 
 Apparently, the Apache developers considered that the changes made
 between those two versions were significant enough that they may impact
 third-party modules using the Apache API.  Thus, your PHP module, built
 for the old version of Apache, is not really safe to run with the new
 one.  Remove the PHP module, rebuild it, and it will pick up the
 currently installed Apache version and work just fine.
 
 G'luck,
 Peter
 
 -- 
 Peter Pentchev	roam@ringlet.net	roam@FreeBSD.org
 PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
 Key fingerprint	FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
 When you are not looking at it, this sentence is in Spanish.

From: Alex <freebsd-reply@akruijff.dds.nl>
To: Peter Pentchev <roam@ringlet.net>
Cc: Alex <freebsd-reply@akruijff.dds.nl>, bug-followup@FreeBSD.org
Subject: Re[2]: misc/43747: Apache2 port error
Date: Tue, 8 Oct 2002 19:58:56 +0200

 Hello/Beste Peter,
 
 Tuesday, October 08, 2002, 1:23:54 PM, you wrote:
 
 PP> On Tue, Oct 08, 2002 at 02:40:02AM -0700, Alex wrote:
 >> The following reply was made to PR misc/43747; it has been noted by GNATS.
 >> 
 >>  Hello/Beste Harry,
 >>  
 >>  Monday, October 07, 2002, 10:28:42 AM, you wrote:
 >>  
 >>  HO> After the portupgrade of apache2, I upgraded mod_php4.
 >>  HO> That fixed the problem. So check all modules installed
 >>  HO> separate from apache2.
 >>  
 >>  HO> A portupgrade -r will probabely fix this problem.
 >>  
 >>  Tanks for you help, but i still have the problem.
 >>  I made the following two aliases which i use for updating.
 >>  pv = portversion | grep -v '='
 >>  pu = potupgrade -Rr
 >>  
 >>  Intranet# pv
 >>  XFree86-Server              <
 >>  XFree86-clients             <
 >>  cups-base                   <
 >>  pkg_tarup                   ?
 >>  samba                       <
 >>  
 >>  Intranet# apachectl restart
 >>  httpd: module "sapi_apache2.c" is not compatible with this version of Apache (found 20020628, need 20020903).
 >>  Please contact the vendor for the correct version.
 
 PP> I think Harry is not saying that your mod_php4 port is out-of-date with
 PP> respect to the FreeBSD Ports Collection.  Its version has not been
 PP> changed, so portversion would not report it as being out-of-date.
 
 PP> What has changed, though, is the Apache 2 code itself.  The PHP module
 PP> uses some functions and library calls from the Apache server source;
 PP> whenever the Apache code changes, there is a chance that some of the API
 PP> calls would change - either become invalid, or do something else, with
 PP> bad, unintended consequences either way.  Thus, there is a version check
 PP> at module loading time: the Apache binary queries the module, obtains
 PP> the Apache API version for which it was built, and compares it with its
 PP> own.
 
 PP> Apparently, the Apache developers considered that the changes made
 PP> between those two versions were significant enough that they may impact
 PP> third-party modules using the Apache API.  Thus, your PHP module, built
 PP> for the old version of Apache, is not really safe to run with the new
 PP> one.  Remove the PHP module, rebuild it, and it will pick up the
 PP> currently installed Apache version and work just fine.
 
 PP> G'luck,
 PP> Peter
 
 
 Tanks, that did the trick.
 
 -- 
 Best regards/Met vriendelijke groet,
 Alex
 
State-Changed-From-To: open->closed 
State-Changed-By: roam 
State-Changed-When: Wed Oct 9 02:47:15 PDT 2002 
State-Changed-Why:  
The submitter confirmed that updating the mod_php4 port did the trick. 
In fact, it would be wise, if a bit time-consuming, to always update all 
dependent ports when updating any port. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=43747 
>Unformatted:
