Bug 1206840

Summary: [abrt] systemd: socket(): systemd-logind killed by SIGABRT
Product: [Fedora] Fedora Reporter: iliketurtlesbro
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: johannbg, jsynacek, lnykryn, msekleta, s, systemd-maint, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a5afb29a9a27c604c16c882968984cd9ee3e789d
Whiteboard: abrt_hash:ab77957d2441ab0bc6f3187edcbbc7efeb50d889
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-20 14:02:46 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: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description iliketurtlesbro 2015-03-28 23:45:24 UTC 
Version-Release number of selected component:
systemd-219-9.fc22

Additional info:
reporter:       libreport-2.5.0
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd-logind
crash_function: socket
executable:     /usr/lib/systemd/systemd-logind
kernel:         4.0.0-0.rc4.git0.1.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 socket at ../sysdeps/unix/syscall-template.S:81
 #1 sd_pid_notify_with_fds at ../src/libsystemd/sd-daemon/sd-daemon.c:383
 #2 sd_notify.constprop.35 at ../src/libsystemd/sd-daemon/sd-daemon.c:469
 #3 process_watchdog at ../src/libsystemd/sd-event/sd-event.c:2295
 #4 sd_event_wait at ../src/libsystemd/sd-event/sd-event.c:2411
 #5 sd_event_run at ../src/libsystemd/sd-event/sd-event.c:2499
 #6 manager_run at ../src/login/logind.c:1119
Comment 1 iliketurtlesbro 2015-03-28 23:45:47 UTC 
Created attachment 1007829 [details]
File: backtrace
Comment 2 iliketurtlesbro 2015-03-28 23:45:50 UTC 
Created attachment 1007830 [details]
File: cgroup
Comment 3 iliketurtlesbro 2015-03-28 23:46:02 UTC 
Created attachment 1007831 [details]
File: core_backtrace
Comment 4 iliketurtlesbro 2015-03-28 23:46:08 UTC 
Created attachment 1007832 [details]
File: dso_list
Comment 5 iliketurtlesbro 2015-03-28 23:46:11 UTC 
Created attachment 1007833 [details]
File: environ
Comment 6 iliketurtlesbro 2015-03-28 23:46:21 UTC 
Created attachment 1007834 [details]
File: limits
Comment 7 iliketurtlesbro 2015-03-28 23:46:30 UTC 
Created attachment 1007835 [details]
File: maps
Comment 8 iliketurtlesbro 2015-03-28 23:46:33 UTC 
Created attachment 1007836 [details]
File: open_fds
Comment 9 iliketurtlesbro 2015-03-28 23:46:39 UTC 
Created attachment 1007837 [details]
File: proc_pid_status
Comment 10 iliketurtlesbro 2015-03-28 23:46:46 UTC 
Created attachment 1007838 [details]
File: var_log_messages
Comment 11 Zbigniew Jędrzejewski-Szmek 2015-07-25 23:11:36 UTC 
So, systemd-logind is trying to ping systemd with WATCHDOG=1, and systemd kills systemd-logind because it hasn't received watchdog ping in one minute. Seems most likely that something is gone wrong with the notification socket.
Comment 12 Jan Synacek 2016-01-20 14:02:46 UTC 

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