Re: oops.kernel.org, reporting. [Was: [ATTEND] oops.kernel.org prospect]

[Anton Arapov <anton@redhat.com>]

On Fri, Sep 06, 2013 at 04:02:28PM -0400, Joseph Salisbury wrote:
> On 08/22/2013 06:35 AM, Anton Arapov wrote:
> > Hello,
> >
> > Thank you for contacting me. I will cross-post this to LKML, as there
> > is an information that might be interested for other folks.
> >
> > On Wed, Aug 21, 2013 at 10:31:21PM +0200, Tom Wijsman wrote:
> >> We, the Gentoo Kernel Project Team at Gentoo Linux, might be interested
> >> to contribute oopses to oops.kernel.org; but from a first look over what
> >> can be found on the ML and the internet about that site, there seems to
> >> be no information available about submitting to oops.kernel.org.
> > This kind of information will be there soon.
> >
> >
> >> So, could you please highlight the details on how submission happens?
> >> Does this (have to) happen automatically? Can we do manual submissions?
> > oops.kernel.org uses the old legacy kerneloops.org's api for data
> > collecting. Both, http://submit.kerneloops.org/submitoops.php (old) and
> > http://oops.kernel.org/submitoops.php (new, stick to this one) works today.
> 
> The Ubuntu distro is still configured to submit oops to
> http://submit.kerneloops.org/submitoops.php using the kerneloops package
> developed by Arjan.  However, it has been disabled since the original
> kerneloops.org site went down.  We can re-enable oops submissions.  Will
> the old submit URL still work, or are you migrating to the new
> http://oops.kernel.org/submitoops.php URL?

Old URL still works, so you can use the kerneloops package as is and
it should work. 

I will update the package itself later, with new url and few
improvements for oopses detection. 

Anton.

> 
> >
> > Reporting doesn't happen automatically. Two tools available for
> > sending reports: abrt/libreport (1) and former kerneloops daemon (2).
> > Either of these can send reports automatically or manually.
> >
> >
> > (1) https://fedorahosted.org/abrt/ - iirc, is already packaged in gentoo.
> > (2) There are no link to kerneloops, this is what I was able to google:
> > http://ftp.debian.org/debian/pool/main/k/kerneloops/kerneloops_0.12+git20090217.orig.tar.gz
> > Abrt has a better scanner/reporter, which produce less false-positive reports.
> >
> >
> > I don't know what way Gentoo will choose, but the original kerneloops
> > daemon requires some love to make it run under systemd and improve the
> > oops scanner (can be ported from abrt).
> >
> >
> > The source of _scanner_ abrt/dumpoops_plugin:
> > https://git.fedorahosted.org/cgit/abrt.git/tree/src/plugins/abrt-dump-oops.c
> > The source of _reporter_ abrt/libreport/kerneloops_plugin:
> > https://git.fedorahosted.org/cgit/libreport.git/tree/src/plugins/reporter-kerneloops.c
> >
> > libreport allows to report manually using CLI:
> >  $ reporter-kerneloops 
> >  Usage: reporter-kerneloops [-v] [-c CONFFILE]... -d DIR
> >
> >
> >> I think that something that "calls home" might become a concern; maybe
> >> we could still provide that as opt-in, but manual submits would be neat.
> > Few years of experience with Abrt/Bugzilla reports, people fill the
> > additional information in less than 2% of all reports. And, the Abrt
> > team is working towards the least possible interaction with the user.
> > This is mostly to address privacy concerns, as well as leaving the
> > possibility to provide additional data.
> >
> >
> >> Thank you in advance for your explanation.
> > You are welcome, let me know if you'll need any help further.
> >
> > Anton.
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
>