-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
systemd-journal-gatewayd crashes if request has follow
and unmatched KEY=match
parameter
#3873
Closed
1 of 2 tasks
Labels
Comments
follow
and unmatched KEY=match
parameterfollow
and unmatched KEY=match
parameter
eungjun-yi
pushed a commit
to eungjun-yi/systemd
that referenced
this issue
Aug 6, 2016
When client requests to get logs with `follow` and `KEY=match` that doesn't match any log entry, journal-gatewayd segfaulted. Make request_reader_entries to return zero in such case to wait for matching entries. This fixes systemd#3873.
eungjun-yi
pushed a commit
to eungjun-yi/systemd
that referenced
this issue
Aug 6, 2016
When client requests to get logs with `follow` and `KEY=match` that doesn't match any log entry, journal-gatewayd segfaulted. Make request_reader_entries to return zero in such case to wait for matching entries. This fixes systemd#3873.
keszybz
pushed a commit
that referenced
this issue
Aug 6, 2016
When client requests to get logs with `follow` and `KEY=match` that doesn't match any log entry, journal-gatewayd segfaulted. Make request_reader_entries to return zero in such case to wait for matching entries. This fixes #3873.
edolstra
pushed a commit
to NixOS/systemd
that referenced
this issue
Sep 30, 2016
When client requests to get logs with `follow` and `KEY=match` that doesn't match any log entry, journal-gatewayd segfaulted. Make request_reader_entries to return zero in such case to wait for matching entries. This fixes systemd#3873. (cherry picked from commit 3475fc5)
AnchorCat
pushed a commit
to AnchorCat/systemd
that referenced
this issue
May 9, 2017
When client requests to get logs with `follow` and `KEY=match` that doesn't match any log entry, journal-gatewayd segfaulted. Make request_reader_entries to return zero in such case to wait for matching entries. This fixes systemd#3873. (cherry picked from commit 3475fc5)
keszybz
pushed a commit
to systemd/systemd-stable
that referenced
this issue
May 30, 2017
When client requests to get logs with `follow` and `KEY=match` that doesn't match any log entry, journal-gatewayd segfaulted. Make request_reader_entries to return zero in such case to wait for matching entries. This fixes systemd/systemd#3873. (cherry picked from commit 3475fc5)
keszybz
pushed a commit
to systemd/systemd-stable
that referenced
this issue
May 30, 2017
When client requests to get logs with `follow` and `KEY=match` that doesn't match any log entry, journal-gatewayd segfaulted. Make request_reader_entries to return zero in such case to wait for matching entries. This fixes systemd/systemd#3873. (cherry picked from commit 3475fc5)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submission type
NOTE: Do not submit anything other than bug reports or RFEs via the issue tracker!
systemd version the issue has been seen with
systemd 231
Used distribution
Arch Linux
In case of bug report: Expected behaviour you didn't see
systemd-journal-gatewayd doesn't crash
In case of bug report: Unexpected behaviour you saw
systemd-journal-gatewayd crashes as follows:
In case of bug report: Steps to reproduce the problem
Start systemd-journald-gatewayd
sudo systemctl start systemd-journal-gatewayd
Request logs with
follow
andKEY=match
parameter that doesn't match any log entry.curl http://localhost:19531/entries?follow&FOO=bar
The text was updated successfully, but these errors were encountered: