Re: [rsyslog] segfault with mmkubernetes

2018-04-10 Thread David Lang
On Tue, 10 Apr 2018, Rich Megginson wrote: I think this PR will address most of your concerns: https://github.com/rsyslog/rsyslog/pull/2635 Thanks, that looks like it does a lot! I've got a problem that our test cluster doesn't yet have anything running on it other than kubernetes itself,

Re: [rsyslog] segfault with mmkubernetes

2018-04-10 Thread Rich Megginson via rsyslog
I think this PR will address most of your concerns: https://github.com/rsyslog/rsyslog/pull/2635 > Is there a way to change the log-driver for just one pod/container as opposed to the entire cluster? Not sure. On 04/05/2018 08:12 PM, David Lang wrote: On Thu, 5 Apr 2018, Rich Megginson via

Re: [rsyslog] segfault with mmkubernetes

2018-04-09 Thread Rich Megginson via rsyslog
On 04/06/2018 10:36 PM, David Lang wrote: On Fri, 6 Apr 2018, Rich Megginson wrote: On 04/06/2018 09:08 PM, David Lang wrote: In addition to the authentication, it looks like there is some other issue. where some info isn't there and it logs "filename: ''" and it looks like nothing is

Re: [rsyslog] segfault with mmkubernetes

2018-04-06 Thread David Lang
On Fri, 6 Apr 2018, Rich Megginson wrote: On 04/06/2018 09:08 PM, David Lang wrote: In addition to the authentication, it looks like there is some other issue. where some info isn't there and it logs "filename: ''" and it looks like nothing is attempted 9992.862530379:main Q:Reg/w0  :

Re: [rsyslog] segfault with mmkubernetes

2018-04-06 Thread Rich Megginson via rsyslog
On 04/06/2018 09:08 PM, David Lang wrote: In addition to the authentication, it looks like there is some other issue. where some info isn't there and it logs "filename: ''" and it looks like nothing is attempted 9992.862530379:main Q:Reg/w0  : ruleset.c: processBATCH: next msg 43: E0329

Re: [rsyslog] segfault with mmkubernetes

2018-04-06 Thread David Lang
by comparison 9992.875013025:main Q:Reg/w0 : mmkubernetes.c: mmkubernetes: CONTAINER_NAME: 'k8s_tiller_tiller-deploy-68544fcd8b-g6l9k_kube-system_10decbb3-339f-11e8-a1cb-90e2ba989580_0' CONTAINER_ID_FULL: '1afa1dd3043a9ea4fb8155c05ae074b55247a2f4f8df53cc2f90162c744f5f7f'.

Re: [rsyslog] segfault with mmkubernetes

2018-04-06 Thread David Lang
In addition to the authentication, it looks like there is some other issue. where some info isn't there and it logs "filename: ''" and it looks like nothing is attempted 9992.862530379:main Q:Reg/w0 : ruleset.c: processBATCH: next msg 43: E0329 22:17:55.816218 13181 dns.go:131] Nameserver

Re: [rsyslog] segfault with mmkubernetes

2018-04-06 Thread Rich Megginson via rsyslog
On 04/06/2018 04:07 PM, David Lang wrote: On Fri, 6 Apr 2018, Rich Megginson via rsyslog wrote: It is establishing a connection with the kubernetes server and passing the SSL handshake, I can't see what's happening over the connection, so I don't know what messages are being passed. Is

Re: [rsyslog] segfault with mmkubernetes

2018-04-06 Thread David Lang
On Fri, 6 Apr 2018, Rich Megginson via rsyslog wrote: It is establishing a connection with the kubernetes server and passing the SSL handshake, I can't see what's happening over the connection, so I don't know what messages are being passed. Is there a way to get more detailed info from

Re: [rsyslog] segfault with mmkubernetes

2018-04-06 Thread Rich Megginson via rsyslog
On 04/06/2018 02:48 PM, David Lang wrote: On Thu, 5 Apr 2018, David Lang wrote: now that I have it working, what do we want to do in this release to make it better :-) (thanks for your help by the way) It still doesn't look like it is working.  There should be fields for kubernetes

Re: [rsyslog] segfault with mmkubernetes

2018-04-06 Thread David Lang
On Thu, 5 Apr 2018, David Lang wrote: now that I have it working, what do we want to do in this release to make it better :-) (thanks for your help by the way) It still doesn't look like it is working.  There should be fields for kubernetes namespace_id, pod_id, labels, and usually

Re: [rsyslog] segfault with mmkubernetes

2018-04-05 Thread David Lang
On Thu, 5 Apr 2018, Rich Megginson via rsyslog wrote: this seems to work (I am new to kubernetes and docker, so I don't know what's correct, just that I'm getting data I wasn't before :-) An interesting point, when it wasn't matching, it was adding metadata:{} (empty) to the variables, but

Re: [rsyslog] segfault with mmkubernetes

2018-04-05 Thread Rich Megginson via rsyslog
On 04/05/2018 07:33 PM, David Lang wrote: On Thu, 5 Apr 2018, David Lang wrote: On Thu, 5 Apr 2018, Rich Megginson via rsyslog wrote: On 04/05/2018 01:59 PM, David Lang wrote: I had the wrong URL, but even fixing the URL doesn't seem to be working, I see no attempts to establish a

Re: [rsyslog] segfault with mmkubernetes

2018-04-05 Thread David Lang
On Thu, 5 Apr 2018, David Lang wrote: On Thu, 5 Apr 2018, Rich Megginson via rsyslog wrote: On 04/05/2018 01:59 PM, David Lang wrote: I had the wrong URL, but even fixing the URL doesn't seem to be working, I see no attempts to establish a connection to the kubernetes server

Re: [rsyslog] segfault with mmkubernetes

2018-04-05 Thread David Lang
On Thu, 5 Apr 2018, Rich Megginson via rsyslog wrote: On 04/05/2018 01:59 PM, David Lang wrote: I had the wrong URL, but even fixing the URL doesn't seem to be working, I see no attempts to establish a connection to the kubernetes server module(load="imuxsock") # provides support for local

Re: [rsyslog] segfault with mmkubernetes

2018-04-05 Thread Rich Megginson via rsyslog
On 04/05/2018 01:59 PM, David Lang wrote: I had the wrong URL, but even fixing the URL doesn't seem to be working, I see no attempts to establish a connection to the kubernetes server module(load="imuxsock") # provides support for local system logging (e.g. via logger command)

Re: [rsyslog] segfault with mmkubernetes

2018-04-05 Thread David Lang
I had the wrong URL, but even fixing the URL doesn't seem to be working, I see no attempts to establish a connection to the kubernetes server module(load="imuxsock") # provides support for local system logging (e.g. via logger command) module(load="imklog") # provides kernel logging support

Re: [rsyslog] segfault with mmkubernetes

2018-04-05 Thread David Lang
On Wed, 4 Apr 2018, Rich Megginson via rsyslog wrote: Is there a way to not use them with later versions? Yes, but apparently not without crashing . . . Try defining both filenamerulebase and containerrulebase: module(load="mmkubernetes"

Re: [rsyslog] segfault with mmkubernetes

2018-04-04 Thread Rich Megginson via rsyslog
On 04/04/2018 08:05 PM, Rich Megginson via rsyslog wrote: On 04/04/2018 07:51 PM, David Lang wrote: On Wed, 4 Apr 2018, Rich Megginson wrote: On 04/04/2018 07:18 PM, David Lang wrote: On Wed, 4 Apr 2018, Rich Megginson wrote: On 04/04/2018 06:42 PM, David Lang wrote: On Wed, 4 Apr 2018,

Re: [rsyslog] segfault with mmkubernetes

2018-04-04 Thread Rich Megginson via rsyslog
On 04/04/2018 07:51 PM, David Lang wrote: On Wed, 4 Apr 2018, Rich Megginson wrote: On 04/04/2018 07:18 PM, David Lang wrote: On Wed, 4 Apr 2018, Rich Megginson wrote: On 04/04/2018 06:42 PM, David Lang wrote: On Wed, 4 Apr 2018, Rich Megginson wrote: Stacktrace? a bit hard to get

Re: [rsyslog] segfault with mmkubernetes

2018-04-04 Thread David Lang
On Wed, 4 Apr 2018, Rich Megginson wrote: On 04/04/2018 07:18 PM, David Lang wrote: On Wed, 4 Apr 2018, Rich Megginson wrote: On 04/04/2018 06:42 PM, David Lang wrote: On Wed, 4 Apr 2018, Rich Megginson wrote: Stacktrace? a bit hard to get (things are being run on a production machine

Re: [rsyslog] segfault with mmkubernetes

2018-04-04 Thread Rich Megginson via rsyslog
On 04/04/2018 07:18 PM, David Lang wrote: On Wed, 4 Apr 2018, Rich Megginson wrote: On 04/04/2018 06:42 PM, David Lang wrote: On Wed, 4 Apr 2018, Rich Megginson wrote: Stacktrace? a bit hard to get (things are being run on a production machine after umpteen layers of automation)

Re: [rsyslog] segfault with mmkubernetes

2018-04-04 Thread David Lang
On Wed, 4 Apr 2018, Rich Megginson wrote: On 04/04/2018 06:42 PM, David Lang wrote: On Wed, 4 Apr 2018, Rich Megginson wrote: Stacktrace? a bit hard to get (things are being run on a production machine after umpteen layers of automation) here's what I can get so far ok - so

Re: [rsyslog] segfault with mmkubernetes

2018-04-04 Thread David Lang
On Wed, 4 Apr 2018, Rich Megginson wrote: On 04/04/2018 06:42 PM, David Lang wrote: On Wed, 4 Apr 2018, Rich Megginson wrote: Stacktrace? a bit hard to get (things are being run on a production machine after umpteen layers of automation) here's what I can get so far ok - so

Re: [rsyslog] segfault with mmkubernetes

2018-04-04 Thread Rich Megginson via rsyslog
On 04/04/2018 06:42 PM, David Lang wrote: On Wed, 4 Apr 2018, Rich Megginson wrote: Stacktrace? a bit hard to get (things are being run on a production machine after umpteen layers of automation) here's what I can get so far ok - so definitely something wrong with the filenamerules

Re: [rsyslog] segfault with mmkubernetes

2018-04-04 Thread David Lang
On Wed, 4 Apr 2018, Rich Megginson wrote: Stacktrace? a bit hard to get (things are being run on a production machine after umpteen layers of automation) here's what I can get so far # gdb /usr/sbin/rsyslogd core.3364 GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-100.el7_4.1 Copyright (C)

Re: [rsyslog] segfault with mmkubernetes

2018-04-04 Thread Rich Megginson via rsyslog
On 04/04/2018 06:28 PM, David Lang wrote: On Wed, 4 Apr 2018, David Lang wrote: On Wed, 4 Apr 2018, Rich Megginson wrote: On 04/04/2018 05:57 PM, David Lang wrote: On Wed, 4 Apr 2018, Rich Megginson via rsyslog wrote: On 04/04/2018 05:22 PM, David Lang wrote: I'm trying to use

Re: [rsyslog] segfault with mmkubernetes

2018-04-04 Thread David Lang
On Wed, 4 Apr 2018, David Lang wrote: On Wed, 4 Apr 2018, Rich Megginson wrote: On 04/04/2018 05:57 PM, David Lang wrote: On Wed, 4 Apr 2018, Rich Megginson via rsyslog wrote: On 04/04/2018 05:22 PM, David Lang wrote: I'm trying to use mmkubernetes where the docker containers are logging

Re: [rsyslog] segfault with mmkubernetes

2018-04-04 Thread David Lang
On Wed, 4 Apr 2018, Rich Megginson wrote: On 04/04/2018 05:57 PM, David Lang wrote: On Wed, 4 Apr 2018, Rich Megginson via rsyslog wrote: On 04/04/2018 05:22 PM, David Lang wrote: I'm trying to use mmkubernetes where the docker containers are logging via journald. my config is:

Re: [rsyslog] segfault with mmkubernetes

2018-04-04 Thread Rich Megginson via rsyslog
On 04/04/2018 05:57 PM, David Lang wrote: On Wed, 4 Apr 2018, Rich Megginson via rsyslog wrote: On 04/04/2018 05:22 PM, David Lang wrote: I'm trying to use mmkubernetes where the docker containers are logging via journald. my config is: module(load="imfile" PollingInterval="10") # provided

Re: [rsyslog] segfault with mmkubernetes

2018-04-04 Thread David Lang
On Wed, 4 Apr 2018, Rich Megginson via rsyslog wrote: On 04/04/2018 05:22 PM, David Lang wrote: I'm trying to use mmkubernetes where the docker containers are logging via journald. my config is: module(load="imfile" PollingInterval="10") # provided support for monitoring alternate log

Re: [rsyslog] segfault with mmkubernetes

2018-04-04 Thread Rich Megginson via rsyslog
On 04/04/2018 05:43 PM, Rich Megginson via rsyslog wrote: On 04/04/2018 05:22 PM, David Lang wrote: I'm trying to use mmkubernetes where the docker containers are logging via journald. my config is: module(load="imfile" PollingInterval="10") # provided support for monitoring alternate log

Re: [rsyslog] segfault with mmkubernetes

2018-04-04 Thread Rich Megginson via rsyslog
On 04/04/2018 05:22 PM, David Lang wrote: I'm trying to use mmkubernetes where the docker containers are logging via journald. my config is: module(load="imfile" PollingInterval="10") # provided support for monitoring alternate log files module(load="imuxsock") # provides support for local

[rsyslog] segfault with mmkubernetes

2018-04-04 Thread David Lang
I'm trying to use mmkubernetes where the docker containers are logging via journald. my config is: module(load="imfile" PollingInterval="10") # provided support for monitoring alternate log files module(load="imuxsock") # provides support for local system logging (e.g. via logger command)