dx-packages team mailing list archive
-
dx-packages team
-
Mailing list archive
-
Message #20456
[Bug 1350536] Re: url-dispatcher report_recoverable_problem() handler triggers reports filed against upstart
** Also affects: url-dispatcher
Importance: Undecided
Status: New
** Changed in: url-dispatcher
Importance: Undecided => High
** Changed in: url-dispatcher
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to url-dispatcher in Ubuntu.
https://bugs.launchpad.net/bugs/1350536
Title:
url-dispatcher report_recoverable_problem() handler triggers reports
filed against upstart
Status in URL Dispatcher:
New
Status in “url-dispatcher” package in Ubuntu:
New
Bug description:
Currently, the top crasher reported on arm for the phones is in url-
dispatcher:
https://errors.ubuntu.com/problem/e17057d970fd4d64e71eb28c6f18b8a6468df471
This is a recoverable error, reported by url-dispatcher's explicit
"recoverable problem" handling.
The problem is, a large number of these are being reported against
*upstart* as the package. They're being correctly included in the
right bucket, but since the package is listed as upstart instead of
url-dispatcher, the version information is a bit junk.
url-dispatcher's handler only sometimes calls
/usr/share/apport/recoverable_problem with a pid. Sometimes it calls
it without one. In that case, /usr/share/apport/recoverable_problem
looks at the parent pid. However, if url-dispatcher *exits* before
recoverable_problem processes the request, recoverable_problem will be
reparented to upstart.
There may be an underlying issue causing url-dispatcher to exit
abnormally here, which we are subsequently not capturing. But I think
url-dispatcher should be unconditionally passing a PID, to avoid this
misbucketing.
The other option would be to spawn recoverable_problem synchronously,
to make sure the parent process doesn't exit before it's had a chance
to look at it. That obviously has other tradeoffs, though.
To manage notifications about this bug go to:
https://bugs.launchpad.net/url-dispatcher/+bug/1350536/+subscriptions
References