FS#52012 - [systemd] systemd-journal max journal size misdetected

Attached to Project: Arch Linux
Opened by Dimos Dimoulis (dimosd) - Thursday, 01 December 2016, 06:56 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 07 December 2016, 19:49 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

After upgrading to systemd 232-4 I was getting a message similar to this
System journal (/var/log/journal/) is 0M, max 0M, 0B free
As a result the journal was non-persistent. Reverting to 231-4 the max journal size was correctly detected again.
This task depends upon

Closed by  Dave Reisner (falconindy)
Wednesday, 07 December 2016, 19:49 GMT
Reason for closing:  Fixed
Additional comments about closing:  systemd-232-5
Comment by Dave Reisner (falconindy) - Thursday, 01 December 2016, 13:06 GMT
And the contents of your journald.conf?
Comment by Dimos Dimoulis (dimosd) - Thursday, 01 December 2016, 19:44 GMT
I tried this on 2 Arch installations, same behaviour. I am attaching journal fragments from the 2nd installation where journald.conf was as shipped.
On the 1st installation I also tried setting Storage=persistent but it didn't work.
   journal-231-4.txt (0.4 KiB)
   journal-232-4.txt (0.4 KiB)
   journald.conf (1 KiB)
Comment by Dave Reisner (falconindy) - Thursday, 01 December 2016, 20:04 GMT
https://github.com/systemd/systemd/issues/4790

Loading...