Your message dated Fri, 24 Jun 2022 08:49:44 +0200
with message-id <[email protected]>
and subject line Re: Bug#1013464: rsyslog omelasticsearch plugin unable to talk
to opensearch 2.0 with bulkmode on
has caused the Debian Bug report #1013464,
regarding rsyslog omelasticsearch plugin unable to talk to opensearch 2.0 with
bulkmode on
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1013464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013464
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rsyslog
Version: 8.2102.0-2+deb11u1
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
I use rsyslog omelasticsearch plugin to feed logs to Opensearch 2.0. It works
well when bulkmode is turned off. But it throws errors when bulkmode is on,
with example below,
{ "request": { "url": "https:\/\/localhost:9200\/_bulk", "postdata":
"{\"index\":{\"_index\":
\"special-2022.06.23\",\"_type\":\"_doc\"}}\n{\"time\":\"2022-06-23T16:25:36.266848+12:00\",\"timereceived\":\"2022-06-23T16:25:36.266848+12:00\",\"severity\":\"INFO\",\"tag\":\"systemd[1]\",
\"msg\": \"Started System Logging Service.\", \"pname\": \"systemd\",
\"host\": \"host123\", \"fromhost\": \"host123\", \"fac\": \"daemon\", \"pri\":
\"30\" }\n\n" }, "reply": { "error": { "root_cause": [ { "type":
"illegal_argument_exception", "reason": "Action\/metadata line [1] contains an
unknown parameter [_type]" } ], "type": "illegal_argument_exception", "reason":
"Action\/metadata line [1] contains an unknown parameter [_type]" }, "status":
400 } }
I have reported this problem upstream, see bug report in
https://github.com/rsyslog/rsyslog/issues/4908
What I have observed so far is the latest rsyslog v8.2206.0 has fixed this
problem. Is there a plan to make this version available soon to Debian stable
or backport?
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-14-amd64 (SMP w/2 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages rsyslog depends on:
ii init-system-helpers 1.60
ii libc6 2.31-13+deb11u3
ii libestr0 0.1.10-2.1+b1
ii libfastjson4 0.99.9-1
ii liblognorm5 2.0.5-1.1
ii libsystemd0 247.3-7
ii libuuid1 2.36.1-8+deb11u1
ii zlib1g 1:1.2.11.dfsg-2+deb11u1
Versions of packages rsyslog recommends:
ii logrotate 3.18.0-2
Versions of packages rsyslog suggests:
pn rsyslog-doc <none>
pn rsyslog-gssapi <none>
pn rsyslog-mongodb <none>
pn rsyslog-mysql | rsyslog-pgsql <none>
pn rsyslog-openssl | rsyslog-gnutls <none>
ii rsyslog-relp 8.2102.0-2+deb11u1
--- End Message ---
--- Begin Message ---
Version: 8.2206.0-1
Am 24.06.22 um 08:18 schrieb David Williams:
Package: rsyslog
Version: 8.2102.0-2+deb11u1
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
I use rsyslog omelasticsearch plugin to feed logs to Opensearch 2.0. It works
well when bulkmode is turned off. But it throws errors when bulkmode is on,
with example below,
{ "request": { "url": "https:\/\/localhost:9200\/_bulk", "postdata": "{\"index\":{\"_index\": \"special-2022.06.23\",\"_type\":\"_doc\"}}\n{\"time\":\"2022-06-23T16:25:36.266848+12:00\",\"timereceived\":\"2022-06-23T16:25:36.266848+12:00\",\"severity\":\"INFO\",\"tag\":\"systemd[1]\", \"msg\": \"Started
System Logging Service.\", \"pname\": \"systemd\", \"host\": \"host123\", \"fromhost\": \"host123\", \"fac\": \"daemon\", \"pri\": \"30\" }\n\n" }, "reply": { "error": { "root_cause": [ { "type": "illegal_argument_exception", "reason": "Action\/metadata line [1] contains an unknown parameter [_type]" } ],
"type": "illegal_argument_exception", "reason": "Action\/metadata line [1] contains an unknown parameter [_type]" }, "status": 400 } }
I have reported this problem upstream, see bug report in
https://github.com/rsyslog/rsyslog/issues/4908
What I have observed so far is the latest rsyslog v8.2206.0 has fixed this problem.
Marking as fixed for that version.
Is there a plan to make this version available soon to Debian stable or
backport?
Sure, I'll update the backport accordingly.
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
