[opensuse] corrupt journals (13.2)
Howdy. While going to the logs to investigate a problem, I find they are corrupt. "journalctl --list-boots" shows only some ancient boots ending in December 2014, 21 in total, while there are actually more: journalctl --list-boots | wc -l 21 journalctl -F _BOOT_ID | wc -l 316 "journalctl --verify" shows a bunch of problems so I thought I would just clear the journals up to the last month or so, but the expected "--vacuum-time=" option apparently doesn't work in openSuSe 13.2. Is there another preferred way to clear the corrupt part of the logs? Thanks. Ralph My desktop is lxde (gtk) and the 13.2 os is: 3.16.7-29-desktop #1 SMP PREEMPT Fri Oct 23 00:46:04 UTC 2015 (6be6a97) x86_64 x86_64 x86_64 GNU/Linux -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday 03 Nov 2015 04:37:35 listreader wrote:
Howdy.
While going to the logs to investigate a problem, I find they are corrupt. "journalctl --list-boots" shows only some ancient boots ending in December 2014, 21 in total, while there are actually more:
journalctl --list-boots | wc -l 21 journalctl -F _BOOT_ID | wc -l 316
"journalctl --verify" shows a bunch of problems so I thought I would just clear the journals up to the last month or so, but the expected "--vacuum-time=" option apparently doesn't work in openSuSe 13.2. Is there another preferred way to clear the corrupt part of the logs?
I think the journal, when it detects corruption, closes that particular file down and creates a new one but don't quote me on it.
Thanks.
Ralph
My desktop is lxde (gtk) and the 13.2 os is: 3.16.7-29-desktop #1 SMP PREEMPT Fri Oct 23 00:46:04 UTC 2015 (6be6a97) x86_64 x86_64 x86_64 GNU/Linux
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 03 Nov 2015 11:11:06 +0000 ianseeks <ianseeks@yahoo.co.uk> wrote:
On Tuesday 03 Nov 2015 04:37:35 listreader wrote:
"journalctl --verify" shows a bunch of problems so I thought I would just clear the journals up to the last month or so, but the expected "--vacuum-time=" option apparently doesn't work in openSuSe 13.2. Is there another preferred way to clear the corrupt part of the logs?
I think the journal, when it detects corruption, closes that particular file down and creates a new one but don't quote me on it.
Considering the current condition of my logs, that appears unfortunately not to be so. I need to get rid of the corrupt logs as they are preventing many of the journalctl commands from working properly. "vacuum-time" seems to be one option to do so according to a brief google of the problem - just keep the newer, un-corrupt parts - but the option doesn't work in openSuSe 13.2. Surely someone has done this before. How? Thanks. Ralph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op woensdag 4 november 2015 01:04:18 schreef listreader:
I need to get rid of the corrupt logs as they are preventing many of the journalctl commands from working properly. "vacuum-time" seems to be one option to do so according to a brief google of the problem - just keep the newer, un-corrupt parts - but the option doesn't work in openSuSe 13.2.
Surely someone has done this before. How?
The persistent logs are in /var/log/journal/ You can delete everything in that folder. Maybe you need to restart the journal daemon after that. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 04 Nov 2015 10:43:34 +0100 Freek de Kruijf <freek@opensuse.org> wrote:
Op woensdag 4 november 2015 01:04:18 schreef listreader:
I need to get rid of the corrupt logs as they are preventing many of the journalctl commands from working properly. "vacuum-time" seems to be one option to do so according to a brief google of the problem - just keep the newer, un-corrupt parts - but the option doesn't work in openSuSe 13.2.
Surely someone has done this before. How?
The persistent logs are in /var/log/journal/ You can delete everything in that folder. Maybe you need to restart the journal daemon after that.
Thank you. I will first try deleting just the files up to and including the latest dated of the corrupt files as identified by ""--verify". Ralph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday 04 Nov 2015 01:04:18 listreader wrote:
On Tue, 03 Nov 2015 11:11:06 +0000
ianseeks <ianseeks@yahoo.co.uk> wrote:
On Tuesday 03 Nov 2015 04:37:35 listreader wrote:
"journalctl --verify" shows a bunch of problems so I thought I would just clear the journals up to the last month or so, but the expected "--vacuum-time=" option apparently doesn't work in openSuSe 13.2. Is there another preferred way to clear the corrupt part of the logs?
I think the journal, when it detects corruption, closes that particular file down and creates a new one but don't quote me on it.
Considering the current condition of my logs, that appears unfortunately not to be so.
I need to get rid of the corrupt logs as they are preventing many of the journalctl commands from working properly. "vacuum-time" seems to be one option to do so according to a brief google of the problem - just keep the newer, un-corrupt parts - but the option doesn't work in openSuSe 13.2.
Surely someone has done this before. How?
Thanks.
Ralph I don;t have anything else to offer. check this old bug report about corrupt journal files, it has some explanations and what/why from LP himself etc https://bugs.freedesktop.org/show_bug.cgi?id=64116 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 04 Nov 2015 10:47:39 +0000 ianseeks <ianseeks@yahoo.co.uk> wrote:
I don;t have anything else to offer. check this old bug report about corrupt journal files, it has some explanations and what/why from LP himself etc https://bugs.freedesktop.org/show_bug.cgi?id=64116
Actually, no, you have everything to offer with that link. Answers the question. Thanks very much. That link explains it all pretty well. A "won't fix" called a "NOTABUG" and offered up as a desired feature by its Creator. What isn't evident is why openSuSe doesn't have the pruning option "--vacuum-time=" to journalctl which apparently exists in other distributions but I guess I can just go manually delete the individual logs older than the latest corruption reported by "--verify" and that should allow the rest of the journalctl tools such as "--list-boots" to correctly work again. Thanks. Ralph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Freek de Kruijf -
ianseeks -
listreader