similar to: [Bug 871] New: Running two instances of ulog causes abort in libnfnetlink

Displaying 20 results from an estimated 500 matches similar to: "[Bug 871] New: Running two instances of ulog causes abort in libnfnetlink"

2007 Jul 31
0
[ANNOUNCE] libnfnetlink release 0.0.30
Hi! The netfilter project proudly presents libnfnetlink 0.0.30 libnfnetlink is the low-level library for netfilter related kernel/userspace communication. It provides a generic messaging infrastructure for in-kernel netfilter subsystems (such as nfnetlink_log, nfnetlink_queue, nfnetlink_conntrack) and their respective users and/or management tools in userspace. You can download it from:
2005 Sep 25
0
[ANNOUNCE] Release of libnfnetlink, libnfnetlink_conntrack and conntrack
Hi! The netfilter project proudly presents: libnfnetlink-0.0.10 libnfnetlink_conntrack-0.0.10 conntrack-0.81 Each of those three releases is the first official release of the respective project. They're the counterparts to the first pieces of the "next generation" netfilter subsystem that will be present in the 2.6.14 linux kernel release. libnfnetlink is the low-level
2018 Apr 27
0
[Bug 1251] New: Hide private symbols in libnfnetlink
https://bugzilla.netfilter.org/show_bug.cgi?id=1251 Bug ID: 1251 Summary: Hide private symbols in libnfnetlink Product: libnfnetlink Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: libnfnetlink Assignee: netfilter-buglog at
2012 Jun 17
0
[ANNOUNCE] ulogd 2.0.0 release
Hi! The Netfilter project proudly presents: ulogd 2.0.0 ulogd is a userspace logging daemon for netfilter/iptables related logging. This includes per-packet logging of security violations, per-packet logging for accounting, per-flow logging and flexible user-defined accounting. ulogd was almost entirely written by Harald Welte, with contributions from fellow hackers such as Pablo Neira
2016 Dec 19
0
[Bug 1103] New: ulogd installation error
https://bugzilla.netfilter.org/show_bug.cgi?id=1103 Bug ID: 1103 Summary: ulogd installation error Product: ulogd Version: 2.0.0beta1 Hardware: x86_64 OS: Ubuntu Status: NEW Severity: enhancement Priority: P5 Component: ulogd Assignee: netfilter-buglog at lists.netfilter.org
2017 Jun 20
2
[ovirt-users] Very poor GlusterFS performance
[Adding gluster-users] On Mon, Jun 19, 2017 at 8:16 PM, Chris Boot <bootc at bootc.net> wrote: > Hi folks, > > I have 3x servers in a "hyper-converged" oVirt 4.1.2 + GlusterFS 3.10 > configuration. My VMs run off a replica 3 arbiter 1 volume comprised of > 6 bricks, which themselves live on two SSDs in each of the servers (one > brick per SSD). The bricks are
2017 Jun 20
5
[ovirt-users] Very poor GlusterFS performance
Couple of things: 1. Like Darrell suggested, you should enable stat-prefetch and increase client and server event threads to 4. # gluster volume set <VOL> performance.stat-prefetch on # gluster volume set <VOL> client.event-threads 4 # gluster volume set <VOL> server.event-threads 4 2. Also glusterfs-3.10.1 and above has a shard performance bug fix -
2005 Nov 05
0
[ANNOUNCE] multiple netfilter.org releases
Hi! Today the netfilter project released libnfnetlink-0.0.11 ftp://ftp.netfilter.org/pub/libnfnetlink/libnfnetlink-0.0.11.tar.bz2 This is the low-level communications library libnetfilter_log-0.0.10 ftp://ftp.netfilter.org/pub/libnetfilter_log/libnetfilter_log-0.0.10.tar.bz2 This is the userspace library for nfnetlink_log in 2.6.14 It is used by the upcoming ulogd-2.00beta release Needs
2017 Jun 20
0
[ovirt-users] Very poor GlusterFS performance
Have you tried with: performance.strict-o-direct : off performance.strict-write-ordering : off They can be changed dynamically. On 20 June 2017 at 17:21, Sahina Bose <sabose at redhat.com> wrote: > [Adding gluster-users] > > On Mon, Jun 19, 2017 at 8:16 PM, Chris Boot <bootc at bootc.net> wrote: > >> Hi folks, >> >> I have 3x servers in a
2017 Jun 20
0
[ovirt-users] Very poor GlusterFS performance
Dear Krutika, Sorry for asking so naively but can you tell me on what factor do you base that the client and server event-threads parameters for a volume should be set to 4? Is this metric for example based on the number of cores a GlusterFS server has? I am asking because I saw my GlusterFS volumes are set to 2 and would like to set these parameters to something meaningful for performance
2013 Oct 16
0
Is UPSD necessary for average users?
On 16/10/13 06:40, David N Melik wrote: > On Tue, 15 Oct 2013 21:56:16 -0400 > Charles Lepple <clepple at gmail.com> wrote: >>>> > >> What are you trying to optimize? >>> > > >>> > > nothing, but I just did not want another daemon running, or at >>> > > least I do not want a port open that can access the UPS, because I
2013 Nov 04
2
Is UPSD necessary for average users?
On Wed, 16 Oct 2013 08:19:11 +0100 Chris Boot <bootc at bootc.net> wrote: > >> > I forgot to mention: by default, NUT listens on localhost. If > >> > you are using Linux, you could add a "-m owner --uid-owner" rule > >> > to iptables to only match the UID for the NUT system user. > > > > Thanks; if it listens on localhost by default,
2014 Nov 02
0
[Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol
https://bugzilla.netfilter.org/show_bug.cgi?id=977 --- Comment #6 from Netbug <b1b30ee4 at opayq.com> --- I upgraded to ulogd 2.0.4 & kernel 3.17.2 but these did not make a difference, here's how the output looks now; Sat Nov 1 17:07:03 2014 <5> ulogd.c:843 building new pluginstance stack:
2014 Nov 22
0
[Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol
https://bugzilla.netfilter.org/show_bug.cgi?id=977 Netbug <b1b30ee4 at opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #27 from Netbug <b1b30ee4 at opayq.com>
2005 May 31
0
ULOG logging may fail on some ulogd/logrotate configurations
FYI. I have not been able to determine 100% that logrotate does this, but ulogd appears to stop logging whenever logrotate runs. So far, the only obvious commonality that I see is that logrotate ran and that the /var/log/ulogd/ulogd.syslogemu is completely empty until I restart ulogd. I have proven that the logging is broken by manually performing a network operation that Shorewall normally
2013 Sep 19
3
UPS compatibility list
On 19/09/13 01:30, Kris Jordan wrote: > Luke-Jr wrote, On 9/18/2013 1:02 PM: >> I wanted to suggest some rating for functionality. I got the UPS >> available >> that seemed to have the best possible rating from NUT's list (Eaton >> Powerware >> UPS 1500), and found out it doesn't support telling me battery level or >> runtime! :/ > > I'm
2006 Mar 22
0
[ulog 1.24] wrong version and no log in ulogd.log
hi. ulogd.c use 1.23 as its version while it is shipped with ulog 1.24 moreover ulogd does not log anymore in ulogd.log like ulogd 1.23 did
2003 Jul 29
1
Web Interface to browse ULOG messages real time
Going deeper on last post "[Shorewall-users] logging", I found a very nice package that handles ULOG messages in a web interface, where you can browse the events from a MySql database produced by ULOGD. Real time. The name is: ULOGD-PHP From the site: ------------------------------------------- ulogd-php is able to : show the last hosts that broke packets on your firewall. show the
2013 Aug 15
12
[Bug 845] New: checking for LIBNFNETLINK... configure: error: Package requirements (libnfnetlink >= 0.0.41) were not met:
https://bugzilla.netfilter.org/show_bug.cgi?id=845 Summary: checking for LIBNFNETLINK... configure: error: Package requirements (libnfnetlink >= 0.0.41) were not met: Product: libnetfilter_queue Version: unspecified Platform: i386 OS/Version: RedHat Linux Status: NEW Severity: normal
2014 Nov 07
7
[Bug 986] New: ulogd fails to build against linux headers >= 3.17.0 due to ULOG target removal
https://bugzilla.netfilter.org/show_bug.cgi?id=986 Bug ID: 986 Summary: ulogd fails to build against linux headers >= 3.17.0 due to ULOG target removal Product: ulogd Version: SVN (please provide timestamp) Hardware: x86_64 OS: Gentoo Status: NEW Severity: major Priority: