[Bug 967968] New: systemd 228-2.1 segfaults and gives "freezing execution"
http://bugzilla.opensuse.org/show_bug.cgi?id=967968 Bug ID: 967968 Summary: systemd 228-2.1 segfaults and gives "freezing execution" Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: susebugzilla@sajj.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 666655 --> http://bugzilla.opensuse.org/attachment.cgi?id=666655&action=edit Systemd core dump Hi, one of my systems had problems last night. It dropped me a message saying: "Message from syslogd@alpha at Feb 23 21:38:24 ... kernel: [295139.801642] systemd[1]: segfault at 55c1198268b8 ip 00007fde212befc9 sp 00007ffe343fa380 error 6 in libc-2.22.so[7fde21244000+19c000]" The journal contains following: Feb 23 21:38:24 alpha audit[2310]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=2310 comm="systemd" exe="/usr/lib/systemd/systemd" sig=11 Feb 23 21:38:24 alpha kernel: systemd[1]: segfault at 55c1198268b8 ip 00007fde212befc9 sp 00007ffe343fa380 error 6 in libc-2.22.so[7fde21244000+19c000] Feb 23 21:38:24 alpha systemd[1]: Caught <SEGV>, dumped core as pid 2310. Feb 23 21:38:24 alpha systemd[1]: Freezing execution. Feb 23 21:38:26 alpha systemd-coredump[2311]: Process 2310 (systemd) of user 0 dumped core. Feb 23 21:45:01 alpha audit[2347]: USER_ACCT pid=2347 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_listfile acct="wwwrun" exe="/usr/sbin/cron Feb 23 21:45:01 alpha cron[2347]: pam_unix(crond:session): session opened for user wwwrun by (uid=0) Feb 23 21:45:01 alpha audit[2347]: CRED_ACQ pid=2347 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="wwwrun" exe="/usr/sbin/cron" host Feb 23 21:45:01 alpha audit[2398]: USER_AUTH pid=2398 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_rootok acct="root" exe="/usr/bin/su" h Feb 23 21:45:01 alpha audit[2398]: USER_ACCT pid=2398 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_rootok acct="root" exe="/usr/bin/su" hostn Feb 23 21:45:01 alpha su[2398]: (to root) root on none Feb 23 21:45:01 alpha audit[2398]: CRED_ACQ pid=2398 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="root" exe="/usr/bin/su" hostname= Feb 23 21:45:01 alpha su[2398]: pam_unix(su:session): session opened for user root by (uid=0) Feb 23 21:45:26 alpha systemd-logind[1094]: Failed to start user slice user-30.slice, ignoring: Connection timed out (org.freedesktop.DBus.Error.Timeout) Feb 23 21:45:26 alpha audit[2347]: USER_START pid=2347 uid=0 auid=30 ses=414 msg='op=PAM:session_open grantors=pam_loginuid,pam_limits,pam_unix,pam_umask,pam_gnome_keyri Feb 23 21:45:26 alpha cron[2347]: pam_systemd(crond:session): Failed to create session: Connection timed out Feb 23 21:45:26 alpha audit[2347]: CRED_REFR pid=2347 uid=0 auid=30 ses=414 msg='op=PAM:setcred grantors=pam_rootok acct="wwwrun" exe="/usr/sbin/cron" hostname=? addr=? Feb 23 21:45:26 alpha CRON[2400]: (wwwrun) CMD (php -f /srv/www/htdocs/owncloud/cron.php) Feb 23 21:45:26 alpha su[2398]: pam_systemd(su:session): Failed to create session: Connection timed out Feb 23 21:45:26 alpha audit[2398]: USER_START pid=2398 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_umask,pam_gnome_key Feb 23 21:45:26 alpha audit[2347]: CRED_DISP pid=2347 uid=0 auid=30 ses=414 msg='op=PAM:setcred grantors=pam_rootok acct="wwwrun" exe="/usr/sbin/cron" hostname=? addr=? Last systemd update was on Feb, 6 and was an update to systemd-228-2.1.x86_64. Attached a core dump for further information. The repo-list: # | Alias | Name | Enabled | GPG Check | Refresh --+----------------------------------+---------------------------------+---------+-----------+-------- 1 | Filesystems_TW | Filesystems TW | Yes | (r ) Yes | Yes 2 | Owncloud_TW_1 | Owncloud TW | Yes | (r ) Yes | Yes 3 | PHP_Redis_ | PHP Redis | Yes | (r ) Yes | Yes 4 | PHP_openSUSE_Factory | PHP openSUSE_Factory | Yes | (r ) Yes | Yes 5 | Packman | Packman | Yes | (r ) Yes | Yes 6 | download.opensuse.org-non-oss | Haupt-Repository (NON-OSS) | Yes | (r ) Yes | Yes 7 | download.opensuse.org-oss | Haupt-Repository (OSS) | Yes | (r ) Yes | Yes 8 | download.opensuse.org-tumbleweed | Hauptaktualisierungs-Repository | Yes | (r ) Yes | Yes Filesystem repo was added yesterday, in case that matters.. System is still up and running, but is rather unresponsive. SSH-login via local network works, but takes half a minute or so to prompt. If further info is need, let me know. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=967968 http://bugzilla.opensuse.org/show_bug.cgi?id=967968#c8 --- Comment #8 from Andreas Joppich <susebugzilla@sajj.de> --- Hi all, just for your information: Andreas Schwabs' term "memory corruption" made me thinking yesterday, so I simply installed memtest+ and let the system perform a memtest. Dropped many errors almost immediately. I Opened up the box (a HP microserver), cleaned out too much dust and re-plugged all connectors and RAM modules. After that a new memtest ran fine for at least an hour, but then again some errors were reported. So I think, I might have a bad RAM module and need to replace it. This could also explain some unexpected crashes/restarts during the last months. Thanks to all! Andreas -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com