On 2017-07-28 15:21, Mark Hounschell wrote:
On 07/27/2017 08:02 PM, Carlos E. R. wrote:
On 2017-07-27 21:09, Mark Hounschell wrote:
6218 root 20 0 119128 92796 2040 R 55.15 0.564 0:04.28 systemd-coredum
What the heck is this? Can barely send this email
Some process is crashing and restarting. A core dump is being saved to disk for study by a developer. On the system log you will get a log entry stating which process crashed and perhaps why, so look in the log and find out, then impede it restarting.
dmesg showed nothing abnormal.
Not dmesg. journalctl | grep coredum Example: cer@Isengard:~> journalctl | grep coredum Jan 11 04:40:38 Isengard systemd-coredump[4590]: Process 4587 (obconf) of user 1000 dumped core. Jan 11 04:40:54 Isengard systemd-coredump[4599]: Process 4596 (obconf) of user 1000 dumped core. Feb 05 04:32:26 Isengard systemd-coredump[6384]: Process 6345 (panel-15-system) of user 1000 dumped core. Then I look in detail around that timestamp and find more info, but this time I seek in syslog because I also keep it: <3.6> 2017-01-11T04:40:01.932293+01:00 Isengard systemd 1 - - Stopping User Manager for UID 0... <3.6> 2017-01-11T04:40:01.933641+01:00 Isengard systemd 4544 - - Stopped target Default. <3.6> 2017-01-11T04:40:01.934157+01:00 Isengard systemd 4544 - - Stopped target Basic System. <3.6> 2017-01-11T04:40:01.935194+01:00 Isengard systemd 4544 - - Stopped target Timers. <3.6> 2017-01-11T04:40:01.975561+01:00 Isengard systemd 4544 - - Reached target Shutdown. <3.6> 2017-01-11T04:40:01.976051+01:00 Isengard systemd 4544 - - Starting Exit the Session... <3.6> 2017-01-11T04:40:01.976427+01:00 Isengard systemd 4544 - - Stopped target Sockets. <3.6> 2017-01-11T04:40:01.976797+01:00 Isengard systemd 4544 - - Stopped target Paths. <3.6> 2017-01-11T04:40:02.000011+01:00 Isengard systemd 4544 - - Received SIGRTMIN+24 from PID 4572 (kill). <10.6> 2017-01-11T04:40:02.004232+01:00 Isengard systemd - - - pam_unix(systemd-user:session): session closed for user root <3.6> 2017-01-11T04:40:02.010475+01:00 Isengard systemd 1 - - Stopped User Manager for UID 0. <3.6> 2017-01-11T04:40:02.020141+01:00 Isengard systemd 1 - - Removed slice User Slice of root. <0.4> 2017-01-11T04:40:36.618668+01:00 Isengard kernel - - - [3028957.795445] show_signal_msg: 105 callbacks suppressed <0.6> 2017-01-11T04:40:36.618703+01:00 Isengard kernel - - - [3028957.795464] obconf[4587]: segfault at 0 ip 00007fae8eaa1486 sp 00007ffeace8d0a0 error 4 in libc-2.22.so[7fae8ea69000+19a000] <0.2> 2017-01-11T04:40:38.415747+01:00 Isengard systemd-coredump 4590 - - Process 4587 (obconf) of user 1000 dumped core. <0.6> 2017-01-11T04:40:53.054943+01:00 Isengard kernel - - - [3028974.232263] obconf[4596]: segfault at 0 ip 00007f7de6205486 sp 00007ffe51db24d0 error 4 in libc-2.22.so[7f7de61cd000+19a000] <0.2> 2017-01-11T04:40:54.843895+01:00 Isengard systemd-coredump 4599 - - Process 4596 (obconf) of user 1000 dumped core. <10.3> 2017-01-11T04:42:09.914187+01:00 Isengard gnomesu-pam-backend - - - gkr-pam: couldn't get the password from user: Critical error - immediate abort <10.3> 2017-01-11T04:42:09.916654+01:00 Isengard gnomesu-pam-backend - - - pam_unix(gnomesu-pam:auth): conversation failed <10.2> 2017-01-11T04:42:09.917253+01:00 Isengard gnomesu-pam-backend - - - pam_unix(gnomesu-pam:auth): auth could not identify password for [root] The important line would be this one: <0.6> 2017-01-11T04:40:36.618703+01:00 Isengard kernel - - - [3028957.795464] obconf[4587]: segfault at 0 ip 00007fae8eaa1486 sp 00007ffeace8d0a0 error 4 in libc-2.22.so[7fae8ea69000+19a000] A developer could find out what is wrong using the core file and that info. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)