<div>Hi Ravi,</div> <div> </div> <div>Download <A href="ftp://ftp.sunfreeware.com/pub/freeware/sparc/10/pkgconfig-0.20-sol10-sparc-local.gz">pkgconfig-0.20-sol10-sparc-local.gz</A> fron sunfreeware.com and install on your system. And copy eventlog.pc to path of pkg-config libray path.</div> <div> </div> <div> </div> <div> </div> <div>Thanks<BR>Shamim<BR><B><I>syslog-ng-request@lists.balabit.hu</I></B> wrote:</div> <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Send syslog-ng mailing list submissions to<BR>syslog-ng@lists.balabit.hu<BR><BR>To subscribe or unsubscribe via the World Wide Web, visit<BR>https://lists.balabit.hu/mailman/listinfo/syslog-ng<BR>or, via email, send a message with subject or body 'help' to<BR>syslog-ng-request@lists.balabit.hu<BR><BR>You can reach the person managing the list
at<BR>syslog-ng-owner@lists.balabit.hu<BR><BR>When replying, please edit your Subject line so it is more specific<BR>than "Re: Contents of syslog-ng digest..."<BR><BR><BR>Today's Topics:<BR><BR>1. Syslog-ng 2.0.3 compile error <BR>(Ravi Papisetti -X (rpapiset - HCL at Cisco))<BR>2. Syslog-ng 2.0.3 make error <BR>(Ravi Papisetti -X (rpapiset - HCL at Cisco))<BR>3. Re: weird messages from syslog. ()\(@sS)<BR><BR><BR>----------------------------------------------------------------------<BR><BR>Message: 1<BR>Date: Wed, 25 Apr 2007 22:58:07 +0530<BR>From: "Ravi Papisetti -X (rpapiset - HCL at Cisco)"<BR><RPAPISET@CISCO.COM><BR>Subject: [syslog-ng] Syslog-ng 2.0.3 compile error <BR>To: "Syslog-ng users' and developers' mailing list"<BR><SYSLOG-NG@LISTS.BALABIT.HU><BR>Message-ID:<BR><6499201801FBC6419ED8C910302F67AC02EC283B@xmb-blr-417.apac.cisco.com><BR>Content-Type: text/plain; charset="us-ascii"<BR><BR>Hi,<BR><BR>I am trying to configure syslog-ng 2.0.3 on solaris 10 and
below is the<BR>error<BR><BR>checking for EVTLOG... Package eventlog was not found in the pkg-config<BR>search path.<BR>Perhaps you should add the directory containing `eventlog.pc'<BR>to the PKG_CONFIG_PATH environment variable<BR>No package 'eventlog' found<BR>configure: error: Cannot find eventlog version >= 0.2: is pkg-config in<BR>path?<BR><BR>I have installed libnet-1.20 and libol-0.3.18, then ran ./configure from<BR>/syslog-ng-2.0.3.<BR><BR>Am I missing something?<BR><BR>Thanks,<BR>Ravi Kumar P.<BR><BR><BR>------------------------------<BR><BR>Message: 2<BR>Date: Thu, 26 Apr 2007 01:04:06 +0530<BR>From: "Ravi Papisetti -X (rpapiset - HCL at Cisco)"<BR><RPAPISET@CISCO.COM><BR>Subject: [syslog-ng] Syslog-ng 2.0.3 make error <BR>To: "Syslog-ng users' and developers' mailing list"<BR><SYSLOG-NG@LISTS.BALABIT.HU><BR>Message-ID:<BR><6499201801FBC6419ED8C910302F67AC02EC284D@xmb-blr-417.apac.cisco.com><BR>Content-Type: text/plain;
charset="us-ascii"<BR><BR><BR>Hi,<BR><BR>I see below error when I run make && make install<BR><BR>make all-recursive<BR>make[1]: Entering directory `/usr/local/syslog-ng/syslog-ng-2.0.3'<BR>Making all in src<BR>make[2]: Entering directory `/usr/local/syslog-ng/syslog-ng-2.0.3/src'<BR>if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/glib-2.0<BR>-I/usr/lib/glib-2.0/include -I/usr/local/include/eventlog<BR>-D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -Wall<BR>-g -MT cfg-grammar.o -MD -MP -MF ".deps/cfg-grammar.Tpo" \<BR>-c -o cfg-grammar.o `test -f 'cfg-grammar.c' || echo<BR>'./'`cfg-grammar.c; \<BR>then mv -f ".deps/cfg-grammar.Tpo" ".deps/cfg-grammar.Po"; \<BR>else rm -f ".deps/cfg-grammar.Tpo"; exit 1; \<BR>fi<BR>In file included from<BR>/home/bazsi/zwa/work/syslog-ng-2.0/syslog-ng/src/cfg-grammar.y:15:<BR>afinet.h:30:20: libnet.h: No such file or directory<BR>In file included
from<BR>/home/bazsi/zwa/work/syslog-ng-2.0/syslog-ng/src/cfg-grammar.y:15:<BR>afinet.h:61: error: syntax error before "libnet_t"<BR>afinet.h:61: warning: no semicolon at end of struct or union<BR>afinet.h:63: warning: type defaults to `int' in declaration of<BR>`AFInetDestDriver'<BR>afinet.h:63: warning: data definition has no type or storage class<BR>/home/bazsi/zwa/work/syslog-ng-2.0/syslog-ng/src/cfg-grammar.y: In<BR>function `yyparse':<BR>/home/bazsi/zwa/work/syslog-ng-2.0/syslog-ng/src/cfg-grammar.y:592:<BR>error: syntax error before ')' token<BR>/home/bazsi/zwa/work/syslog-ng-2.0/syslog-ng/src/cfg-grammar.y:626:<BR>error: syntax error before ')' token<BR>make[2]: *** [cfg-grammar.o] Error 1<BR>make[2]: Leaving directory `/usr/local/syslog-ng/syslog-ng-2.0.3/src'<BR>make[1]: *** [all-recursive] Error 1<BR>make[1]: Leaving directory `/usr/local/syslog-ng/syslog-ng-2.0.3'<BR>make: *** [all] Error 2<BR><BR><BR>Some one could tell me the reason.<BR><BR>Thanks,<BR>Ravi
Kumar P.<BR><BR><BR>------------------------------<BR><BR>Message: 3<BR>Date: Thu, 26 Apr 2007 01:23:05 +0300<BR>From: ")\\(@sS" <ATHANASIOS.SILIS@GMAIL.COM><BR>Subject: Re: [syslog-ng] weird messages from syslog.<BR>To: "Syslog-ng users' and developers' mailing list"<BR><SYSLOG-NG@LISTS.BALABIT.HU><BR>Message-ID:<BR><770db8dc0704251523q280820d3jdfabc2af9f4f11b7@mail.gmail.com><BR>Content-Type: text/plain; charset="utf-8"<BR><BR>well thats definitely abit of a relief considering all the pc hardware parts<BR>are completely new.<BR>i don't mind doing a reinstallation of the OS... but here is smth new:<BR>i noticed that some of the messages talked abit about 'smbd' and<BR>'printers'..<BR>i decided to comment out 'load printers' from smb.conf and so far (half a<BR>day later) i haven't got the messages i ported before... i have some new<BR>ones though:) here is a dmesg dump:<BR><BR><UNKNOWN>: hw csum failure.<BR>[<C04D056D>]
skb_copy_and_csum_datagram_iovec+0x10d/0x120<BR>[<C0511A05>] udp_recvmsg+0x135/0x280<BR>[<C04CC195>] sock_common_recvmsg+0x45/0x70<BR>[<C04C8038>] sock_recvmsg+0xd8/0x130<BR>[<F92733D6>] _nv003589rm+0x26/0x2c [nvidia]<BR>[<F9474BEF>] _nv007223rm+0x23/0x28 [nvidia]<BR>[<F9474B30>] _nv007225rm+0x28/0x44 [nvidia]<BR>[<C0132370>] autoremove_wake_function+0x0/0x50<BR>[<F928D77D>] rm_set_interrupts+0x129/0x15c [nvidia]<BR>[<F928D796>] rm_set_interrupts+0x142/0x15c [nvidia]<BR>[<C02EE77B>] copy_to_user+0x2b/0x40<BR>[<C04C92E5>] sys_recvfrom+0xd5/0x160<BR>[<F928897C>] _nv002554rm+0xa8/0xb4 [nvidia]<BR>[<C01730E3>] fcntl_setlk64+0x203/0x290<BR>[<C04C9B75>] sys_socketcall+0x1c5/0x250<BR>[<C0102EB8>] syscall_call+0x7/0xb<BR>=======================<BR><UNKNOWN>: hw csum failure.<BR>[<C04D056D>] skb_copy_and_csum_datagram_iovec+0x10d/0x120<BR>[<C0511A05>] udp_recvmsg+0x135/0x280<BR>[<C04CC195>] sock_common_recvmsg+0x45/0x70<BR>[<C04C8038>] sock_recvmsg+0xd8/0x130<BR>[<C0132370>]
autoremove_wake_function+0x0/0x50<BR>[<C0173B2A>] dput+0x8a/0x140<BR>[<C02EE77B>] copy_to_user+0x2b/0x40<BR>[<C04C92E5>] sys_recvfrom+0xd5/0x160<BR>[<C015FC3C>] cache_alloc_refill+0xcc/0x1e0<BR>[<C01730E3>] fcntl_setlk64+0x203/0x290<BR>[<C01837BA>] invalidate_inode_buffers+0x1a/0xe0<BR>[<C0576D45>] schedule+0x465/0x7a0<BR>[<C04C9B75>] sys_socketcall+0x1c5/0x250<BR>[<C0102EB8>] syscall_call+0x7/0xb<BR>=======================<BR><UNKNOWN>: hw csum failure.<BR>[<C04D056D>] skb_copy_and_csum_datagram_iovec+0x10d/0x120<BR>[<C0511A05>] udp_recvmsg+0x135/0x280<BR>[<C04CC195>] sock_common_recvmsg+0x45/0x70<BR>[<C04C8038>] sock_recvmsg+0xd8/0x130<BR>[<F92733D6>] _nv003589rm+0x26/0x2c [nvidia]<BR>[<F9474BEF>] _nv007223rm+0x23/0x28 [nvidia]<BR>[<F9474B30>] _nv007225rm+0x28/0x44 [nvidia]<BR>[<C0132370>] autoremove_wake_function+0x0/0x50<BR>[<F928D77D>] rm_set_interrupts+0x129/0x15c [nvidia]<BR>[<F928D796>] rm_set_interrupts+0x142/0x15c [nvidia]<BR>[<C02EE77B>]
copy_to_user+0x2b/0x40<BR>[<C04C92E5>] sys_recvfrom+0xd5/0x160<BR>[<C015FC3C>] cache_alloc_refill+0xcc/0x1e0<BR>[<C01730E3>] fcntl_setlk64+0x203/0x290<BR>[<C01837BA>] invalidate_inode_buffers+0x1a/0xe0<BR>[<C04C9B75>] sys_socketcall+0x1c5/0x250<BR>[<C0102EB8>] syscall_call+0x7/0xb<BR>=======================<BR><UNKNOWN>: hw csum failure.<BR>[<C04D056D>] skb_copy_and_csum_datagram_iovec+0x10d/0x120<BR>[<C0511A05>] udp_recvmsg+0x135/0x280<BR>[<C04CC195>] sock_common_recvmsg+0x45/0x70<BR>[<C04C8038>] sock_recvmsg+0xd8/0x130<BR>[<C04C7EBF>] sock_sendmsg+0xbf/0x110<BR>[<F9474B30>] _nv007225rm+0x28/0x44 [nvidia]<BR>[<C0132370>] autoremove_wake_function+0x0/0x50<BR>[<F928D77D>] rm_set_interrupts+0x129/0x15c [nvidia]<BR>[<F928D796>] rm_set_interrupts+0x142/0x15c [nvidia]<BR>[<C02EE77B>] copy_to_user+0x2b/0x40<BR>[<C04C92E5>] sys_recvfrom+0xd5/0x160<BR>[<C015FC3C>] cache_alloc_refill+0xcc/0x1e0<BR>[<C01730E3>] fcntl_setlk64+0x203/0x290<BR>[<C01837BA>]
invalidate_inode_buffers+0x1a/0xe0<BR>[<C01353D7>] hrtimer_run_queues+0x47/0xe0<BR>[<C04C9B75>] sys_socketcall+0x1c5/0x250<BR>[<C0102EB8>] syscall_call+0x7/0xb<BR>=======================<BR><UNKNOWN>: hw csum failure.<BR>[<C04D056D>] skb_copy_and_csum_datagram_iovec+0x10d/0x120<BR>[<C0511A05>] udp_recvmsg+0x135/0x280<BR>[<C04CC195>] sock_common_recvmsg+0x45/0x70<BR>[<C04C8038>] sock_recvmsg+0xd8/0x130<BR>[<C04C7EBF>] sock_sendmsg+0xbf/0x110<BR>[<F9474B30>] _nv007225rm+0x28/0x44 [nvidia]<BR>[<C0132370>] autoremove_wake_function+0x0/0x50<BR>[<F928D77D>] rm_set_interrupts+0x129/0x15c [nvidia]<BR>[<F928D796>] rm_set_interrupts+0x142/0x15c [nvidia]<BR>[<C02EE77B>] copy_to_user+0x2b/0x40<BR>[<C04C92E5>] sys_recvfrom+0xd5/0x160<BR>[<C012719B>] change_clocksource+0x12b/0x170<BR>[<C01278E0>] update_wall_time+0x190/0x280<BR>[<C04C9B75>] sys_socketcall+0x1c5/0x250<BR>[<C0102EB8>] syscall_call+0x7/0xb<BR>=======================<BR><UNKNOWN>: hw csum failure.<BR>[<C04D056D>]
skb_copy_and_csum_datagram_iovec+0x10d/0x120<BR>[<C0511A05>] udp_recvmsg+0x135/0x280<BR>[<C04CC195>] sock_common_recvmsg+0x45/0x70<BR>[<C04C8038>] sock_recvmsg+0xd8/0x130<BR>[<C0132370>] autoremove_wake_function+0x0/0x50<BR>[<C0173B2A>] dput+0x8a/0x140<BR>[<C02EE77B>] copy_to_user+0x2b/0x40<BR>[<C04C92E5>] sys_recvfrom+0xd5/0x160<BR>[<C05171CB>] devinet_ioctl+0x2db/0x570<BR>[<C051830E>] inet_sock_destruct+0xbe/0x200<BR>[<C05783C8>] _spin_lock_bh+0x8/0x20<BR>[<C01837BA>] invalidate_inode_buffers+0x1a/0xe0<BR>[<C04C9B75>] sys_socketcall+0x1c5/0x250<BR>[<C0102EB8>] syscall_call+0x7/0xb<BR>[<C0570033>] rpc_unlink+0xc3/0xf0<BR>=======================<BR><UNKNOWN>: hw csum failure.<BR>[<C04D056D>] skb_copy_and_csum_datagram_iovec+0x10d/0x120<BR>[<C0511A05>] udp_recvmsg+0x135/0x280<BR>[<C04CC195>] sock_common_recvmsg+0x45/0x70<BR>[<C04C8038>] sock_recvmsg+0xd8/0x130<BR>[<F92733D6>] _nv003589rm+0x26/0x2c [nvidia]<BR>[<F9474BEF>] _nv007223rm+0x23/0x28 [nvidia]<BR>[<F9474B30>]
_nv007225rm+0x28/0x44 [nvidia]<BR>[<C0132370>] autoremove_wake_function+0x0/0x50<BR>[<F928D77D>] rm_set_interrupts+0x129/0x15c [nvidia]<BR>[<F928D796>] rm_set_interrupts+0x142/0x15c [nvidia]<BR>[<C02EE77B>] copy_to_user+0x2b/0x40<BR>[<C04C92E5>] sys_recvfrom+0xd5/0x160<BR>[<C015FC3C>] cache_alloc_refill+0xcc/0x1e0<BR>[<C01730E3>] fcntl_setlk64+0x203/0x290<BR>[<C01278E0>] update_wall_time+0x190/0x280<BR>[<C0576D45>] schedule+0x465/0x7a0<BR>[<C04C9B75>] sys_socketcall+0x1c5/0x250<BR>[<C0102EB8>] syscall_call+0x7/0xb<BR>=======================<BR><UNKNOWN>: hw csum failure.<BR>[<C04D056D>] skb_copy_and_csum_datagram_iovec+0x10d/0x120<BR>[<C0511A05>] udp_recvmsg+0x135/0x280<BR>[<C04CC195>] sock_common_recvmsg+0x45/0x70<BR>[<C04C8038>] sock_recvmsg+0xd8/0x130<BR>[<F92733D6>] _nv003589rm+0x26/0x2c [nvidia]<BR>[<F9474BEF>] _nv007223rm+0x23/0x28 [nvidia]<BR>[<F9474B30>] _nv007225rm+0x28/0x44 [nvidia]<BR>[<C0132370>] autoremove_wake_function+0x0/0x50<BR>[<F928D77D>]
rm_set_interrupts+0x129/0x15c [nvidia]<BR>[<F928D796>] rm_set_interrupts+0x142/0x15c [nvidia]<BR>[<C02EE77B>] copy_to_user+0x2b/0x40<BR>[<C04C92E5>] sys_recvfrom+0xd5/0x160<BR>[<C015FC3C>] cache_alloc_refill+0xcc/0x1e0<BR>[<C01730E3>] fcntl_setlk64+0x203/0x290<BR>[<C01837BA>] invalidate_inode_buffers+0x1a/0xe0<BR>[<C01353D7>] hrtimer_run_queues+0x47/0xe0<BR>[<C04C9B75>] sys_socketcall+0x1c5/0x250<BR>[<C0102EB8>] syscall_call+0x7/0xb<BR>=======================<BR><UNKNOWN>: hw csum failure.<BR>[<C04D056D>] skb_copy_and_csum_datagram_iovec+0x10d/0x120<BR>[<C0511A05>] udp_recvmsg+0x135/0x280<BR>[<C04CC195>] sock_common_recvmsg+0x45/0x70<BR>[<C04C8038>] sock_recvmsg+0xd8/0x130<BR>[<C0132370>] autoremove_wake_function+0x0/0x50<BR>[<C0173B2A>] dput+0x8a/0x140<BR>[<C02EE77B>] copy_to_user+0x2b/0x40<BR>[<C04C92E5>] sys_recvfrom+0xd5/0x160<BR>[<C015FC3C>] cache_alloc_refill+0xcc/0x1e0<BR>[<C01730E3>] fcntl_setlk64+0x203/0x290<BR>[<C0576D45>] schedule+0x465/0x7a0<BR>[<C04C9B75>]
sys_socketcall+0x1c5/0x250<BR>[<C0102EB8>] syscall_call+0x7/0xb<BR>=======================<BR><UNKNOWN>: hw csum failure.<BR>[<C04D056D>] skb_copy_and_csum_datagram_iovec+0x10d/0x120<BR>[<C0511A05>] udp_recvmsg+0x135/0x280<BR>[<C04CC195>] sock_common_recvmsg+0x45/0x70<BR>[<C04C8038>] sock_recvmsg+0xd8/0x130<BR>[<C04C7EBF>] sock_sendmsg+0xbf/0x110<BR>[<F9474B30>] _nv007225rm+0x28/0x44 [nvidia]<BR>[<C0132370>] autoremove_wake_function+0x0/0x50<BR>[<F928D77D>] rm_set_interrupts+0x129/0x15c [nvidia]<BR>[<F928D796>] rm_set_interrupts+0x142/0x15c [nvidia]<BR>[<C02EE77B>] copy_to_user+0x2b/0x40<BR>[<C04C92E5>] sys_recvfrom+0xd5/0x160<BR>[<C01730E3>] fcntl_setlk64+0x203/0x290<BR>[<C01837BA>] invalidate_inode_buffers+0x1a/0xe0<BR>[<C04C9B75>] sys_socketcall+0x1c5/0x250<BR>[<C0102EB8>] syscall_call+0x7/0xb<BR>=======================<BR><UNKNOWN>: hw csum failure.<BR>[<C04D056D>] skb_copy_and_csum_datagram_iovec+0x10d/0x120<BR>[<C0511A05>] udp_recvmsg+0x135/0x280<BR>[<C04CC195>]
sock_common_recvmsg+0x45/0x70<BR>[<C04C8038>] sock_recvmsg+0xd8/0x130<BR>[<C04C7EBF>] sock_sendmsg+0xbf/0x110<BR>[<C0132370>] autoremove_wake_function+0x0/0x50<BR>[<C0173B2A>] dput+0x8a/0x140<BR>[<C02EE77B>] copy_to_user+0x2b/0x40<BR>[<C04C92E5>] sys_recvfrom+0xd5/0x160<BR>[<C015FB02>] cache_grow+0x102/0x170<BR>[<C04C9B75>] sys_socketcall+0x1c5/0x250<BR>[<C0102EB8>] syscall_call+0x7/0xb<BR>[<C0570033>] rpc_unlink+0xc3/0xf0<BR>=======================<BR>root@Stargaze:~#<BR><BR>im actually reading somewhere that sky2 network driver for Yukon2 PCI-E<BR>Marvell based controllers seems to have hw csum failures... the dump of<BR>those is not exactly the same...<BR><BR>nass<BR><BR><BR>On 4/25/07, Balazs Scheidler <BAZSI@BALABIT.HU>wrote:<BR>><BR>> On Wed, 2007-04-25 at 14:54 +0300, )\(@sS wrote:<BR>> > im sorry i understood nothing of your explanation... :)<BR>> > thats due to my lack of any knowledge on the matter..<BR>> > i will get ksymoops but could
you break down what you mean by back<BR>> > traces and what by 'bogus'<BR>><BR>> Oopses basically happen for two reasons: software and hardware failure.<BR>> Hardware failures tend to cause mystic and nondeterministic behaviour,<BR>> crashing at random locations. On the consistent backtraces I meant that<BR>> several of the Oopses that you posted had the same backtrace (e.g. the<BR>> same crash location), which indicates that it's more likely a software<BR>> related problem.<BR>><BR>> The listing I gave you, is the direct x86 dissassembly of the code found<BR>> at the crash location, this is reported as a sequence of bytes in the<BR>> Oops output, right after the "Code:" label.<BR>><BR>> I said it was bogus as it made no sense. This is not valid code, so<BR>> either something corrupted the instruction pointer (by jumping to an<BR>> invalid function pointer), or something overwrote the stack.<BR>><BR>> I checked the
oopses again, don't go to LKML, your kernel is tainted<BR>> (e.g. it has a proprietary module loaded, they will not help you).<BR>><BR>> --<BR>> Bazsi<BR>><BR>> _______________________________________________<BR>> syslog-ng maillist - syslog-ng@lists.balabit.hu<BR>> https://lists.balabit.hu/mailman/listinfo/syslog-ng<BR>> Frequently asked questions at http://www.campin.net/syslog-ng/faq.html<BR>><BR>><BR>-------------- next part --------------<BR>An HTML attachment was scrubbed...<BR>URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20070426/c73047f6/attachment.htm<BR><BR>------------------------------<BR><BR>_______________________________________________<BR>syslog-ng maillist - syslog-ng@lists.balabit.hu<BR>https://lists.balabit.hu/mailman/listinfo/syslog-ng<BR><BR><BR>End of syslog-ng Digest, Vol 24, Issue 28<BR>*****************************************<BR></BLOCKQUOTE><BR><p> 
<hr size=1>
Yahoo! Mail is the world's favourite email. Don't settle for less, <a
href="http://uk.rd.yahoo.com/evt=44106/*http://uk.docs.yahoo.com/mail/winter07.html">sign up for your free
account today</a>.