On Tue, Oct 15, 2002 at 12:16:13PM +0200, Sean Boran wrote:
Hi,
I'm a new comer to syslog-ng and wanted to try it out on Solaris. I wish to use the 1.5 branch so I can perhaps divert to sql later..
Anyway, I run configure with no options and the make. It compiles all modules but fails on linking:
"gcc -g -O2 -Wall -I/usr/local/include/libol -D_GNU_SOURCE -o syslog-ng main.o sources.o center.o filters.o destinations.o log.o cfgfile.o cfg-grammar.o cfg-lex.o affile.o afsocket.o afunix.o afinet.o afinter.o afuser.o afstreams.o afprogram.o afremctrl.o nscache.o utils.o syslog-names.o getopt.o getopt1.o -lpthread -ldoor /usr/local/lib/libol.a -l socket -lnsl -lxnet Undefined first referenced symbol in file res_init main.o yywrap cfg-lex.o ld: fatal: Symbol referencing errors. No output written to syslog-ng collect2: ld returned 1 exit status"
- Then I though maybe I should install FLEX, so I installed flex-2.5.4a, and redid the configure and make, the result is the same.
- libol-0.3.3 compiled and installed just fine. - I'm compiled on Solaris 8 sun4u, with pretty recent patches, if that helps. - I know litte about flex, so was unsure how to proceed with debugging.. - I see one reference to res_init in main.c, but no explanation as what is is or where it comes from..
Have you any tips for me?
res_init can be solved by adding -lresolv to link flags. yywrap can be solved by linking against -lfl (part of flex) instead of simply -ll (part of lex as distributed with Solaris) res_init() seems to be platform dependant, so I added a configure test in 1.5.22 (which has been released, but not uploaded to our website) -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
In article <20021015130802.GA9694@balabit.hu>, Balazs Scheidler <bazsi@balabit.hu> wrote; } res_init() seems to be platform dependant, so I added a configure test in } 1.5.22 (which has been released, but not uploaded to our website) Any chance to fix dumping core with this version? -- Katsuhiro Kondou
On Tue, Oct 15, 2002 at 10:17:04PM +0900, Katsuhiro Kondou wrote:
In article <20021015130802.GA9694@balabit.hu>, Balazs Scheidler <bazsi@balabit.hu> wrote;
} res_init() seems to be platform dependant, so I added a configure test in } 1.5.22 (which has been released, but not uploaded to our website)
Any chance to fix dumping core with this version?
not yet, sorry. I once managed to cause a SEGFAULT, but the resulting backtrace was not usable. What seems to be true is that there's some kind of memory corruption going on. It seems to be related to TCP support, but don't I know whether destination or source. Narrowing down the problem to some component (e.g. only occurs with TCP sources or destinations) Does it happen when only a simple, persistent TCP connection exists, or it is somehow related to connection establishment? I'd need to add some more debug info to the output (e.g. dmalloc or something similar). So there are many questions, and I don't really have enough time now. It also doesn't help that it took several hours to get syslog-ng crash. I've fixed the most important things (res_init(), the problem with binding sockets, etc.) that's 1.5.22 and libol 0.3.5 -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
In article <20021015133712.GA11558@balabit.hu>, Balazs Scheidler <bazsi@balabit.hu> wrote; } Does it happen when only a simple, persistent TCP connection exists, or it } is somehow related to connection establishment? Yes and no, since when syslog-ng died it just handled incoming message from TCP, but while so syslog-ng might establish another TCP connection. -- Katsuhiro Kondou
Balazs Scheidler <bazsi@balabit.hu> wrote:
On Tue, Oct 15, 2002 at 10:17:04PM +0900, Katsuhiro Kondou wrote:
Any chance to fix dumping core with this version?
not yet, sorry. I once managed to cause a SEGFAULT, but the resulting backtrace was not usable. What seems to be true is that there's some kind of memory corruption going on. It seems to be related to TCP support, but don't I know whether destination or source. Narrowing down the problem to some component (e.g. only occurs with TCP sources or destinations)
I only see segfaults on our central syslog server, not clients, so I'd say source has been my experience.
Does it happen when only a simple, persistent TCP connection exists, or it is somehow related to connection establishment?
Hmm, I'll see if I can pinpoint that. I know nothing is ever written to disk (not a log line, files/directories aren't created, nothing) so it's before that happens.
I'd need to add some more debug info to the output (e.g. dmalloc or something similar).
So there are many questions, and I don't really have enough time now. It also doesn't help that it took several hours to get syslog-ng crash.
I've fixed the most important things (res_init(), the problem with binding sockets, etc.) that's 1.5.22 and libol 0.3.5
Luckily the patch posted to bugtraq applies to several versions :-)
Thanks, yes that works fine (I changed the LIBS in the Makefile to include "-lresolv -lfl "). Regards, Sean
-----Original Message----- From: Balazs Scheidler [mailto:bazsi@balabit.hu] Sent: Dienstag, 15. Oktober 2002 15:08 To: Sean Boran Cc: syslog-ng@lists.balabit.hu Subject: Re: syslog-ng-1.5.21 on Solaris8
On Tue, Oct 15, 2002 at 12:16:13PM +0200, Sean Boran wrote:
Hi,
I'm a new comer to syslog-ng and wanted to try it out on Solaris. I wish to use the 1.5 branch so I can perhaps divert to sql later..
Anyway, I run configure with no options and the make. It compiles all modules but fails on linking:
"gcc -g -O2 -Wall -I/usr/local/include/libol -D_GNU_SOURCE -o syslog-ng main.o sources.o center.o filters.o destinations.o log.o cfgfile.o cfg-grammar.o cfg-lex.o affile.o afsocket.o afunix.o afinet.o afinter.o afuser.o afstreams.o afprogram.o afremctrl.o nscache.o utils.o syslog-names.o getopt.o getopt1.o -lpthread -ldoor /usr/local/lib/libol.a -l socket -lnsl -lxnet Undefined first referenced symbol in file res_init main.o yywrap cfg-lex.o ld: fatal: Symbol referencing errors. No output written to syslog-ng collect2: ld returned 1 exit status"
- Then I though maybe I should install FLEX, so I installed flex-2.5.4a, and redid the configure and make, the result is the same.
- libol-0.3.3 compiled and installed just fine. - I'm compiled on Solaris 8 sun4u, with pretty recent patches, if that helps. - I know litte about flex, so was unsure how to proceed with debugging.. - I see one reference to res_init in main.c, but no explanation as what is is or where it comes from..
Have you any tips for me?
res_init can be solved by adding -lresolv to link flags.
yywrap can be solved by linking against -lfl (part of flex) instead of simply -ll (part of lex as distributed with Solaris)
res_init() seems to be platform dependant, so I added a configure test in 1.5.22 (which has been released, but not uploaded to our website)
-- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
participants (4)
-
Balazs Scheidler
-
Katsuhiro Kondou
-
Sean Boran
-
William Yodlowsky