Bug 1680004

Summary: [abrt] systemd-container: __clock_gettime(): systemd-machined killed by SIGABRT
Product: [Fedora] Fedora Reporter: aoellerer
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/bae402d43689d400696c1549967930e2061b3276
Whiteboard: abrt_hash:860b82138d70ec079939449b560e8efa451426ef;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-25 07:31:38 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 aoellerer 2019-02-22 13:41:35 UTC 
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_gettime
executable:     /usr/lib/systemd/systemd-machined
journald_cursor: s=08ccdd0fc34948cab07c8b2ce2dafb1d;i=4a;b=dc5683bd87b74f1c9b49d16c14429c06;m=5a1b52669;t=582691ddf1d38;x=686440c3f8248350
kernel:         4.20.8-200.fc29.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 __clock_gettime at ../sysdeps/unix/clock_gettime.c:115
 #1 now at ../src/basic/time-util.c:53
 #2 triple_timestamp_get at ../src/basic/time-util.c:78
 #3 sd_event_wait at ../src/libsystemd/sd-event/sd-event.c:3412
 #4 sd_event_run at ../src/libsystemd/sd-event/sd-event.c:3566
 #5 bus_event_loop_with_idle at ../src/shared/bus-util.c:119
 #6 manager_run at ../src/machine/machined.c:390

Potential duplicate: bug 1599328
Comment 1 aoellerer 2019-02-22 13:41:37 UTC 
Created attachment 1537494 [details]
File: backtrace
Comment 2 aoellerer 2019-02-22 13:41:38 UTC 
Created attachment 1537496 [details]
File: cgroup
Comment 3 aoellerer 2019-02-22 13:41:39 UTC 
Created attachment 1537497 [details]
File: core_backtrace
Comment 4 aoellerer 2019-02-22 13:41:41 UTC 
Created attachment 1537499 [details]
File: cpuinfo
Comment 5 aoellerer 2019-02-22 13:41:42 UTC 
Created attachment 1537501 [details]
File: dso_list
Comment 6 aoellerer 2019-02-22 13:41:43 UTC 
Created attachment 1537502 [details]
File: environ
Comment 7 aoellerer 2019-02-22 13:41:44 UTC 
Created attachment 1537504 [details]
File: limits
Comment 8 aoellerer 2019-02-22 13:41:46 UTC 
Created attachment 1537506 [details]
File: maps
Comment 9 aoellerer 2019-02-22 13:41:48 UTC 
Created attachment 1537508 [details]
File: mountinfo
Comment 10 aoellerer 2019-02-22 13:41:49 UTC 
Created attachment 1537510 [details]
File: open_fds
Comment 11 aoellerer 2019-02-22 13:41:51 UTC 
Created attachment 1537512 [details]
File: proc_pid_status
Comment 12 aoellerer 2019-02-22 13:42:24 UTC 
*** Bug 1680006 has been marked as a duplicate of this bug. ***
Comment 13 Zbigniew Jędrzejewski-Szmek 2019-02-25 07:31:38 UTC 
Thank you for doing the triage, it's very helpful and appreciated.

The same as for other bugs, I'm pretty sure the service is being killed by a watchdog, and the problem is either in extreme resource starvation or a kernel bug. Based on the logs it might be possible to figure out which.

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