Bug#816612: systemd: Assertion failure, systemd stopped responding

[Sam Morris]

On Thu, 2016-03-03 at 19:26 +0100, Michael Biebl wrote:
> Am 03.03.2016 um 14:47 schrieb Sam Morris:
> > 
> > Package: systemd
> > Version: 229-2
> > Severity: important
> > 
> > systemd seems to have stopped reponding to requests. The journal
> > contains:
> > 
> > 	Mar 03 13:08:24 wintermute systemd[1]: Reloading.
> > 	Mar 03 13:08:24 wintermute systemd[1]: Assertion 'e->key == i->next_key' failed at ../src/basic/hashmap.c:634, function hashmap_iterate_in_internal_order().
> This seems to be an upstream issue and looks like it was already
> filed
> upstream at https://github.com/systemd/systemd/issues/2676
> 
> Would be great if you can test the fix from
> https://github.com/systemd/systemd/pull/2702

Ah, I didn't consider that bug since I thought it was just for
resolved. It's probably the same bug. I don't think I'll be able to
reproduce it anyway: I've only seen it once during several years *
several machines running systemd. :)

-- 
Sam Morris <https://robots.org.uk/>
CAAA AA1A CA69 A83A 892B  1855 D20B 4202 5CDA 27B9

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160304/20f17f73/attachment-0002.sig>