[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [atomic-devel] How to handle crashes
- From: Jakub Filak <jfilak redhat com>
- To: Jeremy Eder <jeder redhat com>, Derek Carr <decarr redhat com>
- Cc: atomic-devel <atomic-devel projectatomic io>
- Subject: Re: [atomic-devel] How to handle crashes
- Date: Mon, 17 Oct 2016 16:35:32 +0200
Creating ABRT image is definitely possible. ABRT provides an D-Bus API for
accessing detected problems and it's possible to set up ABRT on nodes to
report detected problems to a central ABRT daemon.
The main difference between ABRT and node-problem-detector is that
node-problem-detector is tuned for running on a node, so it is aware of
stuff that ABRT does not know about.
ABRT is tuned for detecting problems like core dumps, python exceptions,
ruby exceptions, kernel oopses, MCEs etc. and bringing them to user's attention.
ABRT cannot detect unresponsive programs yet. But if someone tell us how to
do it or if we get a request to develop such a feature, we will do it.
ABRT is easily extensible, so adding new types of detect problems is just a
matter of finding a way how to detect them.
Do you have any idea how to start?
I played with docker and ABRT last year:
https://github.com/abrt/docker-abrt
And I've recently proved that we can use *nsenter* to run abrt's
core_pattern helper from a docker image:
https://github.com/abrt/abrt/wiki/ABRT-docker-image-experiments
And we can report Python exceptions from containers to ABRT container:
https://github.com/abrt/abrt/pull/1182
Regards,
Jakub
On 09/15/2016 02:28 AM, Jeremy Eder wrote:
> Anyone know? There's a node-problem-detector proposed in Kubernetes but ...
> abrt is far more comprehensive.
> https://github.com/kubernetes/node-problem-detector
>
> The difference is that node-problem-detector has hooks to call back to the
> kubernetes control plane to inform it that a node has problems.
> We could create an abrt container that does the same for RH-based ecosystem.
>
> On Fri, Sep 9, 2016 at 11:21 AM, Jeremy Eder <jeder redhat com
> <mailto:jeder redhat com>> wrote:
>
> Hmm, appears this was not integrated into Fedora Atomic? Is there a
> plan to do so?
>
> On Fri, Mar 20, 2015 at 5:50 AM, Jakub Filak <jfilak redhat com
> <mailto:jfilak redhat com>> wrote:
>
> __
>
> Hello,
>
>
>
> I've been working on integration of ABRT with Project Atomic and,
> today, my work landed in Fedora 22 [1].
>
>
>
> To enable abrt core_dump helper on Atomic hosts, it is necessary to
> install abrt-atomic package and enable abrt-coredump-helper service.
> After doing so core dump files will be stored in sub-directories of
> /var/tmp/abrt/.
>
>
>
> You can find more technical details here:
>
> https://github.com/abrt/abrt/wiki/Containers-and-chroots#abrt---project-atomic
> <https://github.com/abrt/abrt/wiki/Containers-and-chroots#abrt---project-atomic>
>
>
>
>
>
> Should I write a new proposal for the oversight repository or should
> I just open a new pull request for fedora-atomic repository?
>
>
>
>
>
>
>
> Regards,
>
> Jakub
>
>
>
>
>
> 1:
> https://admin.fedoraproject.org/updates/gnome-abrt-1.1.0-1.fc22,abrt-2.5.0-2.fc22,libreport-2.5.0-1.fc22
> <https://admin.fedoraproject.org/updates/gnome-abrt-1.1.0-1.fc22,abrt-2.5.0-2.fc22,libreport-2.5.0-1.fc22>
>
>
>
>
> --
>
> -- Jeremy Eder
>
>
>
>
> --
>
> -- Jeremy Eder
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]