[CentOS] systemd-journald errors

C. L. Martinez carlopmart at gmail.com
Sun Oct 29 08:06:07 UTC 2017


On Sun, Oct 29, 2017 at 07:54:50AM +0000, C. L. Martinez wrote:
> Hi all,
> 
>  I have 5 CentOS 7 virtual guests installed (all fully patched to latest release) and i have the following error in all of them:
> 
> systemd-journald[7779]: File /run/log/journal/b4a41f4214ca44f898638301891a6f2e/system.journal corrupted or uncleanly shut down, renaming and replacing.
> 
>  ?? .. And I don't understand why. I have configured "Storage=volatile" in journald.conf ...
> 
>  How can I debug this error? Is it possible to disable systemd-journald thoroughly?
> 
> Thanks
> -- 
> Greetings,
> C. L. Martinez

Yep, I have changed "Storage=none" in journald.conf's file and now:

[  173.254585] INFO: rcu_sched self-detected stall on CPU { 0}  (t=104510 jiffies g=2869 c=2868 q=8)
[  173.255985] Task dump for CPU 0:
[  173.256473] swapper/0       R  running task        0     0      0 0x00000000
[  173.257557]  ffffffff819f9480 0d5a685ae9da1018 ffff88004fc03db8 ffffffff810c3aa8
[  173.258744]  0000000000000000 ffffffff81a550c0 ffff88004fc03dd0 ffffffff810c7439
[  173.259928]  0000000000000001 ffff88004fc03e00 ffffffff81137b20 ffff88004fc10260
[  173.261158] Call Trace:
[  173.261533]  <IRQ>  [<ffffffff810c3aa8>] sched_show_task+0xa8/0x110
[  173.262502]  [<ffffffff810c7439>] dump_cpu_task+0x39/0x70
[  173.263297]  [<ffffffff81137b20>] rcu_dump_cpu_stacks+0x90/0xd0
[  173.264163]  [<ffffffff8113b142>] rcu_check_callbacks+0x442/0x730
[  173.265054]  [<ffffffff810eb41c>] ? update_wall_time+0x26c/0x6c0
[  173.265936]  [<ffffffff810f3000>] ? tick_sched_do_timer+0x50/0x50
[  173.266833]  [<ffffffff8109a306>] update_process_times+0x46/0x80
[  173.267725]  [<ffffffff810f2e00>] tick_sched_handle+0x30/0x70
[  173.268565]  [<ffffffff810f3039>] tick_sched_timer+0x39/0x80
[  173.269397]  [<ffffffff810b4af4>] __hrtimer_run_queues+0xd4/0x260
[  173.270287]  [<ffffffff810b508f>] hrtimer_interrupt+0xaf/0x1d0
[  173.271140]  [<ffffffff81053895>] local_apic_timer_interrupt+0x35/0x60
[  173.272097]  [<ffffffff816b777d>] smp_apic_timer_interrupt+0x3d/0x50
[  173.273023]  [<ffffffff816b5cdd>] apic_timer_interrupt+0x6d/0x80
[  173.273898]  <EOI>  [<ffffffff816ab566>] ? native_safe_halt+0x6/0x10
[  173.274872]  [<ffffffff816ab3fe>] default_idle+0x1e/0xc0
[  173.275652]  [<ffffffff81035006>] arch_cpu_idle+0x26/0x30
[  173.276442]  [<ffffffff810e7bda>] cpu_startup_entry+0x14a/0x1c0
[  173.277322]  [<ffffffff81692d17>] rest_init+0x77/0x80
[  173.278065]  [<ffffffff81b45060>] start_kernel+0x439/0x45a
[  173.278865]  [<ffffffff81b44a30>] ? repair_env_string+0x5c/0x5c
[  173.279724]  [<ffffffff81b44120>] ? early_idt_handler_array+0x120/0x120
[  173.280682]  [<ffffffff81b445ef>] x86_64_start_reservations+0x24/0x26
[  173.281616]  [<ffffffff81b44740>] x86_64_start_kernel+0x14f/0x172

 ¿¿??? WTF??? ...

-- 
Greetings,
C. L. Martinez



More information about the CentOS mailing list