Bug 1677313

Summary: [abrt] systemd-container: clock_boottime_supported(): systemd-machined killed by SIGABRT
Product: [Fedora] Fedora Reporter: Martin Kolman <mkolman>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: lnykryn, msekleta, ssahani, s, systemd-maint, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/577fedca04feae2f9c1458b79b20ed1e82a518db
Whiteboard: abrt_hash:08d11b69708839798e22786c9a0055880b7b8842;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-07 09:29:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Martin Kolman 2019-02-14 14:15:33 UTC 
Description of problem:
Happend on locked machine over night, so not really sure what happened, but systemd-logind crashed the same night, taking the logged-in session with it.

Version-Release number of selected component:
systemd-container-239-11.git4dc7dce.fc29

Additional info:
reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd-machined
crash_function: clock_boottime_supported
executable:     /usr/lib/systemd/systemd-machined
journald_cursor: s=583d50c7c1df4d4585d17d052917b6ca;i=45bb;b=07fa6cc498324f10a19a710b06d6eb5b;m=315172eb3b;t=581ced3927c8a;x=6767208f0b320f9c
kernel:         4.20.6-200.fc29.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 clock_boottime_supported at ../src/basic/time-util.c:1347
 #1 triple_timestamp_get at ../src/basic/time-util.c:80
 #2 sd_event_wait at ../src/libsystemd/sd-event/sd-event.c:3412
 #3 sd_event_run at ../src/libsystemd/sd-event/sd-event.c:3566
 #4 bus_event_loop_with_idle at ../src/shared/bus-util.c:119
 #5 manager_run at ../src/machine/machined.c:390

Potential duplicate: bug 1412612
Comment 1 Martin Kolman 2019-02-14 14:15:35 UTC 
Created attachment 1534828 [details]
File: backtrace
Comment 2 Martin Kolman 2019-02-14 14:15:37 UTC 
Created attachment 1534829 [details]
File: cgroup
Comment 3 Martin Kolman 2019-02-14 14:15:38 UTC 
Created attachment 1534830 [details]
File: core_backtrace
Comment 4 Martin Kolman 2019-02-14 14:15:39 UTC 
Created attachment 1534831 [details]
File: cpuinfo
Comment 5 Martin Kolman 2019-02-14 14:15:40 UTC 
Created attachment 1534832 [details]
File: dso_list
Comment 6 Martin Kolman 2019-02-14 14:15:41 UTC 
Created attachment 1534833 [details]
File: environ
Comment 7 Martin Kolman 2019-02-14 14:15:42 UTC 
Created attachment 1534834 [details]
File: limits
Comment 8 Martin Kolman 2019-02-14 14:15:43 UTC 
Created attachment 1534835 [details]
File: maps
Comment 9 Martin Kolman 2019-02-14 14:15:44 UTC 
Created attachment 1534836 [details]
File: mountinfo
Comment 10 Martin Kolman 2019-02-14 14:15:45 UTC 
Created attachment 1534837 [details]
File: open_fds
Comment 11 Martin Kolman 2019-02-14 14:15:46 UTC 
Created attachment 1534838 [details]
File: proc_pid_status
Comment 12 Zbigniew Jędrzejewski-Szmek 2019-04-07 09:29:44 UTC 
It's hard to say for certain without additional logs, but it looks like the usual watchdog failure. I guess that the kernel hung in some driver, causing logind to hang.

*** This bug has been marked as a duplicate of bug 1300212 ***