You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Michael Felt <ma...@gmail.com> on 2012/02/26 21:30:54 UTC
Cannot start httpd v2.4.1 with mpm_build on AIX
Unfortunately, although it builds fine, it does not start:
httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
/opt/httpd/libexec/mod_mpm_worker.so into server: rtld: 0712-001 Symbol
ap_fatal_signal_setup was referenced\n from module
/opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
the symbol was not found.\nrtld: 0712-001 Symbol ap_pid_fname was
referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a
runtime definition\n of the symbol was not found.\nrtld: 0712-001
Symbol ap_reclaim_child_processes was referenced\n from module
/opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
the symbol was not found.\nrtld: 0712-001 Symbol ap_relieve_child_processes
was referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(),
but a runtime definition\n of the symbol was not found.\nrtld:
0712-001 Symbol ap_graceful_shutdown_timeout was referenced\n from
module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
definition\n of the symbol was not found.\nrtld: 0712-001 Symbol
ap_mpm_safe_kill was referenced\n from module
/opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
the symbol was not found.\nrtld: 0712-001 Symbol ap_wait_or_timeout was
referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a
runtime definition\n of the symbol was not found.\n\t0509-021
Additional errors occurred but are not reported.
I have been able to find a few of these routines in source code, e,g,
server/mpm_unix.c, but the routines are not included in
server/mpm_worker.o, hence ....
Suggestions welcome (other than filing a bug report).
Michael
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
Update:
configure argument changed to --with-mpm=prefork
and at least it loads:
+++++++++++++
michael@x054:[/etc]/opt/httpd/sbin/apachectl -t
AH00558: httpd: Could not reliably determine the server's fully qualified
domain name, using 192.168.129.54. Set the 'ServerName' directive globally
to suppress this message
Syntax OK
+++++++++++++
rebuilding with --with-mpm=worker to test that configuration...
On Sun, Feb 26, 2012 at 9:30 PM, Michael Felt <ma...@gmail.com> wrote:
> Unfortunately, although it builds fine, it does not start:
>
> httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
> /opt/httpd/libexec/mod_mpm_worker.so into server: rtld: 0712-001 Symbol
> ap_fatal_signal_setup was referenced\n from module
> /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
> the symbol was not found.\nrtld: 0712-001 Symbol ap_pid_fname was
> referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a
> runtime definition\n of the symbol was not found.\nrtld: 0712-001
> Symbol ap_reclaim_child_processes was referenced\n from module
> /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
> the symbol was not found.\nrtld: 0712-001 Symbol ap_relieve_child_processes
> was referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(),
> but a runtime definition\n of the symbol was not found.\nrtld:
> 0712-001 Symbol ap_graceful_shutdown_timeout was referenced\n from
> module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> definition\n of the symbol was not found.\nrtld: 0712-001 Symbol
> ap_mpm_safe_kill was referenced\n from module
> /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
> the symbol was not found.\nrtld: 0712-001 Symbol ap_wait_or_timeout was
> referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a
> runtime definition\n of the symbol was not found.\n\t0509-021
> Additional errors occurred but are not reported.
>
> I have been able to find a few of these routines in source code, e,g,
> server/mpm_unix.c, but the routines are not included in
> server/mpm_worker.o, hence ....
>
> Suggestions welcome (other than filing a bug report).
>
> Michael
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
michael@x054:[/data/prj/httpd-2.4.1]/opt/httpd/sbin/apachectl
-t
ksh: /opt/httpd/sbin/apachectl: not found.
michael@x054:[/data/prj/httpd-2.4.1]installp -d
/data/prj/httpd*.1/build/aix -ac ASF.httpd.rte
+-----------------------------------------------------------------------------+
Pre-installation Verification...
+-----------------------------------------------------------------------------+
Verifying selections...done
Verifying requisites...done
Results...
....
Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
ASF.httpd.rte 2.4.1.0 USR APPLY
SUCCESS
ASF.httpd.rte 2.4.1.0 ROOT APPLY
SUCCESS
michael@x054:[/data/prj/httpd-2.4.1]
michael@x054:[/data/prj/httpd-2.4.1]/opt/httpd/sbin/apachectl
-t
httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
/opt/httpd/libexec/mod_mpm_worker.so into server: rtld: 0712-001 Symbol
ap_fatal_signal_setup was referenced\n from module
/opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
the symbol was not found.\nrtld: 0712-001 Symbol ap_reclaim_child_processes
was referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(),
but a runtime definition\n of the symbol was not found.\nrtld:
0712-001 Symbol ap_relieve_child_processes was referenced\n from
module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
definition\n of the symbol was not found.\nrtld: 0712-001 Symbol
ap_mpm_safe_kill was referenced\n from module
/opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
the symbol was not found.\nrtld: 0712-001 Symbol ap_wait_or_timeout was
referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a
runtime definition\n of the symbol was not found.\nrtld: 0712-001
Symbol ap_process_child_status was referenced\n from module
/opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
the symbol was not found.\nrtld: 0712-001 Symbol
ap_unregister_extra_mpm_process was referenced\n from module
/opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
the symbol was not found.\n\t0509-021 Additional errors occurred but are
not reported.
michael@x054:[/data/prj/httpd-2.4.1]
+++++++++
My conclusion is that there is something not right in the configure
script/logic.
How can I be of assistance in tracking this down? (tomorrow and beyond)
Michael
On Sun, Feb 26, 2012 at 10:32 PM, Michael Felt <ma...@gmail.com> wrote:
> I am quite sure. Just ran a build with --with-mpm=worker and that works
> fine as well.
>
> Currently building again with:
> ./configure \
> --enable-layout=$LAYOUT \
> --with-apr=$apr_config \
> --with-apr-util=$apu_config \
> --enable-mpms-shared=all \
> --enable-mods-shared=all \
> --disable-lua > build/aix/configure.out
>
> Just to be sure the error is repeatable. :)
>
>
> On Sun, Feb 26, 2012 at 10:09 PM, Graham Leggett <mi...@sharp.fm> wrote:
>
>> On 26 Feb 2012, at 10:30 PM, Michael Felt wrote:
>>
>> > Unfortunately, although it builds fine, it does not start:
>> >
>> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
>> /opt/httpd/libexec/mod_mpm_worker.so into server: rtld: 0712-001 Symbol
>> ap_fatal_signal_setup was referenced\n from module
>> /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
>> the symbol was not found.\nrtld: 0712-001 Symbol ap_pid_fname was
>> referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a
>> runtime definition\n of the symbol was not found.\nrtld: 0712-001
>> Symbol ap_reclaim_child_processes was referenced\n from module
>> /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
>> the symbol was not found.\nrtld: 0712-001 Symbol ap_relieve_child_processes
>> was referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(),
>> but a runtime definition\n of the symbol was not found.\nrtld:
>> 0712-001 Symbol ap_graceful_shutdown_timeout was referenced\n from
>> module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n
>> of the symbol was not found.\nrtld: 0712-001 Symbol ap_mpm_safe_kill was
>> referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a
>> runtime definition\n of the symbol was not found.\nrtld: 0712-001
>> Symbol ap_wait_or_timeout was referenced\n from module
>> /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
>> the symbol was not found.\n\t0509-021 Additional errors occurred but are
>> not reported.
>> >
>> > I have been able to find a few of these routines in source code, e,g,
>> server/mpm_unix.c, but the routines are not included in
>> server/mpm_worker.o, hence ....
>>
>> Are you 100% sure your system doesn't have a mix of competing binaries?
>> In other words, just one copy of httpd, and just one copy of the httpd
>> modules?
>>
>> Also, you're trying to load just one MPM, and not all of them?
>>
>> Regards,
>> Graham
>> --
>>
>>
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
I am quite sure. Just ran a build with --with-mpm=worker and that works
fine as well.
Currently building again with:
./configure \
--enable-layout=$LAYOUT \
--with-apr=$apr_config \
--with-apr-util=$apu_config \
--enable-mpms-shared=all \
--enable-mods-shared=all \
--disable-lua > build/aix/configure.out
Just to be sure the error is repeatable. :)
On Sun, Feb 26, 2012 at 10:09 PM, Graham Leggett <mi...@sharp.fm> wrote:
> On 26 Feb 2012, at 10:30 PM, Michael Felt wrote:
>
> > Unfortunately, although it builds fine, it does not start:
> >
> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
> /opt/httpd/libexec/mod_mpm_worker.so into server: rtld: 0712-001 Symbol
> ap_fatal_signal_setup was referenced\n from module
> /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
> the symbol was not found.\nrtld: 0712-001 Symbol ap_pid_fname was
> referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a
> runtime definition\n of the symbol was not found.\nrtld: 0712-001
> Symbol ap_reclaim_child_processes was referenced\n from module
> /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
> the symbol was not found.\nrtld: 0712-001 Symbol ap_relieve_child_processes
> was referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(),
> but a runtime definition\n of the symbol was not found.\nrtld:
> 0712-001 Symbol ap_graceful_shutdown_timeout was referenced\n from
> module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n
> of the symbol was not found.\nrtld: 0712-001 Symbol ap_mpm_safe_kill was
> referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a
> runtime definition\n of the symbol was not found.\nrtld: 0712-001
> Symbol ap_wait_or_timeout was referenced\n from module
> /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
> the symbol was not found.\n\t0509-021 Additional errors occurred but are
> not reported.
> >
> > I have been able to find a few of these routines in source code, e,g,
> server/mpm_unix.c, but the routines are not included in
> server/mpm_worker.o, hence ....
>
> Are you 100% sure your system doesn't have a mix of competing binaries? In
> other words, just one copy of httpd, and just one copy of the httpd modules?
>
> Also, you're trying to load just one MPM, and not all of them?
>
> Regards,
> Graham
> --
>
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Graham Leggett <mi...@sharp.fm>.
On 26 Feb 2012, at 10:30 PM, Michael Felt wrote:
> Unfortunately, although it builds fine, it does not start:
>
> httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load /opt/httpd/libexec/mod_mpm_worker.so into server: rtld: 0712-001 Symbol ap_fatal_signal_setup was referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of the symbol was not found.\nrtld: 0712-001 Symbol ap_pid_fname was referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of the symbol was not found.\nrtld: 0712-001 Symbol ap_reclaim_child_processes was referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of the symbol was not found.\nrtld: 0712-001 Symbol ap_relieve_child_processes was referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of the symbol was not found.\nrtld: 0712-001 Symbol ap_graceful_shutdown_timeout was referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of the symbol was not found.\nrtld: 0712-001 Symbol ap_mpm_safe_kill was referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of the symbol was not found.\nrtld: 0712-001 Symbol ap_wait_or_timeout was referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of the symbol was not found.\n\t0509-021 Additional errors occurred but are not reported.
>
> I have been able to find a few of these routines in source code, e,g, server/mpm_unix.c, but the routines are not included in server/mpm_worker.o, hence ....
Are you 100% sure your system doesn't have a mix of competing binaries? In other words, just one copy of httpd, and just one copy of the httpd modules?
Also, you're trying to load just one MPM, and not all of them?
Regards,
Graham
--
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
OK, well, I'll work on getting the tools built. The RPM's are often ancient
and/or have strange dependencies I am trying to avoid.
tomorrow will do more.
On Sun, Feb 26, 2012 at 11:13 PM, Jeff Trawick <tr...@gmail.com> wrote:
> On Sun, Feb 26, 2012 at 5:09 PM, Michael Felt <ma...@gmail.com> wrote:
> > patched manually, building...
>
> ouch... maybe you have GNU patch installed as gpatch from the AIX Toolbox?
>
> anyway, in a subsequent e-mail I noticed other missing symbols...
> that's in the latest patch and, for the patch impaired, updated
> mpm_common.h, both attached
>
>
> >
> >
> > On Sun, Feb 26, 2012 at 10:56 PM, Michael Felt <ma...@gmail.com>
> wrote:
> >>
> >> er, almost working:
> >> michael@x054:[/data/prj/httpd-2.4.1]patch -p0 -i *.patch
> >> Processing... Looks like a unified context diff...
> >> The text leading up to this was:
> >> --------------------------
> >> |Index: include/mpm_common.h
> >> |===================================================================
> >> |--- include/mpm_common.h (revision 1293841)
> >> |+++ include/mpm_common.h (working copy)
> >> --------------------------
> >> Patching file include/mpm_common.h using Plan A...
> >> patch: 3016-037 Malformed patch at line 9: -void
> >> ap_reclaim_child_processes(int terminate,
> >>
> >>
> >>
> >> On Sun, Feb 26, 2012 at 10:53 PM, Michael Felt <ma...@gmail.com>
> wrote:
> >>>
> >>> :) patch from AIX 6.1 works, starting build.
> >>>
> >>>
> >>> On Sun, Feb 26, 2012 at 10:52 PM, Michael Felt <ma...@gmail.com>
> wrote:
> >>>>
> >>>> re: not exported... They are not in the .o files either (or is that
> >>>> because they are not exported?)
> >>>>
> >>>>
> >>>> On Sun, Feb 26, 2012 at 10:51 PM, Michael Felt <ma...@gmail.com>
> >>>> wrote:
> >>>>>
> >>>>> I am not so smart I fear, and still no svm installed (working on
> >>>>> building gnudiff, but not done yet...
> >>>>>
> >>>>> root@x105:[/data/prj/httpd-2.4.1]patch -i *patch
> >>>>> Processing... I cannot find a patch in there anywhere.
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Sun, Feb 26, 2012 at 10:44 PM, Jeff Trawick <tr...@gmail.com>
> >>>>> wrote:
> >>>>>>
> >>>>>> On Sun, Feb 26, 2012 at 3:30 PM, Michael Felt <ma...@gmail.com>
> >>>>>> wrote:
> >>>>>> > Unfortunately, although it builds fine, it does not start:
> >>>>>> >
> >>>>>> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot
> >>>>>> > load
> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so into server: rtld: 0712-001
> >>>>>> > Symbol
> >>>>>> > ap_fatal_signal_setup was referenced\n from module
> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >>>>>> > definition\n of
> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol ap_pid_fname was
> >>>>>> > referenced\n from module
> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a
> >>>>>> > runtime definition\n of the symbol was not found.\nrtld:
> >>>>>> > 0712-001
> >>>>>> > Symbol ap_reclaim_child_processes was referenced\n from
> module
> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >>>>>> > definition\n of
> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol
> >>>>>> > ap_relieve_child_processes
> >>>>>> > was referenced\n from module
> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(),
> >>>>>> > but a runtime definition\n of the symbol was not
> found.\nrtld:
> >>>>>> > 0712-001
> >>>>>> > Symbol ap_graceful_shutdown_timeout was referenced\n from
> >>>>>> > module
> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >>>>>> > definition\n of
> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol ap_mpm_safe_kill
> >>>>>> > was
> >>>>>> > referenced\n from module
> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a
> >>>>>> > runtime definition\n of the symbol was not found.\nrtld:
> >>>>>> > 0712-001
> >>>>>> > Symbol ap_wait_or_timeout was referenced\n from module
> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >>>>>> > definition\n of
> >>>>>> > the symbol was not found.\n\t0509-021 Additional errors occurred
> but
> >>>>>> > are not
> >>>>>> > reported.
> >>>>>> >
> >>>>>> > I have been able to find a few of these routines in source code,
> >>>>>> > e,g,
> >>>>>> > server/mpm_unix.c, but the routines are not included in
> >>>>>> > server/mpm_worker.o,
> >>>>>> > hence ....
> >>>>>> >
> >>>>>> > Suggestions welcome (other than filing a bug report).
> >>>>>>
> >>>>>> I guess the problem is that those MPM APIs are not decorated with
> >>>>>> AP_DECLARE() so they don't get added to httpd.exp so they don't get
> >>>>>> exported from httpd on AIX.
> >>>>>>
> >>>>>> Can you try the attached patch to mpm_common.h?
> >>>>>
> >>>>>
> >>>>
> >>>
> >>
> >
>
>
>
> --
> Born in Roswell... married an alien...
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Jeff Trawick <tr...@gmail.com>.
On Mon, Feb 27, 2012 at 5:14 PM, Michael Felt <ma...@gmail.com> wrote:
> Works, but...
thanks
> the prefork loadmodule line needed to be added manually
that's expected; you only get one MPM LoadModule directive...
>
> #LoadModule mpm_worker_module libexec/mod_mpm_worker.so
> LoadModule mpm_prefork_module libexec/mod_mpm_prefork.so
> LoadModule unixd_module libexec/mod_unixd.so
> #LoadModule heartbeat_module libexec/mod_heartbeat.so
> #LoadModule heartmonitor_module libexec/mod_heartmonitor.so
> #LoadModule dav_module libexec/mod_dav.so
> LoadModule status_module libexec/mod_status.so
> LoadModule autoindex_module libexec/mod_autoindex.so
>
> from the looks of it, seemsI need to remove several # to test loading all
> modules :)
>
>
>
>
> On Mon, Feb 27, 2012 at 11:05 PM, Jeff Trawick <tr...@gmail.com> wrote:
>>
>> On Mon, Feb 27, 2012 at 4:58 PM, Michael Felt <ma...@gmail.com> wrote:
>> > That fixed it!
>> > michael@x054:[/data/home/michael]/opt/httpd/sbin/apachectl
>> > -t
>> > AH00558: httpd: Could not reliably determine the server's fully
>> > qualified
>> > domain name, using 192.168.129.54. Set the 'ServerName' directive
>> > globally
>> > to suppress this message
>> > Syntax OK
>> >
>> > Further testing continues...
>>
>> Cool!
>>
>> Can you see if it prefork loads too? (Comment out the LoadModule for
>> mpm_worker_module and add a similar one for prefork and try apachectl
>> -t.) I can check the completeness of the fix from a theoretical
>> standpoint, but empirical results would be appreciated.
>>
>> >
>> >
>> > On Mon, Feb 27, 2012 at 1:18 PM, Jeff Trawick <tr...@gmail.com> wrote:
>> >>
>> >> On Mon, Feb 27, 2012 at 4:25 AM, Michael Felt <ma...@gmail.com>
>> >> wrote:
>> >> > The patch impaired me moved the file to ./include and rebuilt.
>> >> > Similiar issues:
>> >> >
>> >> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
>> >> > /opt/httpd/libexec/mod_mpm_worker.so into server:
>> >> > rtld: 0712-001 Symbol ap_fatal_signal_child_setup was referenced
>> >> >
>> >> > from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>> >> > definition
>> >> > of the symbol was not found.
>> >> > rtld: 0712-001 Symbol ap_reopen_scoreboard was referenced
>> >> >
>> >> > from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>> >> > definition
>> >> > of the symbol was not found.
>> >> > rtld: 0712-001 Symbol ap_mpm_set_graceful_shutdown was referenced
>> >> >
>> >> > from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>> >> > definition
>> >> > of the symbol was not found.
>> >>
>> >> getting much closer AFAICT
>> >>
>> >> please try with the pdated mpm_common.h and scoreboard.h attached
>> >>
>> >> >
>> >> > rtld is"runtime linker/loader", for those wondering...
>> >> >
>> >> >
>> >> > On Sun, Feb 26, 2012 at 11:13 PM, Jeff Trawick <tr...@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> On Sun, Feb 26, 2012 at 5:09 PM, Michael Felt <ma...@gmail.com>
>> >> >> wrote:
>> >> >> > patched manually, building...
>> >> >>
>> >> >> ouch... maybe you have GNU patch installed as gpatch from the AIX
>> >> >> Toolbox?
>> >> >>
>> >> >> anyway, in a subsequent e-mail I noticed other missing symbols...
>> >> >> that's in the latest patch and, for the patch impaired, updated
>> >> >> mpm_common.h, both attached
>> >> >>
>> >> >>
>> >> >> >
>> >> >> >
>> >> >> > On Sun, Feb 26, 2012 at 10:56 PM, Michael Felt <ma...@gmail.com>
>> >> >> > wrote:
>> >> >> >>
>> >> >> >> er, almost working:
>> >> >> >> michael@x054:[/data/prj/httpd-2.4.1]patch -p0 -i *.patch
>> >> >> >> Processing... Looks like a unified context diff...
>> >> >> >> The text leading up to this was:
>> >> >> >> --------------------------
>> >> >> >> |Index: include/mpm_common.h
>> >> >> >>
>> >> >> >> |===================================================================
>> >> >> >> |--- include/mpm_common.h (revision 1293841)
>> >> >> >> |+++ include/mpm_common.h (working copy)
>> >> >> >> --------------------------
>> >> >> >> Patching file include/mpm_common.h using Plan A...
>> >> >> >> patch: 3016-037 Malformed patch at line 9: -void
>> >> >> >> ap_reclaim_child_processes(int terminate,
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> On Sun, Feb 26, 2012 at 10:53 PM, Michael Felt
>> >> >> >> <ma...@gmail.com>
>> >> >> >> wrote:
>> >> >> >>>
>> >> >> >>> :) patch from AIX 6.1 works, starting build.
>> >> >> >>>
>> >> >> >>>
>> >> >> >>> On Sun, Feb 26, 2012 at 10:52 PM, Michael Felt
>> >> >> >>> <ma...@gmail.com>
>> >> >> >>> wrote:
>> >> >> >>>>
>> >> >> >>>> re: not exported... They are not in the .o files either (or is
>> >> >> >>>> that
>> >> >> >>>> because they are not exported?)
>> >> >> >>>>
>> >> >> >>>>
>> >> >> >>>> On Sun, Feb 26, 2012 at 10:51 PM, Michael Felt
>> >> >> >>>> <ma...@gmail.com>
>> >> >> >>>> wrote:
>> >> >> >>>>>
>> >> >> >>>>> I am not so smart I fear, and still no svm installed (working
>> >> >> >>>>> on
>> >> >> >>>>> building gnudiff, but not done yet...
>> >> >> >>>>>
>> >> >> >>>>> root@x105:[/data/prj/httpd-2.4.1]patch -i *patch
>> >> >> >>>>> Processing... I cannot find a patch in there anywhere.
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >>>>> On Sun, Feb 26, 2012 at 10:44 PM, Jeff Trawick
>> >> >> >>>>> <tr...@gmail.com>
>> >> >> >>>>> wrote:
>> >> >> >>>>>>
>> >> >> >>>>>> On Sun, Feb 26, 2012 at 3:30 PM, Michael Felt
>> >> >> >>>>>> <ma...@gmail.com>
>> >> >> >>>>>> wrote:
>> >> >> >>>>>> > Unfortunately, although it builds fine, it does not start:
>> >> >> >>>>>> >
>> >> >> >>>>>> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf:
>> >> >> >>>>>> > Cannot
>> >> >> >>>>>> > load
>> >> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so into server: rtld:
>> >> >> >>>>>> > 0712-001
>> >> >> >>>>>> > Symbol
>> >> >> >>>>>> > ap_fatal_signal_setup was referenced\n from module
>> >> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>> >> >> >>>>>> > definition\n of
>> >> >> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol
>> >> >> >>>>>> > ap_pid_fname
>> >> >> >>>>>> > was
>> >> >> >>>>>> > referenced\n from module
>> >> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a
>> >> >> >>>>>> > runtime definition\n of the symbol was not
>> >> >> >>>>>> > found.\nrtld:
>> >> >> >>>>>> > 0712-001
>> >> >> >>>>>> > Symbol ap_reclaim_child_processes was referenced\n
>> >> >> >>>>>> > from
>> >> >> >>>>>> > module
>> >> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>> >> >> >>>>>> > definition\n of
>> >> >> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol
>> >> >> >>>>>> > ap_relieve_child_processes
>> >> >> >>>>>> > was referenced\n from module
>> >> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(),
>> >> >> >>>>>> > but a runtime definition\n of the symbol was not
>> >> >> >>>>>> > found.\nrtld:
>> >> >> >>>>>> > 0712-001
>> >> >> >>>>>> > Symbol ap_graceful_shutdown_timeout was referenced\n
>> >> >> >>>>>> > from
>> >> >> >>>>>> > module
>> >> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>> >> >> >>>>>> > definition\n of
>> >> >> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol
>> >> >> >>>>>> > ap_mpm_safe_kill
>> >> >> >>>>>> > was
>> >> >> >>>>>> > referenced\n from module
>> >> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a
>> >> >> >>>>>> > runtime definition\n of the symbol was not
>> >> >> >>>>>> > found.\nrtld:
>> >> >> >>>>>> > 0712-001
>> >> >> >>>>>> > Symbol ap_wait_or_timeout was referenced\n from module
>> >> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>> >> >> >>>>>> > definition\n of
>> >> >> >>>>>> > the symbol was not found.\n\t0509-021 Additional errors
>> >> >> >>>>>> > occurred
>> >> >> >>>>>> > but
>> >> >> >>>>>> > are not
>> >> >> >>>>>> > reported.
>> >> >> >>>>>> >
>> >> >> >>>>>> > I have been able to find a few of these routines in source
>> >> >> >>>>>> > code,
>> >> >> >>>>>> > e,g,
>> >> >> >>>>>> > server/mpm_unix.c, but the routines are not included in
>> >> >> >>>>>> > server/mpm_worker.o,
>> >> >> >>>>>> > hence ....
>> >> >> >>>>>> >
>> >> >> >>>>>> > Suggestions welcome (other than filing a bug report).
>> >> >> >>>>>>
>> >> >> >>>>>> I guess the problem is that those MPM APIs are not decorated
>> >> >> >>>>>> with
>> >> >> >>>>>> AP_DECLARE() so they don't get added to httpd.exp so they
>> >> >> >>>>>> don't
>> >> >> >>>>>> get
>> >> >> >>>>>> exported from httpd on AIX.
>> >> >> >>>>>>
>> >> >> >>>>>> Can you try the attached patch to mpm_common.h?
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >>>>
>> >> >> >>>
>> >> >> >>
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Born in Roswell... married an alien...
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Born in Roswell... married an alien...
>> >
>> >
>>
>>
>>
>> --
>> Born in Roswell... married an alien...
>
>
--
Born in Roswell... married an alien...
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
it was easy to reset -- cp /etc/httpd/original/httpd.conf /etc/httpd
But I shall remember that for the future!
On Tue, Feb 28, 2012 at 7:37 AM, Rainer Jung <ra...@kippdata.de>wrote:
> On 27.02.2012 23:14, Michael Felt wrote:
>
>> LoadModule unixd_module libexec/mod_unixd.so
>> #LoadModule heartbeat_module libexec/mod_heartbeat.so
>> #LoadModule heartmonitor_module libexec/mod_heartmonitor.so
>> #LoadModule dav_module libexec/mod_dav.so
>> LoadModule status_module libexec/mod_status.so
>> LoadModule autoindex_module libexec/mod_autoindex.so
>>
>> from the looks of it, seemsI need to remove several # to test loading
>> all modules :)
>>
>
> For testing purposes like what you are doing right now, there is a
> configure flag
>
> --enable-load-all-modules
>
> which will activate all LoadModule lines during installation. But as
> already said by others: we think it is an improvement, that 2.4 does no
> longer activate all modules by default, so don't package wth
> "--enable-load-all-modules".
>
> Regards,
>
> Rainer
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Rainer Jung <ra...@kippdata.de>.
On 27.02.2012 23:14, Michael Felt wrote:
> LoadModule unixd_module libexec/mod_unixd.so
> #LoadModule heartbeat_module libexec/mod_heartbeat.so
> #LoadModule heartmonitor_module libexec/mod_heartmonitor.so
> #LoadModule dav_module libexec/mod_dav.so
> LoadModule status_module libexec/mod_status.so
> LoadModule autoindex_module libexec/mod_autoindex.so
>
> from the looks of it, seemsI need to remove several # to test loading
> all modules :)
For testing purposes like what you are doing right now, there is a
configure flag
--enable-load-all-modules
which will activate all LoadModule lines during installation. But as
already said by others: we think it is an improvement, that 2.4 does no
longer activate all modules by default, so don't package wth
"--enable-load-all-modules".
Regards,
Rainer
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
FYI - with all LoadModules activated (only one of prefork/worker) Syntax OK,
with both MPM active gives error, as expected (AH00534: httpd:
Configuration error: More than one MPM loaded.)
On Mon, Feb 27, 2012 at 11:26 PM, Michael Felt <ma...@gmail.com> wrote:
> so, mod_mpm_event...
>
> I have, with the patch just supplied for build/aix the following mods:
> michael@x054:[/opt/httpd/libexec]ls -l *mpm*
> -rwxr-xr-x 1 root system 53006 Feb 27 21:38
> mod_mpm_prefork.so
> -rwxr-xr-x 1 root system 86085 Feb 27 21:38 mod_mpm_worker.so
> michael@x054:[/opt/httpd/libexec]ls -l *event*
> ls: 0653-341 The file *event* does not exist.
>
> What configure option will create the mod_mpm_event part?
>
> Understood about the shipping part! minimal.
>
>
> On Mon, Feb 27, 2012 at 11:20 PM, Graham Leggett <mi...@sharp.fm> wrote:
>
>> On 28 Feb 2012, at 12:14 AM, Michael Felt wrote:
>>
>> > Works, but...
>> > the prefork loadmodule line needed to be added manually
>>
>> AFAIK mod_mpm_event is the default now.
>>
>> > #LoadModule mpm_worker_module libexec/mod_mpm_worker.so
>> > LoadModule mpm_prefork_module libexec/mod_mpm_prefork.so
>> > LoadModule unixd_module libexec/mod_unixd.so
>> > #LoadModule heartbeat_module libexec/mod_heartbeat.so
>> > #LoadModule heartmonitor_module libexec/mod_heartmonitor.so
>> > #LoadModule dav_module libexec/mod_dav.so
>> > LoadModule status_module libexec/mod_status.so
>> > LoadModule autoindex_module libexec/mod_autoindex.so
>> >
>> > from the looks of it, seemsI need to remove several # to test loading
>> all modules :)
>>
>> To test them, you'll need to remove the commented out lines yes, but
>> don't ship a default config file like that. The administrator should only
>> enable the modules they need, anything more is a waste of resources on the
>> server. In other words, definitely build the modules, but don't switch them
>> on by default.
>>
>> Regards,
>> Graham
>> --
>>
>>
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
so, mod_mpm_event...
I have, with the patch just supplied for build/aix the following mods:
michael@x054:[/opt/httpd/libexec]ls -l *mpm*
-rwxr-xr-x 1 root system 53006 Feb 27 21:38 mod_mpm_prefork.so
-rwxr-xr-x 1 root system 86085 Feb 27 21:38 mod_mpm_worker.so
michael@x054:[/opt/httpd/libexec]ls -l *event*
ls: 0653-341 The file *event* does not exist.
What configure option will create the mod_mpm_event part?
Understood about the shipping part! minimal.
On Mon, Feb 27, 2012 at 11:20 PM, Graham Leggett <mi...@sharp.fm> wrote:
> On 28 Feb 2012, at 12:14 AM, Michael Felt wrote:
>
> > Works, but...
> > the prefork loadmodule line needed to be added manually
>
> AFAIK mod_mpm_event is the default now.
>
> > #LoadModule mpm_worker_module libexec/mod_mpm_worker.so
> > LoadModule mpm_prefork_module libexec/mod_mpm_prefork.so
> > LoadModule unixd_module libexec/mod_unixd.so
> > #LoadModule heartbeat_module libexec/mod_heartbeat.so
> > #LoadModule heartmonitor_module libexec/mod_heartmonitor.so
> > #LoadModule dav_module libexec/mod_dav.so
> > LoadModule status_module libexec/mod_status.so
> > LoadModule autoindex_module libexec/mod_autoindex.so
> >
> > from the looks of it, seemsI need to remove several # to test loading
> all modules :)
>
> To test them, you'll need to remove the commented out lines yes, but don't
> ship a default config file like that. The administrator should only enable
> the modules they need, anything more is a waste of resources on the server.
> In other words, definitely build the modules, but don't switch them on by
> default.
>
> Regards,
> Graham
> --
>
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Jeff Trawick <tr...@gmail.com>.
On Mon, Feb 27, 2012 at 5:20 PM, Graham Leggett <mi...@sharp.fm> wrote:
> On 28 Feb 2012, at 12:14 AM, Michael Felt wrote:
>
>> Works, but...
>> the prefork loadmodule line needed to be added manually
>
> AFAIK mod_mpm_event is the default now.
Event requires some APR poll features not implemented on AIX... The
MPM selection logic in 2.4 will fallback to worker or even prefork if
necessary due to lack of support of necessary features.
>
>> #LoadModule mpm_worker_module libexec/mod_mpm_worker.so
>> LoadModule mpm_prefork_module libexec/mod_mpm_prefork.so
>> LoadModule unixd_module libexec/mod_unixd.so
>> #LoadModule heartbeat_module libexec/mod_heartbeat.so
>> #LoadModule heartmonitor_module libexec/mod_heartmonitor.so
>> #LoadModule dav_module libexec/mod_dav.so
>> LoadModule status_module libexec/mod_status.so
>> LoadModule autoindex_module libexec/mod_autoindex.so
>>
>> from the looks of it, seemsI need to remove several # to test loading all modules :)
>
> To test them, you'll need to remove the commented out lines yes, but don't ship a default config file like that. The administrator should only enable the modules they need, anything more is a waste of resources on the server. In other words, definitely build the modules, but don't switch them on by default.
>
> Regards,
> Graham
> --
>
--
Born in Roswell... married an alien...
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Graham Leggett <mi...@sharp.fm>.
On 28 Feb 2012, at 12:14 AM, Michael Felt wrote:
> Works, but...
> the prefork loadmodule line needed to be added manually
AFAIK mod_mpm_event is the default now.
> #LoadModule mpm_worker_module libexec/mod_mpm_worker.so
> LoadModule mpm_prefork_module libexec/mod_mpm_prefork.so
> LoadModule unixd_module libexec/mod_unixd.so
> #LoadModule heartbeat_module libexec/mod_heartbeat.so
> #LoadModule heartmonitor_module libexec/mod_heartmonitor.so
> #LoadModule dav_module libexec/mod_dav.so
> LoadModule status_module libexec/mod_status.so
> LoadModule autoindex_module libexec/mod_autoindex.so
>
> from the looks of it, seemsI need to remove several # to test loading all modules :)
To test them, you'll need to remove the commented out lines yes, but don't ship a default config file like that. The administrator should only enable the modules they need, anything more is a waste of resources on the server. In other words, definitely build the modules, but don't switch them on by default.
Regards,
Graham
--
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
Works, but...
the prefork loadmodule line needed to be added manually
#LoadModule mpm_worker_module libexec/mod_mpm_worker.so
LoadModule mpm_prefork_module libexec/mod_mpm_prefork.so
LoadModule unixd_module libexec/mod_unixd.so
#LoadModule heartbeat_module libexec/mod_heartbeat.so
#LoadModule heartmonitor_module libexec/mod_heartmonitor.so
#LoadModule dav_module libexec/mod_dav.so
LoadModule status_module libexec/mod_status.so
LoadModule autoindex_module libexec/mod_autoindex.so
from the looks of it, seemsI need to remove several # to test loading all
modules :)
On Mon, Feb 27, 2012 at 11:05 PM, Jeff Trawick <tr...@gmail.com> wrote:
> On Mon, Feb 27, 2012 at 4:58 PM, Michael Felt <ma...@gmail.com> wrote:
> > That fixed it!
> > michael@x054:[/data/home/michael]/opt/httpd/sbin/apachectl
> > -t
> > AH00558: httpd: Could not reliably determine the server's fully qualified
> > domain name, using 192.168.129.54. Set the 'ServerName' directive
> globally
> > to suppress this message
> > Syntax OK
> >
> > Further testing continues...
>
> Cool!
>
> Can you see if it prefork loads too? (Comment out the LoadModule for
> mpm_worker_module and add a similar one for prefork and try apachectl
> -t.) I can check the completeness of the fix from a theoretical
> standpoint, but empirical results would be appreciated.
>
> >
> >
> > On Mon, Feb 27, 2012 at 1:18 PM, Jeff Trawick <tr...@gmail.com> wrote:
> >>
> >> On Mon, Feb 27, 2012 at 4:25 AM, Michael Felt <ma...@gmail.com>
> wrote:
> >> > The patch impaired me moved the file to ./include and rebuilt.
> >> > Similiar issues:
> >> >
> >> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
> >> > /opt/httpd/libexec/mod_mpm_worker.so into server:
> >> > rtld: 0712-001 Symbol ap_fatal_signal_child_setup was referenced
> >> >
> >> > from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >> > definition
> >> > of the symbol was not found.
> >> > rtld: 0712-001 Symbol ap_reopen_scoreboard was referenced
> >> >
> >> > from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >> > definition
> >> > of the symbol was not found.
> >> > rtld: 0712-001 Symbol ap_mpm_set_graceful_shutdown was referenced
> >> >
> >> > from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >> > definition
> >> > of the symbol was not found.
> >>
> >> getting much closer AFAICT
> >>
> >> please try with the pdated mpm_common.h and scoreboard.h attached
> >>
> >> >
> >> > rtld is"runtime linker/loader", for those wondering...
> >> >
> >> >
> >> > On Sun, Feb 26, 2012 at 11:13 PM, Jeff Trawick <tr...@gmail.com>
> >> > wrote:
> >> >>
> >> >> On Sun, Feb 26, 2012 at 5:09 PM, Michael Felt <ma...@gmail.com>
> >> >> wrote:
> >> >> > patched manually, building...
> >> >>
> >> >> ouch... maybe you have GNU patch installed as gpatch from the AIX
> >> >> Toolbox?
> >> >>
> >> >> anyway, in a subsequent e-mail I noticed other missing symbols...
> >> >> that's in the latest patch and, for the patch impaired, updated
> >> >> mpm_common.h, both attached
> >> >>
> >> >>
> >> >> >
> >> >> >
> >> >> > On Sun, Feb 26, 2012 at 10:56 PM, Michael Felt <ma...@gmail.com>
> >> >> > wrote:
> >> >> >>
> >> >> >> er, almost working:
> >> >> >> michael@x054:[/data/prj/httpd-2.4.1]patch -p0 -i *.patch
> >> >> >> Processing... Looks like a unified context diff...
> >> >> >> The text leading up to this was:
> >> >> >> --------------------------
> >> >> >> |Index: include/mpm_common.h
> >> >> >>
> |===================================================================
> >> >> >> |--- include/mpm_common.h (revision 1293841)
> >> >> >> |+++ include/mpm_common.h (working copy)
> >> >> >> --------------------------
> >> >> >> Patching file include/mpm_common.h using Plan A...
> >> >> >> patch: 3016-037 Malformed patch at line 9: -void
> >> >> >> ap_reclaim_child_processes(int terminate,
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> On Sun, Feb 26, 2012 at 10:53 PM, Michael Felt <mamfelt@gmail.com
> >
> >> >> >> wrote:
> >> >> >>>
> >> >> >>> :) patch from AIX 6.1 works, starting build.
> >> >> >>>
> >> >> >>>
> >> >> >>> On Sun, Feb 26, 2012 at 10:52 PM, Michael Felt <
> mamfelt@gmail.com>
> >> >> >>> wrote:
> >> >> >>>>
> >> >> >>>> re: not exported... They are not in the .o files either (or is
> >> >> >>>> that
> >> >> >>>> because they are not exported?)
> >> >> >>>>
> >> >> >>>>
> >> >> >>>> On Sun, Feb 26, 2012 at 10:51 PM, Michael Felt <
> mamfelt@gmail.com>
> >> >> >>>> wrote:
> >> >> >>>>>
> >> >> >>>>> I am not so smart I fear, and still no svm installed (working
> on
> >> >> >>>>> building gnudiff, but not done yet...
> >> >> >>>>>
> >> >> >>>>> root@x105:[/data/prj/httpd-2.4.1]patch -i *patch
> >> >> >>>>> Processing... I cannot find a patch in there anywhere.
> >> >> >>>>>
> >> >> >>>>>
> >> >> >>>>>
> >> >> >>>>> On Sun, Feb 26, 2012 at 10:44 PM, Jeff Trawick
> >> >> >>>>> <tr...@gmail.com>
> >> >> >>>>> wrote:
> >> >> >>>>>>
> >> >> >>>>>> On Sun, Feb 26, 2012 at 3:30 PM, Michael Felt
> >> >> >>>>>> <ma...@gmail.com>
> >> >> >>>>>> wrote:
> >> >> >>>>>> > Unfortunately, although it builds fine, it does not start:
> >> >> >>>>>> >
> >> >> >>>>>> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf:
> >> >> >>>>>> > Cannot
> >> >> >>>>>> > load
> >> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so into server: rtld:
> >> >> >>>>>> > 0712-001
> >> >> >>>>>> > Symbol
> >> >> >>>>>> > ap_fatal_signal_setup was referenced\n from module
> >> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >> >> >>>>>> > definition\n of
> >> >> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol
> ap_pid_fname
> >> >> >>>>>> > was
> >> >> >>>>>> > referenced\n from module
> >> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a
> >> >> >>>>>> > runtime definition\n of the symbol was not
> found.\nrtld:
> >> >> >>>>>> > 0712-001
> >> >> >>>>>> > Symbol ap_reclaim_child_processes was referenced\n from
> >> >> >>>>>> > module
> >> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >> >> >>>>>> > definition\n of
> >> >> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol
> >> >> >>>>>> > ap_relieve_child_processes
> >> >> >>>>>> > was referenced\n from module
> >> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(),
> >> >> >>>>>> > but a runtime definition\n of the symbol was not
> >> >> >>>>>> > found.\nrtld:
> >> >> >>>>>> > 0712-001
> >> >> >>>>>> > Symbol ap_graceful_shutdown_timeout was referenced\n
> from
> >> >> >>>>>> > module
> >> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >> >> >>>>>> > definition\n of
> >> >> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol
> >> >> >>>>>> > ap_mpm_safe_kill
> >> >> >>>>>> > was
> >> >> >>>>>> > referenced\n from module
> >> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a
> >> >> >>>>>> > runtime definition\n of the symbol was not
> found.\nrtld:
> >> >> >>>>>> > 0712-001
> >> >> >>>>>> > Symbol ap_wait_or_timeout was referenced\n from module
> >> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >> >> >>>>>> > definition\n of
> >> >> >>>>>> > the symbol was not found.\n\t0509-021 Additional errors
> >> >> >>>>>> > occurred
> >> >> >>>>>> > but
> >> >> >>>>>> > are not
> >> >> >>>>>> > reported.
> >> >> >>>>>> >
> >> >> >>>>>> > I have been able to find a few of these routines in source
> >> >> >>>>>> > code,
> >> >> >>>>>> > e,g,
> >> >> >>>>>> > server/mpm_unix.c, but the routines are not included in
> >> >> >>>>>> > server/mpm_worker.o,
> >> >> >>>>>> > hence ....
> >> >> >>>>>> >
> >> >> >>>>>> > Suggestions welcome (other than filing a bug report).
> >> >> >>>>>>
> >> >> >>>>>> I guess the problem is that those MPM APIs are not decorated
> >> >> >>>>>> with
> >> >> >>>>>> AP_DECLARE() so they don't get added to httpd.exp so they
> don't
> >> >> >>>>>> get
> >> >> >>>>>> exported from httpd on AIX.
> >> >> >>>>>>
> >> >> >>>>>> Can you try the attached patch to mpm_common.h?
> >> >> >>>>>
> >> >> >>>>>
> >> >> >>>>
> >> >> >>>
> >> >> >>
> >> >> >
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Born in Roswell... married an alien...
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> Born in Roswell... married an alien...
> >
> >
>
>
>
> --
> Born in Roswell... married an alien...
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Jeff Trawick <tr...@gmail.com>.
On Mon, Feb 27, 2012 at 4:58 PM, Michael Felt <ma...@gmail.com> wrote:
> That fixed it!
> michael@x054:[/data/home/michael]/opt/httpd/sbin/apachectl
> -t
> AH00558: httpd: Could not reliably determine the server's fully qualified
> domain name, using 192.168.129.54. Set the 'ServerName' directive globally
> to suppress this message
> Syntax OK
>
> Further testing continues...
Cool!
Can you see if it prefork loads too? (Comment out the LoadModule for
mpm_worker_module and add a similar one for prefork and try apachectl
-t.) I can check the completeness of the fix from a theoretical
standpoint, but empirical results would be appreciated.
>
>
> On Mon, Feb 27, 2012 at 1:18 PM, Jeff Trawick <tr...@gmail.com> wrote:
>>
>> On Mon, Feb 27, 2012 at 4:25 AM, Michael Felt <ma...@gmail.com> wrote:
>> > The patch impaired me moved the file to ./include and rebuilt.
>> > Similiar issues:
>> >
>> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
>> > /opt/httpd/libexec/mod_mpm_worker.so into server:
>> > rtld: 0712-001 Symbol ap_fatal_signal_child_setup was referenced
>> >
>> > from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>> > definition
>> > of the symbol was not found.
>> > rtld: 0712-001 Symbol ap_reopen_scoreboard was referenced
>> >
>> > from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>> > definition
>> > of the symbol was not found.
>> > rtld: 0712-001 Symbol ap_mpm_set_graceful_shutdown was referenced
>> >
>> > from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>> > definition
>> > of the symbol was not found.
>>
>> getting much closer AFAICT
>>
>> please try with the pdated mpm_common.h and scoreboard.h attached
>>
>> >
>> > rtld is"runtime linker/loader", for those wondering...
>> >
>> >
>> > On Sun, Feb 26, 2012 at 11:13 PM, Jeff Trawick <tr...@gmail.com>
>> > wrote:
>> >>
>> >> On Sun, Feb 26, 2012 at 5:09 PM, Michael Felt <ma...@gmail.com>
>> >> wrote:
>> >> > patched manually, building...
>> >>
>> >> ouch... maybe you have GNU patch installed as gpatch from the AIX
>> >> Toolbox?
>> >>
>> >> anyway, in a subsequent e-mail I noticed other missing symbols...
>> >> that's in the latest patch and, for the patch impaired, updated
>> >> mpm_common.h, both attached
>> >>
>> >>
>> >> >
>> >> >
>> >> > On Sun, Feb 26, 2012 at 10:56 PM, Michael Felt <ma...@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> er, almost working:
>> >> >> michael@x054:[/data/prj/httpd-2.4.1]patch -p0 -i *.patch
>> >> >> Processing... Looks like a unified context diff...
>> >> >> The text leading up to this was:
>> >> >> --------------------------
>> >> >> |Index: include/mpm_common.h
>> >> >> |===================================================================
>> >> >> |--- include/mpm_common.h (revision 1293841)
>> >> >> |+++ include/mpm_common.h (working copy)
>> >> >> --------------------------
>> >> >> Patching file include/mpm_common.h using Plan A...
>> >> >> patch: 3016-037 Malformed patch at line 9: -void
>> >> >> ap_reclaim_child_processes(int terminate,
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Sun, Feb 26, 2012 at 10:53 PM, Michael Felt <ma...@gmail.com>
>> >> >> wrote:
>> >> >>>
>> >> >>> :) patch from AIX 6.1 works, starting build.
>> >> >>>
>> >> >>>
>> >> >>> On Sun, Feb 26, 2012 at 10:52 PM, Michael Felt <ma...@gmail.com>
>> >> >>> wrote:
>> >> >>>>
>> >> >>>> re: not exported... They are not in the .o files either (or is
>> >> >>>> that
>> >> >>>> because they are not exported?)
>> >> >>>>
>> >> >>>>
>> >> >>>> On Sun, Feb 26, 2012 at 10:51 PM, Michael Felt <ma...@gmail.com>
>> >> >>>> wrote:
>> >> >>>>>
>> >> >>>>> I am not so smart I fear, and still no svm installed (working on
>> >> >>>>> building gnudiff, but not done yet...
>> >> >>>>>
>> >> >>>>> root@x105:[/data/prj/httpd-2.4.1]patch -i *patch
>> >> >>>>> Processing... I cannot find a patch in there anywhere.
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> On Sun, Feb 26, 2012 at 10:44 PM, Jeff Trawick
>> >> >>>>> <tr...@gmail.com>
>> >> >>>>> wrote:
>> >> >>>>>>
>> >> >>>>>> On Sun, Feb 26, 2012 at 3:30 PM, Michael Felt
>> >> >>>>>> <ma...@gmail.com>
>> >> >>>>>> wrote:
>> >> >>>>>> > Unfortunately, although it builds fine, it does not start:
>> >> >>>>>> >
>> >> >>>>>> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf:
>> >> >>>>>> > Cannot
>> >> >>>>>> > load
>> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so into server: rtld:
>> >> >>>>>> > 0712-001
>> >> >>>>>> > Symbol
>> >> >>>>>> > ap_fatal_signal_setup was referenced\n from module
>> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>> >> >>>>>> > definition\n of
>> >> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol ap_pid_fname
>> >> >>>>>> > was
>> >> >>>>>> > referenced\n from module
>> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a
>> >> >>>>>> > runtime definition\n of the symbol was not found.\nrtld:
>> >> >>>>>> > 0712-001
>> >> >>>>>> > Symbol ap_reclaim_child_processes was referenced\n from
>> >> >>>>>> > module
>> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>> >> >>>>>> > definition\n of
>> >> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol
>> >> >>>>>> > ap_relieve_child_processes
>> >> >>>>>> > was referenced\n from module
>> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(),
>> >> >>>>>> > but a runtime definition\n of the symbol was not
>> >> >>>>>> > found.\nrtld:
>> >> >>>>>> > 0712-001
>> >> >>>>>> > Symbol ap_graceful_shutdown_timeout was referenced\n from
>> >> >>>>>> > module
>> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>> >> >>>>>> > definition\n of
>> >> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol
>> >> >>>>>> > ap_mpm_safe_kill
>> >> >>>>>> > was
>> >> >>>>>> > referenced\n from module
>> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a
>> >> >>>>>> > runtime definition\n of the symbol was not found.\nrtld:
>> >> >>>>>> > 0712-001
>> >> >>>>>> > Symbol ap_wait_or_timeout was referenced\n from module
>> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>> >> >>>>>> > definition\n of
>> >> >>>>>> > the symbol was not found.\n\t0509-021 Additional errors
>> >> >>>>>> > occurred
>> >> >>>>>> > but
>> >> >>>>>> > are not
>> >> >>>>>> > reported.
>> >> >>>>>> >
>> >> >>>>>> > I have been able to find a few of these routines in source
>> >> >>>>>> > code,
>> >> >>>>>> > e,g,
>> >> >>>>>> > server/mpm_unix.c, but the routines are not included in
>> >> >>>>>> > server/mpm_worker.o,
>> >> >>>>>> > hence ....
>> >> >>>>>> >
>> >> >>>>>> > Suggestions welcome (other than filing a bug report).
>> >> >>>>>>
>> >> >>>>>> I guess the problem is that those MPM APIs are not decorated
>> >> >>>>>> with
>> >> >>>>>> AP_DECLARE() so they don't get added to httpd.exp so they don't
>> >> >>>>>> get
>> >> >>>>>> exported from httpd on AIX.
>> >> >>>>>>
>> >> >>>>>> Can you try the attached patch to mpm_common.h?
>> >> >>>>>
>> >> >>>>>
>> >> >>>>
>> >> >>>
>> >> >>
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Born in Roswell... married an alien...
>> >
>> >
>>
>>
>>
>> --
>> Born in Roswell... married an alien...
>
>
--
Born in Roswell... married an alien...
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
That fixed it!
michael@x054:[/data/home/michael]/opt/httpd/sbin/apachectl
-t
AH00558: httpd: Could not reliably determine the server's fully qualified
domain name, using 192.168.129.54. Set the 'ServerName' directive globally
to suppress this message
Syntax OK
Further testing continues...
On Mon, Feb 27, 2012 at 1:18 PM, Jeff Trawick <tr...@gmail.com> wrote:
> On Mon, Feb 27, 2012 at 4:25 AM, Michael Felt <ma...@gmail.com> wrote:
> > The patch impaired me moved the file to ./include and rebuilt.
> > Similiar issues:
> >
> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
> > /opt/httpd/libexec/mod_mpm_worker.so into server:
> > rtld: 0712-001 Symbol ap_fatal_signal_child_setup was referenced
> >
> > from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> definition
> > of the symbol was not found.
> > rtld: 0712-001 Symbol ap_reopen_scoreboard was referenced
> >
> > from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> definition
> > of the symbol was not found.
> > rtld: 0712-001 Symbol ap_mpm_set_graceful_shutdown was referenced
> >
> > from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> definition
> > of the symbol was not found.
>
> getting much closer AFAICT
>
> please try with the pdated mpm_common.h and scoreboard.h attached
>
> >
> > rtld is"runtime linker/loader", for those wondering...
> >
> >
> > On Sun, Feb 26, 2012 at 11:13 PM, Jeff Trawick <tr...@gmail.com>
> wrote:
> >>
> >> On Sun, Feb 26, 2012 at 5:09 PM, Michael Felt <ma...@gmail.com>
> wrote:
> >> > patched manually, building...
> >>
> >> ouch... maybe you have GNU patch installed as gpatch from the AIX
> >> Toolbox?
> >>
> >> anyway, in a subsequent e-mail I noticed other missing symbols...
> >> that's in the latest patch and, for the patch impaired, updated
> >> mpm_common.h, both attached
> >>
> >>
> >> >
> >> >
> >> > On Sun, Feb 26, 2012 at 10:56 PM, Michael Felt <ma...@gmail.com>
> >> > wrote:
> >> >>
> >> >> er, almost working:
> >> >> michael@x054:[/data/prj/httpd-2.4.1]patch -p0 -i *.patch
> >> >> Processing... Looks like a unified context diff...
> >> >> The text leading up to this was:
> >> >> --------------------------
> >> >> |Index: include/mpm_common.h
> >> >> |===================================================================
> >> >> |--- include/mpm_common.h (revision 1293841)
> >> >> |+++ include/mpm_common.h (working copy)
> >> >> --------------------------
> >> >> Patching file include/mpm_common.h using Plan A...
> >> >> patch: 3016-037 Malformed patch at line 9: -void
> >> >> ap_reclaim_child_processes(int terminate,
> >> >>
> >> >>
> >> >>
> >> >> On Sun, Feb 26, 2012 at 10:53 PM, Michael Felt <ma...@gmail.com>
> >> >> wrote:
> >> >>>
> >> >>> :) patch from AIX 6.1 works, starting build.
> >> >>>
> >> >>>
> >> >>> On Sun, Feb 26, 2012 at 10:52 PM, Michael Felt <ma...@gmail.com>
> >> >>> wrote:
> >> >>>>
> >> >>>> re: not exported... They are not in the .o files either (or is that
> >> >>>> because they are not exported?)
> >> >>>>
> >> >>>>
> >> >>>> On Sun, Feb 26, 2012 at 10:51 PM, Michael Felt <ma...@gmail.com>
> >> >>>> wrote:
> >> >>>>>
> >> >>>>> I am not so smart I fear, and still no svm installed (working on
> >> >>>>> building gnudiff, but not done yet...
> >> >>>>>
> >> >>>>> root@x105:[/data/prj/httpd-2.4.1]patch -i *patch
> >> >>>>> Processing... I cannot find a patch in there anywhere.
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> On Sun, Feb 26, 2012 at 10:44 PM, Jeff Trawick <trawick@gmail.com
> >
> >> >>>>> wrote:
> >> >>>>>>
> >> >>>>>> On Sun, Feb 26, 2012 at 3:30 PM, Michael Felt <mamfelt@gmail.com
> >
> >> >>>>>> wrote:
> >> >>>>>> > Unfortunately, although it builds fine, it does not start:
> >> >>>>>> >
> >> >>>>>> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf:
> Cannot
> >> >>>>>> > load
> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so into server: rtld:
> 0712-001
> >> >>>>>> > Symbol
> >> >>>>>> > ap_fatal_signal_setup was referenced\n from module
> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >> >>>>>> > definition\n of
> >> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol ap_pid_fname
> was
> >> >>>>>> > referenced\n from module
> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a
> >> >>>>>> > runtime definition\n of the symbol was not found.\nrtld:
> >> >>>>>> > 0712-001
> >> >>>>>> > Symbol ap_reclaim_child_processes was referenced\n from
> >> >>>>>> > module
> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >> >>>>>> > definition\n of
> >> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol
> >> >>>>>> > ap_relieve_child_processes
> >> >>>>>> > was referenced\n from module
> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(),
> >> >>>>>> > but a runtime definition\n of the symbol was not
> >> >>>>>> > found.\nrtld:
> >> >>>>>> > 0712-001
> >> >>>>>> > Symbol ap_graceful_shutdown_timeout was referenced\n from
> >> >>>>>> > module
> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >> >>>>>> > definition\n of
> >> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol
> ap_mpm_safe_kill
> >> >>>>>> > was
> >> >>>>>> > referenced\n from module
> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a
> >> >>>>>> > runtime definition\n of the symbol was not found.\nrtld:
> >> >>>>>> > 0712-001
> >> >>>>>> > Symbol ap_wait_or_timeout was referenced\n from module
> >> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >> >>>>>> > definition\n of
> >> >>>>>> > the symbol was not found.\n\t0509-021 Additional errors
> occurred
> >> >>>>>> > but
> >> >>>>>> > are not
> >> >>>>>> > reported.
> >> >>>>>> >
> >> >>>>>> > I have been able to find a few of these routines in source
> code,
> >> >>>>>> > e,g,
> >> >>>>>> > server/mpm_unix.c, but the routines are not included in
> >> >>>>>> > server/mpm_worker.o,
> >> >>>>>> > hence ....
> >> >>>>>> >
> >> >>>>>> > Suggestions welcome (other than filing a bug report).
> >> >>>>>>
> >> >>>>>> I guess the problem is that those MPM APIs are not decorated with
> >> >>>>>> AP_DECLARE() so they don't get added to httpd.exp so they don't
> get
> >> >>>>>> exported from httpd on AIX.
> >> >>>>>>
> >> >>>>>> Can you try the attached patch to mpm_common.h?
> >> >>>>>
> >> >>>>>
> >> >>>>
> >> >>>
> >> >>
> >> >
> >>
> >>
> >>
> >> --
> >> Born in Roswell... married an alien...
> >
> >
>
>
>
> --
> Born in Roswell... married an alien...
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Jeff Trawick <tr...@gmail.com>.
On Mon, Feb 27, 2012 at 4:25 AM, Michael Felt <ma...@gmail.com> wrote:
> The patch impaired me moved the file to ./include and rebuilt.
> Similiar issues:
>
> httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
> /opt/httpd/libexec/mod_mpm_worker.so into server:
> rtld: 0712-001 Symbol ap_fatal_signal_child_setup was referenced
>
> from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition
> of the symbol was not found.
> rtld: 0712-001 Symbol ap_reopen_scoreboard was referenced
>
> from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition
> of the symbol was not found.
> rtld: 0712-001 Symbol ap_mpm_set_graceful_shutdown was referenced
>
> from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition
> of the symbol was not found.
getting much closer AFAICT
please try with the pdated mpm_common.h and scoreboard.h attached
>
> rtld is"runtime linker/loader", for those wondering...
>
>
> On Sun, Feb 26, 2012 at 11:13 PM, Jeff Trawick <tr...@gmail.com> wrote:
>>
>> On Sun, Feb 26, 2012 at 5:09 PM, Michael Felt <ma...@gmail.com> wrote:
>> > patched manually, building...
>>
>> ouch... maybe you have GNU patch installed as gpatch from the AIX
>> Toolbox?
>>
>> anyway, in a subsequent e-mail I noticed other missing symbols...
>> that's in the latest patch and, for the patch impaired, updated
>> mpm_common.h, both attached
>>
>>
>> >
>> >
>> > On Sun, Feb 26, 2012 at 10:56 PM, Michael Felt <ma...@gmail.com>
>> > wrote:
>> >>
>> >> er, almost working:
>> >> michael@x054:[/data/prj/httpd-2.4.1]patch -p0 -i *.patch
>> >> Processing... Looks like a unified context diff...
>> >> The text leading up to this was:
>> >> --------------------------
>> >> |Index: include/mpm_common.h
>> >> |===================================================================
>> >> |--- include/mpm_common.h (revision 1293841)
>> >> |+++ include/mpm_common.h (working copy)
>> >> --------------------------
>> >> Patching file include/mpm_common.h using Plan A...
>> >> patch: 3016-037 Malformed patch at line 9: -void
>> >> ap_reclaim_child_processes(int terminate,
>> >>
>> >>
>> >>
>> >> On Sun, Feb 26, 2012 at 10:53 PM, Michael Felt <ma...@gmail.com>
>> >> wrote:
>> >>>
>> >>> :) patch from AIX 6.1 works, starting build.
>> >>>
>> >>>
>> >>> On Sun, Feb 26, 2012 at 10:52 PM, Michael Felt <ma...@gmail.com>
>> >>> wrote:
>> >>>>
>> >>>> re: not exported... They are not in the .o files either (or is that
>> >>>> because they are not exported?)
>> >>>>
>> >>>>
>> >>>> On Sun, Feb 26, 2012 at 10:51 PM, Michael Felt <ma...@gmail.com>
>> >>>> wrote:
>> >>>>>
>> >>>>> I am not so smart I fear, and still no svm installed (working on
>> >>>>> building gnudiff, but not done yet...
>> >>>>>
>> >>>>> root@x105:[/data/prj/httpd-2.4.1]patch -i *patch
>> >>>>> Processing... I cannot find a patch in there anywhere.
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> On Sun, Feb 26, 2012 at 10:44 PM, Jeff Trawick <tr...@gmail.com>
>> >>>>> wrote:
>> >>>>>>
>> >>>>>> On Sun, Feb 26, 2012 at 3:30 PM, Michael Felt <ma...@gmail.com>
>> >>>>>> wrote:
>> >>>>>> > Unfortunately, although it builds fine, it does not start:
>> >>>>>> >
>> >>>>>> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot
>> >>>>>> > load
>> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so into server: rtld: 0712-001
>> >>>>>> > Symbol
>> >>>>>> > ap_fatal_signal_setup was referenced\n from module
>> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>> >>>>>> > definition\n of
>> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol ap_pid_fname was
>> >>>>>> > referenced\n from module
>> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a
>> >>>>>> > runtime definition\n of the symbol was not found.\nrtld:
>> >>>>>> > 0712-001
>> >>>>>> > Symbol ap_reclaim_child_processes was referenced\n from
>> >>>>>> > module
>> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>> >>>>>> > definition\n of
>> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol
>> >>>>>> > ap_relieve_child_processes
>> >>>>>> > was referenced\n from module
>> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(),
>> >>>>>> > but a runtime definition\n of the symbol was not
>> >>>>>> > found.\nrtld:
>> >>>>>> > 0712-001
>> >>>>>> > Symbol ap_graceful_shutdown_timeout was referenced\n from
>> >>>>>> > module
>> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>> >>>>>> > definition\n of
>> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol ap_mpm_safe_kill
>> >>>>>> > was
>> >>>>>> > referenced\n from module
>> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a
>> >>>>>> > runtime definition\n of the symbol was not found.\nrtld:
>> >>>>>> > 0712-001
>> >>>>>> > Symbol ap_wait_or_timeout was referenced\n from module
>> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>> >>>>>> > definition\n of
>> >>>>>> > the symbol was not found.\n\t0509-021 Additional errors occurred
>> >>>>>> > but
>> >>>>>> > are not
>> >>>>>> > reported.
>> >>>>>> >
>> >>>>>> > I have been able to find a few of these routines in source code,
>> >>>>>> > e,g,
>> >>>>>> > server/mpm_unix.c, but the routines are not included in
>> >>>>>> > server/mpm_worker.o,
>> >>>>>> > hence ....
>> >>>>>> >
>> >>>>>> > Suggestions welcome (other than filing a bug report).
>> >>>>>>
>> >>>>>> I guess the problem is that those MPM APIs are not decorated with
>> >>>>>> AP_DECLARE() so they don't get added to httpd.exp so they don't get
>> >>>>>> exported from httpd on AIX.
>> >>>>>>
>> >>>>>> Can you try the attached patch to mpm_common.h?
>> >>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>
>> >
>>
>>
>>
>> --
>> Born in Roswell... married an alien...
>
>
--
Born in Roswell... married an alien...
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Graham Leggett <mi...@sharp.fm>.
On 27 Feb 2012, at 11:25 AM, Michael Felt wrote:
> The patch impaired me moved the file to ./include and rebuilt.
> Similiar issues:
> httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load /opt/httpd/libexec/mod_mpm_worker.so into server:
> rtld: 0712-001 Symbol ap_fatal_signal_child_setup was referenced
> from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition
> of the symbol was not found.
A quick search for this symbol shows this:
include/mpm_common.h:extern apr_status_t ap_fatal_signal_child_setup(server_rec *s);
server/mpm/event/event.c: ap_fatal_signal_child_setup(ap_server_conf);
server/mpm/prefork/prefork.c: ap_fatal_signal_child_setup(ap_server_conf);
server/mpm/worker/worker.c: ap_fatal_signal_child_setup(ap_server_conf);
server/mpm_unix.c:apr_status_t ap_fatal_signal_child_setup(server_rec *s)
Is server/mpm_unix.c included in your build?
The httpd binary should contain the symbol:
Little-Net:httpd-trunk minfrin$ nm httpd | grep ap_fatal_signal_child_setup
000000010001eca0 T _ap_fatal_signal_child_setup
Regards,
Graham
--
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
The patch impaired me moved the file to ./include and rebuilt.
Similiar issues:
httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
/opt/httpd/libexec/mod_mpm_worker.so into server:
rtld: 0712-001 Symbol ap_fatal_signal_child_setup was referenced
from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol ap_reopen_scoreboard was referenced
from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol ap_mpm_set_graceful_shutdown was referenced
from module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition
of the symbol was not found.
rtld is"runtime linker/loader", for those wondering...
On Sun, Feb 26, 2012 at 11:13 PM, Jeff Trawick <tr...@gmail.com> wrote:
> On Sun, Feb 26, 2012 at 5:09 PM, Michael Felt <ma...@gmail.com> wrote:
> > patched manually, building...
>
> ouch... maybe you have GNU patch installed as gpatch from the AIX Toolbox?
>
> anyway, in a subsequent e-mail I noticed other missing symbols...
> that's in the latest patch and, for the patch impaired, updated
> mpm_common.h, both attached
>
>
> >
> >
> > On Sun, Feb 26, 2012 at 10:56 PM, Michael Felt <ma...@gmail.com>
> wrote:
> >>
> >> er, almost working:
> >> michael@x054:[/data/prj/httpd-2.4.1]patch -p0 -i *.patch
> >> Processing... Looks like a unified context diff...
> >> The text leading up to this was:
> >> --------------------------
> >> |Index: include/mpm_common.h
> >> |===================================================================
> >> |--- include/mpm_common.h (revision 1293841)
> >> |+++ include/mpm_common.h (working copy)
> >> --------------------------
> >> Patching file include/mpm_common.h using Plan A...
> >> patch: 3016-037 Malformed patch at line 9: -void
> >> ap_reclaim_child_processes(int terminate,
> >>
> >>
> >>
> >> On Sun, Feb 26, 2012 at 10:53 PM, Michael Felt <ma...@gmail.com>
> wrote:
> >>>
> >>> :) patch from AIX 6.1 works, starting build.
> >>>
> >>>
> >>> On Sun, Feb 26, 2012 at 10:52 PM, Michael Felt <ma...@gmail.com>
> wrote:
> >>>>
> >>>> re: not exported... They are not in the .o files either (or is that
> >>>> because they are not exported?)
> >>>>
> >>>>
> >>>> On Sun, Feb 26, 2012 at 10:51 PM, Michael Felt <ma...@gmail.com>
> >>>> wrote:
> >>>>>
> >>>>> I am not so smart I fear, and still no svm installed (working on
> >>>>> building gnudiff, but not done yet...
> >>>>>
> >>>>> root@x105:[/data/prj/httpd-2.4.1]patch -i *patch
> >>>>> Processing... I cannot find a patch in there anywhere.
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Sun, Feb 26, 2012 at 10:44 PM, Jeff Trawick <tr...@gmail.com>
> >>>>> wrote:
> >>>>>>
> >>>>>> On Sun, Feb 26, 2012 at 3:30 PM, Michael Felt <ma...@gmail.com>
> >>>>>> wrote:
> >>>>>> > Unfortunately, although it builds fine, it does not start:
> >>>>>> >
> >>>>>> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot
> >>>>>> > load
> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so into server: rtld: 0712-001
> >>>>>> > Symbol
> >>>>>> > ap_fatal_signal_setup was referenced\n from module
> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >>>>>> > definition\n of
> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol ap_pid_fname was
> >>>>>> > referenced\n from module
> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a
> >>>>>> > runtime definition\n of the symbol was not found.\nrtld:
> >>>>>> > 0712-001
> >>>>>> > Symbol ap_reclaim_child_processes was referenced\n from
> module
> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >>>>>> > definition\n of
> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol
> >>>>>> > ap_relieve_child_processes
> >>>>>> > was referenced\n from module
> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(),
> >>>>>> > but a runtime definition\n of the symbol was not
> found.\nrtld:
> >>>>>> > 0712-001
> >>>>>> > Symbol ap_graceful_shutdown_timeout was referenced\n from
> >>>>>> > module
> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >>>>>> > definition\n of
> >>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol ap_mpm_safe_kill
> >>>>>> > was
> >>>>>> > referenced\n from module
> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a
> >>>>>> > runtime definition\n of the symbol was not found.\nrtld:
> >>>>>> > 0712-001
> >>>>>> > Symbol ap_wait_or_timeout was referenced\n from module
> >>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
> >>>>>> > definition\n of
> >>>>>> > the symbol was not found.\n\t0509-021 Additional errors occurred
> but
> >>>>>> > are not
> >>>>>> > reported.
> >>>>>> >
> >>>>>> > I have been able to find a few of these routines in source code,
> >>>>>> > e,g,
> >>>>>> > server/mpm_unix.c, but the routines are not included in
> >>>>>> > server/mpm_worker.o,
> >>>>>> > hence ....
> >>>>>> >
> >>>>>> > Suggestions welcome (other than filing a bug report).
> >>>>>>
> >>>>>> I guess the problem is that those MPM APIs are not decorated with
> >>>>>> AP_DECLARE() so they don't get added to httpd.exp so they don't get
> >>>>>> exported from httpd on AIX.
> >>>>>>
> >>>>>> Can you try the attached patch to mpm_common.h?
> >>>>>
> >>>>>
> >>>>
> >>>
> >>
> >
>
>
>
> --
> Born in Roswell... married an alien...
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Jeff Trawick <tr...@gmail.com>.
On Sun, Feb 26, 2012 at 5:09 PM, Michael Felt <ma...@gmail.com> wrote:
> patched manually, building...
ouch... maybe you have GNU patch installed as gpatch from the AIX Toolbox?
anyway, in a subsequent e-mail I noticed other missing symbols...
that's in the latest patch and, for the patch impaired, updated
mpm_common.h, both attached
>
>
> On Sun, Feb 26, 2012 at 10:56 PM, Michael Felt <ma...@gmail.com> wrote:
>>
>> er, almost working:
>> michael@x054:[/data/prj/httpd-2.4.1]patch -p0 -i *.patch
>> Processing... Looks like a unified context diff...
>> The text leading up to this was:
>> --------------------------
>> |Index: include/mpm_common.h
>> |===================================================================
>> |--- include/mpm_common.h (revision 1293841)
>> |+++ include/mpm_common.h (working copy)
>> --------------------------
>> Patching file include/mpm_common.h using Plan A...
>> patch: 3016-037 Malformed patch at line 9: -void
>> ap_reclaim_child_processes(int terminate,
>>
>>
>>
>> On Sun, Feb 26, 2012 at 10:53 PM, Michael Felt <ma...@gmail.com> wrote:
>>>
>>> :) patch from AIX 6.1 works, starting build.
>>>
>>>
>>> On Sun, Feb 26, 2012 at 10:52 PM, Michael Felt <ma...@gmail.com> wrote:
>>>>
>>>> re: not exported... They are not in the .o files either (or is that
>>>> because they are not exported?)
>>>>
>>>>
>>>> On Sun, Feb 26, 2012 at 10:51 PM, Michael Felt <ma...@gmail.com>
>>>> wrote:
>>>>>
>>>>> I am not so smart I fear, and still no svm installed (working on
>>>>> building gnudiff, but not done yet...
>>>>>
>>>>> root@x105:[/data/prj/httpd-2.4.1]patch -i *patch
>>>>> Processing... I cannot find a patch in there anywhere.
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Feb 26, 2012 at 10:44 PM, Jeff Trawick <tr...@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> On Sun, Feb 26, 2012 at 3:30 PM, Michael Felt <ma...@gmail.com>
>>>>>> wrote:
>>>>>> > Unfortunately, although it builds fine, it does not start:
>>>>>> >
>>>>>> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot
>>>>>> > load
>>>>>> > /opt/httpd/libexec/mod_mpm_worker.so into server: rtld: 0712-001
>>>>>> > Symbol
>>>>>> > ap_fatal_signal_setup was referenced\n from module
>>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>>>>>> > definition\n of
>>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol ap_pid_fname was
>>>>>> > referenced\n from module
>>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a
>>>>>> > runtime definition\n of the symbol was not found.\nrtld:
>>>>>> > 0712-001
>>>>>> > Symbol ap_reclaim_child_processes was referenced\n from module
>>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>>>>>> > definition\n of
>>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol
>>>>>> > ap_relieve_child_processes
>>>>>> > was referenced\n from module
>>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(),
>>>>>> > but a runtime definition\n of the symbol was not found.\nrtld:
>>>>>> > 0712-001
>>>>>> > Symbol ap_graceful_shutdown_timeout was referenced\n from
>>>>>> > module
>>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>>>>>> > definition\n of
>>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol ap_mpm_safe_kill
>>>>>> > was
>>>>>> > referenced\n from module
>>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a
>>>>>> > runtime definition\n of the symbol was not found.\nrtld:
>>>>>> > 0712-001
>>>>>> > Symbol ap_wait_or_timeout was referenced\n from module
>>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>>>>>> > definition\n of
>>>>>> > the symbol was not found.\n\t0509-021 Additional errors occurred but
>>>>>> > are not
>>>>>> > reported.
>>>>>> >
>>>>>> > I have been able to find a few of these routines in source code,
>>>>>> > e,g,
>>>>>> > server/mpm_unix.c, but the routines are not included in
>>>>>> > server/mpm_worker.o,
>>>>>> > hence ....
>>>>>> >
>>>>>> > Suggestions welcome (other than filing a bug report).
>>>>>>
>>>>>> I guess the problem is that those MPM APIs are not decorated with
>>>>>> AP_DECLARE() so they don't get added to httpd.exp so they don't get
>>>>>> exported from httpd on AIX.
>>>>>>
>>>>>> Can you try the attached patch to mpm_common.h?
>>>>>
>>>>>
>>>>
>>>
>>
>
--
Born in Roswell... married an alien...
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
patched manually, building...
On Sun, Feb 26, 2012 at 10:56 PM, Michael Felt <ma...@gmail.com> wrote:
> er, almost working:
> michael@x054:[/data/prj/httpd-2.4.1]patch -p0 -i *.patch
> Processing... Looks like a unified context diff...
> The text leading up to this was:
> --------------------------
> |Index: include/mpm_common.h
> |===================================================================
> |--- include/mpm_common.h (revision 1293841)
> |+++ include/mpm_common.h (working copy)
> --------------------------
> Patching file include/mpm_common.h using Plan A...
> patch: 3016-037 Malformed patch at line 9: -void
> ap_reclaim_child_processes(int terminate,
>
>
>
> On Sun, Feb 26, 2012 at 10:53 PM, Michael Felt <ma...@gmail.com> wrote:
>
>> :) patch from AIX 6.1 works, starting build.
>>
>>
>> On Sun, Feb 26, 2012 at 10:52 PM, Michael Felt <ma...@gmail.com> wrote:
>>
>>> re: not exported... They are not in the .o files either (or is that
>>> because they are not exported?)
>>>
>>>
>>> On Sun, Feb 26, 2012 at 10:51 PM, Michael Felt <ma...@gmail.com>wrote:
>>>
>>>> I am not so smart I fear, and still no svm installed (working on
>>>> building gnudiff, but not done yet...
>>>>
>>>> root@x105:[/data/prj/httpd-2.4.1]patch -i *patch
>>>> Processing... I cannot find a patch in there anywhere.
>>>>
>>>>
>>>>
>>>> On Sun, Feb 26, 2012 at 10:44 PM, Jeff Trawick <tr...@gmail.com>wrote:
>>>>
>>>>> On Sun, Feb 26, 2012 at 3:30 PM, Michael Felt <ma...@gmail.com>
>>>>> wrote:
>>>>> > Unfortunately, although it builds fine, it does not start:
>>>>> >
>>>>> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
>>>>> > /opt/httpd/libexec/mod_mpm_worker.so into server: rtld: 0712-001
>>>>> Symbol
>>>>> > ap_fatal_signal_setup was referenced\n from module
>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>>>>> definition\n of
>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol ap_pid_fname was
>>>>> > referenced\n from module
>>>>> /opt/httpd/libexec/mod_mpm_worker.so(), but a
>>>>> > runtime definition\n of the symbol was not found.\nrtld:
>>>>> 0712-001
>>>>> > Symbol ap_reclaim_child_processes was referenced\n from module
>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>>>>> definition\n of
>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol
>>>>> ap_relieve_child_processes
>>>>> > was referenced\n from module
>>>>> /opt/httpd/libexec/mod_mpm_worker.so(),
>>>>> > but a runtime definition\n of the symbol was not found.\nrtld:
>>>>> 0712-001
>>>>> > Symbol ap_graceful_shutdown_timeout was referenced\n from module
>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>>>>> definition\n of
>>>>> > the symbol was not found.\nrtld: 0712-001 Symbol ap_mpm_safe_kill was
>>>>> > referenced\n from module
>>>>> /opt/httpd/libexec/mod_mpm_worker.so(), but a
>>>>> > runtime definition\n of the symbol was not found.\nrtld:
>>>>> 0712-001
>>>>> > Symbol ap_wait_or_timeout was referenced\n from module
>>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>>>>> definition\n of
>>>>> > the symbol was not found.\n\t0509-021 Additional errors occurred but
>>>>> are not
>>>>> > reported.
>>>>> >
>>>>> > I have been able to find a few of these routines in source code, e,g,
>>>>> > server/mpm_unix.c, but the routines are not included in
>>>>> server/mpm_worker.o,
>>>>> > hence ....
>>>>> >
>>>>> > Suggestions welcome (other than filing a bug report).
>>>>>
>>>>> I guess the problem is that those MPM APIs are not decorated with
>>>>> AP_DECLARE() so they don't get added to httpd.exp so they don't get
>>>>> exported from httpd on AIX.
>>>>>
>>>>> Can you try the attached patch to mpm_common.h?
>>>>>
>>>>
>>>>
>>>
>>
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
er, almost working:
michael@x054:[/data/prj/httpd-2.4.1]patch -p0 -i *.patch
Processing... Looks like a unified context diff...
The text leading up to this was:
--------------------------
|Index: include/mpm_common.h
|===================================================================
|--- include/mpm_common.h (revision 1293841)
|+++ include/mpm_common.h (working copy)
--------------------------
Patching file include/mpm_common.h using Plan A...
patch: 3016-037 Malformed patch at line 9: -void
ap_reclaim_child_processes(int terminate,
On Sun, Feb 26, 2012 at 10:53 PM, Michael Felt <ma...@gmail.com> wrote:
> :) patch from AIX 6.1 works, starting build.
>
>
> On Sun, Feb 26, 2012 at 10:52 PM, Michael Felt <ma...@gmail.com> wrote:
>
>> re: not exported... They are not in the .o files either (or is that
>> because they are not exported?)
>>
>>
>> On Sun, Feb 26, 2012 at 10:51 PM, Michael Felt <ma...@gmail.com> wrote:
>>
>>> I am not so smart I fear, and still no svm installed (working on
>>> building gnudiff, but not done yet...
>>>
>>> root@x105:[/data/prj/httpd-2.4.1]patch -i *patch
>>> Processing... I cannot find a patch in there anywhere.
>>>
>>>
>>>
>>> On Sun, Feb 26, 2012 at 10:44 PM, Jeff Trawick <tr...@gmail.com>wrote:
>>>
>>>> On Sun, Feb 26, 2012 at 3:30 PM, Michael Felt <ma...@gmail.com>
>>>> wrote:
>>>> > Unfortunately, although it builds fine, it does not start:
>>>> >
>>>> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
>>>> > /opt/httpd/libexec/mod_mpm_worker.so into server: rtld: 0712-001
>>>> Symbol
>>>> > ap_fatal_signal_setup was referenced\n from module
>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>>>> definition\n of
>>>> > the symbol was not found.\nrtld: 0712-001 Symbol ap_pid_fname was
>>>> > referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(),
>>>> but a
>>>> > runtime definition\n of the symbol was not found.\nrtld: 0712-001
>>>> > Symbol ap_reclaim_child_processes was referenced\n from module
>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>>>> definition\n of
>>>> > the symbol was not found.\nrtld: 0712-001 Symbol
>>>> ap_relieve_child_processes
>>>> > was referenced\n from module
>>>> /opt/httpd/libexec/mod_mpm_worker.so(),
>>>> > but a runtime definition\n of the symbol was not found.\nrtld:
>>>> 0712-001
>>>> > Symbol ap_graceful_shutdown_timeout was referenced\n from module
>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>>>> definition\n of
>>>> > the symbol was not found.\nrtld: 0712-001 Symbol ap_mpm_safe_kill was
>>>> > referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(),
>>>> but a
>>>> > runtime definition\n of the symbol was not found.\nrtld: 0712-001
>>>> > Symbol ap_wait_or_timeout was referenced\n from module
>>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>>>> definition\n of
>>>> > the symbol was not found.\n\t0509-021 Additional errors occurred but
>>>> are not
>>>> > reported.
>>>> >
>>>> > I have been able to find a few of these routines in source code, e,g,
>>>> > server/mpm_unix.c, but the routines are not included in
>>>> server/mpm_worker.o,
>>>> > hence ....
>>>> >
>>>> > Suggestions welcome (other than filing a bug report).
>>>>
>>>> I guess the problem is that those MPM APIs are not decorated with
>>>> AP_DECLARE() so they don't get added to httpd.exp so they don't get
>>>> exported from httpd on AIX.
>>>>
>>>> Can you try the attached patch to mpm_common.h?
>>>>
>>>
>>>
>>
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
:) patch from AIX 6.1 works, starting build.
On Sun, Feb 26, 2012 at 10:52 PM, Michael Felt <ma...@gmail.com> wrote:
> re: not exported... They are not in the .o files either (or is that
> because they are not exported?)
>
>
> On Sun, Feb 26, 2012 at 10:51 PM, Michael Felt <ma...@gmail.com> wrote:
>
>> I am not so smart I fear, and still no svm installed (working on building
>> gnudiff, but not done yet...
>>
>> root@x105:[/data/prj/httpd-2.4.1]patch -i *patch
>> Processing... I cannot find a patch in there anywhere.
>>
>>
>>
>> On Sun, Feb 26, 2012 at 10:44 PM, Jeff Trawick <tr...@gmail.com> wrote:
>>
>>> On Sun, Feb 26, 2012 at 3:30 PM, Michael Felt <ma...@gmail.com> wrote:
>>> > Unfortunately, although it builds fine, it does not start:
>>> >
>>> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
>>> > /opt/httpd/libexec/mod_mpm_worker.so into server: rtld: 0712-001 Symbol
>>> > ap_fatal_signal_setup was referenced\n from module
>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>>> definition\n of
>>> > the symbol was not found.\nrtld: 0712-001 Symbol ap_pid_fname was
>>> > referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(),
>>> but a
>>> > runtime definition\n of the symbol was not found.\nrtld: 0712-001
>>> > Symbol ap_reclaim_child_processes was referenced\n from module
>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>>> definition\n of
>>> > the symbol was not found.\nrtld: 0712-001 Symbol
>>> ap_relieve_child_processes
>>> > was referenced\n from module
>>> /opt/httpd/libexec/mod_mpm_worker.so(),
>>> > but a runtime definition\n of the symbol was not found.\nrtld:
>>> 0712-001
>>> > Symbol ap_graceful_shutdown_timeout was referenced\n from module
>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>>> definition\n of
>>> > the symbol was not found.\nrtld: 0712-001 Symbol ap_mpm_safe_kill was
>>> > referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(),
>>> but a
>>> > runtime definition\n of the symbol was not found.\nrtld: 0712-001
>>> > Symbol ap_wait_or_timeout was referenced\n from module
>>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
>>> definition\n of
>>> > the symbol was not found.\n\t0509-021 Additional errors occurred but
>>> are not
>>> > reported.
>>> >
>>> > I have been able to find a few of these routines in source code, e,g,
>>> > server/mpm_unix.c, but the routines are not included in
>>> server/mpm_worker.o,
>>> > hence ....
>>> >
>>> > Suggestions welcome (other than filing a bug report).
>>>
>>> I guess the problem is that those MPM APIs are not decorated with
>>> AP_DECLARE() so they don't get added to httpd.exp so they don't get
>>> exported from httpd on AIX.
>>>
>>> Can you try the attached patch to mpm_common.h?
>>>
>>
>>
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
re: not exported... They are not in the .o files either (or is that because
they are not exported?)
On Sun, Feb 26, 2012 at 10:51 PM, Michael Felt <ma...@gmail.com> wrote:
> I am not so smart I fear, and still no svm installed (working on building
> gnudiff, but not done yet...
>
> root@x105:[/data/prj/httpd-2.4.1]patch -i *patch
> Processing... I cannot find a patch in there anywhere.
>
>
>
> On Sun, Feb 26, 2012 at 10:44 PM, Jeff Trawick <tr...@gmail.com> wrote:
>
>> On Sun, Feb 26, 2012 at 3:30 PM, Michael Felt <ma...@gmail.com> wrote:
>> > Unfortunately, although it builds fine, it does not start:
>> >
>> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
>> > /opt/httpd/libexec/mod_mpm_worker.so into server: rtld: 0712-001 Symbol
>> > ap_fatal_signal_setup was referenced\n from module
>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n
>> of
>> > the symbol was not found.\nrtld: 0712-001 Symbol ap_pid_fname was
>> > referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(),
>> but a
>> > runtime definition\n of the symbol was not found.\nrtld: 0712-001
>> > Symbol ap_reclaim_child_processes was referenced\n from module
>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n
>> of
>> > the symbol was not found.\nrtld: 0712-001 Symbol
>> ap_relieve_child_processes
>> > was referenced\n from module
>> /opt/httpd/libexec/mod_mpm_worker.so(),
>> > but a runtime definition\n of the symbol was not found.\nrtld:
>> 0712-001
>> > Symbol ap_graceful_shutdown_timeout was referenced\n from module
>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n
>> of
>> > the symbol was not found.\nrtld: 0712-001 Symbol ap_mpm_safe_kill was
>> > referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(),
>> but a
>> > runtime definition\n of the symbol was not found.\nrtld: 0712-001
>> > Symbol ap_wait_or_timeout was referenced\n from module
>> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n
>> of
>> > the symbol was not found.\n\t0509-021 Additional errors occurred but
>> are not
>> > reported.
>> >
>> > I have been able to find a few of these routines in source code, e,g,
>> > server/mpm_unix.c, but the routines are not included in
>> server/mpm_worker.o,
>> > hence ....
>> >
>> > Suggestions welcome (other than filing a bug report).
>>
>> I guess the problem is that those MPM APIs are not decorated with
>> AP_DECLARE() so they don't get added to httpd.exp so they don't get
>> exported from httpd on AIX.
>>
>> Can you try the attached patch to mpm_common.h?
>>
>
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
I am not so smart I fear, and still no svm installed (working on building
gnudiff, but not done yet...
root@x105:[/data/prj/httpd-2.4.1]patch -i *patch
Processing... I cannot find a patch in there anywhere.
On Sun, Feb 26, 2012 at 10:44 PM, Jeff Trawick <tr...@gmail.com> wrote:
> On Sun, Feb 26, 2012 at 3:30 PM, Michael Felt <ma...@gmail.com> wrote:
> > Unfortunately, although it builds fine, it does not start:
> >
> > httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
> > /opt/httpd/libexec/mod_mpm_worker.so into server: rtld: 0712-001 Symbol
> > ap_fatal_signal_setup was referenced\n from module
> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n
> of
> > the symbol was not found.\nrtld: 0712-001 Symbol ap_pid_fname was
> > referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(),
> but a
> > runtime definition\n of the symbol was not found.\nrtld: 0712-001
> > Symbol ap_reclaim_child_processes was referenced\n from module
> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n
> of
> > the symbol was not found.\nrtld: 0712-001 Symbol
> ap_relieve_child_processes
> > was referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(),
> > but a runtime definition\n of the symbol was not found.\nrtld:
> 0712-001
> > Symbol ap_graceful_shutdown_timeout was referenced\n from module
> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n
> of
> > the symbol was not found.\nrtld: 0712-001 Symbol ap_mpm_safe_kill was
> > referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(),
> but a
> > runtime definition\n of the symbol was not found.\nrtld: 0712-001
> > Symbol ap_wait_or_timeout was referenced\n from module
> > /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n
> of
> > the symbol was not found.\n\t0509-021 Additional errors occurred but are
> not
> > reported.
> >
> > I have been able to find a few of these routines in source code, e,g,
> > server/mpm_unix.c, but the routines are not included in
> server/mpm_worker.o,
> > hence ....
> >
> > Suggestions welcome (other than filing a bug report).
>
> I guess the problem is that those MPM APIs are not decorated with
> AP_DECLARE() so they don't get added to httpd.exp so they don't get
> exported from httpd on AIX.
>
> Can you try the attached patch to mpm_common.h?
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
The patched 2.4.2 version passes the syntax test:
Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
ASF.httpd.rte 2.4.2.0 USR APPLY
SUCCESS
ASF.httpd.rte 2.4.2.0 ROOT APPLY
SUCCESS
root@x103:[/data/prj/httpd-2.4.x]lslpp -L | grep ASF
ASF.apr.rte 1.5.0.0 C F apr version 1.5.0 for
powerpc
ASF.apu.rte 1.5.0.0 C F apu version 1.5.0 for
powerpc
ASF.httpd.rte 2.4.2.0 C F httpd version 2.4.2 for
root@x103:[/data/prj/httpd-2.4.x]/opt/httpd/sbin/apachectl -t
Syntax OK
root@x103:[/data/prj/httpd-2.4.x]
The httpd-2.5.x also passes (used vac.11, and AIX 6.1)
Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
ASF.httpd.rte 2.5.0.0 USR APPLY
SUCCESS
ASF.httpd.rte 2.5.0.0 ROOT APPLY
SUCCESS
root@x104:[/data/prj/httpd-2.5.x]/opt/httpd/sbin/apachectl -t
AH00544: httpd: bad group name daemon
root@x104:[/data/prj/httpd-2.5.x]mkgroup daemon
root@x104:[/data/prj/httpd-2.5.x]/opt/httpd/sbin/apachectl -t
Syntax OK
root@x104:[/data/prj/httpd-2.5.x]lslpp -L | grep ASF
ASF.apr.rte 1.5.0.0 C F apr version 1.5.0 for
powerpc
ASF.apu.rte 1.5.0.0 C F apu version 1.5.0 for
powerpc
ASF.httpd.rte 2.5.0.0 C F httpd version 2.5.0 for
root@x104:[/data/prj/httpd-2.5.x]
On Wed, Mar 28, 2012 at 3:41 PM, Guenter Knauf <fu...@apache.org> wrote:
> Hi Michael,
> Am 27.03.2012 09:07, schrieb Michael Felt:
>
>> since my packaging scripts are not part of apr or apr-util I believe the
>> following change is warrented:
>>
>> --- httpd-2.4.x/build/aix/**buildaix.ksh (revision 1305578)
>> +++ httpd-2.4.x/build/aix/**buildaix.ksh (working copy)
>> @@ -62,14 +62,12 @@
>>
>> if [ ! -f "$apr_config" -a ! -f "$apr_config/configure.in
>> <http://configure.in>" ]; then
>>
>> echo "The apr source directory / apr-1-config could not be found"
>> - echo "If available, install the ASF.apu.rte and ASF.apr.rte filesets"
>> echo "Usage: $cmd [--with-apr=[dir|file]] [--with-apr-util=[dir|file]]"
>> exit 1
>> fi
>>
>> if [ ! -f "$apu_config" -a ! -f "$apu_config/configure.in
>> <http://configure.in>" ]; then
>>
>> echo "The apu source directory / apu-1-config could not be found"
>> - echo "If available, install the ASF.apu.rte and ASF.apr.rte filesets"
>> echo "Usage: $cmd [--with-apr=[dir|file]] [--with-apr-util=[dir|file]]"
>> exit 1
>> fi
>>
> I'd say let these hints in, and lets look forward that your build scripts
> will make it finally into APR/APU too;
> perhaps also do a checkout of APR/APU 1.5.x and post (again?) a patch for
> this branch to the apr-dev list.
>
>
> Also, the file "aixproto.ksh" needs to be removed. It was renamed/has
>> been replaced by mkinstallp.ksh.
>>
> since I have no knowledge about this I leave that for someone familar with
> AIX; Graham perhaps?
>
> Gün.
>
>
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Guenter Knauf <fu...@apache.org>.
Hi Michael,
Am 27.03.2012 09:07, schrieb Michael Felt:
> since my packaging scripts are not part of apr or apr-util I believe the
> following change is warrented:
>
> --- httpd-2.4.x/build/aix/buildaix.ksh (revision 1305578)
> +++ httpd-2.4.x/build/aix/buildaix.ksh (working copy)
> @@ -62,14 +62,12 @@
>
> if [ ! -f "$apr_config" -a ! -f "$apr_config/configure.in
> <http://configure.in>" ]; then
> echo "The apr source directory / apr-1-config could not be found"
> - echo "If available, install the ASF.apu.rte and ASF.apr.rte filesets"
> echo "Usage: $cmd [--with-apr=[dir|file]] [--with-apr-util=[dir|file]]"
> exit 1
> fi
>
> if [ ! -f "$apu_config" -a ! -f "$apu_config/configure.in
> <http://configure.in>" ]; then
> echo "The apu source directory / apu-1-config could not be found"
> - echo "If available, install the ASF.apu.rte and ASF.apr.rte filesets"
> echo "Usage: $cmd [--with-apr=[dir|file]] [--with-apr-util=[dir|file]]"
> exit 1
> fi
I'd say let these hints in, and lets look forward that your build
scripts will make it finally into APR/APU too;
perhaps also do a checkout of APR/APU 1.5.x and post (again?) a patch
for this branch to the apr-dev list.
> Also, the file "aixproto.ksh" needs to be removed. It was renamed/has
> been replaced by mkinstallp.ksh.
since I have no knowledge about this I leave that for someone familar
with AIX; Graham perhaps?
Gün.
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
since my packaging scripts are not part of apr or apr-util I believe the
following change is warrented:
--- httpd-2.4.x/build/aix/buildaix.ksh (revision 1305578)
+++ httpd-2.4.x/build/aix/buildaix.ksh (working copy)
@@ -62,14 +62,12 @@
if [ ! -f "$apr_config" -a ! -f "$apr_config/configure.in" ]; then
echo "The apr source directory / apr-1-config could not be found"
- echo "If available, install the ASF.apu.rte and ASF.apr.rte filesets"
echo "Usage: $cmd [--with-apr=[dir|file]] [--with-apr-util=[dir|file]]"
exit 1
fi
if [ ! -f "$apu_config" -a ! -f "$apu_config/configure.in" ]; then
echo "The apu source directory / apu-1-config could not be found"
- echo "If available, install the ASF.apu.rte and ASF.apr.rte filesets"
echo "Usage: $cmd [--with-apr=[dir|file]] [--with-apr-util=[dir|file]]"
exit 1
fi
Also, the file "aixproto.ksh" needs to be removed. It was renamed/has been
replaced by mkinstallp.ksh.
On Tue, Mar 27, 2012 at 1:47 AM, Guenter Knauf <fu...@apache.org> wrote:
> Hi Michael,
> Am 26.03.2012 23:50, schrieb Michael Felt:
>
> Installation Summary
>> --------------------
>> Name Level Part Event Result
>> ------------------------------**------------------------------**
>> -------------------
>> ASF.httpd.rte 2.4.2.0 USR APPLY
>> SUCCESS
>> ASF.httpd.rte 2.4.2.0 ROOT APPLY
>> SUCCESS
>> root@x103:[/data/prj/httpd-2.**4.x]
>>
>> root@x103:[/data/prj/httpd-2.**4.x]/opt/httpd/sbin/apachectl -t
>> Syntax OK
>> root@x103:[/data/prj/httpd-2.**4.x]
>>
> thanks very much for testing and confirming that it works!
>
> greets, Gün.
>
>
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Guenter Knauf <fu...@apache.org>.
Hi Michael,
Am 26.03.2012 23:50, schrieb Michael Felt:
> Installation Summary
> --------------------
> Name Level Part Event Result
> -------------------------------------------------------------------------------
> ASF.httpd.rte 2.4.2.0 USR APPLY SUCCESS
> ASF.httpd.rte 2.4.2.0 ROOT APPLY SUCCESS
> root@x103:[/data/prj/httpd-2.4.x]
>
> root@x103:[/data/prj/httpd-2.4.x]/opt/httpd/sbin/apachectl -t
> Syntax OK
> root@x103:[/data/prj/httpd-2.4.x]
thanks very much for testing and confirming that it works!
greets, Gün.
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Guenter Knauf <fu...@apache.org>.
Hi Michael,
Am 21.03.2012 19:45, schrieb Michael Felt:
> Unfortunately - 2.4.2 is a nogo...
here's the 2.4.x patch I've just proposed for backport:
http://people.apache.org/~fuankg/diffs/mpm_dso_exports.diff
Gün.
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
My development machines are different - just seems like a lot of
dependancies for perl modules - I assume perl is alos used (elsewhere) for
production environments.
Last time I worked with CPAN to any extent was 8 to 10 years ago - and it
"worked" better on UNIX, read AIX. As I want to test on AIX I need to
figure out what these dependencies are, and/or if force install will hurt
the testing process.
In short, working on it - my problem. Suggestions always welcome. :)
On Thu, Mar 22, 2012 at 11:55 AM, Guenter Knauf <fu...@apache.org> wrote:
> Hi Michael,
> Am 22.03.2012 10:53, schrieb Michael Felt:
>
> Will do Gun. Thanks for the feedback.
>>
>> Like this in the future (or as an attachment - although I assumed (my
>> error) you would cut/paste into a "notebook" - which is how I clear up
>> formats I cannot read).
>>
>> In any case I hope you know what you need to know - I was not sure which
>> one was needing testing.
>>
>> Unfortunately I am still fighting with perl, and getting extra mods
>> installed. AIX 6.1 TYL7 does know have the ability to have a TAP
>> interface, so that has taken care of a few modules - but I am really
>> wondering how well perl mods have been tested for portability if they
>> MUST have things that you might not want to have active in a secured
>> production environment. Just my gut feeling - no comment on the testing
>> process.
>>
> well, thats what your effort with building RPMs is good for: normally the
> development machine is another one than the production machine ;-)
>
> Gün.
>
>
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Guenter Knauf <fu...@apache.org>.
Hi Michael,
Am 22.03.2012 10:53, schrieb Michael Felt:
> Will do Gun. Thanks for the feedback.
>
> Like this in the future (or as an attachment - although I assumed (my
> error) you would cut/paste into a "notebook" - which is how I clear up
> formats I cannot read).
>
> In any case I hope you know what you need to know - I was not sure which
> one was needing testing.
>
> Unfortunately I am still fighting with perl, and getting extra mods
> installed. AIX 6.1 TYL7 does know have the ability to have a TAP
> interface, so that has taken care of a few modules - but I am really
> wondering how well perl mods have been tested for portability if they
> MUST have things that you might not want to have active in a secured
> production environment. Just my gut feeling - no comment on the testing
> process.
well, thats what your effort with building RPMs is good for: normally
the development machine is another one than the production machine ;-)
Gün.
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
Will do Gun. Thanks for the feedback.
Like this in the future (or as an attachment - although I assumed (my
error) you would cut/paste into a "notebook" - which is how I clear up
formats I cannot read).
In any case I hope you know what you need to know - I was not sure which
one was needing testing.
Unfortunately I am still fighting with perl, and getting extra mods
installed. AIX 6.1 TYL7 does know have the ability to have a TAP interface,
so that has taken care of a few modules - but I am really wondering how
well perl mods have been tested for portability if they MUST have things
that you might not want to have active in a secured production environment.
Just my gut feeling - no comment on the testing process.
On Thu, Mar 22, 2012 at 1:06 AM, Guenter Knauf <fu...@apache.org> wrote:
> Am 21.03.2012 19:45, schrieb Michael Felt:
>
> Unfortunately - 2.4.2 is a nogo...
>>
>> Same compiler warning messages, install and then ...
>>
>> Installation Summary
>> --------------------
>> Name Level Part Event Result
>> ------------------------------**------------------------------**
>> -------------------
>> ASF.httpd.rte 2.4.2.0 USR APPLY
>> SUCCESS
>> ASF.httpd.man.en_US 2.4.2.0 USR APPLY
>> SUCCESS
>> ASF.httpd.rte 2.4.2.0 ROOT APPLY
>> SUCCESS
>> ASF.httpd.man.en_US 2.4.2.0 ROOT APPLY
>> SUCCESS
>> root@x103:[/data/prj/httpd-2.**4.x]/opt/httpd/sbin/apachectl -t
>> httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
>> /opt/httpd/libexec/mod_mpm_**worker.so into server: rtld: 0712-001 Symbol
>> ap_fatal_signal_setup was referenced\n from module
>>
> sure! The patch is only in trunk for now - once confirmed all is well we
> will propose a packport to 2.4.2 ;-)
> btw. I would appreciate if you could post in plain-text format since then
> your compiler/build outputs are a lot easier to read ... ;-)
>
> thanks, Gün.
>
>
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Guenter Knauf <fu...@apache.org>.
Am 21.03.2012 19:45, schrieb Michael Felt:
> Unfortunately - 2.4.2 is a nogo...
>
> Same compiler warning messages, install and then ...
>
> Installation Summary
> --------------------
> Name Level Part Event Result
> -------------------------------------------------------------------------------
> ASF.httpd.rte 2.4.2.0 USR APPLY SUCCESS
> ASF.httpd.man.en_US 2.4.2.0 USR APPLY SUCCESS
> ASF.httpd.rte 2.4.2.0 ROOT APPLY SUCCESS
> ASF.httpd.man.en_US 2.4.2.0 ROOT APPLY SUCCESS
> root@x103:[/data/prj/httpd-2.4.x]/opt/httpd/sbin/apachectl -t
> httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
> /opt/httpd/libexec/mod_mpm_worker.so into server: rtld: 0712-001 Symbol
> ap_fatal_signal_setup was referenced\n from module
sure! The patch is only in trunk for now - once confirmed all is well we
will propose a packport to 2.4.2 ;-)
btw. I would appreciate if you could post in plain-text format since
then your compiler/build outputs are a lot easier to read ... ;-)
thanks, Gün.
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
Unfortunately - 2.4.2 is a nogo...
Same compiler warning messages, install and then ...
Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
ASF.httpd.rte 2.4.2.0 USR APPLY
SUCCESS
ASF.httpd.man.en_US 2.4.2.0 USR APPLY
SUCCESS
ASF.httpd.rte 2.4.2.0 ROOT APPLY
SUCCESS
ASF.httpd.man.en_US 2.4.2.0 ROOT APPLY
SUCCESS
root@x103:[/data/prj/httpd-2.4.x]/opt/httpd/sbin/apachectl -t
httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
/opt/httpd/libexec/mod_mpm_worker.so into server: rtld: 0712-001 Symbol
ap_fatal_signal_setup was referenced\n from module
/opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
the symbol was not found.\nrtld: 0712-001 Symbol ap_reclaim_child_processes
was referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(),
but a runtime definition\n of the symbol was not found.\nrtld:
0712-001 Symbol ap_relieve_child_processes was referenced\n from
module /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime
definition\n of the symbol was not found.\nrtld: 0712-001 Symbol
ap_mpm_safe_kill was referenced\n from module
/opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
the symbol was not found.\nrtld: 0712-001 Symbol ap_wait_or_timeout was
referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a
runtime definition\n of the symbol was not found.\nrtld: 0712-001
Symbol ap_process_child_status was referenced\n from module
/opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
the symbol was not found.\nrtld: 0712-001 Symbol
ap_unregister_extra_mpm_process was referenced\n from module
/opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
the symbol was not found.\n\t0509-021 Additional errors occurred but are
not reported.
On Wed, Mar 21, 2012 at 7:17 PM, Michael Felt <ma...@gmail.com> wrote:
> root@x103:[/data/prj/httpd-trunk]build/aix/buildaix.ksh
>
> + ./configure
> --enable-layout=AIX
> --with-apr=/opt/bin/apr-1-config
> --with-apr-util=/opt/bin/apu-1-config
> --enable-mpms-shared=all
> --enable-mods-shared=all
> --enable-load-all-modules
> --disable-lua > build/aix/configure.out
> configure: WARNING: apr/apr-util is compiled without ldap support
> configure: WARNING: apr/apr-util is compiled without ldap support
> + make > build/aix/make.out
> "util_expr_eval.c", line 1553.7: 1506-196 (W) Initialization between types
> "const void*" and "const char*(*)(struct {...}*,const void*)" is not
> allowed.
> "util_expr_eval.c", line 1554.7: 1506-196 (W) Initialization between types
> "const void*" and "const char*(*)(struct {...}*,const void*)" is not
> allowed.
> "util_expr_eval.c", line 1555.7: 1506-196 (W) Initialization between types
> "const void*" and "const char*(*)(struct {...}*,const void*)" is not
> allowed.
> "util_expr_eval.c", line 1556.7: 1506-196 (W) Initialization between types
> "const void*" and "const char*(*)(struct {...}*,const void*)" is not
> allowed.
> "util_expr_eval.c", line 1561.7: 1506-196 (W) Initialization between types
> "const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
> is not allowed.
> "util_expr_eval.c", line 1562.7: 1506-196 (W) Initialization between types
> "const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
> is not allowed.
> "util_expr_eval.c", line 1563.7: 1506-196 (W) Initialization between types
> "const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
> is not allowed.
> "util_expr_eval.c", line 1564.7: 1506-196 (W) Initialization between types
> "const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
> is not allowed.
> "util_expr_eval.c", line 1566.7: 1506-196 (W) Initialization between types
> "const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
> is not allowed.
> "util_expr_eval.c", line 1567.7: 1506-196 (W) Initialization between types
> "const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
> is not allowed.
> "util_expr_eval.c", line 1568.7: 1506-196 (W) Initialization between types
> "const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
> is not allowed.
> "util_expr_eval.c", line 1569.7: 1506-196 (W) Initialization between types
> "const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
> is not allowed.
> "util_expr_eval.c", line 1570.7: 1506-196 (W) Initialization between types
> "const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
> is not allowed.
> "util_expr_eval.c", line 1571.7: 1506-196 (W) Initialization between types
> "const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
> is not allowed.
> "util_expr_eval.c", line 1572.7: 1506-196 (W) Initialization between types
> "const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
> is not allowed.
> "util_expr_eval.c", line 1573.7: 1506-196 (W) Initialization between types
> "const void*" and "const char*(*)(struct {...}*,const void*,char*)" is not
> allowed.
> "util_expr_eval.c", line 1574.7: 1506-196 (W) Initialization between types
> "const void*" and "const char*(*)(struct {...}*,const void*,char*)" is not
> allowed.
> "util_expr_eval.c", line 1580.7: 1506-196 (W) Initialization between types
> "const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
> allowed.
> "util_expr_eval.c", line 1581.7: 1506-196 (W) Initialization between types
> "const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
> allowed.
> "util_expr_eval.c", line 1582.7: 1506-196 (W) Initialization between types
> "const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
> allowed.
> "util_expr_eval.c", line 1583.7: 1506-196 (W) Initialization between types
> "const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
> allowed.
> "util_expr_eval.c", line 1584.7: 1506-196 (W) Initialization between types
> "const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
> allowed.
> "util_expr_eval.c", line 1585.7: 1506-196 (W) Initialization between types
> "const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
> allowed.
> "util_expr_eval.c", line 1586.7: 1506-196 (W) Initialization between types
> "const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
> allowed.
> "util_expr_eval.c", line 1587.7: 1506-196 (W) Initialization between types
> "const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
> allowed.
> "util_expr_eval.c", line 1588.7: 1506-196 (W) Initialization between types
> "const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
> allowed.
> "util_expr_eval.c", line 1589.7: 1506-196 (W) Initialization between types
> "const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
> allowed.
> "util_expr_eval.c", line 1590.7: 1506-196 (W) Initialization between types
> "const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
> allowed.
> "util_expr_eval.c", line 1591.7: 1506-196 (W) Initialization between types
> "const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
> allowed.
> "util_expr_eval.c", line 1592.7: 1506-196 (W) Initialization between types
> "const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
> allowed.
> "util_expr_eval.c", line 1593.7: 1506-196 (W) Initialization between types
> "const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
> allowed.
> "util_expr_eval.c", line 1598.7: 1506-196 (W) Initialization between types
> "const void*" and "int(*)(struct {...}*,const void*,const char*,const
> char*)" is not allowed.
> "util_expr_eval.c", line 1599.7: 1506-196 (W) Initialization between types
> "const void*" and "int(*)(struct {...}*,const void*,const char*,const
> char*)" is not allowed.
> "util_expr_eval.c", line 1600.7: 1506-196 (W) Initialization between types
> "const void*" and "int(*)(struct {...}*,const void*,const char*,const
> char*)" is not allowed.
> "util_expr_eval.c", line 1601.7: 1506-196 (W) Initialization between types
> "const void*" and "int(*)(struct {...}*,const void*,const char*,const
> char*)" is not allowed.
> "mod_include.c", line 721.26: 1506-068 (W) Operation between types "const
> void*" and "const char*(*)(struct {...}*,const void*,const char*)" is not
> allowed.
> "mod_headers.c", line 898.43: 1506-280 (W) Function argument assignment
> between types "const void*" and "const char*(*)(struct request_rec*,char*)"
> is not allowed.
> "ssl_engine_vars.c", line 88.26: 1506-068 (W) Operation between types
> "const void*" and "const char*(*)(struct {...}*,const void*)" is not
> allowed.
> "ssl_engine_vars.c", line 95.26: 1506-068 (W) Operation between types
> "const void*" and "struct apr_array_header_t*(*)(struct {...}*,const
> void*,const char*)" is not allowed.
> + make install DESTDIR=/var/tmp/root/httpd.2.5.0 > build/aix/install.out
> mkdir /var/tmp/root/httpd.2.5.0
> mkdir /var/tmp/root/httpd.2.5.0/opt
> mkdir /var/tmp/root/httpd.2.5.0/opt/httpd
> mkdir /var/tmp/root/httpd.2.5.0/opt/httpd/libexec
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/libexec'
> mkdir /var/tmp/root/httpd.2.5.0/opt/httpd/bin
> mkdir /var/tmp/root/httpd.2.5.0/opt/httpd/sbin
> mkdir /var/tmp/root/httpd.2.5.0/etc
> mkdir /var/tmp/root/httpd.2.5.0/etc/httpd
> mkdir /var/tmp/root/httpd.2.5.0/etc/httpd/extra
> mkdir /var/tmp/root/httpd.2.5.0/etc/httpd/original
> mkdir /var/tmp/root/httpd.2.5.0/etc/httpd/original/extra
> mkdir /var/tmp/root/httpd.2.5.0/var
> mkdir /var/tmp/root/httpd.2.5.0/var/httpd
> mkdir /var/tmp/root/httpd.2.5.0/var/httpd/htdocs
> mkdir /var/tmp/root/httpd.2.5.0/var/httpd/error
> mkdir /var/tmp/root/httpd.2.5.0/opt/httpd/icons
> mkdir /var/tmp/root/httpd.2.5.0/var/httpd/logs
> mkdir /var/tmp/root/httpd.2.5.0/var/httpd/run
> mkdir /var/tmp/root/httpd.2.5.0/var/httpd/cgi-bin
> mkdir /var/tmp/root/httpd.2.5.0/opt/httpd/include
> mkdir /var/tmp/root/httpd.2.5.0/var/httpd/build
> mkdir /var/tmp/root/httpd.2.5.0/usr
> mkdir /var/tmp/root/httpd.2.5.0/usr/share
> mkdir /var/tmp/root/httpd.2.5.0/usr/share/man
> mkdir /var/tmp/root/httpd.2.5.0/usr/share/man/man1
> mkdir /var/tmp/root/httpd.2.5.0/usr/share/man/man8
> mkdir /var/tmp/root/httpd.2.5.0/opt/httpd/manual
> + build/aix/mkinstallp.ksh /var/tmp/root/httpd.2.5.0 >
> build/aix/mkinstallp.out
> readline() on closed filehandle RAL at /usr/sbin/makebff.pl line 276.
> ========================
> ASF.httpd:ASF.httpd.man.en_US:2.5.0.0::I:T:::::N:httpd 2.5.0 man pages
> Apache Software Foundation::::0::
> ASF.httpd:ASF.httpd.rte:2.5.0.0::I:T:::::N:httpd version 2.5.0 for
> powerpc Apache Software Foundation::::0::
> ========================
>
> ....
> Installation Summary
> --------------------
> Name Level Part Event Result
>
> -------------------------------------------------------------------------------
> ASF.httpd.rte 2.5.0.0 USR APPLY
> SUCCESS
> ASF.httpd.man.en_US 2.5.0.0 USR APPLY
> SUCCESS
> ASF.httpd.rte 2.5.0.0 ROOT APPLY
> SUCCESS
> ASF.httpd.man.en_US 2.5.0.0 ROOT APPLY
> SUCCESS
> root@x103:[/data/prj/httpd-trunk]/opt/httpd/sbin/apachectl -t
> AH00544: httpd: bad group name daemon
> root@x103:[/data/prj/httpd-trunk]mkgroup daemon
> root@x103:[/data/prj/httpd-trunk]/opt/httpd/sbin/apachectl -t
> Syntax OK
> root@x103:[/data/prj/httpd-trunk]
>
> So, for trunk - the Syntax test is succesful.
> Building 2.4.2 now.
>
>
>
>
> On Wed, Mar 21, 2012 at 6:44 PM, Michael Felt <ma...@gmail.com> wrote:
>
>> root@x103:[/data/prj/httpd-trunk]mv ../apr ../aprx
>> root@x103:[/data/prj/httpd-trunk]./buildconf
>>
>> You don't have a copy of the apr source in srclib/apr.
>> Please get the source using the following instructions,
>> or specify the location of the source with
>> --with-apr=[path to apr] :
>>
>> svn co http://svn.apache.org/repos/asf/apr/apr/trunk srclib/apr
>> ========
>> root@x103:[/data/prj/httpd-trunk]cd ..
>> root@x103:[/data/prj]ln -s /data/prj/apr-1.4.6 apr
>> root@x103:[/data/prj]ls -l apr
>> lrwxrwxrwx 1 root system 19 Mar 21 2012 apr -> /data/prj/apr-1.4.6
>> root@x103:[/data/prj]
>> root@x103:[/data/prj/httpd-trunk]./buildconf
>> found apr source: ../apr
>>
>> You don't have a copy of the apr-util source in srclib/apr-util.
>> Please get one the source using the following instructions,
>> or specify the location of the source with
>> --with-apr-util=[path to apr-util]:
>>
>> svn co http://svn.apache.org/repos/asf/apr/apr-util/trunksrclib/apr-util
>>
>> === Surprised here, because there is a copy of ../apr-util ===
>> lrwxrwxrwx 1 root system 19 Mar 21 2012 ../apr ->
>> /data/prj/apr-1.4.6
>> drwxr-x--- 24 michael nobody 4096 Feb 29 23:01 ../apr-1.3.8
>> drwxr-xr-x 26 michael 10001 4096 Mar 21 2012 ../apr-1.4.6
>> drwxr-xr-x 3 root system 256 Mar 2 12:19 ../apr-util
>> drwxr-x--- 19 michael nobody 4096 Feb 29 23:01 ../apr-util-1.3.9
>> drwxr-xr-x 20 nobody nobody 4096 Mar 1 00:18 ../apr-util-1.4.1
>> drwxr-xr-x 39 root system 4096 Mar 21 17:35 ../aprx
>> ========
>> root@x103:[/data/prj/httpd-trunk]cd ..
>> root@x103:[/data/prj]mv apr-util apr-util-x
>> root@x103:[/data/prj]ln -s /data/prj/apr-util-1.4.1 apr-util
>> root@x103:[/data/prj]ls -ld apr-util
>> lrwxrwxrwx 1 root system 24 Mar 21 2012 apr-util ->
>> /data/prj/apr-util-1.4.1
>> root@x103:[/data/prj]ls -ld apr*
>> lrwxrwxrwx 1 root system 19 Mar 21 2012 apr -> /data/prj/apr-1.4.6
>> drwxr-x--- 24 michael nobody 4096 Feb 29 23:01 apr-1.3.8
>> drwxr-xr-x 26 michael 10001 4096 Mar 21 2012 apr-1.4.6
>> lrwxrwxrwx 1 root system 24 Mar 21 2012 apr-util ->
>> /data/prj/apr-util-1.4.1
>> drwxr-x--- 19 michael nobody 4096 Feb 29 23:01 apr-util-1.3.9
>> drwxr-xr-x 20 nobody nobody 4096 Mar 1 00:18 apr-util-1.4.1
>> drwxr-xr-x 3 root system 256 Mar 2 12:19 apr-util-x
>> drwxr-xr-x 39 root system 4096 Mar 21 17:35 aprx
>>
>> root@x103:[/data/prj]cd -
>> /data/prj/httpd-trunk
>> root@x103:[/data/prj/httpd-trunk]./buildconf
>> found apr source: ../apr
>> found apr-util source: ../apr-util
>> copying build files
>> rebuilding include/ap_config_auto.h.in
>> rebuilding configure
>> rebuilding rpm spec file
>> fixing timestamps for ap_expr sources
>> =======
>> So, there sems to something wierd with the new versions of apr and/or
>> apr-util - CAPS needed??
>>
>> the build process has started...
>>
>>
>> On Wed, Mar 21, 2012 at 5:43 PM, Michael Felt <ma...@gmail.com> wrote:
>>
>>>
>>>
>>> On Wed, Mar 21, 2012 at 2:36 AM, Gregg Smith <gl...@gknw.net> wrote:
>>>
>>>> Gün,
>>>>
>>>> It Works!
>>>>
>>>>
>>>> On 3/20/2012 4:18 PM, Guenter Knauf wrote:
>>>>
>>>>>
>>>>> Gregg, can you please run a Windows build?
>>>>>
>>>>> Gün.
>>>>>
>>>>
>>>> tried to build from fresh apr, apr-util and httpd-trunk
>>>
>>> could not run buildconf for apr because I do not have python installed.
>>> I'll worry about that later.
>>>
>>> loaded apr-1.4.6 and apr-util-1.4.1
>>>
>>> ran buildconf in httpd-trunk
>>>
>>> it found ../apr as apr source, rather than the one installed in /opt/bin
>>>
>>> result:
>>> + ./configure
>>> --enable-layout=AIX
>>> --with-apr=/opt/bin/apr-1-config
>>> --with-apr-util=/opt/bin/apu-1-config
>>> --enable-mpms-shared=all
>>> --enable-mods-shared=all
>>> --enable-load-all-modules
>>> --disable-lua > build/aix/configure.out
>>> configure: error: APR-util not found. Please read the documentation.
>>>
>>> Note capital letters in APR-util - is that a bug?
>>>
>>> Anyway, will try some other experiments that do not demand I install
>>> python.
>>>
>>
>>
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
root@x103:[/data/prj/httpd-trunk]build/aix/buildaix.ksh
+ ./configure
--enable-layout=AIX
--with-apr=/opt/bin/apr-1-config
--with-apr-util=/opt/bin/apu-1-config
--enable-mpms-shared=all
--enable-mods-shared=all
--enable-load-all-modules
--disable-lua > build/aix/configure.out
configure: WARNING: apr/apr-util is compiled without ldap support
configure: WARNING: apr/apr-util is compiled without ldap support
+ make > build/aix/make.out
"util_expr_eval.c", line 1553.7: 1506-196 (W) Initialization between types
"const void*" and "const char*(*)(struct {...}*,const void*)" is not
allowed.
"util_expr_eval.c", line 1554.7: 1506-196 (W) Initialization between types
"const void*" and "const char*(*)(struct {...}*,const void*)" is not
allowed.
"util_expr_eval.c", line 1555.7: 1506-196 (W) Initialization between types
"const void*" and "const char*(*)(struct {...}*,const void*)" is not
allowed.
"util_expr_eval.c", line 1556.7: 1506-196 (W) Initialization between types
"const void*" and "const char*(*)(struct {...}*,const void*)" is not
allowed.
"util_expr_eval.c", line 1561.7: 1506-196 (W) Initialization between types
"const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
is not allowed.
"util_expr_eval.c", line 1562.7: 1506-196 (W) Initialization between types
"const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
is not allowed.
"util_expr_eval.c", line 1563.7: 1506-196 (W) Initialization between types
"const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
is not allowed.
"util_expr_eval.c", line 1564.7: 1506-196 (W) Initialization between types
"const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
is not allowed.
"util_expr_eval.c", line 1566.7: 1506-196 (W) Initialization between types
"const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
is not allowed.
"util_expr_eval.c", line 1567.7: 1506-196 (W) Initialization between types
"const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
is not allowed.
"util_expr_eval.c", line 1568.7: 1506-196 (W) Initialization between types
"const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
is not allowed.
"util_expr_eval.c", line 1569.7: 1506-196 (W) Initialization between types
"const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
is not allowed.
"util_expr_eval.c", line 1570.7: 1506-196 (W) Initialization between types
"const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
is not allowed.
"util_expr_eval.c", line 1571.7: 1506-196 (W) Initialization between types
"const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
is not allowed.
"util_expr_eval.c", line 1572.7: 1506-196 (W) Initialization between types
"const void*" and "const char*(*)(struct {...}*,const void*,const char*)"
is not allowed.
"util_expr_eval.c", line 1573.7: 1506-196 (W) Initialization between types
"const void*" and "const char*(*)(struct {...}*,const void*,char*)" is not
allowed.
"util_expr_eval.c", line 1574.7: 1506-196 (W) Initialization between types
"const void*" and "const char*(*)(struct {...}*,const void*,char*)" is not
allowed.
"util_expr_eval.c", line 1580.7: 1506-196 (W) Initialization between types
"const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
allowed.
"util_expr_eval.c", line 1581.7: 1506-196 (W) Initialization between types
"const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
allowed.
"util_expr_eval.c", line 1582.7: 1506-196 (W) Initialization between types
"const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
allowed.
"util_expr_eval.c", line 1583.7: 1506-196 (W) Initialization between types
"const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
allowed.
"util_expr_eval.c", line 1584.7: 1506-196 (W) Initialization between types
"const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
allowed.
"util_expr_eval.c", line 1585.7: 1506-196 (W) Initialization between types
"const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
allowed.
"util_expr_eval.c", line 1586.7: 1506-196 (W) Initialization between types
"const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
allowed.
"util_expr_eval.c", line 1587.7: 1506-196 (W) Initialization between types
"const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
allowed.
"util_expr_eval.c", line 1588.7: 1506-196 (W) Initialization between types
"const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
allowed.
"util_expr_eval.c", line 1589.7: 1506-196 (W) Initialization between types
"const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
allowed.
"util_expr_eval.c", line 1590.7: 1506-196 (W) Initialization between types
"const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
allowed.
"util_expr_eval.c", line 1591.7: 1506-196 (W) Initialization between types
"const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
allowed.
"util_expr_eval.c", line 1592.7: 1506-196 (W) Initialization between types
"const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
allowed.
"util_expr_eval.c", line 1593.7: 1506-196 (W) Initialization between types
"const void*" and "int(*)(struct {...}*,const void*,const char*)" is not
allowed.
"util_expr_eval.c", line 1598.7: 1506-196 (W) Initialization between types
"const void*" and "int(*)(struct {...}*,const void*,const char*,const
char*)" is not allowed.
"util_expr_eval.c", line 1599.7: 1506-196 (W) Initialization between types
"const void*" and "int(*)(struct {...}*,const void*,const char*,const
char*)" is not allowed.
"util_expr_eval.c", line 1600.7: 1506-196 (W) Initialization between types
"const void*" and "int(*)(struct {...}*,const void*,const char*,const
char*)" is not allowed.
"util_expr_eval.c", line 1601.7: 1506-196 (W) Initialization between types
"const void*" and "int(*)(struct {...}*,const void*,const char*,const
char*)" is not allowed.
"mod_include.c", line 721.26: 1506-068 (W) Operation between types "const
void*" and "const char*(*)(struct {...}*,const void*,const char*)" is not
allowed.
"mod_headers.c", line 898.43: 1506-280 (W) Function argument assignment
between types "const void*" and "const char*(*)(struct request_rec*,char*)"
is not allowed.
"ssl_engine_vars.c", line 88.26: 1506-068 (W) Operation between types
"const void*" and "const char*(*)(struct {...}*,const void*)" is not
allowed.
"ssl_engine_vars.c", line 95.26: 1506-068 (W) Operation between types
"const void*" and "struct apr_array_header_t*(*)(struct {...}*,const
void*,const char*)" is not allowed.
+ make install DESTDIR=/var/tmp/root/httpd.2.5.0 > build/aix/install.out
mkdir /var/tmp/root/httpd.2.5.0
mkdir /var/tmp/root/httpd.2.5.0/opt
mkdir /var/tmp/root/httpd.2.5.0/opt/httpd
mkdir /var/tmp/root/httpd.2.5.0/opt/httpd/libexec
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
libtool: install: warning: remember to run `libtool --finish
/opt/httpd/libexec'
mkdir /var/tmp/root/httpd.2.5.0/opt/httpd/bin
mkdir /var/tmp/root/httpd.2.5.0/opt/httpd/sbin
mkdir /var/tmp/root/httpd.2.5.0/etc
mkdir /var/tmp/root/httpd.2.5.0/etc/httpd
mkdir /var/tmp/root/httpd.2.5.0/etc/httpd/extra
mkdir /var/tmp/root/httpd.2.5.0/etc/httpd/original
mkdir /var/tmp/root/httpd.2.5.0/etc/httpd/original/extra
mkdir /var/tmp/root/httpd.2.5.0/var
mkdir /var/tmp/root/httpd.2.5.0/var/httpd
mkdir /var/tmp/root/httpd.2.5.0/var/httpd/htdocs
mkdir /var/tmp/root/httpd.2.5.0/var/httpd/error
mkdir /var/tmp/root/httpd.2.5.0/opt/httpd/icons
mkdir /var/tmp/root/httpd.2.5.0/var/httpd/logs
mkdir /var/tmp/root/httpd.2.5.0/var/httpd/run
mkdir /var/tmp/root/httpd.2.5.0/var/httpd/cgi-bin
mkdir /var/tmp/root/httpd.2.5.0/opt/httpd/include
mkdir /var/tmp/root/httpd.2.5.0/var/httpd/build
mkdir /var/tmp/root/httpd.2.5.0/usr
mkdir /var/tmp/root/httpd.2.5.0/usr/share
mkdir /var/tmp/root/httpd.2.5.0/usr/share/man
mkdir /var/tmp/root/httpd.2.5.0/usr/share/man/man1
mkdir /var/tmp/root/httpd.2.5.0/usr/share/man/man8
mkdir /var/tmp/root/httpd.2.5.0/opt/httpd/manual
+ build/aix/mkinstallp.ksh /var/tmp/root/httpd.2.5.0 >
build/aix/mkinstallp.out
readline() on closed filehandle RAL at /usr/sbin/makebff.pl line 276.
========================
ASF.httpd:ASF.httpd.man.en_US:2.5.0.0::I:T:::::N:httpd 2.5.0 man pages
Apache Software Foundation::::0::
ASF.httpd:ASF.httpd.rte:2.5.0.0::I:T:::::N:httpd version 2.5.0 for powerpc
Apache Software Foundation::::0::
========================
....
Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
ASF.httpd.rte 2.5.0.0 USR APPLY
SUCCESS
ASF.httpd.man.en_US 2.5.0.0 USR APPLY
SUCCESS
ASF.httpd.rte 2.5.0.0 ROOT APPLY
SUCCESS
ASF.httpd.man.en_US 2.5.0.0 ROOT APPLY
SUCCESS
root@x103:[/data/prj/httpd-trunk]/opt/httpd/sbin/apachectl -t
AH00544: httpd: bad group name daemon
root@x103:[/data/prj/httpd-trunk]mkgroup daemon
root@x103:[/data/prj/httpd-trunk]/opt/httpd/sbin/apachectl -t
Syntax OK
root@x103:[/data/prj/httpd-trunk]
So, for trunk - the Syntax test is succesful.
Building 2.4.2 now.
On Wed, Mar 21, 2012 at 6:44 PM, Michael Felt <ma...@gmail.com> wrote:
> root@x103:[/data/prj/httpd-trunk]mv ../apr ../aprx
> root@x103:[/data/prj/httpd-trunk]./buildconf
>
> You don't have a copy of the apr source in srclib/apr.
> Please get the source using the following instructions,
> or specify the location of the source with
> --with-apr=[path to apr] :
>
> svn co http://svn.apache.org/repos/asf/apr/apr/trunk srclib/apr
> ========
> root@x103:[/data/prj/httpd-trunk]cd ..
> root@x103:[/data/prj]ln -s /data/prj/apr-1.4.6 apr
> root@x103:[/data/prj]ls -l apr
> lrwxrwxrwx 1 root system 19 Mar 21 2012 apr -> /data/prj/apr-1.4.6
> root@x103:[/data/prj]
> root@x103:[/data/prj/httpd-trunk]./buildconf
> found apr source: ../apr
>
> You don't have a copy of the apr-util source in srclib/apr-util.
> Please get one the source using the following instructions,
> or specify the location of the source with
> --with-apr-util=[path to apr-util]:
>
> svn co http://svn.apache.org/repos/asf/apr/apr-util/trunksrclib/apr-util
>
> === Surprised here, because there is a copy of ../apr-util ===
> lrwxrwxrwx 1 root system 19 Mar 21 2012 ../apr ->
> /data/prj/apr-1.4.6
> drwxr-x--- 24 michael nobody 4096 Feb 29 23:01 ../apr-1.3.8
> drwxr-xr-x 26 michael 10001 4096 Mar 21 2012 ../apr-1.4.6
> drwxr-xr-x 3 root system 256 Mar 2 12:19 ../apr-util
> drwxr-x--- 19 michael nobody 4096 Feb 29 23:01 ../apr-util-1.3.9
> drwxr-xr-x 20 nobody nobody 4096 Mar 1 00:18 ../apr-util-1.4.1
> drwxr-xr-x 39 root system 4096 Mar 21 17:35 ../aprx
> ========
> root@x103:[/data/prj/httpd-trunk]cd ..
> root@x103:[/data/prj]mv apr-util apr-util-x
> root@x103:[/data/prj]ln -s /data/prj/apr-util-1.4.1 apr-util
> root@x103:[/data/prj]ls -ld apr-util
> lrwxrwxrwx 1 root system 24 Mar 21 2012 apr-util ->
> /data/prj/apr-util-1.4.1
> root@x103:[/data/prj]ls -ld apr*
> lrwxrwxrwx 1 root system 19 Mar 21 2012 apr -> /data/prj/apr-1.4.6
> drwxr-x--- 24 michael nobody 4096 Feb 29 23:01 apr-1.3.8
> drwxr-xr-x 26 michael 10001 4096 Mar 21 2012 apr-1.4.6
> lrwxrwxrwx 1 root system 24 Mar 21 2012 apr-util ->
> /data/prj/apr-util-1.4.1
> drwxr-x--- 19 michael nobody 4096 Feb 29 23:01 apr-util-1.3.9
> drwxr-xr-x 20 nobody nobody 4096 Mar 1 00:18 apr-util-1.4.1
> drwxr-xr-x 3 root system 256 Mar 2 12:19 apr-util-x
> drwxr-xr-x 39 root system 4096 Mar 21 17:35 aprx
>
> root@x103:[/data/prj]cd -
> /data/prj/httpd-trunk
> root@x103:[/data/prj/httpd-trunk]./buildconf
> found apr source: ../apr
> found apr-util source: ../apr-util
> copying build files
> rebuilding include/ap_config_auto.h.in
> rebuilding configure
> rebuilding rpm spec file
> fixing timestamps for ap_expr sources
> =======
> So, there sems to something wierd with the new versions of apr and/or
> apr-util - CAPS needed??
>
> the build process has started...
>
>
> On Wed, Mar 21, 2012 at 5:43 PM, Michael Felt <ma...@gmail.com> wrote:
>
>>
>>
>> On Wed, Mar 21, 2012 at 2:36 AM, Gregg Smith <gl...@gknw.net> wrote:
>>
>>> Gün,
>>>
>>> It Works!
>>>
>>>
>>> On 3/20/2012 4:18 PM, Guenter Knauf wrote:
>>>
>>>>
>>>> Gregg, can you please run a Windows build?
>>>>
>>>> Gün.
>>>>
>>>
>>> tried to build from fresh apr, apr-util and httpd-trunk
>>
>> could not run buildconf for apr because I do not have python installed.
>> I'll worry about that later.
>>
>> loaded apr-1.4.6 and apr-util-1.4.1
>>
>> ran buildconf in httpd-trunk
>>
>> it found ../apr as apr source, rather than the one installed in /opt/bin
>>
>> result:
>> + ./configure
>> --enable-layout=AIX
>> --with-apr=/opt/bin/apr-1-config
>> --with-apr-util=/opt/bin/apu-1-config
>> --enable-mpms-shared=all
>> --enable-mods-shared=all
>> --enable-load-all-modules
>> --disable-lua > build/aix/configure.out
>> configure: error: APR-util not found. Please read the documentation.
>>
>> Note capital letters in APR-util - is that a bug?
>>
>> Anyway, will try some other experiments that do not demand I install
>> python.
>>
>
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
root@x103:[/data/prj/httpd-trunk]mv ../apr ../aprx
root@x103:[/data/prj/httpd-trunk]./buildconf
You don't have a copy of the apr source in srclib/apr.
Please get the source using the following instructions,
or specify the location of the source with
--with-apr=[path to apr] :
svn co http://svn.apache.org/repos/asf/apr/apr/trunk srclib/apr
========
root@x103:[/data/prj/httpd-trunk]cd ..
root@x103:[/data/prj]ln -s /data/prj/apr-1.4.6 apr
root@x103:[/data/prj]ls -l apr
lrwxrwxrwx 1 root system 19 Mar 21 2012 apr -> /data/prj/apr-1.4.6
root@x103:[/data/prj]
root@x103:[/data/prj/httpd-trunk]./buildconf
found apr source: ../apr
You don't have a copy of the apr-util source in srclib/apr-util.
Please get one the source using the following instructions,
or specify the location of the source with
--with-apr-util=[path to apr-util]:
svn co http://svn.apache.org/repos/asf/apr/apr-util/trunk srclib/apr-util
=== Surprised here, because there is a copy of ../apr-util ===
lrwxrwxrwx 1 root system 19 Mar 21 2012 ../apr -> /data/prj/apr-1.4.6
drwxr-x--- 24 michael nobody 4096 Feb 29 23:01 ../apr-1.3.8
drwxr-xr-x 26 michael 10001 4096 Mar 21 2012 ../apr-1.4.6
drwxr-xr-x 3 root system 256 Mar 2 12:19 ../apr-util
drwxr-x--- 19 michael nobody 4096 Feb 29 23:01 ../apr-util-1.3.9
drwxr-xr-x 20 nobody nobody 4096 Mar 1 00:18 ../apr-util-1.4.1
drwxr-xr-x 39 root system 4096 Mar 21 17:35 ../aprx
========
root@x103:[/data/prj/httpd-trunk]cd ..
root@x103:[/data/prj]mv apr-util apr-util-x
root@x103:[/data/prj]ln -s /data/prj/apr-util-1.4.1 apr-util
root@x103:[/data/prj]ls -ld apr-util
lrwxrwxrwx 1 root system 24 Mar 21 2012 apr-util ->
/data/prj/apr-util-1.4.1
root@x103:[/data/prj]ls -ld apr*
lrwxrwxrwx 1 root system 19 Mar 21 2012 apr -> /data/prj/apr-1.4.6
drwxr-x--- 24 michael nobody 4096 Feb 29 23:01 apr-1.3.8
drwxr-xr-x 26 michael 10001 4096 Mar 21 2012 apr-1.4.6
lrwxrwxrwx 1 root system 24 Mar 21 2012 apr-util ->
/data/prj/apr-util-1.4.1
drwxr-x--- 19 michael nobody 4096 Feb 29 23:01 apr-util-1.3.9
drwxr-xr-x 20 nobody nobody 4096 Mar 1 00:18 apr-util-1.4.1
drwxr-xr-x 3 root system 256 Mar 2 12:19 apr-util-x
drwxr-xr-x 39 root system 4096 Mar 21 17:35 aprx
root@x103:[/data/prj]cd -
/data/prj/httpd-trunk
root@x103:[/data/prj/httpd-trunk]./buildconf
found apr source: ../apr
found apr-util source: ../apr-util
copying build files
rebuilding include/ap_config_auto.h.in
rebuilding configure
rebuilding rpm spec file
fixing timestamps for ap_expr sources
=======
So, there sems to something wierd with the new versions of apr and/or
apr-util - CAPS needed??
the build process has started...
On Wed, Mar 21, 2012 at 5:43 PM, Michael Felt <ma...@gmail.com> wrote:
>
>
> On Wed, Mar 21, 2012 at 2:36 AM, Gregg Smith <gl...@gknw.net> wrote:
>
>> Gün,
>>
>> It Works!
>>
>>
>> On 3/20/2012 4:18 PM, Guenter Knauf wrote:
>>
>>>
>>> Gregg, can you please run a Windows build?
>>>
>>> Gün.
>>>
>>
>> tried to build from fresh apr, apr-util and httpd-trunk
>
> could not run buildconf for apr because I do not have python installed.
> I'll worry about that later.
>
> loaded apr-1.4.6 and apr-util-1.4.1
>
> ran buildconf in httpd-trunk
>
> it found ../apr as apr source, rather than the one installed in /opt/bin
>
> result:
> + ./configure
> --enable-layout=AIX
> --with-apr=/opt/bin/apr-1-config
> --with-apr-util=/opt/bin/apu-1-config
> --enable-mpms-shared=all
> --enable-mods-shared=all
> --enable-load-all-modules
> --disable-lua > build/aix/configure.out
> configure: error: APR-util not found. Please read the documentation.
>
> Note capital letters in APR-util - is that a bug?
>
> Anyway, will try some other experiments that do not demand I install
> python.
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
On Wed, Mar 21, 2012 at 2:36 AM, Gregg Smith <gl...@gknw.net> wrote:
> Gün,
>
> It Works!
>
>
> On 3/20/2012 4:18 PM, Guenter Knauf wrote:
>
>>
>> Gregg, can you please run a Windows build?
>>
>> Gün.
>>
>
> tried to build from fresh apr, apr-util and httpd-trunk
could not run buildconf for apr because I do not have python installed.
I'll worry about that later.
loaded apr-1.4.6 and apr-util-1.4.1
ran buildconf in httpd-trunk
it found ../apr as apr source, rather than the one installed in /opt/bin
result:
+ ./configure
--enable-layout=AIX
--with-apr=/opt/bin/apr-1-config
--with-apr-util=/opt/bin/apu-1-config
--enable-mpms-shared=all
--enable-mods-shared=all
--enable-load-all-modules
--disable-lua > build/aix/configure.out
configure: error: APR-util not found. Please read the documentation.
Note capital letters in APR-util - is that a bug?
Anyway, will try some other experiments that do not demand I install python.
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Gregg Smith <gl...@gknw.net>.
Gün,
It Works!
On 3/20/2012 4:18 PM, Guenter Knauf wrote:
>
> Gregg, can you please run a Windows build?
>
> Gün.
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Guenter Knauf <fu...@apache.org>.
Hi Michael,
Am 18.03.2012 19:16, schrieb Michael Felt:
> I hope 2.4.2 can wait for the patch! I shall cherish my patched source
> tree for now then.
I've just comitted the patch with r1303201 - please verify that it still
works for ya!
Jeff, please take aso a look and check if I did catch all ...
Gregg, can you please run a Windows build?
Gün.
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
I hope 2.4.2 can wait for the patch! I shall cherish my patched source tree
for now then.
On Sat, Mar 17, 2012 at 3:55 AM, Guenter Knauf <fu...@apache.org> wrote:
> Hi Michael,
> Am 16.03.2012 16:01, schrieb Michael Felt:
>
> Does this mean AIX is now broken?
>>
> yep - but stay tuned, I will soon bring back a fxied version of Jeff's
> patch ...
>
> Gün.
>
>
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Guenter Knauf <fu...@apache.org>.
Hi Michael,
Am 16.03.2012 16:01, schrieb Michael Felt:
> Does this mean AIX is now broken?
yep - but stay tuned, I will soon bring back a fxied version of Jeff's
patch ...
Gün.
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Michael Felt <ma...@gmail.com>.
Does this mean AIX is now broken?
On Fri, Mar 16, 2012 at 1:00 AM, Guenter Knauf <fu...@apache.org> wrote:
> Am 16.03.2012 00:53, schrieb Jeff Trawick:
>
>> whoops, just reverted :)
>>
> darn! I should have commited mpm_common.h change 1st instead of the awk
> fix - then you would have faced the conflict :D
>
> Gün.
>
>
>
>
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Guenter Knauf <fu...@apache.org>.
Am 16.03.2012 00:53, schrieb Jeff Trawick:
> whoops, just reverted :)
darn! I should have commited mpm_common.h change 1st instead of the awk
fix - then you would have faced the conflict :D
Gün.
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Jeff Trawick <tr...@gmail.com>.
On Thu, Mar 15, 2012 at 7:47 PM, Guenter Knauf <fu...@apache.org> wrote:
> Jeff,
> Am 16.03.2012 00:33, schrieb Jeff Trawick:
>
>> On Thu, Mar 15, 2012 at 5:48 PM, Guenter Knauf<fu...@apache.org> wrote:
>>>
>>> Jeff,
>>> Am 15.03.2012 22:32, schrieb Jeff Trawick:
>>>
>>>> The short form is that I'm going to revert the trunk commit(s) today,
>>>> and when there's a good solution I'll put them back with the fix and
>>>> propose them for backport to 2.4.x.
>>>
>>>
>>> if we are fine with few '#ifndef NETWARE' in mpm_common.h then I commit
>>> this
>>> - I have it already here for testing ...
>>
>>
>> More fixes are needed besides NETWARE...
>
> I know, as I assumed Windows is broken either - Gregg just comfirmed ...
> I proceed, and commit some fixes for both NetWare and Windows, so no need to
> revert; and BTW if I would build the NetWare MPM as a module instead of
> statically linking I would certainly face similar issues ...
whoops, just reverted :)
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Guenter Knauf <fu...@apache.org>.
Jeff,
Am 16.03.2012 00:33, schrieb Jeff Trawick:
> On Thu, Mar 15, 2012 at 5:48 PM, Guenter Knauf<fu...@apache.org> wrote:
>> Jeff,
>> Am 15.03.2012 22:32, schrieb Jeff Trawick:
>>
>>> The short form is that I'm going to revert the trunk commit(s) today,
>>> and when there's a good solution I'll put them back with the fix and
>>> propose them for backport to 2.4.x.
>>
>> if we are fine with few '#ifndef NETWARE' in mpm_common.h then I commit this
>> - I have it already here for testing ...
>
> More fixes are needed besides NETWARE...
I know, as I assumed Windows is broken either - Gregg just comfirmed ...
I proceed, and commit some fixes for both NetWare and Windows, so no
need to revert; and BTW if I would build the NetWare MPM as a module
instead of statically linking I would certainly face similar issues ...
Gün.
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Jeff Trawick <tr...@gmail.com>.
On Thu, Mar 15, 2012 at 5:48 PM, Guenter Knauf <fu...@apache.org> wrote:
> Jeff,
> Am 15.03.2012 22:32, schrieb Jeff Trawick:
>
>> The short form is that I'm going to revert the trunk commit(s) today,
>> and when there's a good solution I'll put them back with the fix and
>> propose them for backport to 2.4.x.
>
> if we are fine with few '#ifndef NETWARE' in mpm_common.h then I commit this
> - I have it already here for testing ...
More fixes are needed besides NETWARE...
> and dont get my ping a rant - I only wanted to know how to proceed with this
> issue.
no offence taken
>
> Gün.
>
>
--
Born in Roswell... married an alien...
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Guenter Knauf <fu...@apache.org>.
Jeff,
Am 15.03.2012 22:32, schrieb Jeff Trawick:
> The short form is that I'm going to revert the trunk commit(s) today,
> and when there's a good solution I'll put them back with the fix and
> propose them for backport to 2.4.x.
if we are fine with few '#ifndef NETWARE' in mpm_common.h then I commit
this - I have it already here for testing ...
and dont get my ping a rant - I only wanted to know how to proceed with
this issue.
Gün.
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Jeff Trawick <tr...@gmail.com>.
On Thu, Mar 15, 2012 at 2:47 PM, Guenter Knauf <fu...@apache.org> wrote:
> Hi Jeff,
> Am 07.03.2012 13:27, schrieb Jeff Trawick:
>
>> On Tue, Mar 6, 2012 at 8:00 PM, Guenter Knauf<fu...@apache.org> wrote:
>>>
>>> Hi Jeff,
>>> Am 26.02.2012 22:44, schrieb Jeff Trawick:
>>>
>>>> I guess the problem is that those MPM APIs are not decorated with
>>>> AP_DECLARE() so they don't get added to httpd.exp so they don't get
>>>> exported from httpd on AIX.
>>>>
>>>> Can you try the attached patch to mpm_common.h?
>>>
>>>
>>> it seems that this breaks the NetWare build now; I've not looked into it
>>> myself since I'm swamped currently with other stuff, but Norm just sent
>>> me
>>> this mail:
>>>
>>> Hi,
>>> Tried to send this to devAThttpd-apache but it got bounced; how peasant
>>> compared to other lists I've sent issues to. I'll watch for fixes.
>>>
>>> r1294936 causes extra export symbols.
>>> Hi,
>>> Re httpd-trunk:
>>> r1294936 added AP_DECLARE_xxx() to a number of func prototypes/vars in
>>> mpm_common.h. These are now found by the 'build/nw_exp_var.awk' script,
>>> which causes the NetWare apache2 link to fail for missing exports. As
>>> these functions are NOT common to NetWare or likely other non-Unix OS
>>> (all seem to be in mpm_unix or related mpm's such as event and worker),
>>> should these prototypes/vsrs now be in ap_mpm.h instead?
>>>
>>> Norm
>>>
>>
>> Thanks; I'll look into that.
>
> any news on that? Sorry, but unless you give a clear statement on how to
> proceed with these I'm unable to fix it self;
The short form is that I'm going to revert the trunk commit(s) today,
and when there's a good solution I'll put them back with the fix and
propose them for backport to 2.4.x.
I acknowledge wrowe's comment later in the thread, but wonder first
how practical it is to ensure that the declarations are visible only
if there is an implementation without going back to an equivalent of
the old AP_MPM_WANT_thisfunction, AP_MPM_WANT_thatfunction.
> if you say that these
> functions need to be extported by every platform then fine - we must then
> either provide dummies for those platforms which dont have them, or ifdef;
> or we need to move these into a unix-only header;
> its IMO not ok to suddenly decide to export these functions in order to fix
> one platform and break another one for that; and also I'm curious how
> Windows builds can cope with that, and wonder that nothing yet came from
> this end ...
> here are the sysmbols in question:
> LINK obj_release/Apache2.nlm
> ### mwldnlm Linker Error:
> # Undefined symbol: ] in
> # Export list
> ### mwldnlm Linker Error:
> # Undefined symbol: ap_fatal_signal_child_setup in
> # Export list
> ### mwldnlm Linker Error:
> # Undefined symbol: ap_fatal_signal_setup in
> # Export list
> ### mwldnlm Linker Error:
> # Undefined symbol: ap_mpm_safe_kill in
> # Export list
> ### mwldnlm Linker Error:
> # Undefined symbol: ap_process_child_status in
> # Export list
> ### mwldnlm Linker Error:
> # Undefined symbol: ap_reclaim_child_processes in
> # Export list
> ### mwldnlm Linker Error:
> # Undefined symbol: ap_register_extra_mpm_process in
> # Export list
> ### mwldnlm Linker Error:
> # Undefined symbol: ap_relieve_child_processes in
> # Export list
> ### mwldnlm Linker Error:
> # Undefined symbol: ap_unregister_extra_mpm_process in
> # Export list
>
> where the 1st one is a quirk from the awk script ...
>
> Gün.
>
>
>
--
Born in Roswell... married an alien...
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by "William A. Rowe Jr." <wr...@rowe-clan.net>.
On 3/15/2012 1:47 PM, Guenter Knauf wrote:
> any news on that? Sorry, but unless you give a clear statement on how to proceed with
> these I'm unable to fix it self; if you say that these functions need to be extported by
> every platform then fine - we must then either provide dummies for those platforms which
> dont have them, or ifdef; or we need to move these into a unix-only header;
> its IMO not ok to suddenly decide to export these functions in order to fix one platform
> and break another one for that; and also I'm curious how Windows builds can cope with
> that, and wonder that nothing yet came from this end ...
> here are the sysmbols in question:
I believe the NW implementation is probably an abuse of that macro.
You are responsible for ignoring anything that wasz #if[n]def'ed away.
Here's a thought; can we cleverly do something to run those headers
through the cpp to drop all of the not-netware defined declarations,
picking up only the remaining declarations in the netware code path?
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Guenter Knauf <fu...@apache.org>.
Hi Jeff,
Am 07.03.2012 13:27, schrieb Jeff Trawick:
> On Tue, Mar 6, 2012 at 8:00 PM, Guenter Knauf<fu...@apache.org> wrote:
>> Hi Jeff,
>> Am 26.02.2012 22:44, schrieb Jeff Trawick:
>>
>>> I guess the problem is that those MPM APIs are not decorated with
>>> AP_DECLARE() so they don't get added to httpd.exp so they don't get
>>> exported from httpd on AIX.
>>>
>>> Can you try the attached patch to mpm_common.h?
>>
>> it seems that this breaks the NetWare build now; I've not looked into it
>> myself since I'm swamped currently with other stuff, but Norm just sent me
>> this mail:
>>
>> Hi,
>> Tried to send this to devAThttpd-apache but it got bounced; how peasant
>> compared to other lists I've sent issues to. I'll watch for fixes.
>>
>> r1294936 causes extra export symbols.
>> Hi,
>> Re httpd-trunk:
>> r1294936 added AP_DECLARE_xxx() to a number of func prototypes/vars in
>> mpm_common.h. These are now found by the 'build/nw_exp_var.awk' script,
>> which causes the NetWare apache2 link to fail for missing exports. As
>> these functions are NOT common to NetWare or likely other non-Unix OS
>> (all seem to be in mpm_unix or related mpm's such as event and worker),
>> should these prototypes/vsrs now be in ap_mpm.h instead?
>>
>> Norm
>>
>
> Thanks; I'll look into that.
any news on that? Sorry, but unless you give a clear statement on how to
proceed with these I'm unable to fix it self; if you say that these
functions need to be extported by every platform then fine - we must
then either provide dummies for those platforms which dont have them, or
ifdef; or we need to move these into a unix-only header;
its IMO not ok to suddenly decide to export these functions in order to
fix one platform and break another one for that; and also I'm curious
how Windows builds can cope with that, and wonder that nothing yet came
from this end ...
here are the sysmbols in question:
LINK obj_release/Apache2.nlm
### mwldnlm Linker Error:
# Undefined symbol: ] in
# Export list
### mwldnlm Linker Error:
# Undefined symbol: ap_fatal_signal_child_setup in
# Export list
### mwldnlm Linker Error:
# Undefined symbol: ap_fatal_signal_setup in
# Export list
### mwldnlm Linker Error:
# Undefined symbol: ap_mpm_safe_kill in
# Export list
### mwldnlm Linker Error:
# Undefined symbol: ap_process_child_status in
# Export list
### mwldnlm Linker Error:
# Undefined symbol: ap_reclaim_child_processes in
# Export list
### mwldnlm Linker Error:
# Undefined symbol: ap_register_extra_mpm_process in
# Export list
### mwldnlm Linker Error:
# Undefined symbol: ap_relieve_child_processes in
# Export list
### mwldnlm Linker Error:
# Undefined symbol: ap_unregister_extra_mpm_process in
# Export list
where the 1st one is a quirk from the awk script ...
Gün.
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Jeff Trawick <tr...@gmail.com>.
On Tue, Mar 6, 2012 at 8:00 PM, Guenter Knauf <fu...@apache.org> wrote:
> Hi Jeff,
> Am 26.02.2012 22:44, schrieb Jeff Trawick:
>
>> I guess the problem is that those MPM APIs are not decorated with
>> AP_DECLARE() so they don't get added to httpd.exp so they don't get
>> exported from httpd on AIX.
>>
>> Can you try the attached patch to mpm_common.h?
>
> it seems that this breaks the NetWare build now; I've not looked into it
> myself since I'm swamped currently with other stuff, but Norm just sent me
> this mail:
>
> Hi,
> Tried to send this to devAThttpd-apache but it got bounced; how peasant
> compared to other lists I've sent issues to. I'll watch for fixes.
>
> r1294936 causes extra export symbols.
> Hi,
> Re httpd-trunk:
> r1294936 added AP_DECLARE_xxx() to a number of func prototypes/vars in
> mpm_common.h. These are now found by the 'build/nw_exp_var.awk' script,
> which causes the NetWare apache2 link to fail for missing exports. As
> these functions are NOT common to NetWare or likely other non-Unix OS
> (all seem to be in mpm_unix or related mpm's such as event and worker),
> should these prototypes/vsrs now be in ap_mpm.h instead?
>
> Norm
>
Thanks; I'll look into that.
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Guenter Knauf <fu...@apache.org>.
Hi Jeff,
Am 26.02.2012 22:44, schrieb Jeff Trawick:
> I guess the problem is that those MPM APIs are not decorated with
> AP_DECLARE() so they don't get added to httpd.exp so they don't get
> exported from httpd on AIX.
>
> Can you try the attached patch to mpm_common.h?
it seems that this breaks the NetWare build now; I've not looked into it
myself since I'm swamped currently with other stuff, but Norm just sent
me this mail:
Hi,
Tried to send this to devAThttpd-apache but it got bounced; how peasant
compared to other lists I've sent issues to. I'll watch for fixes.
r1294936 causes extra export symbols.
Hi,
Re httpd-trunk:
r1294936 added AP_DECLARE_xxx() to a number of func prototypes/vars in
mpm_common.h. These are now found by the 'build/nw_exp_var.awk' script,
which causes the NetWare apache2 link to fail for missing exports. As
these functions are NOT common to NetWare or likely other non-Unix OS
(all seem to be in mpm_unix or related mpm's such as event and worker),
should these prototypes/vsrs now be in ap_mpm.h instead?
Norm
Re: Cannot start httpd v2.4.1 with mpm_build on AIX
Posted by Jeff Trawick <tr...@gmail.com>.
On Sun, Feb 26, 2012 at 3:30 PM, Michael Felt <ma...@gmail.com> wrote:
> Unfortunately, although it builds fine, it does not start:
>
> httpd: Syntax error on line 143 of /etc/httpd/httpd.conf: Cannot load
> /opt/httpd/libexec/mod_mpm_worker.so into server: rtld: 0712-001 Symbol
> ap_fatal_signal_setup was referenced\n from module
> /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
> the symbol was not found.\nrtld: 0712-001 Symbol ap_pid_fname was
> referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a
> runtime definition\n of the symbol was not found.\nrtld: 0712-001
> Symbol ap_reclaim_child_processes was referenced\n from module
> /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
> the symbol was not found.\nrtld: 0712-001 Symbol ap_relieve_child_processes
> was referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(),
> but a runtime definition\n of the symbol was not found.\nrtld: 0712-001
> Symbol ap_graceful_shutdown_timeout was referenced\n from module
> /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
> the symbol was not found.\nrtld: 0712-001 Symbol ap_mpm_safe_kill was
> referenced\n from module /opt/httpd/libexec/mod_mpm_worker.so(), but a
> runtime definition\n of the symbol was not found.\nrtld: 0712-001
> Symbol ap_wait_or_timeout was referenced\n from module
> /opt/httpd/libexec/mod_mpm_worker.so(), but a runtime definition\n of
> the symbol was not found.\n\t0509-021 Additional errors occurred but are not
> reported.
>
> I have been able to find a few of these routines in source code, e,g,
> server/mpm_unix.c, but the routines are not included in server/mpm_worker.o,
> hence ....
>
> Suggestions welcome (other than filing a bug report).
I guess the problem is that those MPM APIs are not decorated with
AP_DECLARE() so they don't get added to httpd.exp so they don't get
exported from httpd on AIX.
Can you try the attached patch to mpm_common.h?