Syslog-ng experiences a segmentation fault whenever a message is processed: <stop syslogd first> # syslog-ng -d -d -v -F -e syslog-ng starting up; version='2.0.5' Incoming log entry; line='<28>Nov 9 10:11:24 xinetd[12285]: Exiting...' Filter rule evaluation begins; filter_rule='f_emerg' Filter node evaluation result; filter_result='not-match', filter_type='level' Filter rule evaluation result; filter_result='not-match', filter_rule='f_emerg' Filter rule evaluation begins; filter_rule='f_secure' Filter node evaluation result; filter_result='not-match', filter_type='facility' Filter rule evaluation result; filter_result='not-match', filter_rule='f_secure' Filter rule evaluation begins; filter_rule='f_cron' Filter node evaluation result; filter_result='not-match', filter_type='facility' Filter rule evaluation result; filter_result='not-match', filter_rule='f_cron' Filter rule evaluation begins; filter_rule='f_spooler' Filter node evaluation result; filter_result='not-match', filter_type='facility' Filter node evaluation result; filter_result='not-match', filter_type='AND' Filter rule evaluation result; filter_result='not-match', filter_rule='f_spooler' Filter rule evaluation begins; filter_rule='f_local7' Filter node evaluation result; filter_result='not-match', filter_type='facility' Filter rule evaluation result; filter_result='not-match', filter_rule='f_local7' Filter rule evaluation begins; filter_rule='f_messages' Filter node evaluation result; filter_result='match', filter_type='level' Filter rule evaluation result; filter_result='match', filter_rule='f_messages' Initializing destination file writer; template='/var/log/messages', filename='/var/log/messages' Segmentation fault Platform is VMware Guest running RHEL5 x86_64. I used the following steps to build from source: Download eventlog-0.2.5 source ./configure --prefix=/usr --sysconfdir=/etc make make install export PKG_CONFIG_PATH="/usr/lib/pkgconfig" Download syslog-ng-2.0.5 source. ./configure --sysconfdir=/etc make make install I've basically used the supplied config file for Redhat in contrib folder. I'm uncommented the relevant lines in order to use syslog-ng in place of syslogd. Syslog-ng runs OK but as soon as it tries to process a syslog message, it dies with a segmentation fault. Any ideas anyone? Daniel This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments. It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email. For information about our privacy policy, visit the IMC Communications website at www.imc.net.au This email has been checked by IMC's SMTP gateway. -&-
On Thu, 2007-11-08 at 13:32 +1100, Daniel Szmandiuk wrote:
Syslog-ng experiences a segmentation fault whenever a message is processed:
<stop syslogd first> # syslog-ng -d -d -v -F -e syslog-ng starting up; version='2.0.5' Incoming log entry; line='<28>Nov 9 10:11:24 xinetd[12285]: Exiting...' Filter rule evaluation begins; filter_rule='f_emerg' Filter node evaluation result; filter_result='not-match', filter_type='level' Filter rule evaluation result; filter_result='not-match', filter_rule='f_emerg' Filter rule evaluation begins; filter_rule='f_secure' Filter node evaluation result; filter_result='not-match', filter_type='facility' Filter rule evaluation result; filter_result='not-match', filter_rule='f_secure' Filter rule evaluation begins; filter_rule='f_cron' Filter node evaluation result; filter_result='not-match', filter_type='facility' Filter rule evaluation result; filter_result='not-match', filter_rule='f_cron' Filter rule evaluation begins; filter_rule='f_spooler' Filter node evaluation result; filter_result='not-match', filter_type='facility' Filter node evaluation result; filter_result='not-match', filter_type='AND' Filter rule evaluation result; filter_result='not-match', filter_rule='f_spooler' Filter rule evaluation begins; filter_rule='f_local7' Filter node evaluation result; filter_result='not-match', filter_type='facility' Filter rule evaluation result; filter_result='not-match', filter_rule='f_local7' Filter rule evaluation begins; filter_rule='f_messages' Filter node evaluation result; filter_result='match', filter_type='level' Filter rule evaluation result; filter_result='match', filter_rule='f_messages' Initializing destination file writer; template='/var/log/messages', filename='/var/log/messages' Segmentation fault
Platform is VMware Guest running RHEL5 x86_64.
I used the following steps to build from source:
Download eventlog-0.2.5 source ./configure --prefix=/usr --sysconfdir=/etc make make install
export PKG_CONFIG_PATH="/usr/lib/pkgconfig"
Download syslog-ng-2.0.5 source. ./configure --sysconfdir=/etc make make install
I've basically used the supplied config file for Redhat in contrib folder. I'm uncommented the relevant lines in order to use syslog-ng in place of syslogd.
Syslog-ng runs OK but as soon as it tries to process a syslog message, it dies with a segmentation fault.
Any ideas anyone?
Daniel
Could you generate a backtrace, with debugging symbols enabled? E.g. make sure that -g is present in the compiler options, enable core files using "ulimit -c", wait while syslog-ng crashes and then: gdb /usr/sbin/syslog-ng -c <path-to-core-file> (gdb) bt full and post the results. -- Bazsi
Here's the backtrace: GNU gdb Red Hat Linux (6.5-16.el5rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1". Reading symbols from /lib64/libnsl.so.1...done. Loaded symbols for /lib64/libnsl.so.1 Reading symbols from /lib64/librt.so.1...done. Loaded symbols for /lib64/librt.so.1 Reading symbols from /lib64/libc.so.6...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /lib64/libpthread.so.0...done. Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/ld-linux-x86-64.so.2...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Core was generated by `syslog-ng -d -d -v -e -F -f /etc/syslog-ng.conf'. Program terminated with signal 11, Segmentation fault. #0 0x00000035eb071f6b in free () from /lib64/libc.so.6 (gdb) bt full #0 0x00000035eb071f6b in free () from /lib64/libc.so.6 No symbol table info available. #1 0x000000000040e140 in log_msg_clear_matches (self=0x14b0f8b0) at logmsg.c:512 i = 0 #2 0x000000000040e1c2 in log_msg_free (self=0x14b0f8b0) at logmsg.c:532 No locals. #3 0x000000000040e273 in log_msg_unref (self=0x14b0f8b0) at logmsg.c:562 __PRETTY_FUNCTION__ = "log_msg_unref" #4 0x0000000000410cce in log_writer_flush_log (self=0x14b0fb70, fd=0x14b0f820) at logwriter.c:324 lm = (LogMessage *) 0x14b0f8b0 path_flags = 1 line = (GString *) 0x14b0f040 rc = 1194600290 #5 0x00000000004106b4 in log_writer_fd_dispatch (source=0x14b0fbf0, callback=0, user_data=0x0) at logwriter.c:144 self = (LogWriterWatch *) 0x14b0fbf0 #6 0x000000000041ee09 in g_main_context_dispatch () No symbol table info available. #7 0x0000000000421886 in g_main_context_iterate () No symbol table info available. #8 0x0000000000421d0a in g_main_context_iteration () ---Type <return> to continue, or q <return> to quit--- No symbol table info available. #9 0x0000000000404aed in main_loop_run (cfg=0x7fffe3d3ac30) at main.c:164 main_loop = (GMainLoop *) 0x14b0f600 iters = 0 stats_timer_id = 4 #10 0x0000000000405144 in main (argc=8, argv=0x7fffe3d3ad38) at main.c:426 cfg = (GlobalConfig *) 0x14b01d40 syslog_ng_options = {{name = 0x441583 "cfgfile", has_arg = 1, flag = 0x0, val = 102}, {name = 0x44158b "pidfile", has_arg = 1, flag = 0x0, val = 112}, {name = 0x441593 "debug", has_arg = 0, flag = 0x0, val = 100}, {name = 0x441599 "syntax-only", has_arg = 0, flag = 0x0, val = 115}, {name = 0x4415a5 "verbose", has_arg = 0, flag = 0x0, val = 118}, {name = 0x4415ad "foreground", has_arg = 0, flag = 0x0, val = 70}, {name = 0x4415b8 "help", has_arg = 0, flag = 0x0, val = 104}, { name = 0x441497 "version", has_arg = 0, flag = 0x0, val = 86}, { name = 0x4415bd "chroot", has_arg = 1, flag = 0x0, val = 67}, { name = 0x4415c4 "user", has_arg = 1, flag = 0x0, val = 117}, { name = 0x4415c9 "group", has_arg = 1, flag = 0x0, val = 103}, { name = 0x4415cf "stderr", has_arg = 0, flag = 0x0, val = 101}, { name = 0x4415d6 "yydebug", has_arg = 0, flag = 0x0, val = 121}, { name = 0x0, has_arg = 0, flag = 0x0, val = 0}} syntax_only = 0 log_to_stderr = 1 ---Type <return> to continue, or q <return> to quit--- persist = (PersistentConfig *) 0x14b071e0 opt = -1 rc = 0 (gdb) (gdb) Hope this helps. Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu on behalf of Balazs Scheidler Sent: Thu 11/8/2007 6:29 PM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault On Thu, 2007-11-08 at 13:32 +1100, Daniel Szmandiuk wrote:
Syslog-ng experiences a segmentation fault whenever a message is processed:
<stop syslogd first> # syslog-ng -d -d -v -F -e syslog-ng starting up; version='2.0.5' Incoming log entry; line='<28>Nov 9 10:11:24 xinetd[12285]: Exiting...' Filter rule evaluation begins; filter_rule='f_emerg' Filter node evaluation result; filter_result='not-match', filter_type='level' Filter rule evaluation result; filter_result='not-match', filter_rule='f_emerg' Filter rule evaluation begins; filter_rule='f_secure' Filter node evaluation result; filter_result='not-match', filter_type='facility' Filter rule evaluation result; filter_result='not-match', filter_rule='f_secure' Filter rule evaluation begins; filter_rule='f_cron' Filter node evaluation result; filter_result='not-match', filter_type='facility' Filter rule evaluation result; filter_result='not-match', filter_rule='f_cron' Filter rule evaluation begins; filter_rule='f_spooler' Filter node evaluation result; filter_result='not-match', filter_type='facility' Filter node evaluation result; filter_result='not-match', filter_type='AND' Filter rule evaluation result; filter_result='not-match', filter_rule='f_spooler' Filter rule evaluation begins; filter_rule='f_local7' Filter node evaluation result; filter_result='not-match', filter_type='facility' Filter rule evaluation result; filter_result='not-match', filter_rule='f_local7' Filter rule evaluation begins; filter_rule='f_messages' Filter node evaluation result; filter_result='match', filter_type='level' Filter rule evaluation result; filter_result='match', filter_rule='f_messages' Initializing destination file writer; template='/var/log/messages', filename='/var/log/messages' Segmentation fault
Platform is VMware Guest running RHEL5 x86_64.
I used the following steps to build from source:
Download eventlog-0.2.5 source ./configure --prefix=/usr --sysconfdir=/etc make make install
export PKG_CONFIG_PATH="/usr/lib/pkgconfig"
Download syslog-ng-2.0.5 source. ./configure --sysconfdir=/etc make make install
I've basically used the supplied config file for Redhat in contrib folder. I'm uncommented the relevant lines in order to use syslog-ng in place of syslogd.
Syslog-ng runs OK but as soon as it tries to process a syslog message, it dies with a segmentation fault.
Any ideas anyone?
Daniel
Could you generate a backtrace, with debugging symbols enabled? E.g. make sure that -g is present in the compiler options, enable core files using "ulimit -c", wait while syslog-ng crashes and then: gdb /usr/sbin/syslog-ng -c <path-to-core-file> (gdb) bt full and post the results. -- Bazsi _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments. It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email. For information about our privacy policy, visit the IMC Communications website at www.imc.net.au This email has been checked by IMC's SMTP gateway. -&-
Hm.. the same has been reported on a mips64 system. This must be a 64 bit related issue, then. I'll try to get a 64 compile environment. Anyone else who uses syslog-ng 2.0.x on 64 bit systems? On Thu, 2007-11-08 at 23:34 +1100, Daniel Szmandiuk wrote:
Here's the backtrace: GNU gdb Red Hat Linux (6.5-16.el5rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1".
-- Bazsi
I was hitting this issue on mips64 (had reported it on this list). Debugging the issue the culprit seemed to be the call g_free(self->re_matches) in function log_msg_clear_matches (logmsg.c). The values of the self->re_matches was zero when it was getting segfault but the pointer self->re_matches had a non-null value. Making the g_free conditional seemed to work for me. I was able to get past this issue but was seeing some other strange behavior and could not get the syslog-ng to work on mips64. I was not able to get the messages to log to the log file /var/log/messages (reported it on this list). Debugging the issue it seemed the g_string_printf in log_write_format_log function was not working properly on 64bit mips and thus the log was never written to the file or any other output device. -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Thursday, November 08, 2007 7:21 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault Hm.. the same has been reported on a mips64 system. This must be a 64 bit related issue, then. I'll try to get a 64 compile environment. Anyone else who uses syslog-ng 2.0.x on 64 bit systems? On Thu, 2007-11-08 at 23:34 +1100, Daniel Szmandiuk wrote:
Here's the backtrace: GNU gdb Red Hat Linux (6.5-16.el5rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1".
-- Bazsi _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
Shashank, Did you successfully get any older version of syslog-ng compiled & working on your mips64 system? I'm trying to get a syslog-ng system up and running for testing fairly quickly at the moment. Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Shashank Vinchurkar Sent: Friday, 9 November 2007 5:35 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault I was hitting this issue on mips64 (had reported it on this list). Debugging the issue the culprit seemed to be the call g_free(self->re_matches) in function log_msg_clear_matches (logmsg.c). The values of the self->re_matches was zero when it was getting segfault but the pointer self->re_matches had a non-null value. Making the g_free conditional seemed to work for me. I was able to get past this issue but was seeing some other strange behavior and could not get the syslog-ng to work on mips64. I was not able to get the messages to log to the log file /var/log/messages (reported it on this list). Debugging the issue it seemed the g_string_printf in log_write_format_log function was not working properly on 64bit mips and thus the log was never written to the file or any other output device. -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Thursday, November 08, 2007 7:21 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault Hm.. the same has been reported on a mips64 system. This must be a 64 bit related issue, then. I'll try to get a 64 compile environment. Anyone else who uses syslog-ng 2.0.x on 64 bit systems? On Thu, 2007-11-08 at 23:34 +1100, Daniel Szmandiuk wrote:
Here's the backtrace: GNU gdb Red Hat Linux (6.5-16.el5rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1".
-- Bazsi _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments. It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email. For information about our privacy policy, visit the IMC Communications website at www.imc.net.au This email has been checked by IMC's SMTP gateway. -&-
Daniel, I didn't try with older version of syslog-ng. You can get around the first problem with the changes I had suggested. The second problem seemed to be related to glib library. I could get around it by hacking the value of the Gstring returned by the g_string_printf. But it didn't seem to be right solution. I tried older version of glib but it didn't seem to work. I was cross compiling both syslog-ng and glib. -Shashank -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Daniel Szmandiuk Sent: Thursday, November 08, 2007 2:33 PM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault Shashank, Did you successfully get any older version of syslog-ng compiled & working on your mips64 system? I'm trying to get a syslog-ng system up and running for testing fairly quickly at the moment. Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Shashank Vinchurkar Sent: Friday, 9 November 2007 5:35 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault I was hitting this issue on mips64 (had reported it on this list). Debugging the issue the culprit seemed to be the call g_free(self->re_matches) in function log_msg_clear_matches (logmsg.c). The values of the self->re_matches was zero when it was getting segfault but the pointer self->re_matches had a non-null value. Making the g_free conditional seemed to work for me. I was able to get past this issue but was seeing some other strange behavior and could not get the syslog-ng to work on mips64. I was not able to get the messages to log to the log file /var/log/messages (reported it on this list). Debugging the issue it seemed the g_string_printf in log_write_format_log function was not working properly on 64bit mips and thus the log was never written to the file or any other output device. -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Thursday, November 08, 2007 7:21 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault Hm.. the same has been reported on a mips64 system. This must be a 64 bit related issue, then. I'll try to get a 64 compile environment. Anyone else who uses syslog-ng 2.0.x on 64 bit systems? On Thu, 2007-11-08 at 23:34 +1100, Daniel Szmandiuk wrote:
Here's the backtrace: GNU gdb Red Hat Linux (6.5-16.el5rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1".
-- Bazsi _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments. It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email. For information about our privacy policy, visit the IMC Communications website at www.imc.net.au This email has been checked by IMC's SMTP gateway. -&- _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
Shashank, Unfortunately I'm no C programmer, but I can hack code with some instructions. I'm not quite sure what I need to do get around the problems. Can you supply me with some more detailed instructions? Something like "change line x from A to B" would be great... Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Shashank Vinchurkar Sent: Friday, 9 November 2007 10:44 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault Daniel, I didn't try with older version of syslog-ng. You can get around the first problem with the changes I had suggested. The second problem seemed to be related to glib library. I could get around it by hacking the value of the Gstring returned by the g_string_printf. But it didn't seem to be right solution. I tried older version of glib but it didn't seem to work. I was cross compiling both syslog-ng and glib. -Shashank -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Daniel Szmandiuk Sent: Thursday, November 08, 2007 2:33 PM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault Shashank, Did you successfully get any older version of syslog-ng compiled & working on your mips64 system? I'm trying to get a syslog-ng system up and running for testing fairly quickly at the moment. Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Shashank Vinchurkar Sent: Friday, 9 November 2007 5:35 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault I was hitting this issue on mips64 (had reported it on this list). Debugging the issue the culprit seemed to be the call g_free(self->re_matches) in function log_msg_clear_matches (logmsg.c). The values of the self->re_matches was zero when it was getting segfault but the pointer self->re_matches had a non-null value. Making the g_free conditional seemed to work for me. I was able to get past this issue but was seeing some other strange behavior and could not get the syslog-ng to work on mips64. I was not able to get the messages to log to the log file /var/log/messages (reported it on this list). Debugging the issue it seemed the g_string_printf in log_write_format_log function was not working properly on 64bit mips and thus the log was never written to the file or any other output device. -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Thursday, November 08, 2007 7:21 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault Hm.. the same has been reported on a mips64 system. This must be a 64 bit related issue, then. I'll try to get a 64 compile environment. Anyone else who uses syslog-ng 2.0.x on 64 bit systems? On Thu, 2007-11-08 at 23:34 +1100, Daniel Szmandiuk wrote:
Here's the backtrace: GNU gdb Red Hat Linux (6.5-16.el5rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1".
-- Bazsi _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments. It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email. For information about our privacy policy, visit the IMC Communications website at www.imc.net.au This email has been checked by IMC's SMTP gateway. -&- _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
file : logmsg.c, function : void log_msg_clear_matches(LogMessage *self) replace line : g_free(self->re_matches); with if (self->num_re_matches) { g_free(self->re_matches); } -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Daniel Szmandiuk Sent: Thursday, November 08, 2007 4:32 PM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault Shashank, Unfortunately I'm no C programmer, but I can hack code with some instructions. I'm not quite sure what I need to do get around the problems. Can you supply me with some more detailed instructions? Something like "change line x from A to B" would be great... Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Shashank Vinchurkar Sent: Friday, 9 November 2007 10:44 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault Daniel, I didn't try with older version of syslog-ng. You can get around the first problem with the changes I had suggested. The second problem seemed to be related to glib library. I could get around it by hacking the value of the Gstring returned by the g_string_printf. But it didn't seem to be right solution. I tried older version of glib but it didn't seem to work. I was cross compiling both syslog-ng and glib. -Shashank -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Daniel Szmandiuk Sent: Thursday, November 08, 2007 2:33 PM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault Shashank, Did you successfully get any older version of syslog-ng compiled & working on your mips64 system? I'm trying to get a syslog-ng system up and running for testing fairly quickly at the moment. Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Shashank Vinchurkar Sent: Friday, 9 November 2007 5:35 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault I was hitting this issue on mips64 (had reported it on this list). Debugging the issue the culprit seemed to be the call g_free(self->re_matches) in function log_msg_clear_matches (logmsg.c). The values of the self->re_matches was zero when it was getting segfault but the pointer self->re_matches had a non-null value. Making the g_free conditional seemed to work for me. I was able to get past this issue but was seeing some other strange behavior and could not get the syslog-ng to work on mips64. I was not able to get the messages to log to the log file /var/log/messages (reported it on this list). Debugging the issue it seemed the g_string_printf in log_write_format_log function was not working properly on 64bit mips and thus the log was never written to the file or any other output device. -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Thursday, November 08, 2007 7:21 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault Hm.. the same has been reported on a mips64 system. This must be a 64 bit related issue, then. I'll try to get a 64 compile environment. Anyone else who uses syslog-ng 2.0.x on 64 bit systems? On Thu, 2007-11-08 at 23:34 +1100, Daniel Szmandiuk wrote:
Here's the backtrace: GNU gdb Red Hat Linux (6.5-16.el5rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1".
-- Bazsi _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments. It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email. For information about our privacy policy, visit the IMC Communications website at www.imc.net.au This email has been checked by IMC's SMTP gateway. -&- _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
Yes, I am using syslog-ng 2.0.5 on redhat4 64bit and not having any problem with crashing etc. Anything I can help with I will try and do. Evan. Balazs Scheidler wrote:
Hm.. the same has been reported on a mips64 system. This must be a 64 bit related issue, then. I'll try to get a 64 compile environment.
Anyone else who uses syslog-ng 2.0.x on 64 bit systems?
On Thu, 2007-11-08 at 23:34 +1100, Daniel Szmandiuk wrote:
Here's the backtrace: GNU gdb Red Hat Linux (6.5-16.el5rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1".
-- Evan Rempel erempel@uvic.ca Senior Programmer Analyst 250.721.7691 Computing Services University of Victoria
Ditto. I also am running it on 64bit hosts (CentOS 4 & Fedora Core 3), albeit only for a couple days now (2.0.5 that is) - without any segfault'ing issues. Evan Rempel wrote:
Yes, I am using syslog-ng 2.0.5 on redhat4 64bit and not having any problem with crashing etc.
Anything I can help with I will try and do.
Evan.
Balazs Scheidler wrote:
Hm.. the same has been reported on a mips64 system. This must be a 64 bit related issue, then. I'll try to get a 64 compile environment.
Anyone else who uses syslog-ng 2.0.x on 64 bit systems?
On Thu, 2007-11-08 at 23:34 +1100, Daniel Szmandiuk wrote:
Here's the backtrace: GNU gdb Red Hat Linux (6.5-16.el5rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1".
Scott / Evan Did you compile from source or did you use the supplied binaries? Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of ScottO Sent: Friday, 9 November 2007 5:59 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault Ditto. I also am running it on 64bit hosts (CentOS 4 & Fedora Core 3), albeit only for a couple days now (2.0.5 that is) - without any segfault'ing issues. Evan Rempel wrote:
Yes, I am using syslog-ng 2.0.5 on redhat4 64bit and not having any problem with crashing etc.
Anything I can help with I will try and do.
Evan.
Balazs Scheidler wrote:
Hm.. the same has been reported on a mips64 system. This must be a 64
bit related issue, then. I'll try to get a 64 compile environment.
Anyone else who uses syslog-ng 2.0.x on 64 bit systems?
On Thu, 2007-11-08 at 23:34 +1100, Daniel Szmandiuk wrote:
Here's the backtrace: GNU gdb Red Hat Linux (6.5-16.el5rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and
you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1".
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments. It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email. For information about our privacy policy, visit the IMC Communications website at www.imc.net.au This email has been checked by IMC's SMTP gateway. -&-
I compiled from source. env PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure --enable-static-linking --enable-tcp-wrapper=no glib2-2.4.7-1 glib2-devel-2.4.7-1 gcc-c++-3.4.6-8 gcc-3.4.6-8 Evan. Daniel Szmandiuk wrote:
Scott / Evan
Did you compile from source or did you use the supplied binaries?
Daniel
-----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of ScottO Sent: Friday, 9 November 2007 5:59 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault
Ditto.
I also am running it on 64bit hosts (CentOS 4 & Fedora Core 3), albeit only for a couple days now (2.0.5 that is) - without any segfault'ing issues.
Evan Rempel wrote:
Yes, I am using syslog-ng 2.0.5 on redhat4 64bit and not having any problem with crashing etc.
Anything I can help with I will try and do.
Evan.
Balazs Scheidler wrote:
Hm.. the same has been reported on a mips64 system. This must be a 64
bit related issue, then. I'll try to get a 64 compile environment.
Anyone else who uses syslog-ng 2.0.x on 64 bit systems?
On Thu, 2007-11-08 at 23:34 +1100, Daniel Szmandiuk wrote:
Here's the backtrace: GNU gdb Red Hat Linux (6.5-16.el5rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and
you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1".
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments.
It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email.
For information about our privacy policy, visit the IMC Communications website at www.imc.net.au
This email has been checked by IMC's SMTP gateway. -&- _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
-- Evan Rempel erempel@uvic.ca Senior Programmer Analyst 250.721.7691 Computing Services University of Victoria
Evan, Please excuse by ignorance but what do the following options do? --enable-static-linking --enable-tcp-wrapper=no Thanks in advance, Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Evan Rempel Sent: Friday, 9 November 2007 9:31 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault I compiled from source. env PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure --enable-static-linking --enable-tcp-wrapper=no glib2-2.4.7-1 glib2-devel-2.4.7-1 gcc-c++-3.4.6-8 gcc-3.4.6-8 Evan. Daniel Szmandiuk wrote:
Scott / Evan
Did you compile from source or did you use the supplied binaries?
Daniel
-----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of ScottO Sent: Friday, 9 November 2007 5:59 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault
Ditto.
I also am running it on 64bit hosts (CentOS 4 & Fedora Core 3), albeit
only for a couple days now (2.0.5 that is) - without any segfault'ing issues.
Evan Rempel wrote:
Yes, I am using syslog-ng 2.0.5 on redhat4 64bit and not having any problem with crashing etc.
Anything I can help with I will try and do.
Evan.
Balazs Scheidler wrote:
Hm.. the same has been reported on a mips64 system. This must be a 64
bit related issue, then. I'll try to get a 64 compile environment.
Anyone else who uses syslog-ng 2.0.x on 64 bit systems?
On Thu, 2007-11-08 at 23:34 +1100, Daniel Szmandiuk wrote:
Here's the backtrace: GNU gdb Red Hat Linux (6.5-16.el5rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and
you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1".
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments.
It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email.
For information about our privacy policy, visit the IMC Communications
website at www.imc.net.au
This email has been checked by IMC's SMTP gateway. -&- _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
-- Evan Rempel erempel@uvic.ca Senior Programmer Analyst 250.721.7691 Computing Services University of Victoria _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
These options are documented in the "./configure --help" which is the script provided with the source tree for compilation, but since you are already reading this... --enable-static-linking makes the compiled binary independent from anything else on the system. The intent is to provide an application that will not get "broken" when shared libraries are updated sometime in the future. There are a couple of caveates about this, but I'm not going to get into that here. --enable-tcp-wrapper=no makes the resulting syslog-ng NOT check the /etc/hosts.allow and /etc/hosts.deny files for remote connection authorization. Evan. Daniel Szmandiuk wrote:
Evan,
Please excuse by ignorance but what do the following options do?
--enable-static-linking --enable-tcp-wrapper=no
Thanks in advance,
Daniel
-----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Evan Rempel Sent: Friday, 9 November 2007 9:31 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault
I compiled from source.
env PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure --enable-static-linking --enable-tcp-wrapper=no
glib2-2.4.7-1 glib2-devel-2.4.7-1 gcc-c++-3.4.6-8 gcc-3.4.6-8
Evan.
Daniel Szmandiuk wrote:
Scott / Evan
Did you compile from source or did you use the supplied binaries?
Daniel
-----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of ScottO Sent: Friday, 9 November 2007 5:59 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault
Ditto.
I also am running it on 64bit hosts (CentOS 4 & Fedora Core 3), albeit
only for a couple days now (2.0.5 that is) - without any segfault'ing issues.
Evan Rempel wrote:
Yes, I am using syslog-ng 2.0.5 on redhat4 64bit and not having any problem with crashing etc.
Anything I can help with I will try and do.
Evan.
Balazs Scheidler wrote:
Hm.. the same has been reported on a mips64 system. This must be a 64 bit related issue, then. I'll try to get a 64 compile environment.
Anyone else who uses syslog-ng 2.0.x on 64 bit systems?
On Thu, 2007-11-08 at 23:34 +1100, Daniel Szmandiuk wrote:
Here's the backtrace: GNU gdb Red Hat Linux (6.5-16.el5rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1".
Evan, That's the sort of answer I was after. Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Evan Rempel Sent: Friday, 9 November 2007 10:10 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault These options are documented in the "./configure --help" which is the script provided with the source tree for compilation, but since you are already reading this... --enable-static-linking makes the compiled binary independent from anything else on the system. The intent is to provide an application that will not get "broken" when shared libraries are updated sometime in the future. There are a couple of caveates about this, but I'm not going to get into that here. --enable-tcp-wrapper=no makes the resulting syslog-ng NOT check the /etc/hosts.allow and /etc/hosts.deny files for remote connection authorization. Evan. Daniel Szmandiuk wrote:
Evan,
Please excuse by ignorance but what do the following options do?
--enable-static-linking --enable-tcp-wrapper=no
Thanks in advance,
Daniel
-----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Evan Rempel Sent: Friday, 9 November 2007 9:31 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault
I compiled from source.
env PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure --enable-static-linking --enable-tcp-wrapper=no
glib2-2.4.7-1 glib2-devel-2.4.7-1 gcc-c++-3.4.6-8 gcc-3.4.6-8
Evan.
Daniel Szmandiuk wrote:
Scott / Evan
Did you compile from source or did you use the supplied binaries?
Daniel
-----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of ScottO Sent: Friday, 9 November 2007 5:59 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault
Ditto.
I also am running it on 64bit hosts (CentOS 4 & Fedora Core 3), albeit
only for a couple days now (2.0.5 that is) - without any segfault'ing
issues.
Evan Rempel wrote:
Yes, I am using syslog-ng 2.0.5 on redhat4 64bit and not having any problem with crashing etc.
Anything I can help with I will try and do.
Evan.
Balazs Scheidler wrote:
Hm.. the same has been reported on a mips64 system. This must be a 64 bit related issue, then. I'll try to get a 64 compile environment.
Anyone else who uses syslog-ng 2.0.x on 64 bit systems?
On Thu, 2007-11-08 at 23:34 +1100, Daniel Szmandiuk wrote:
Here's the backtrace: GNU gdb Red Hat Linux (6.5-16.el5rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for
details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1".
syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments. It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email. For information about our privacy policy, visit the IMC Communications website at www.imc.net.au This email has been checked by IMC's SMTP gateway. -&-
Bazsi, FYI, I'm running the following: glib2-2.12.3-2.fc6 glib2-devel-2.12.3-2.fc6 gcc-4.1.1-52.el5.2 gcc-c++-4.1.1-52.el5.2 I was unable to compile using the "--enable-static-linking" option. Many complaints... Here's a snapshot: /root/libnet/src/libnet_resolve.c:254: warning: Using 'gethostbyname2' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking libsyslog-ng.a(afinet.o): In function `afinet_set_port': /root/syslog-ng-2.0.5/src/afinet.c:58: warning: Using 'getservbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /lib/../lib64/libglib-2.0.a(gtimer.o): In function `g_timer_elapsed': (.text+0x260): undefined reference to `clock_gettime' /lib/../lib64/libglib-2.0.a(gtimer.o): In function `g_timer_continue': (.text+0x311): undefined reference to `clock_gettime' /lib/../lib64/libglib-2.0.a(gtimer.o): In function `g_timer_new': (.text+0x497): undefined reference to `clock_gettime' /lib/../lib64/libglib-2.0.a(gtimer.o): In function `g_timer_reset': (.text+0x3af): undefined reference to `clock_gettime' /lib/../lib64/libglib-2.0.a(gtimer.o): In function `g_timer_stop': (.text+0x3e4): undefined reference to `clock_gettime' /lib/../lib64/libglib-2.0.a(gtimer.o):(.text+0x413): more undefined references to `clock_gettime' follow Not sure if this is relevant. But maybe points you in the right direction? Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Evan Rempel Sent: Friday, 9 November 2007 9:31 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault I compiled from source. env PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure --enable-static-linking --enable-tcp-wrapper=no glib2-2.4.7-1 glib2-devel-2.4.7-1 gcc-c++-3.4.6-8 gcc-3.4.6-8 Evan. Daniel Szmandiuk wrote:
Scott / Evan
Did you compile from source or did you use the supplied binaries?
Daniel
-----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of ScottO Sent: Friday, 9 November 2007 5:59 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault
Ditto.
I also am running it on 64bit hosts (CentOS 4 & Fedora Core 3), albeit
only for a couple days now (2.0.5 that is) - without any segfault'ing issues.
Evan Rempel wrote:
Yes, I am using syslog-ng 2.0.5 on redhat4 64bit and not having any problem with crashing etc.
Anything I can help with I will try and do.
Evan.
Balazs Scheidler wrote:
Hm.. the same has been reported on a mips64 system. This must be a 64
bit related issue, then. I'll try to get a 64 compile environment.
Anyone else who uses syslog-ng 2.0.x on 64 bit systems?
On Thu, 2007-11-08 at 23:34 +1100, Daniel Szmandiuk wrote:
Here's the backtrace: GNU gdb Red Hat Linux (6.5-16.el5rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and
you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1".
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments.
It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email.
For information about our privacy policy, visit the IMC Communications
website at www.imc.net.au
This email has been checked by IMC's SMTP gateway. -&- _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
-- Evan Rempel erempel@uvic.ca Senior Programmer Analyst 250.721.7691 Computing Services University of Victoria _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
from source as well. export PKG_CONFIG=/usr/local/lib/pkgconfig ./configure; make; make install Scott Daniel Szmandiuk wrote:
Scott / Evan
Did you compile from source or did you use the supplied binaries?
Daniel
-----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of ScottO Sent: Friday, 9 November 2007 5:59 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault
Ditto.
I also am running it on 64bit hosts (CentOS 4 & Fedora Core 3), albeit only for a couple days now (2.0.5 that is) - without any segfault'ing issues.
Evan Rempel wrote:
Yes, I am using syslog-ng 2.0.5 on redhat4 64bit and not having any problem with crashing etc.
Anything I can help with I will try and do.
Evan.
Balazs Scheidler wrote:
Hm.. the same has been reported on a mips64 system. This must be a 64
bit related issue, then. I'll try to get a 64 compile environment.
Anyone else who uses syslog-ng 2.0.x on 64 bit systems?
On Thu, 2007-11-08 at 23:34 +1100, Daniel Szmandiuk wrote:
Here's the backtrace: GNU gdb Red Hat Linux (6.5-16.el5rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and
you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1".
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments.
It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email.
For information about our privacy policy, visit the IMC Communications website at www.imc.net.au
This email has been checked by IMC's SMTP gateway. -&- _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
Hm.. the same has been reported on a mips64 system. This must be a 64 bit related issue, then. I'll try to get a 64 compile environment.
Anyone else who uses syslog-ng 2.0.x on 64 bit systems?
Yup, and no problems at all. 2.0.3 on a RHEL5.1 64-bit system. Also worked fine under RHEL5. -- tim -- tim@denmantire.com
I use 2.0.4 on i386_64 RHEL4 - no problem either. On Nov 11, 2007 11:49 AM, Tim Boyer <tim@denmantire.com> wrote:
Hm.. the same has been reported on a mips64 system. This must be a 64 bit related issue, then. I'll try to get a 64 compile environment.
Anyone else who uses syslog-ng 2.0.x on 64 bit systems?
Yup, and no problems at all. 2.0.3 on a RHEL5.1 64-bit system. Also worked fine under RHEL5.
-- tim -- tim@denmantire.com
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
-- stucky
Stucky & Tim, Did you compile from source or did you use supplied binaries? Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of stucky Sent: Monday, 12 November 2007 8:58 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault I use 2.0.4 on i386_64 RHEL4 - no problem either. On Nov 11, 2007 11:49 AM, Tim Boyer <tim@denmantire.com> wrote:
Hm.. the same has been reported on a mips64 system. This must be a 64 bit related issue, then. I'll try to get a 64 compile
environment.
Anyone else who uses syslog-ng 2.0.x on 64 bit systems?
Yup, and no problems at all. 2.0.3 on a RHEL5.1 64-bit system. Also worked fine under RHEL5.
-- tim -- tim@denmantire.com
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
-- stucky _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments. It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email. For information about our privacy policy, visit the IMC Communications website at www.imc.net.au This email has been checked by IMC's SMTP gateway. -&-
I am also running sys.log 2.0.5 on 64 bit AIX without any problems. Evan.
And, what versions of the following are you running? These are mine: glib2-2.12.3-2.fc6 glib2-devel-2.12.3-2.fc6 gcc-4.1.1-52.el5.2 gcc-c++-4.1.1-52.el5.2 Daniel Stucky & Tim, Did you compile from source or did you use supplied binaries? Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of stucky Sent: Monday, 12 November 2007 8:58 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault I use 2.0.4 on i386_64 RHEL4 - no problem either. On Nov 11, 2007 11:49 AM, Tim Boyer <tim@denmantire.com> wrote:
Hm.. the same has been reported on a mips64 system. This must be a 64 bit related issue, then. I'll try to get a 64 compile
environment.
Anyone else who uses syslog-ng 2.0.x on 64 bit systems?
Yup, and no problems at all. 2.0.3 on a RHEL5.1 64-bit system. Also worked fine under RHEL5.
-- tim -- tim@denmantire.com
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
-- stucky _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments. It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email. For information about our privacy policy, visit the IMC Communications website at www.imc.net.au This email has been checked by IMC's SMTP gateway. -&-
And, what versions of the following are you running? These are mine:
glib2-2.12.3-2.fc6 glib2-devel-2.12.3-2.fc6 gcc-4.1.1-52.el5.2 gcc-c++-4.1.1-52.el5.2
glib2-2.12.3-2.fc6 glib2-devel-2.12.3-2.fc6 gcc-4.1.2-14.el5 gcc-c++-4.1.2-14.el5 -- tim --
Tim, Is there any chance you can send me a copy of your ./configure output (& options) when you compiled syslog-ng? I want to compare it to mine. I updated my system to reflect the same versions as your below. Recompiled again, but still syslog-ng still seg faults. Something has to be different! Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Tim Boyer Sent: Monday, 12 November 2007 11:20 AM To: 'Syslog-ng users' and developers' mailing list' Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault
And, what versions of the following are you running? These are mine:
glib2-2.12.3-2.fc6 glib2-devel-2.12.3-2.fc6 gcc-4.1.1-52.el5.2 gcc-c++-4.1.1-52.el5.2
glib2-2.12.3-2.fc6 glib2-devel-2.12.3-2.fc6 gcc-4.1.2-14.el5 gcc-c++-4.1.2-14.el5 -- tim -- _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments. It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email. For information about our privacy policy, visit the IMC Communications website at www.imc.net.au This email has been checked by IMC's SMTP gateway. -&-
Tim,
Is there any chance you can send me a copy of your ./configure output (& options) when you compiled syslog-ng?
I want to compare it to mine.
I updated my system to reflect the same versions as your below. Recompiled again, but still syslog-ng still seg faults. Something has to be different!
Simple as it gets... env PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure I'll email you the config.log. -- tim --
Tim Boyer wrote:
Tim,
Is there any chance you can send me a copy of your ./configure output (& options) when you compiled syslog-ng?
I want to compare it to mine.
I updated my system to reflect the same versions as your below. Recompiled again, but still syslog-ng still seg faults. Something has to be different!
Simple as it gets...
env PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure
I'll email you the config.log.
-- tim --
Hi Guys, I compiled on x86_64 and made rpm. You can find source rpm and instruction here: http://www.unipr.it/~raffaele/software/syslog-ng-2.0.5.tgz Regards Raffaele P.s. BTW the source used in rpm is a snapshot of 2.0.5 of someday last month. Syslog-ng has worked fine for a couple of weeks.... cross finger ;)
Hi, I am able to get syslog-ng working on mips64 bit machine. The issue in my case was that I was not compiling syslog-ng with the correct glib-2 header files. The compilation was using the glib header files from the host system where the cross-build was done. I was able to fix the problem by setting the include path (CFLAGS and CPPFLAGS in configure) to the right set of header files. -Shashank -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Tim Boyer Sent: Sunday, November 11, 2007 7:08 PM To: 'Syslog-ng users' and developers' mailing list' Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault
Tim,
Is there any chance you can send me a copy of your ./configure output (& options) when you compiled syslog-ng?
I want to compare it to mine.
I updated my system to reflect the same versions as your below. Recompiled again, but still syslog-ng still seg faults. Something has to be different!
Simple as it gets... env PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure I'll email you the config.log. -- tim -- _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
Just saw this email.. I just posted something very similar... Can you help me with the correct options to set the include paths correctly? Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Shashank Vinchurkar Sent: Tuesday, 13 November 2007 11:13 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault Hi, I am able to get syslog-ng working on mips64 bit machine. The issue in my case was that I was not compiling syslog-ng with the correct glib-2 header files. The compilation was using the glib header files from the host system where the cross-build was done. I was able to fix the problem by setting the include path (CFLAGS and CPPFLAGS in configure) to the right set of header files. -Shashank -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Tim Boyer Sent: Sunday, November 11, 2007 7:08 PM To: 'Syslog-ng users' and developers' mailing list' Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault
Tim,
Is there any chance you can send me a copy of your ./configure output (& options) when you compiled syslog-ng?
I want to compare it to mine.
I updated my system to reflect the same versions as your below. Recompiled again, but still syslog-ng still seg faults. Something has to be different!
Simple as it gets... env PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure I'll email you the config.log. -- tim -- _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments. It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email. For information about our privacy policy, visit the IMC Communications website at www.imc.net.au This email has been checked by IMC's SMTP gateway. -&-
I have installed glib-2 in GLIB_DIR. As part of make install it copies the header files in GLIB_DIR/install folder. Here's what you need to do: Configure syslog-ng with these options: GLIB_INC_DIR=-I$GLIB_DIR/install/lib/glib-2.0/include -I$GLIB_DIR/install/include/glib-2.0 ./configure CFLAGS="$GLIB_INC_DIR" CPPFLAGS="$GLIB_INC_DIR" (along with other configure options). -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Daniel Szmandiuk Sent: Monday, November 12, 2007 4:21 PM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault Just saw this email.. I just posted something very similar... Can you help me with the correct options to set the include paths correctly? Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Shashank Vinchurkar Sent: Tuesday, 13 November 2007 11:13 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault Hi, I am able to get syslog-ng working on mips64 bit machine. The issue in my case was that I was not compiling syslog-ng with the correct glib-2 header files. The compilation was using the glib header files from the host system where the cross-build was done. I was able to fix the problem by setting the include path (CFLAGS and CPPFLAGS in configure) to the right set of header files. -Shashank -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Tim Boyer Sent: Sunday, November 11, 2007 7:08 PM To: 'Syslog-ng users' and developers' mailing list' Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault
Tim,
Is there any chance you can send me a copy of your ./configure output (& options) when you compiled syslog-ng?
I want to compare it to mine.
I updated my system to reflect the same versions as your below. Recompiled again, but still syslog-ng still seg faults. Something has to be different!
Simple as it gets... env PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure I'll email you the config.log. -- tim -- _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments. It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email. For information about our privacy policy, visit the IMC Communications website at www.imc.net.au This email has been checked by IMC's SMTP gateway. -&- _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
Thanks for your help. I actually ended removing the 32bit GLIB2 and recompiled. All is now good. Thanks everyone for your help over the last few days. BTW, is it normal for a ./configure script to pick 32bit libraries in preference to 64bit ones when both exist??? Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Shashank Vinchurkar Sent: Tuesday, 13 November 2007 11:32 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault I have installed glib-2 in GLIB_DIR. As part of make install it copies the header files in GLIB_DIR/install folder. Here's what you need to do: Configure syslog-ng with these options: GLIB_INC_DIR=-I$GLIB_DIR/install/lib/glib-2.0/include -I$GLIB_DIR/install/include/glib-2.0 ./configure CFLAGS="$GLIB_INC_DIR" CPPFLAGS="$GLIB_INC_DIR" (along with other configure options). -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Daniel Szmandiuk Sent: Monday, November 12, 2007 4:21 PM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault Just saw this email.. I just posted something very similar... Can you help me with the correct options to set the include paths correctly? Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Shashank Vinchurkar Sent: Tuesday, 13 November 2007 11:13 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault Hi, I am able to get syslog-ng working on mips64 bit machine. The issue in my case was that I was not compiling syslog-ng with the correct glib-2 header files. The compilation was using the glib header files from the host system where the cross-build was done. I was able to fix the problem by setting the include path (CFLAGS and CPPFLAGS in configure) to the right set of header files. -Shashank -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Tim Boyer Sent: Sunday, November 11, 2007 7:08 PM To: 'Syslog-ng users' and developers' mailing list' Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault
Tim,
Is there any chance you can send me a copy of your ./configure output (& options) when you compiled syslog-ng?
I want to compare it to mine.
I updated my system to reflect the same versions as your below. Recompiled again, but still syslog-ng still seg faults. Something has to be different!
Simple as it gets... env PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure I'll email you the config.log. -- tim -- _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments. It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email. For information about our privacy policy, visit the IMC Communications website at www.imc.net.au This email has been checked by IMC's SMTP gateway. -&- _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
On Tue, 2007-11-13 at 11:38 +1100, Daniel Szmandiuk wrote:
Thanks for your help.
I actually ended removing the 32bit GLIB2 and recompiled.
All is now good.
Thanks everyone for your help over the last few days.
BTW, is it normal for a ./configure script to pick 32bit libraries in preference to 64bit ones when both exist???
I've posted an explaining mail in the other thread. Am I right to assume that the problem is resolved now? -- Bazsi
Yes. Problem is now resolved. Thanks. Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Tuesday, 13 November 2007 7:23 PM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault On Tue, 2007-11-13 at 11:38 +1100, Daniel Szmandiuk wrote:
Thanks for your help.
I actually ended removing the 32bit GLIB2 and recompiled.
All is now good.
Thanks everyone for your help over the last few days.
BTW, is it normal for a ./configure script to pick 32bit libraries in preference to 64bit ones when both exist???
I've posted an explaining mail in the other thread. Am I right to assume that the problem is resolved now? -- Bazsi _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments. It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email. For information about our privacy policy, visit the IMC Communications website at www.imc.net.au This email has been checked by IMC's SMTP gateway. -&-
I think I know the source of the problem. (with my very limited knowledge) It looks like I have both the 32 & 64bit versions of GLIB2 installed and the configure script is picking up the 32bit version instead of the 64bit. I've compared Tim's config.log with mine and can see differences like this: Tims: CPPFLAGS=' -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/local/include/eventlog -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64' Mine: CPPFLAGS=' -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/eventlog -D_BSD_SOURCE -D__BSD_SOURCE -D__FAVOR_BSD -DHAVE_NET_ETHERNET_H -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64' I don't have /usr/include/glib-2.0, so in my case it is picking up /usr/lib/glib-2.0/include. In Tim's case /usr/lib64/glib-2.0/include So question is why is the configure script not picking up my 64bit libraries? I suspect this is my binary seg faults... How do I force ./configure to use /usr/lib64/glib-2.0/include instead of /usr/lib/glib-2.0/include? Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Tim Boyer Sent: Monday, 12 November 2007 2:08 PM To: 'Syslog-ng users' and developers' mailing list' Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault
Tim,
Is there any chance you can send me a copy of your ./configure output (& options) when you compiled syslog-ng?
I want to compare it to mine.
I updated my system to reflect the same versions as your below. Recompiled again, but still syslog-ng still seg faults. Something has to be different!
Simple as it gets... env PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure I'll email you the config.log. -- tim -- _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments. It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email. For information about our privacy policy, visit the IMC Communications website at www.imc.net.au This email has been checked by IMC's SMTP gateway. -&-
On Tue, 2007-11-13 at 11:19 +1100, Daniel Szmandiuk wrote:
I think I know the source of the problem. (with my very limited knowledge)
It looks like I have both the 32 & 64bit versions of GLIB2 installed and the configure script is picking up the 32bit version instead of the 64bit.
I've compared Tim's config.log with mine and can see differences like this:
Tims: CPPFLAGS=' -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/local/include/eventlog -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64'
Mine: CPPFLAGS=' -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/eventlog -D_BSD_SOURCE -D__BSD_SOURCE -D__FAVOR_BSD -DHAVE_NET_ETHERNET_H -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64'
I don't have /usr/include/glib-2.0, so in my case it is picking up /usr/lib/glib-2.0/include. In Tim's case /usr/lib64/glib-2.0/include
So question is why is the configure script not picking up my 64bit libraries? I suspect this is my binary seg faults...
How do I force ./configure to use /usr/lib64/glib-2.0/include instead of /usr/lib/glib-2.0/include?
It all depends on pkg-config program and your PKG_CONFIG_PATH environment variable, which defaults to /usr/lib/pkgconfig. I assume you have both /usr/lib/pkgconfig/glib-2.0.pc and /usr/lib64/pkgconfig/glib-2.0.pc, right? I'm not sure how pkg-config should handle this situation, as it does not really have an option to specify the target system type. See also: http://lists.freedesktop.org/archives/pkg-config/2005-December/000074.html Until pkg-config gets something like this, the PKG_CONFIG_PATH has to be specified manually. All I can do is add a patch like this, which triggers an error in the case above, however it does not work when cross-compiling. Could you please check if this error message is actually triggered with this patch without specifying PKG_CONFIG_PATH? I've also pushed this patch to my git repository, so it might be easier to check that out. Thanks. diff --git a/configure.in b/configure.in index 75e4b2f..d100794 100644 --- a/configure.in +++ b/configure.in @@ -320,6 +320,30 @@ blb_cv_static_glib=yes, blb_cv_static_glib=no)]) LIBS=$old_LIBS +old_CPPFLAGS=$CPPFLAGS +CPPFLAGS="$GLIB_CFLAGS" + +AC_CACHE_CHECK(sanity checking Glib headers, + blb_cv_glib_sane, +[AC_TRY_RUN([ +#include <glib.h> + +int main() +{ + if (sizeof(long) != GLIB_SIZEOF_LONG) + return 1; + return 0; +} +], +blb_cv_glib_sane=yes, +blb_cv_glib_sane=no, +blb_cv_glib_sane=yes)]) +CPPFLAGS=$old_CPPFLAGS + +if test "x$blb_cv_glib_sane" = "xno"; then + AC_MSG_ERROR([Glib headers inconsistent with current compiler setting. You might be using 32 bit Glib with a 64 bit compiler, check PKG_CONFIG_PATH]) +fi + if test "x$enable_dynamic_linking" = "xyes" -a "x$enable_static_linking" = "xyes"; then AC_MSG_ERROR([You cannot specify dynamic and static linking at the same time.]) fi -- Bazsi
participants (8)
-
Balazs Scheidler
-
Daniel Szmandiuk
-
Evan Rempel
-
Raffaele
-
ScottO
-
Shashank Vinchurkar
-
stucky
-
Tim Boyer