Bug 1708213 - Remote/distributed journal broken in systemd 241 (no workaround), backport 242 required
Summary: Remote/distributed journal broken in systemd 241 (no workaround), backport 24...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 30
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-09 11:28 UTC by kxra
Modified: 2020-02-21 01:17 UTC (History)
5 users (show)

Fixed In Version: systemd-241-14.git18dd3fb.fc30
Clone Of:
Environment:
Last Closed: 2020-02-21 01:17:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 11571 0 None None None 2020-02-06 12:05:59 UTC
Github systemd systemd issues 11571 0 None closed remote logging no longer works with libmicrohttpd 2020-02-06 12:06:00 UTC

Description kxra 2019-05-09 11:28:12 UTC
Description of problem:

Remote/distributed journaling is a pretty important feature for many systemd users.

> At some point, systemd-journal-upload stopped working with libmicrohttpd. systemd-journal-upload doesn't send a Content-Length: header, and therefore libmicrohttpd rejects the upload with a 411 HTTP error. Here's an example session:
> 
> POST /upload HTTP/1.1
> Host: myhost.example
> Transfer-Encoding: chunked
> Content-Type: application/vnd.fdo.journal
> 
> HTTP/1.1 411 Length Required
> Connection: close
> Content-Length: 35
> Content-Type: text/plain
> Date: Thu, 24 Jan 2019 01:21:41 GMT
> 
> The libmicrohttpd maintainers recognize this as a bug (according to the HTTP/1.1 spec, it's okay to omit "Content-Length" if you specify "Transfer-Encoding: chunked"), but they say they won't have time to fix it in the near future. So... either somebody else is going to have to send them a patch, or systemd-journal-remote is going to have to invoke some other method of receiving remote logs.


Version-Release number of selected component (if applicable):
241

How reproducible:
100% always

Steps to Reproduce:
1. Try to use systemd-journal-upload
2. Keep trying
3. Give up

Actual results:

411 error

Expected results:

It communicates with systemd-journal-remote

Additional info:

Comment 1 Zbigniew Jędrzejewski-Szmek 2019-10-21 17:53:52 UTC
Sorry for the delay.

Please set POST on bugzillas which are about applying a patch from upstream. This makes them
easy to spot in the sea of bugs.

Patch applied to v241-stable branch.

Comment 2 Fedora Update System 2020-02-06 15:27:30 UTC
FEDORA-2020-f8e267d6d0 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-f8e267d6d0

Comment 3 Fedora Update System 2020-02-07 01:03:53 UTC
systemd-241-14.git18dd3fb.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-f8e267d6d0

Comment 4 Fedora Update System 2020-02-21 01:17:43 UTC
systemd-241-14.git18dd3fb.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.