journalctl verify fails for directories whose files are created by systemd-journal-remote service.

[sakellar]

"journalctl --verify -D journalctl --verify -D /var/log/journal/somedirectory/" fails
in cases where inside /var/log/journal/somedirectory/ are log files created by systemd-journal-remote service.
error shown :
38f960: data object's entry array not sorted
File corruption detected at /var/log/journal/somedirectory//somefile.journal:000000 (of 8388608 bytes, 0%).

[kihaloul]

Hello,

I reproduced this issue with two Fedora 22 VMs running on virtualbox.
systemd-journal-remote runs on one VM with the following command:

sudo ./systemd-journal-remote --listen-http=192.168.56.101:2000

and systemd-journal-upload on the other:

sudo ./systemd-journal-upload --url=http://192.168.56.101:2000 --save-state

systemd version is 219:
./systemctl --version
systemd 219
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS -KMOD +IDN

And the file in /var/log/journal/remote is corrupted:
journalctl --verify -D /var/log/journal/remote/
38f960: data object's entry array not sorted
File corruption detected at /var/log/journal/remote//remote-fedora22.journal:000000 (of 8388608 bytes, 0%).
FAIL: /var/log/journal/remote//remote-fedora22.journal (Bad message)

No reboots or restarts of upload/remote have taken place. The corruption shows above could be seen both while journal-remote was running, and after it was stopped.
However, logs are received by the sender and read with journalctl, even though the journalctl --verify shows that the remote journal files are corrupted.

[canassa]

I am also getting this error on Ubuntu 16.04