From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-181321-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by finch.gentoo.org (Postfix) with ESMTPS id C30F8139083
for <garchives@archives.gentoo.org>; Mon, 11 Dec 2017 20:56:49 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 6B04EE1094;
Mon, 11 Dec 2017 20:56:44 +0000 (UTC)
Received: from mail-pg0-x230.google.com (mail-pg0-x230.google.com [IPv6:2607:f8b0:400e:c05::230])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id F36F7E1064
for <gentoo-user@lists.gentoo.org>; Mon, 11 Dec 2017 20:56:43 +0000 (UTC)
Received: by mail-pg0-x230.google.com with SMTP id o2so11781129pgc.8
for <gentoo-user@lists.gentoo.org>; Mon, 11 Dec 2017 12:56:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20161025;
h=mime-version:sender:in-reply-to:references:from:date:message-id
:subject:to;
bh=MaC+31MSjuwlQ8jlkmGz6JrjvPS2fIy12vQRSOWVmYA=;
b=PT+CN641DLTEPyAwQ4kCYq1bBiFe8burqhnFxLdPY2ZZ6NwEKWTn7r1oE3U/xohwyp
QIMMC0EE3jRqfJ42vSrFCF8i+b/442xRc1Ba0rILnKZ3Rnvj2FTABQwmLNbsYCvG3ETt
4Z451VJ0hK5/4e9YOkk03U1crNJELPXOgTWGOLdR7J5VJHxrXOd+bG8YMbkShrfF6Fl5
Oj5+NyruXIkVOnvXfClrbGbIInzIbNThAMAUrDfFLs6ws9cEY/b4uyhh2iPi7rfRSuPv
Tuho5HrgcJsD15271uMN2R53gPMvZbBc8kUMrs3h7M2PXF9Om7zctnFtbr3+pk9EI5ju
L7eA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
:date:message-id:subject:to;
bh=MaC+31MSjuwlQ8jlkmGz6JrjvPS2fIy12vQRSOWVmYA=;
b=TD0ze8T3WJsKt2vPClitZk7xoPWJQcttYGKvKYEP7PeX7lnPWs0B/AivdAfD245lNP
FtNWwixx2NaQzYSMPvh85xk+W/ZJb/X09SPSM+drEg1Ho3eyx7k9jOA9ScLpUe9Ccbeg
gDZ2mvHsRmlhAjZC92jCkXAzXtAkrugP4LqHEz7qrU4EBS9yohzDr1cbZKNzT+xKCVqP
jQl0AaJMOEDkuAHOFbkFgZo19pQ0Gru2LjABMNyIgMavuVmbuC2qWg8YoArLxgQaGFJn
BaNrlnGEKgvGX3K0PjZRoAkq5W0p/maW2mP/XEsTRnLvIst17J1jyIrCdlL9Lzp8cirS
o2Lw==
X-Gm-Message-State: AKGB3mJzOu43oVnXrqfdEuJyY3vzjFfYw3vFiFcOQCqUgS1KgzKGmNy6
JEi+4QGcbPoBsEn0kEyMvbhgs4VdkUB55RigsnLi0Pg0
X-Google-Smtp-Source: ACJfBosW04/a0s99y0ksgudal6lBQ10V/rrMtJblcChIDsKchWO7KYxQ7Tr6YmULjtdZtIrS07zcnVcCcKO1q6DegUs=
X-Received: by 10.84.130.67 with SMTP id 61mr1528315plc.368.1513025802444;
Mon, 11 Dec 2017 12:56:42 -0800 (PST)
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Sender: freemanrich@gmail.com
Received: by 10.100.151.169 with HTTP; Mon, 11 Dec 2017 12:56:41 -0800 (PST)
In-Reply-To: <20171211194545.eeyhmu35gqkbrj2r@grusum.endjinn.de>
References: <20171211165842.dovnjea2yza27log@grusum.endjinn.de>
<DBYDB4DM.H33UZDZF.NOJ2JSBF@4LJ2255N.JE52AS6M.VAVRWHVD> <20171211194545.eeyhmu35gqkbrj2r@grusum.endjinn.de>
From: Rich Freeman <rich0@gentoo.org>
Date: Mon, 11 Dec 2017 15:56:41 -0500
X-Google-Sender-Auth: HTv3CxTripYPaGuNKNOcmeUVeVI
Message-ID: <CAGfcS_n4RqPA__kDn5Do4AamWa_z1aeaZo5+=FVd-auTZiGQmg@mail.gmail.com>
Subject: Re: [gentoo-user] How to repair a 'secondary Gentoo system'
To: gentoo-user@lists.gentoo.org
Content-Type: text/plain; charset="UTF-8"
X-Archives-Salt: f1f6ed4c-eed0-44d1-b73b-02c2b2e5a42a
X-Archives-Hash: e680d60901a750eb38b0f59be937e1d4
On Mon, Dec 11, 2017 at 2:45 PM, David Haller <gentoo@dhaller.de> wrote:
>
> On Mon, 11 Dec 2017, Helmut Jarausch wrote:
>>Strangely enough, dmesg shows
>>
>>systemd-coredump[25375]: Failed to connect to coredump service: No such file
> ^^^^^^
>>or directory
>>
>>although I'm not using system but openrc on both system
>
> It seems to me though, that that systemd-coredump thingy is running
> though ...
>
> $ ps a -eo pid,cmd | awk '$1 == 25375 { print;}'
>
That won't show anything, because systemd-coredump isn't a daemon. If
configured to do so, the kernel runs it when a core file is generated,
pipes the core into it, and it in turns passes it along to a
socket-activated service which logs it. Then all those processes
terminate. You wouldn't see them running except for a brief moment
when a process dumps core.
In your case the problem is that the socket doesn't exist, probably
because you aren't actually running systemd. So, systemd-coredump is
being run by the kernel, but it can't pass the core file along to the
service that logs it.
Most likely you have systemd installed but aren't actually running it.
It isn't particularly easy to accidentally install systemd under
Gentoo (I can't imagine that bug going unreported for long around
here...). Presumably you're using a systemd profile, or otherwise
have installed it.
If systemd is installed, then chances are you have this file
installed: /usr/lib/sysctl.d/50-coredump.conf
If that file exists, then I suspect openrc will parse it and set:
kernel.core_pattern=|/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %e
And that will cause the issue you're seeing.
Just move that file someplace else and reboot. Or run sysctl
kernel.core_pattern=/tmp/core.%p or something like that. Then core
files will be dumped to disk and not piped into systemd-coredump.
Long-term you should sort out which service manager you want to run
and configure the entire system accordingly. You might run into
subtle bugs like this one if you have systemd installed and don't use
it. There is nothing wrong with switching back and forth, but it
isn't a well-tested config.
--
Rich