Description of problem: systemd-journal-upload not saving state Version-Release number of selected component (if applicable): systemd-216-20.fc21.x86_64 How reproducible: Every time so far Steps to Reproduce: 1. Configure /etc/systemd/system/systemd-journal-upload.service.d/system-journal-upload.conf to export logs to --url=http://localhost (as noted in https://bugzilla.redhat.com/show_bug.cgi?id=1193143, the User is also set to root in this file) 2. Set up service to listen on port 19532 and export to local file 3. systemctl daemon-reload 4. systemctl start systemd-journal-upload.service 5. Wait until backlog of journald has been received by port 19532 and written to file 6. Stop systemd-journal-upload process 7. systemctl start systemd-journal-upload.service Actual results: journald backlog is written to --url location again. No state file can be found in the default location Expected results: State file (in default location) to save latest log record sent via s-j-upload. Restarting s-j-upload should only upload new log entries to the --url location. Additional info: I have tried specifying my own --save-state file in my /etc/systemd/system/systemd-journal-upload.service.d/system-journal-upload.conf file, but this makes no difference.
The directory was not created properly by the rpm.
systemd-216-23.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/systemd-216-23.fc21
Package systemd-216-24.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-216-24.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-4991/systemd-216-24.fc21 then log in and leave karma (feedback).
Sorry - won't have access to my Fedora test rig as on holiday until mid April. Will test once back.
systemd-216-24.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.