- syslog-ng - lists.balabit.hu

Error resolving user error 3.0.1
by Riza Kamalie 16 Jan '09

16 Jan '09

Hi there, I have recently installed syslog-ng 3.0.1 OSE on fedora 9 running on a SUN X2100. I have an issue when using owner(username) and dir_owner(username) parameters and received the following error when starting up and the logs files don't have the desired ownership. [root@]# /usr/local/syslog-ng/sbin/syslog-ng -F -e -f /usr/local/syslog-ng/etc/syslog-ng.conf *Error resolving user; user='username' Error resolving user; user='username'* syslog-ng starting up; version='3.0.1' Any advise would be great. Excellent application + documentation. Regards Riza

4 6

[patch] Add follow_freq_ms option
by Joe Shaw 16 Jan '09

16 Jan '09

Hi, As I mentioned in the last thread, I've found myself wanting to have better than one second resolution for the follow_freq() option. Attached is a patch which adds a follow_freq_ms option, which takes its value in milliseconds rather than full seconds. follow_freq() continues to work as it did previously. Thanks, Joe

3 7

Too Many Open Files
by Zeek Anow 14 Jan '09

14 Jan '09

We are running Solaris 9, syslog-ng 2.0.5, We are getting: Error opening file for writing; filename='/logs/combo/combo.log.01', error='Too many open files (24)' I went into the startup script, /etc/init.d/syslog-ng and tried to up the limit by putting this in the startup section: ulimit -n 4096. When I stop and start syslog-ng and look at the ulimit settings, it still shows 256. core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited file size (blocks, -f) unlimited open files (-n) 256 pipe size (512 bytes, -p) 10 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 29995 virtual memory (kbytes, -v) unlimited Any ideas on how to set this? Thanks,

3 2

Make throws link errors over glib2 when compiling syslog-ng 3.0.1
by Joost De Cock 14 Jan '09

14 Jan '09

Hello all, I know that the issue of rewriting syslog messages is a recurring debate here on the list :-) but I'm trying to get 3.0.1 up and running as we need to strip out some info to protect the privacy of our users (there, good cause flag set). I'm having a go under Cygwin and configure runs fine, but make dies on me in a flurry of messages (see below). I'm not much of a devhead, but these seem to be glib2 issue to me. Yet I'm a but stumped on how to beat some sense into it, and any pointer would be hugely appreciated. Thanks in advance, Joost tail of configure output: syslog-ng Open Source Edition 3.0.1 configured Compiler options: compiler : gcc compiler options : -g -O2 -Wall -I/usr/include/glib-2.0 -I/usr/lib /glib-2.0/include -I/usr/include/eventlog -D_GNU_SOURCE -D_LARGEFILE_SOU RCE -D_FILE_OFFSET_BITS=64 linker flags : prefix : /usr/local Features: Sun STREAMS support : no Sun Door support : no Debug symbols : no GCC profiling : no Memtrace : no IPV6 support : no spoof-source support : no tcp-wrapper support : no SSL support : yes SQL support : no Linux capability support : no PCRE support : no Env wrapper support : no the part where make goes of the rails: gcc -g -O2 -Wall -o syslog-ng.exe main.o libsyslog-ng.a -Wl,-Bstatic -lfl -lglib-2.0 -lintl -liconv -levtlog -lssl -lcrypto -Wl,-Bdynamic -ld l /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../libcrypto.a(cryptlib.o):cryptlib.c:(. text+0x260): multiple definition of `_DllMain@12' /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../libglib-2.0.a(gutils.o):gutils.c:(.te xt+0x2c0): first defined here main.o: In function `main_loop_wakeup': /download/syslog-ng-3.0.1/src/main.c:119: undefined reference to `__imp__g_threa ds_got_initialized' /download/syslog-ng-3.0.1/src/main.c:119: undefined reference to `__imp__g_threa d_use_default_impl' /download/syslog-ng-3.0.1/src/main.c:119: undefined reference to `__imp__g_threa d_functions_for_glib_use' /download/syslog-ng-3.0.1/src/main.c:122: undefined reference to `__imp__g_threa ds_got_initialized' /download/syslog-ng-3.0.1/src/main.c:122: undefined reference to `__imp__g_threa d_use_default_impl' /download/syslog-ng-3.0.1/src/main.c:122: undefined reference to `__imp__g_threa d_functions_for_glib_use' main.o: In function `main_loop_run': /download/syslog-ng-3.0.1/src/main.c:195: undefined reference to `__imp__g_threa ds_got_initialized' /download/syslog-ng-3.0.1/src/main.c:195: undefined reference to `__imp__g_threa d_use_default_impl' /download/syslog-ng-3.0.1/src/main.c:195: undefined reference to `__imp__g_threa d_functions_for_glib_use' /download/syslog-ng-3.0.1/src/main.c:198: undefined reference to `__imp__g_threa ds_got_initialized' /download/syslog-ng-3.0.1/src/main.c:198: undefined reference to `__imp__g_threa d_use_default_impl' /download/syslog-ng-3.0.1/src/main.c:198: undefined reference to `__imp__g_threa d_functions_for_glib_use' libsyslog-ng.a(messages.o): In function `msg_event_create': /download/syslog-ng-3.0.1/src/messages.c:140: undefined reference to `__imp__g_t hreads_got_initialized' /download/syslog-ng-3.0.1/src/messages.c:140: undefined reference to `__imp__g_t hread_use_default_impl' /download/syslog-ng-3.0.1/src/messages.c:140: undefined reference to `__imp__g_t hread_functions_for_glib_use' /download/syslog-ng-3.0.1/src/messages.c:149: undefined reference to `__imp__g_t hreads_got_initialized' /download/syslog-ng-3.0.1/src/messages.c:149: undefined reference to `__imp__g_t hread_use_default_impl' /download/syslog-ng-3.0.1/src/messages.c:149: undefined reference to `__imp__g_t hread_functions_for_glib_use' libsyslog-ng.a(messages.o): In function `msg_event_send': /download/syslog-ng-3.0.1/src/messages.c:167: undefined reference to `__imp__g_t hreads_got_initialized' /download/syslog-ng-3.0.1/src/messages.c:167: undefined reference to `__imp__g_t hread_use_default_impl' /download/syslog-ng-3.0.1/src/messages.c:167: undefined reference to `__imp__g_t hread_functions_for_glib_use' /download/syslog-ng-3.0.1/src/messages.c:169: undefined reference to `__imp__g_t hreads_got_initialized' /download/syslog-ng-3.0.1/src/messages.c:169: undefined reference to `__imp__g_t hread_use_default_impl' /download/syslog-ng-3.0.1/src/messages.c:169: undefined reference to `__imp__g_t hread_functions_for_glib_use' libsyslog-ng.a(timeutils.o): In function `cached_mktime': /download/syslog-ng-3.0.1/src/timeutils.c:77: undefined reference to `__imp__g_t hreads_got_initialized' /download/syslog-ng-3.0.1/src/timeutils.c:77: undefined reference to `__imp__g_t hread_use_default_impl' /download/syslog-ng-3.0.1/src/timeutils.c:77: undefined reference to `__imp__g_t hread_functions_for_glib_use' /download/syslog-ng-3.0.1/src/timeutils.c:77: undefined reference to `__imp__g_t hreads_got_initialized' /download/syslog-ng-3.0.1/src/timeutils.c:92: undefined reference to `__imp__g_t hreads_got_initialized' /download/syslog-ng-3.0.1/src/timeutils.c:92: undefined reference to `__imp__g_t hread_use_default_impl' /download/syslog-ng-3.0.1/src/timeutils.c:92: undefined reference to `__imp__g_t hread_functions_for_glib_use' /download/syslog-ng-3.0.1/src/timeutils.c:92: undefined reference to `__imp__g_t hreads_got_initialized' /download/syslog-ng-3.0.1/src/timeutils.c:95: undefined reference to `__imp__g_t hread_use_default_impl' /download/syslog-ng-3.0.1/src/timeutils.c:95: undefined reference to `__imp__g_t hread_functions_for_glib_use' /download/syslog-ng-3.0.1/src/timeutils.c:90: undefined reference to `__imp__g_t hread_use_default_impl' /download/syslog-ng-3.0.1/src/timeutils.c:90: undefined reference to `__imp__g_t hread_functions_for_glib_use' libsyslog-ng.a(timeutils.o): In function `cached_localtime': /download/syslog-ng-3.0.1/src/timeutils.c:105: undefined reference to `__imp__g_ threads_got_initialized' /download/syslog-ng-3.0.1/src/timeutils.c:105: undefined reference to `__imp__g_ thread_use_default_impl' /download/syslog-ng-3.0.1/src/timeutils.c:105: undefined reference to `__imp__g_ thread_functions_for_glib_use' /download/syslog-ng-3.0.1/src/timeutils.c:112: undefined reference to `__imp__g_ threads_got_initialized' /download/syslog-ng-3.0.1/src/timeutils.c:114: undefined reference to `__imp__g_ threads_got_initialized' /download/syslog-ng-3.0.1/src/timeutils.c:114: undefined reference to `__imp__g_ thread_use_default_impl' /download/syslog-ng-3.0.1/src/timeutils.c:114: undefined reference to `__imp__g_ thread_functions_for_glib_use' /download/syslog-ng-3.0.1/src/timeutils.c:114: undefined reference to `__imp__g_ threads_got_initialized' /download/syslog-ng-3.0.1/src/timeutils.c:117: undefined reference to `__imp__g_ thread_use_default_impl' /download/syslog-ng-3.0.1/src/timeutils.c:117: undefined reference to `__imp__g_ thread_functions_for_glib_use' /download/syslog-ng-3.0.1/src/timeutils.c:112: undefined reference to `__imp__g_ thread_use_default_impl' /download/syslog-ng-3.0.1/src/timeutils.c:112: undefined reference to `__imp__g_ thread_functions_for_glib_use' /download/syslog-ng-3.0.1/src/timeutils.c:109: undefined reference to `__imp__g_ threads_got_initialized' libsyslog-ng.a(timeutils.o): In function `get_local_timezone_ofs': /download/syslog-ng-3.0.1/src/timeutils.c:134: undefined reference to `__imp__g_ threads_got_initialized' /download/syslog-ng-3.0.1/src/timeutils.c:134: undefined reference to `__imp__g_ thread_use_default_impl' /download/syslog-ng-3.0.1/src/timeutils.c:134: undefined reference to `__imp__g_ thread_functions_for_glib_use' /download/syslog-ng-3.0.1/src/timeutils.c:134: undefined reference to `__imp__g_ threads_got_initialized' /download/syslog-ng-3.0.1/src/timeutils.c:144: undefined reference to `__imp__g_ thread_use_default_impl' /download/syslog-ng-3.0.1/src/timeutils.c:144: undefined reference to `__imp__g_ thread_functions_for_glib_use' /download/syslog-ng-3.0.1/src/timeutils.c:165: undefined reference to `__imp__g_ threads_got_initialized' /download/syslog-ng-3.0.1/src/timeutils.c:165: undefined reference to `__imp__g_ thread_use_default_impl' /download/syslog-ng-3.0.1/src/timeutils.c:165: undefined reference to `__imp__g_ thread_functions_for_glib_use' /download/syslog-ng-3.0.1/src/timeutils.c:165: undefined reference to `__imp__g_ threads_got_initialized' /download/syslog-ng-3.0.1/src/timeutils.c:169: undefined reference to `__imp__g_ thread_use_default_impl' /download/syslog-ng-3.0.1/src/timeutils.c:169: undefined reference to `__imp__g_ thread_functions_for_glib_use' libsyslog-ng.a(timeutils.o): In function `clean_time_cache': /download/syslog-ng-3.0.1/src/timeutils.c:177: undefined reference to `__imp__g_ threads_got_initialized' /download/syslog-ng-3.0.1/src/timeutils.c:177: undefined reference to `__imp__g_ thread_use_default_impl' /download/syslog-ng-3.0.1/src/timeutils.c:177: undefined reference to `__imp__g_ thread_functions_for_glib_use' /download/syslog-ng-3.0.1/src/timeutils.c:177: undefined reference to `__imp__g_ threads_got_initialized' /download/syslog-ng-3.0.1/src/timeutils.c:179: undefined reference to `__imp__g_ thread_use_default_impl' /download/syslog-ng-3.0.1/src/timeutils.c:179: undefined reference to `__imp__g_ thread_functions_for_glib_use' libsyslog-ng.a(radix.o): In function `r_parser_string': /download/syslog-ng-3.0.1/src/radix.c:42: undefined reference to `__imp__g_ascii _table' libsyslog-ng.a(radix.o): In function `r_parser_ipv4': /download/syslog-ng-3.0.1/src/radix.c:108: undefined reference to `__imp__g_asci i_table' libsyslog-ng.a(radix.o): In function `r_parser_number': /download/syslog-ng-3.0.1/src/radix.c:135: undefined reference to `__imp__g_asci i_table' /download/syslog-ng-3.0.1/src/radix.c:135: undefined reference to `__imp__g_asci i_table' collect2: ld returned 1 exit status make[2]: *** [syslog-ng.exe] Error 1 make[2]: Leaving directory `/download/syslog-ng-3.0.1/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/download/syslog-ng-3.0.1' make: *** [all] Error 2

2 2

Configure glitch in 3.0
by Corinna Vinschen 14 Jan '09

14 Jan '09

Hi, I think there's sort of a bug in the configury: if test "x$prefix" = "xNONE"; then prefix=$ac_default_prefix pidfiledir="/var/run" else pidfiledir="${prefix}/var/run" fi This evaluation of the pidfiledir does not take the defaults of autoconf into account. The pidfiledir should rather always default to pidfiledir="${localstatedir}" instead of fiddeling with the prefix itself. Does that make sense? Corinna -- Corinna Vinschen Cygwin Project Co-Leader Red Hat

2 1

are nested quotes possible in parser
by Michael Hocke 14 Jan '09

14 Jan '09

Hi there, my Avocent console servers are sending console port output via syslog to my syslog server running syslog-ng 3.0.1. Console output looks like this: Jan 13 00:18:39 sysl@cyc2 Buffering: S39.gwa [Jan 13 00:14:04.379: % EARL_NETFLOW-SP-4-TCAM_THRLD: Netflow TCAM threshold exceeded, TCAM Utilization [97%]] Jan 13 00:18:53 sysl@cyc2 Buffering: S42.sw2f [2009 Jan 13 00:18:53 EST -05:00 %ETHC-5-PORTTOSTP:Port 3/27 joined bridge port 3/27] Jan 13 00:18:53 sysl@cyc2 Buffering: S42.sw2f [2009 Jan 13 00:18:53 EST -05:00 %DTP-7-PORTLINKDOWN:Port 3/27 Link down] Jan 13 00:18:53 sysl@cyc2 Buffering: S42.sw2f [2009 Jan 13 00:18:53 EST -05:00 %ETHC-5-PORTFROMSTP:Port 3/27 left bridge port 3/27] The goal is to store the console output within square brackets into separate files named after the server that created this output. The first line of the example above should go into the file "gwa" while the others go into "sw2f". This is what I have so far: > source s_udp { udp (); }; > > # --- parse console server output > # separate port description from message > parser p_console_output { > csv-parser (columns ("CONSOLE.SOURCE", "CONSOLE.MSG") > delimiters (" ") > quote-pairs ("[]") > template ("${MSGONLY}")); > }; > > # extract port label from port description > parser p_console_source { > csv-parser (columns ("CONSOLE.PORT", "CONSOLE.LABEL") > delimiters (".") > template ("${CONSOLE.SOURCE}")); > }; > > # --- destination of console output > destination d_console_output { > file ("/usr/local/var/log/remote/${HOST_FROM}/console/$ > {CONSOLE.LABEL}" > template ("${CONSOLE.MSG}\n")); > }; > > # --- filter console output > filter f_console_output { > facility (local7) and host ("^sysl(a)cyc.*"); > }; > > # --- log console output > log { > source (s_udp); > filter (f_console_output); > parser (p_console_output); > parser (p_console_source); > destination (d_console_output); > }; This works just fine with the last three lines of my example data above. The problem I am having is that if the console output (the text between square brackets) contains its own square brackets the message will cut off right after the first occurrence of the closing bracket. The first line of my example data will look like this: Jan 13 00:14:04.379: %EARL_NETFLOW-SP-4-TCAM_THRLD: Netflow TCAM threshold exceeded, TCAM Utilization [97% instead of Jan 13 00:14:04.379: %EARL_NETFLOW-SP-4-TCAM_THRLD: Netflow TCAM threshold exceeded, TCAM Utilization [97%] I could probably get around this by using a rewrite rule using PCRE but considering the amount of data that needs to be looked at this solution is going to be very expensive. Is there a way to make syslog-ng aware of nested quotes? If not, is there something in the pipeline to support this in future releases? If not, I will be willing to take a shot and implement this. Any pointers or suggestions are welcome. Thanks. - Michael

2 1

include branch merged
by Balazs Scheidler 14 Jan '09

14 Jan '09

Hi, After the release of syslog-ng OSE 3.0.1, I merged include file support to mainline. It is already pushed to the git repository, but also should be in tomorrow's snapshot. The syntax is: include "file-or-directory-to-be-included"; If you specify a directory, syslog-ng is going to include the files in alphabetical order. The same rules apply to as to run-parts(8). -- Bazsi

1 0

Getting named pipes to work
by Mike Rykowski 13 Jan '09

13 Jan '09

Hello, I'm new to syslog-ng and trying to get named pipes to work. I'm running version 2.0.2. I get the following messages in the log on start up: Jan 12 10:09:02 netlog-e0 netlog syslog-ng[11791]: syslog-ng starting up; version='2.0.2' Jan 12 10:09:02 netlog-e0 netlog syslog-ng[11791]: Error opening file for writing; filename='/var/log/netlog/sec-pipe', error='No such file or directory (2)' In my conf file I have: destination dst_sec { pipe("/var/log/netlog/sec-pipe")}; On the host I have the pipe setup as: prw-r--r-- 1 syslog-ng syslog-ng 0 Jan 12 10:05 sec-pipe The syslog-ng process is run with user 'syslog-ng'. So I added the owner and group options for the pipe command and set them to syslog-ng and that resulted in the same message. Any ideas? -- Mike Rykowski NU-IT Telecommunications and Network Services

4 7

syslog-ng graceful shutdown
by Rosenblum, Jason 13 Jan '09

13 Jan '09

I have recently compiled syslog-ng open source edition. I noticed that the install does not create a startup/shutdown script in /etc/init.d. What is the proper way to shutdown or reload syslog-ng gracefully? Thanks, Jason

2 1

Re: [syslog-ng] Fw: Error encountered while building syslog-ng-2.1.3 on RHEL3
by Chanchal Verma 12 Jan '09

12 Jan '09

Hi Balazs, Thanks for your expert advise. I have successfully compiled syslog-ng-2.1.3 with --enable-static-linking option. I were using old version of gcc (3.2.3) which causing compilation (make) fail. I upgraded my gcc to 4.1.2 to get rid of compilation errors. Though it is working fine till now, I have faced some error messages on standard video output while doing 'make'. I am not sure if this will impact new build syslog-ng application in terms of created problem in logging features. I am here pasting the error output: ************************************************* macros.c: In function âresult_appendâ: macros.c:137: warning: pointer targets in passing argument 2 of âg_string_append_lenâ differ in signedness macros.c: In function âlog_macro_expandâ: macros.c:149: warning: pointer targets in passing argument 2 of âresult_appendâ differ in signedness macros.c:218: warning: pointer targets in passing argument 2 of âresult_appendâ differ in signedness macros.c:238: warning: pointer targets in passing argument 2 of âresult_appendâ differ in signedness macros.c:246: warning: pointer targets in passing argument 2 of âresult_appendâ differ in signedness macros.c:268: warning: pointer targets in passing argument 2 of âresult_appendâ differ in signedness macros.c:413: warning: pointer targets in passing argument 2 of âresult_appendâ differ in signedness macros.c:432: warning: pointer targets in passing argument 2 of âresult_appendâ differ in signedness macros.c:450: warning: pointer targets in passing argument 2 of âresult_appendâ differ in signedness filter.c: In function âfilter_netmask_evalâ: filter.c:452: warning: âaddr.s_addrâ may be used uninitialized in this function logmsg.c: In function âlog_msg_parseâ: logmsg.c:151: warning: pointer targets in assignment differ in signedness logmsg.c:216: warning: pointer targets in passing argument 2 of âg_string_assign_lenâ differ in signedness logmsg.c:224: warning: pointer targets in assignment differ in signedness logmsg.c:242: warning: pointer targets in passing argument 1 of âstrlenâ differ in signedness logmsg.c:283: warning: pointer targets in passing argument 2 of âg_string_assign_lenâ differ in signedness logmsg.c:309: warning: pointer targets in passing argument 2 of âg_string_assign_lenâ differ in signedness logmsg.c:335: warning: pointer targets in passing argument 2 of âg_string_assign_lenâ differ in signedness logmsg.c:394: warning: pointer targets in assignment differ in signedness logmsg.c:398: warning: pointer targets in assignment differ in signedness logmsg.c:429: warning: pointer targets in assignment differ in signedness logmsg.c:463: warning: pointer targets in assignment differ in signedness logmsg.c:474: warning: pointer targets in assignment differ in signedness logmsg.c:486: warning: pointer targets in assignment differ in signedness logmsg.c:499: warning: pointer targets in assignment differ in signedness logmsg.c:520: warning: pointer targets in assignment differ in signedness logmsg.c:525: warning: pointer targets in assignment differ in signedness logmsg.c:530: warning: pointer targets in passing argument 2 of âg_string_assign_lenâ differ in signedness main.o(.text+0x133): In function `setup_creds': /home/soetest1/syslog-ng-2.1.3/src/main.c:324: Using 'initgroups' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking libsyslog-ng.a(misc.o)(.text+0xc4): In function `resolve_group': /home/soetest1/syslog-ng-2.1.3/src/misc.c:283: Using 'getgrnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking libsyslog-ng.a(misc.o)(.text+0x144): In function `resolve_user': /home/soetest1/syslog-ng-2.1.3/src/misc.c:258: Using 'getpwnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/local/lib/libglib-2.0.a(gutils.o)(.text+0xbd8): In function `g_get_any_init_do': /home/soetest1/glib-2.16.0/glib/gutils.c:1646: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/local/lib/libglib-2.0.a(gutils.o)(.text+0xbc8):/home/soetest1/glib-2.16.0/glib/gutils.c:1645: Using 'setpwent' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/local/lib/libglib-2.0.a(gutils.o)(.text+0xbe3):/home/soetest1/glib-2.16.0/glib/gutils.c:1647: Using 'endpwent' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/local/lib/libglib-2.0.a(gutils.o)(.text+0x9d1):/home/soetest1/glib-2.16.0/glib/gutils.c:1589: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/local/lib/libglib-2.0.a(gutils.o)(.text+0xa10):/home/soetest1/glib-2.16.0/glib/gutils.c:1595: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking libsyslog-ng.a(afinet.o)(.text+0xcbb): In function `afinet_resolve_name': /home/soetest1/syslog-ng-2.1.3/src/afinet.c:103: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking libsyslog-ng.a(misc.o)(.text+0x50a): In function `resolve_hostname': /home/soetest1/syslog-ng-2.1.3/src/misc.c:166: Using 'gethostbyaddr' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking libsyslog-ng.a(misc.o)(.text+0x464): In function `getlonghostname': /home/soetest1/syslog-ng-2.1.3/src/misc.c:71: Using 'gethostbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/local/lib/libnet.a(libnet_resolve.o)(.text+0x4dc): In function `libnet_name2addr6': : Using 'gethostbyname2' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking libsyslog-ng.a(afinet.o)(.text+0x6bb): In function `afinet_set_port': /home/soetest1/syslog-ng-2.1.3/src/afinet.c:58: Using 'getservbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking loggen.o(.text+0x6cc): In function `main': /home/soetest1/syslog-ng-2.1.3/tests/loggen/loggen.c:236: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking ************************************************ Grateful if anybody put their comment on this. With Regards, Chanchal Verma Balazs Scheidler <bazsi(a)balabit.hu> 01/12/2009 08:44 PM To Chanchal Verma/GIS/CSC@CSC cc Subject Re: Fw: [syslog-ng] Error encountered while building syslog-ng-2.1.3 on RHEL3 add -lnsl to the end of your linking command. On Mon, 2009-01-12 at 19:37 +0530, Chanchal Verma wrote: > > Hi Bazsi, > > Could you please help me is resolving error message coming to > syslog-ng, when I am trying to build is with --enable-static-linking? > > Please refer to mail tail for detail. > > > With Regards, > Chanchal Verma > > ----- Forwarded by Chanchal Verma/GIS/CSC on 01/12/2009 07:35 PM > ----- > Chanchal Verma/GIS/CSC@CSC > Sent by: > syslog-ng-bounces(a)lists.balabit.hu > > 01/09/2009 07:25 PM > Please respond to > "Syslog-ng users' and developers' > mailing list" > <syslog-ng(a)lists.balabit.hu> > > > > > To > Kostyantyn > Gushtin > <kgushtin(a)n-ix.com.ua>, syslog-ng(a)lists.balabit.hu > cc > > Subject > Re: [syslog-ng] > Error encountered > while building > syslog-ng-2.1.3 > on > RHEL3 > > > > > > > > > > Hi Kostyantyn, > > I have checked that all required static libraries (.a) are available > at /usr/lib location. I also created linked at /usr/local/lib for all > requried libraries. It is giving same error messages. > Following libraries are checked available at /usr/lib: > > libnsl.a > librt.a > libfl.a > libevtlog.a (Created linked > from /opt/soe/local/syslog-ng-2.1.3/eventlog/lib/libevtlog.a) > libnet.a > libwrap.a > > Here below is error messages: > > ----------------------------------------------------------- > Here below is error messge: > > Compilation option: > [champ@ankit-lin syslog-ng-2.1.3]# ./configure > --enable-static-linking --prefix=/opt/soe/local/syslog-ng-2.1.3 > > Make works fine uptill (Pasted last few lines): > .. > .. > if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include/glib-2.0 > -I/usr/local/lib/glib-2.0/include -I/opt/soe/local/ > syslog-ng-2.1.3/eventlog/include/eventlog -D_BSD_SOURCE > -D__BSD_SOURCE -D__FAVOR_BSD -DHAVE_NET_ETHERNET_H -D_GNU_SOUR > CE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -Wall -MT > globals.o -MD -MP -MF ".deps/globals.Tpo" \ > -c -o globals.o `test -f 'globals.c' || echo './'`globals.c; \ > then mv -f ".deps/globals.Tpo" ".deps/globals.Po"; \ > else rm -f ".deps/globals.Tpo"; exit 1; \ > fi > rm -f libsyslog-ng.a > ar cru libsyslog-ng.a misc.o utils.o messages.o syslog-names.o cfg.o > cfg-lex.o cfg-grammar.o macros.o filter.o logmsg.o l > ogpipe.o logsource.o driver.o sgroup.o dgroup.o center.o templates.o > logreader.o logwriter.o affile.o afstreams.o afuser. > o afprog.o afsocket.o afunix.o afinet.o afinter.o children.o stats.o > gsockaddr.o fdwrite.o fdread.o memtrace.o dnscache.o > apphook.o serialize.o logqueue.o afsql.o alarms.o globals.o > ranlib libsyslog-ng.a > if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include/glib-2.0 > -I/usr/local/lib/glib-2.0/include -I/opt/soe/local/ > syslog-ng-2.1.3/eventlog/include/eventlog -D_BSD_SOURCE > -D__BSD_SOURCE -D__FAVOR_BSD -DHAVE_NET_ETHERNET_H -D_GNU_SOUR > CE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -Wall -MT main.o > -MD -MP -MF ".deps/main.Tpo" \ > -c -o main.o `test -f 'main.c' || echo './'`main.c; \ > then mv -f ".deps/main.Tpo" ".deps/main.Po"; \ > else rm -f ".deps/main.Tpo"; exit 1; \ > fi > gcc -g -O2 -Wall -o syslog-ng main.o libsyslog-ng.a -static -lnsl > -lrt -lfl -L/usr/local/lib -lglib-2.0 -L/opt/soe > /local/syslog-ng-2.1.3/eventlog/lib -levtlog -lnet -lwrap > make[2]: Leaving directory `/home/soetest1/syslog-ng-2.1.3/src' > make[1]: Leaving directory `/home/soetest1/syslog-ng-2.1.3' > > Showing error message on standard output device: > > main.o(.text+0x5ec): In function `setup_creds': > /home/soetest1/syslog-ng-2.1.3/src/main.c:324: Using 'initgroups' in > statically linked applications requires at runtime t > he shared libraries from the glibc version used for linking > libsyslog-ng.a(misc.o)(.text+0x44d): In function `resolve_group': > /home/soetest1/syslog-ng-2.1.3/src/misc.c:283: Using 'getgrnam' in > statically linked applications requires at runtime the > shared libraries from the glibc version used for linking > /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/../../../libwrap.a(options.o)(.text+0x53c): In function `group_option': > : Using 'endgrent' in statically linked applications requires at > runtime the shared libraries from the glibc version used > for linking > libsyslog-ng.a(misc.o)(.text+0x3ed): In function `resolve_user': > /home/soetest1/syslog-ng-2.1.3/src/misc.c:258: Using 'getpwnam' in > statically linked applications requires at runtime the > shared libraries from the glibc version used for linking > /usr/local/lib/libglib-2.0.a(gutils.o)(.text+0xbd8): In function > `g_get_any_init_do': > /home/soetest1/glib-2.16.0/glib/gutils.c:1646: Using 'getpwuid' in > statically linked applications requires at runtime the > shared libraries from the glibc version used for linking > /usr/local/lib/libglib-2.0.a(gutils.o)(.text > +0xbc8):/home/soetest1/glib-2.16.0/glib/gutils.c:1645: Using > 'setpwent' in st > atically linked applications requires at runtime the shared libraries > from the glibc version used for linking > /usr/local/lib/libglib-2.0.a(gutils.o)(.text > +0xbe3):/home/soetest1/glib-2.16.0/glib/gutils.c:1647: Using > 'endpwent' in st > atically linked applications requires at runtime the shared libraries > from the glibc version used for linking > /usr/local/lib/libglib-2.0.a(gutils.o)(.text > +0x9d1):/home/soetest1/glib-2.16.0/glib/gutils.c:1589: Using > 'getpwnam_r' in > statically linked applications requires at runtime the shared > libraries from the glibc version used for linking > /usr/local/lib/libglib-2.0.a(gutils.o)(.text > +0xa10):/home/soetest1/glib-2.16.0/glib/gutils.c:1595: Using > 'getpwuid_r' in > statically linked applications requires at runtime the shared > libraries from the glibc version used for linking > libsyslog-ng.a(afinet.o)(.text+0x163): In function > `afinet_resolve_name': > /home/soetest1/syslog-ng-2.1.3/src/afinet.c:103: Using 'getaddrinfo' > in statically linked applications requires at runtim > e the shared libraries from the glibc version used for linking > libsyslog-ng.a(misc.o)(.text+0x1d1): In function `resolve_hostname': > /home/soetest1/syslog-ng-2.1.3/src/misc.c:166: Using 'gethostbyaddr' > in statically linked applications requires at runtim > e the shared libraries from the glibc version used for linking > libsyslog-ng.a(misc.o)(.text+0xbd): In function `getlonghostname': > /home/soetest1/syslog-ng-2.1.3/src/misc.c:71: Using 'gethostbyname' in > statically linked applications requires at runtime > the shared libraries from the glibc version used for linking > /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/../../../libnet.a(libnet_resolve.o)(.text+0x4dc): In function `libnet_name2addr6 > ': > : Using 'gethostbyname2' in statically linked applications requires at > runtime the shared libraries from the glibc versio > n used for linking > libsyslog-ng.a(afinet.o)(.text+0xb2): In function `afinet_set_port': > /home/soetest1/syslog-ng-2.1.3/src/afinet.c:58: Using 'getservbyname' > in statically linked applications requires at runti > me the shared libraries from the glibc version used for linking > /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/../../../libwrap.a(hosts_access.o)(.text+0x862): In function `host_match': > : undefined reference to `yp_get_default_domain' > collect2: ld returned 1 exit status > make[2]: *** [syslog-ng] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 > ---------------------------------------------------- > > With Regards, > Chanchal Verma > > > Kostyantyn Gushtin > <kgushtin(a)n-ix.com.ua> > > 01/09/2009 06:08 PM > > > > To > Chanchal > Verma/GIS/CSC@CSC > cc > > Subject > Re: [syslog-ng] > Error encountered > while building > syslog-ng-2.1.3 > on RHEL3 > > > > > > > > > > > Chanchal Verma wrote: > > Hi Kostyantyn, > > Yes my compilation with --enable-dynamic-linking option works fine. I > am facing problem while doing static compilation. I have followed the > given steps but still getting error while doing 'make'. > I am not sure how to use 'glib' option for compilation, I have > libglib-2.0.a in '/usr/lib'. > Now you really have problems with glibc :) . glib is just abstraction > (on unix systems it use glibc). > gcc -g -O2 -Wall -o syslog-ng main.o libsyslog-ng.a -static -lnsl > -lrt -lfl -L/usr/local/lib -lglib-2.0 -L/opt/soe > /local/syslog-ng-2.1.3/eventlog/lib -levtlog -lnet -lwrap > make[2]: Leaving directory `/home/soetest1/syslog-ng-2.1.3/src' > make[1]: Leaving directory `/home/soetest1/syslog-ng-2.1.3' > > From this command line you can retrieve info which static libraries > you need (some of them are glibc libraries, some not ). > So you must have thous libraries : libnsl.a (I saw linker error > message that it can't find this library), librt.a, libfl.a, > libevtlog.a, libnet.a, libwrap.a . Maybe you need to install > glibc-devel package and/or others that contains such libraries. > > -- > Kostyantyn Gushtin > Software engineer > N-iX LLC > Solutions for Your success > http://www.n-ix.com________________________________________________________… > Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng > Documentation: > http://www.balabit.com/support/documentation/?product=syslog-ng > FAQ: http://www.campin.net/syslog-ng/faq.html > -- Bazsi

2 1