Bug 54574

Summary:	Assertion 'o->object.type == OBJECT_ENTRY' failed at src/journal/sd-journal.c:64, function init_location(). Aborting.
Product:	systemd	Reporter:	Oleksii Shevchuk <public.avatar>
Component:	general	Assignee:	systemd-bugs
Status:	RESOLVED FIXED	QA Contact:	systemd-bugs
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Oleksii Shevchuk 2012-09-05 19:41:13 UTC

journalctl -fa

Assertion 'o->object.type == OBJECT_ENTRY' failed at src/journal/sd-journal.c:64, function init_location(). Aborting.

gdb$ bt
#0  0xb7768424 in __kernel_vsyscall ()
#1  0xb74f9530 in raise () from /lib/libc.so.6
#2  0xb74fae15 in abort () from /lib/libc.so.6
#3  0xb77947a3 in log_assert (text=text@entry=0xb77a849b "o->object.type == OBJECT_ENTRY", file=file@entry=0xb77a82ef "src/journal/sd-journal.c", line=line@entry=0x40, func=func@entry=0xb77a86e0 <__PRETTY_FUNCTION__.9294> "init_location", format=format@entry=0xb77a7fd0 "Assertion '%s' failed at %s:%u, function %s(). Aborting.") at src/shared/log.c:649
#4  0xb7794c45 in log_assert_failed (text=0xb77a849b "o->object.type == OBJECT_ENTRY", file=0xb77a82ef "src/journal/sd-journal.c", line=0x40, func=0xb77a86e0 <__PRETTY_FUNCTION__.9294> "init_location") at src/shared/log.c:654
#5  0xb77970a5 in compare_order (bo=<optimized out>, bf=<optimized out>, ao=<optimized out>, af=<optimized out>) at src/journal/sd-journal.c:366
#6  real_journal_next (j=j@entry=0xb9654028, direction=direction@entry=DIRECTION_DOWN) at src/journal/sd-journal.c:837
#7  0xb7797b14 in sd_journal_next (j=0xb9654028) at src/journal/sd-journal.c:861
#8  0xb778ff67 in main (argc=0x2, argv=0xbfacaaa4) at src/journal/journalctl.c:838

Comment 1 Lennart Poettering 2012-09-13 17:04:33 UTC

Hmm, this backtrace is corrupted. compare_order() never invokes init_location(), so there's something wrong with the stack.

Which version is this? Can you reproduce this with newest git?

Comment 2 Oleksii Shevchuk 2012-09-13 18:33:55 UTC

All my reports about journalctl/journald is for 189. I think, the madness began after I generated FSS keys

I heavily use 44/188 versions without that issues and segfaults. I don't know, how to manually reproduce that issue

Comment 3 Lennart Poettering 2012-09-24 08:29:53 UTC

I am quite sure this is fixed with 191. Please check if you can reproduce this with 191, if so open a new bug with a bt from 191. Thanks!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.