FS#41884 - [systemd] systemd-journal-remote: assertion failed

Attached to Project: Arch Linux
Opened by Philipp Klein (kleinph) - Tuesday, 09 September 2014, 06:44 GMT
Last edited by Dave Reisner (falconindy) - Monday, 15 September 2014, 17:37 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Thomas Bächler (brain0)
Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I am trying to grab journal logs from a remote host, but when I try to invoke systemd-journal-remote like in the example in the man page it fails:

$ sudo /usr/lib/systemd/systemd-journal-remote --url http://10.0.0.10:19531

Received 0 descriptors
Spawning curl http://10.0.0.10:19531/entries...
File /var/log/journal/remote/remote-presentr.at:19531.journal corrupted or uncleanly shut down, renaming and replacing.
Opened output file /var/log/journal/remote/remote-presentr.at:19531.journal
Assertion 'h' failed at src/shared/hashmap.c:477, function hashmap_put(). Aborting.

I also tried the -o/--output option both with a directory and a file and it also fails. (The man page is a bit unclear as it says for active sources the -o/--output is required, but the example doesn't use it).

PS: the host I tried to connect hast systemd-journal-gatewayd running and I can access it via browser. libmicrohttpd is als installed.
This task depends upon

Closed by  Dave Reisner (falconindy)
Monday, 15 September 2014, 17:37 GMT
Reason for closing:  Upstream
Additional comments about closing:  https://bugs.freedesktop.org/show_bug.cg i?id=83682
Comment by Dave Reisner (falconindy) - Tuesday, 09 September 2014, 18:31 GMT
Have you reported this upstream?
Comment by Philipp Klein (kleinph) - Tuesday, 09 September 2014, 18:35 GMT
No, should I?
I wanted to be sure that is not tied to some arch specific building issue.
But I did a quick search in the upstream bugtracker and found nothing similiar.
Comment by Dave Reisner (falconindy) - Tuesday, 09 September 2014, 18:40 GMT
No, this isn't a packaging problem. Please report this upstream.
Comment by Philipp Klein (kleinph) - Tuesday, 09 September 2014, 19:00 GMT

Loading...