Re: [rsyslog] Lookup Table FH leak?

2016-10-27 Thread singh.janmejay 
Sorry, I meant change log may have a ref(just have a look at master change
log).

On Oct 28, 2016 10:17 AM, "singh.janmejay"  wrote:

> FD leak on reload is fixed upstream already. Can't recall which release.
> Release notes may have a ref.
>
> On Oct 28, 2016 6:15 AM, "David Lang"  wrote:
>
>> I'm catching up on old mail, I think I saw fixes for the lookup table
>> functionality go through recently, can you check with the latest version?
>>
>> David Lang
>>
>> On Mon, 8 Aug 2016, Christian Ramseyer wrote:
>>
>> Date: Mon, 8 Aug 2016 14:31:06 +0200
>>> From: Christian Ramseyer 
>>> Reply-To: rsyslog-users 
>>> To: rsyslog-users 
>>> Subject: [rsyslog] Lookup Table FH leak?
>>>
>>> Hi
>>>
>>> I've been testing the lookup table feature in 8.18.0 for a while now and
>>> it works great, good stuff!
>>>
>>> However there seems to be an issue that reloading the table leaks a
>>> filehandle:
>>>
>>> # config:
>>>
>>> lookup_table(name="mylookup" file="/etc/lookup.json" reloadOnHUP="on")
>>>
>>> # freshly started rsyslog, 1 FH as expected
>>>
>>> #  lsof -p $(pgrep -f rsyslog/sbin/rsyslogd) | fgrep .json
>>> rsyslogd 14135 root 3r REG  254,1 8467305  537540076 /etc/lookup.json
>>>
>>> # HUP a few times
>>>
>>> #  kill -1  $(pgrep -f rsyslog/sbin/rsyslogd)
>>> #  kill -1  $(pgrep -f rsyslog/sbin/rsyslogd)
>>> #  kill -1  $(pgrep -f rsyslog/sbin/rsyslogd)
>>>
>>> # results in 1 FH per HUP
>>>
>>> #  lsof -p $(pgrep -f rsyslog/sbin/rsyslogd) | fgrep .json
>>> rsyslogd 14135 root  3r REG  254,1 8467305  537540076 /etc/lookup.json
>>> rsyslogd 14135 root 11r REG  254,1 8467305  537540076 /etc/lookup.json
>>> rsyslogd 14135 root 12r REG  254,1 8467305  537540076 /etc/lookup.json
>>> rsyslogd 14135 root 13r REG  254,1 8467305  537540076 /etc/lookup.json
>>>
>>>
>>> Is this a known issue? I've looked at the open issues and commits in
>>> 8.19.0/8.20.0 and couldn't find any mention of it so I didn't try a
>>> newer release for now. But I'm of course willing to upgrade if you guys
>>> think this is addressed already.
>>>
>>> Build Info:
>>>
>>> rsyslogd 8.18.0, compiled with:
>>> PLATFORM:   x86_64-pc-linux-gnu
>>> PLATFORM (lsb_release -d):
>>> FEATURE_REGEXP: Yes
>>> GSSAPI Kerberos 5 support:  No
>>> FEATURE_DEBUG (debug build, slow code): No
>>> 32bit Atomic operations supported:  Yes
>>> 64bit Atomic operations supported:  Yes
>>> memory allocator:   system default
>>> Runtime Instrumentation (slow code):No
>>> uuid support:   Yes
>>> Number of Bits in RainerScript integers: 64
>>>
>>> Thanks
>>> Christian
>>> ___
>>> rsyslog mailing list
>>> http://lists.adiscon.net/mailman/listinfo/rsyslog
>>> http://www.rsyslog.com/professional-services/
>>> What's up with rsyslog? Follow https://twitter.com/rgerhards
>>> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad
>>> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
>>> DON'T LIKE THAT.
>>>
>>> ___
>> rsyslog mailing list
>> http://lists.adiscon.net/mailman/listinfo/rsyslog
>> http://www.rsyslog.com/professional-services/
>> What's up with rsyslog? Follow https://twitter.com/rgerhards
>> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad
>> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
>> DON'T LIKE THAT.
>>
>
___
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Re: [rsyslog] Lookup Table FH leak?

2016-10-27 Thread singh.janmejay 
FD leak on reload is fixed upstream already. Can't recall which release.
Release notes may have a ref.

On Oct 28, 2016 6:15 AM, "David Lang"  wrote:

> I'm catching up on old mail, I think I saw fixes for the lookup table
> functionality go through recently, can you check with the latest version?
>
> David Lang
>
> On Mon, 8 Aug 2016, Christian Ramseyer wrote:
>
> Date: Mon, 8 Aug 2016 14:31:06 +0200
>> From: Christian Ramseyer 
>> Reply-To: rsyslog-users 
>> To: rsyslog-users 
>> Subject: [rsyslog] Lookup Table FH leak?
>>
>> Hi
>>
>> I've been testing the lookup table feature in 8.18.0 for a while now and
>> it works great, good stuff!
>>
>> However there seems to be an issue that reloading the table leaks a
>> filehandle:
>>
>> # config:
>>
>> lookup_table(name="mylookup" file="/etc/lookup.json" reloadOnHUP="on")
>>
>> # freshly started rsyslog, 1 FH as expected
>>
>> #  lsof -p $(pgrep -f rsyslog/sbin/rsyslogd) | fgrep .json
>> rsyslogd 14135 root 3r REG  254,1 8467305  537540076 /etc/lookup.json
>>
>> # HUP a few times
>>
>> #  kill -1  $(pgrep -f rsyslog/sbin/rsyslogd)
>> #  kill -1  $(pgrep -f rsyslog/sbin/rsyslogd)
>> #  kill -1  $(pgrep -f rsyslog/sbin/rsyslogd)
>>
>> # results in 1 FH per HUP
>>
>> #  lsof -p $(pgrep -f rsyslog/sbin/rsyslogd) | fgrep .json
>> rsyslogd 14135 root  3r REG  254,1 8467305  537540076 /etc/lookup.json
>> rsyslogd 14135 root 11r REG  254,1 8467305  537540076 /etc/lookup.json
>> rsyslogd 14135 root 12r REG  254,1 8467305  537540076 /etc/lookup.json
>> rsyslogd 14135 root 13r REG  254,1 8467305  537540076 /etc/lookup.json
>>
>>
>> Is this a known issue? I've looked at the open issues and commits in
>> 8.19.0/8.20.0 and couldn't find any mention of it so I didn't try a
>> newer release for now. But I'm of course willing to upgrade if you guys
>> think this is addressed already.
>>
>> Build Info:
>>
>> rsyslogd 8.18.0, compiled with:
>> PLATFORM:   x86_64-pc-linux-gnu
>> PLATFORM (lsb_release -d):
>> FEATURE_REGEXP: Yes
>> GSSAPI Kerberos 5 support:  No
>> FEATURE_DEBUG (debug build, slow code): No
>> 32bit Atomic operations supported:  Yes
>> 64bit Atomic operations supported:  Yes
>> memory allocator:   system default
>> Runtime Instrumentation (slow code):No
>> uuid support:   Yes
>> Number of Bits in RainerScript integers: 64
>>
>> Thanks
>> Christian
>> ___
>> rsyslog mailing list
>> http://lists.adiscon.net/mailman/listinfo/rsyslog
>> http://www.rsyslog.com/professional-services/
>> What's up with rsyslog? Follow https://twitter.com/rgerhards
>> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad
>> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
>> DON'T LIKE THAT.
>>
>> ___
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com/professional-services/
> What's up with rsyslog? Follow https://twitter.com/rgerhards
> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad
> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
> DON'T LIKE THAT.
>
___
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Re: [rsyslog] Lookup Table FH leak?

2016-10-27 Thread David Lang 
I'm catching up on old mail, I think I saw fixes for the lookup table 
functionality go through recently, can you check with the latest version?


David Lang

On Mon, 8 Aug 2016, Christian Ramseyer wrote:


Date: Mon, 8 Aug 2016 14:31:06 +0200
From: Christian Ramseyer 
Reply-To: rsyslog-users 
To: rsyslog-users 
Subject: [rsyslog] Lookup Table FH leak?

Hi

I've been testing the lookup table feature in 8.18.0 for a while now and
it works great, good stuff!

However there seems to be an issue that reloading the table leaks a
filehandle:

# config:

lookup_table(name="mylookup" file="/etc/lookup.json" reloadOnHUP="on")

# freshly started rsyslog, 1 FH as expected

#  lsof -p $(pgrep -f rsyslog/sbin/rsyslogd) | fgrep .json
rsyslogd 14135 root 3r REG  254,1 8467305  537540076 /etc/lookup.json

# HUP a few times

#  kill -1  $(pgrep -f rsyslog/sbin/rsyslogd)
#  kill -1  $(pgrep -f rsyslog/sbin/rsyslogd)
#  kill -1  $(pgrep -f rsyslog/sbin/rsyslogd)

# results in 1 FH per HUP

#  lsof -p $(pgrep -f rsyslog/sbin/rsyslogd) | fgrep .json
rsyslogd 14135 root  3r REG  254,1 8467305  537540076 /etc/lookup.json
rsyslogd 14135 root 11r REG  254,1 8467305  537540076 /etc/lookup.json
rsyslogd 14135 root 12r REG  254,1 8467305  537540076 /etc/lookup.json
rsyslogd 14135 root 13r REG  254,1 8467305  537540076 /etc/lookup.json


Is this a known issue? I've looked at the open issues and commits in
8.19.0/8.20.0 and couldn't find any mention of it so I didn't try a
newer release for now. But I'm of course willing to upgrade if you guys
think this is addressed already.

Build Info:

rsyslogd 8.18.0, compiled with:
PLATFORM:   x86_64-pc-linux-gnu
PLATFORM (lsb_release -d):
FEATURE_REGEXP: Yes
GSSAPI Kerberos 5 support:  No
FEATURE_DEBUG (debug build, slow code): No
32bit Atomic operations supported:  Yes
64bit Atomic operations supported:  Yes
memory allocator:   system default
Runtime Instrumentation (slow code):No
uuid support:   Yes
Number of Bits in RainerScript integers: 64

Thanks
Christian
___
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.


___
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.