[syslog-ng] Problem with Syslog-NG 3.2.5 on Aix 7.1 ... It coredumps..

Jonathan Kaufman jkaufman at footlocker.com
Thu Mar 1 20:03:19 CET 2012


Awesome!

Thank you very much.

Just in case anyone else is working on Aix 7.1 builds of Syslog-NG here is
what worked (or didn't) for me.

	1.  Update to the LATEST version of IBM VisualAge C/C++, I couldn't
get it to compile until I updated to the 2012 patch set (I was at the early
2011 patch set) for V11
	2.  There were also a few Aix APARs that would have affected
compiling code dealing with the assembler or whatnot. I sidestepped them
and upgraded to the latest TL and SP (TL1 SP3)
	3.  I couldn't get  the bundled libtool that is included with the
Syslog-NG source to recognize that you can create shared libraries, so I
couldn't create shared libraries for the modules (that was an issue)
		I "upgraded" the bundled libtool to 2.4.2 which fixed it so I
could created shared libraries for the modules. The make install didn't
copy them, so I had to do it manually but at least it works.
		I would expect this isn't the preferred method for fixing this,
but so far it doesn't seem to have a downside.
	4.  I had the libiconv library from perzl.org loaded for a different
application, and if Syslog-NG used that either during compile or runtime it
would coredump. Moral of the story seems to be to use the IBM libiconv
library.
	5.  And lastly  Sandor's suggestion.  Add the alloca.h include to
evtstr.c
		if you are using the IBM VisualAge compiler you may be able to
use the -ma compiler option. I don't know if it does the same thing, but if
I used the option (and didn't add it to the source) syslog-ng didn't core.
		I will likely just add it to the source, but thought to mention
the -ma option *seems* to work just the same.

Hopefully this will be the last of my instability woes on Aix 7.1 with
Syslog-NG.



Jonathan Kaufman



|------------>
| From:      |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |Sandor Geller <Sandor.Geller at morganstanley.com>                                                                                                   |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To:        |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |"Syslog-ng users' and developers' mailing list" <syslog-ng at lists.balabit.hu>                                                                      |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date:      |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |03/01/2012 11:03 AM                                                                                                                               |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject:   |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |Re: [syslog-ng] Problem with Syslog-NG 3.2.5 on Aix 7.1 ... It	coredumps..                                                                     |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Sent by:   |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |syslog-ng-bounces at lists.balabit.hu                                                                                                                |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|





I had the same issue using Sun Studio for building 64-bit binaries on
Solaris. Could you apply this patch to eventlog, rebuild it and retry?

--- src/evtstr.c-orig   2010-12-03 14:44:25.000000000 +0100
+++ src/evtstr.c        2010-12-03 14:45:21.000000000 +0100
@@ -48,6 +48,7 @@
 #ifdef _MSC_VER
 #include <malloc.h>
 #endif
+#include <alloca.h>

 /* event string handling */

On Thu, Mar 1, 2012 at 3:21 PM, Jonathan Kaufman
<jkaufman at footlocker.com> wrote:
>
> Hello All,
>        I am hoping someone out there has a working installation of 3.2.5
on
> Aix 7.1 and can help me get mine working.
>
>
> I am currently trying to use a self-compiled version of 3.2.5 on an
Power7
> CPU Aix 7.1 TL1 SP3 box. I was able to get Syslog-NG to compile on Aix
7.1
> after I mangled a new libtool release into the source so it would compile
> shared objects.
>
> Unfortunately, when I start syslog-ng it core dumps repeatedly.
>
>
> Core dumps start filling up /sftw/syslog-ng/var and a ps -ef  shows only
> the "supervising syslog-ng process".
>
> a dbx syslog-ng gives this output...
>
> [root at mlwitt71]:[/sftw/syslog-ng/sbin] > dbx syslog-ng
> Type 'help' for help.
> [using memory image in core.10092546.01150742]
> reading symbolic information ...
>
> Segmentation fault in alloca at 0xd2970930 ($t1)
> 0xd2970930 (alloca+0x8) 800c0000         lwz   r0,0x0(r12)
> (dbx) where
> alloca() at 0xd2970930
> evt_str_append_escape_bs() at 0xd2970520
> evtrec_format_plain() at 0xd296feb4
> evt_format() at 0xd2970104
> msg_event_send(e = 0x00000005), line 166 in "messages.c"
> main_loop_run(cfg = (nil)), line 148 in "main.c"
> main(argc = 1, argv = 0x2ff227f4), line 470 in "main.c"
> (dbx)
>
>
> I have also tried using the Syslog-ng rpm's from perzl & Bull. Both of
them
> core dump as well, so I went back to trying to get a self-compiled
release
> to work as I have some control over that.
>
> I used IBM VisualAge C/C++ v11.1.0.9 as the C compiler.
>
> [root at mlwitt71]:[/sftw/syslog-ng/sbin] > lslpp -L | grep vac
>  vac.Bnd                   11.1.0.1    C     F    XL C for AIX Media
> Defined
>  vac.C                     11.1.0.9    C     F    IBM XL C Compiler
>  vac.aix53.lib             11.1.0.9    C     F    XL C for AIX Libraries
> for AIX
>  vac.include               11.1.0.9    C     F    IBM XL C Compiler
> Include
>  vac.lib                   11.1.0.9    C     F    XL C for AIX Libraries
>  vacpp.Bnd                 11.1.0.1    C     F    IBM XL C/C++ Media
> Defined
>  vacpp.cmp.aix53.lib       11.1.0.9    C     F    IBM XL C/C++ Libraries
> for AIX
>  vacpp.cmp.core            11.1.0.9    C     F    IBM XL C/C++ Compiler
>  vacpp.cmp.include         11.1.0.9    C     F    IBM XL C/C++ Compiler
> Include
>  vacpp.cmp.lib             11.1.0.9    C     F    IBM XL C/C++ Libraries
>  vacpp.cmp.rte             11.1.0.9    C     F    IBM XL C/C++ Compiler
>  vacpp.cmp.tools           11.1.0.9    C     F    IBM XL C/C++ Tools
>  vacpp.tnb                 11.1.0.1    C     F    IBM XL C/C++ Evaluation
>
> I mangled libtool 2.4.2 into the source directories so it would
> detect/compile shared libraries (it wouldn't otherwise).
>
> I compiled and installed eventlog 0.2.12 in /sftw/syslog-ng, I also
> compiled OpenSSL 1.0.0g into it staticly.
>
> I am initially trying to start it using the default configuration files.
>
> There were no errors during the compile, and a syslog-ng -s did NOT
> coredump.
>
> I believe syslog-ng is using the following libraries and their locations
> (dynamically linked).
>
> [root at mlwitt71]:[/sftw/syslog-ng/sbin] > ldd syslog-ng
> syslog-ng needs:
>         /sftw/syslog-ng/lib/libsyslog-ng.a(libsyslog-ng.so.0)
>         /usr/lib/libnsl.a(shr.o)
>         /opt/freeware/lib/libgmodule-2.0.so
>         /opt/freeware/lib/libglib-2.0.so
>         /usr/lib/libpthread.a(shr_xpg5.o)
>         /usr/lib/libc.a(shr.o)
>         /sftw/syslog-ng/lib/libevtlog.a(libevtlog.so.0)
>         /usr/lib/librtl.a(shr.o)
>         /opt/freeware/lib/libpcre.a(libpcre.so.0)
>         /usr/lib/libthread.a(shr.o)
>         /usr/lib/libpthreads_compat.a(shr.o)
>         /usr/lib/libpthreads.a(shr_xpg5.o)
>         /usr/lib/libtli.a(shr.o)
>         /opt/freeware/lib/libglib-2.0.a(libglib-2.0.so.0)
>         /opt/freeware/lib/libintl.a(libintl.so.1)
>         /usr/lib/libiconv.a(shr4.o)
>         /usr/lib/libpthreads.a(shr_comm.o)
>         /unix
>         /usr/lib/libcrypt.a(shr.o)
>         /usr/lib/libpthreads.a(shr.o)
>         /usr/lib/libc.a(pse.o)
>
> and the configure command when compiling from source was:
>
> ./configure --prefix=/sftw/syslog-ng \
>        --disable-spoof-source \
>        --enable-dynamic-linking \
>        --enable-debug \
>        --enable-ssl
>
> and I added -g to the CFLAGS
>
> I am using glib2-2.28.6-1 from perzl as well..
> I plan on removing the --enable-debug if I can get it working
>
>
> Any ideas?
>
>
> Jonathan Kaufman
>
>
>
______________________________________________________________________________

> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation:
http://www.balabit.com/support/documentation/?product=syslog-ng
> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>
______________________________________________________________________________

Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation:
http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq






                    Visit us on-line at footlocker.com.

The information in this e-mail, and any attachment therein, is confidential
and for use by the addressee only. If you are not the intended recipient,
please return the e-mail to the sender and delete it from your computer.
Although the Company attempts to sweep e-mail and attachments for viruses,
it does not guarantee that either are virus-free and accepts no liability
for any damage sustained as a result of viruses.



More information about the syslog-ng mailing list