systemd-journald crashed with SIGABRT in journal_file_move_to_object()

[LAZA]

Crashed over night while recovering backup.

.

Xubuntu 15.04 beta1

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: systemd 219-4ubuntu9
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
Date: Tue Mar 24 23:13:27 2015
ExecutablePath: /lib/systemd/systemd-journald
ExecutableTimestamp: 1427124595
InstallationDate: Installed on 2015-03-23 (1 days ago)
InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Gigabyte Technology Co., Ltd. GA-MA790GP-UD4H
ProcCmdline: /lib/systemd/systemd-journald
ProcCwd: /
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic root=UUID=45370e47-0377-4e9d-87fc-81889c091532 ro quiet splash
Signal: 6
SourcePackage: systemd
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: systemd-journald crashed with SIGABRT
UpgradeStatus: Upgraded to vivid on 2015-03-24 (0 days ago)
UserGroups:

dmi.bios.date: 07/08/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F7c
dmi.board.name: GA-MA790GP-UD4H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7c:bd07/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA790GP-UD4H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Apport retracing service (apport)]

StacktraceTop:
 journal_file_move_to_object (f=f@entry=0x7f07dbc145a0, type=type@entry=OBJECT_ENTRY_ARRAY, offset=offset@entry=1562248, ret=ret@entry=0x7fff737475a0) at ../src/journal/journal-file.c:498
 link_entry_into_array.lto_priv.143 (f=f@entry=0x7f07dbc145a0, first=0x7f07d86db6f0, idx=idx@entry=0x7fff73747620, p=p@entry=1632608) at ../src/journal/journal-file.c:1161
 link_entry_into_array_plus_one (p=1632608, idx=0x7f07d86db6f8, first=0x7f07d86db6f0, extra=0x7f07d86db6e8, f=0x7f07dbc145a0) at ../src/journal/journal-file.c:1237
 journal_file_link_entry_item (i=<optimized out>, offset=1632608, o=0x7f07d86db6c0, f=0x7f07dbc145a0) at ../src/journal/journal-file.c:1261
 journal_file_link_entry (offset=1632608, o=0x7f07d8820960, f=0x7f07dbc145a0) at ../src/journal/journal-file.c:1302

[Martin Pitt (pitti)]

Ah, were you perhaps overwriting files in /var/log/journal/, while systemd/journal were actually running? Changing the files underneath it certainly doesn't go well. Can you be more specific what happened here? Can you reproduce this somehow?

[LAZA (laza74)]

No, shure not!

I just recovered files and directories in and into /home/

Systemd-journald crashes twice a day with #1433320 and #1437915 and #1444654 and #1437896 and #1439507 and ...

How can i reproduce this if i dont want to erase the machine complete and recover the backup again?

[Martin Pitt (pitti)]

> How can i reproduce this if i dont want to erase the machine complete and recover the backup again?

Do you have /var/log/journal/ , i. e. enabled persistant journal? If so, you could try and move it away (or just delete it if you don't care). If not, the journal is just kept in /run/log/journal and started fresh with each boot.

[LAZA (laza74)]

Thanks for the hint, Martin.
Maybe there was also a hardware problem cause the PC froze and was dead...

Recovering on a new machine was without problems.

[Martin Pitt (pitti)]

Is there anything left to do/analyze here?

[LAZA (laza74)]

In my opinion not... - i will report a new bug if somethings goes wrong again.

[Martin Pitt (pitti)]

Okay, closing then.

[mxyzptlk (mxyzptlk)]

Keep getting this bug lately in 17.10. Seems to happen most often when using Chrome/Chromium or Opera, and more often still if using one of those browsers on a Google property (Google Search, Google Images, Gmail, YouTube).

[mxyzptlk (mxyzptlk)]

This bug was marked as invalid, but I get the error about every other day. Is there any info I can provide to help verify the bug?

[mxyzptlk (mxyzptlk)]

Another day, another couple systemd-journald crash just like this invalid bug.

[pigs-on-the-swim (dw1-4)]

I get the bug in 18.04 - what does this mean?