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