Bug 1244691

Description of problem:

I use systemd-journal upload service to send logs from multiple virtual machines (senders) to a single virtual machine (receiver) which uses systemd-journal remote service. There are 9 sender virtual machines sending to 1 receiver virtual machine. 

There is a bug in the code of journal-remote service. Instead of writing each virtual machine's (sender) hostname to the beginning of the .journal  under /var/log/journal/remote, it writes the local hostname (i.e. the receiver virtual machine's hostname and not the sender's hostname.
From testing, it seems that each virtual machine (sender) is trying to write to a single .journal file under /var/log/journal/remote which appears to cause a corrupted journal remote service.
I have also noticed that possibly due to this corruption the disk space (of receiver) is quickly filled (available disk space is about 17G and journalctl --disk-usage in each sender node is pretty low ~30MB so this does not justify such a fast filling of 17G disk space)

By monitoring with journalctl -f each sender VM I also noticed that they did not log locally too fast.


Version-Release number of selected component (if applicable):
systemctl --version
systemd 219


How reproducible:
it is reproducible each time you want to send from many virtual machines to a single one via journal-upload and remote services 


Actual results:
remote-receiver_hostname.internalnet.localdomain@*****.journal

Expected results:
remote-sender1_hostname.internalnet.localdomain@*****.journal
remote-sender2_hostname.internalnet.localdomain@*****.journal

Additional info: