I don't know why or when this job was triggered. The uptime of the system was about 1.5-2 days until it happened. I don't have any custom or modified units. The only change i made with systemd is setting the log level to debug. I've seen a sefault while systemd was processing systemd-udevd events too, but i was not sure which of those too actually crashed. My NAS is the only system where this happens. It started with the upgrade to jessie. I can't trigger the crash, it just happens, no matter if i am around or not. Sorry about the lack of logfiles. The last few lines never make it to the disk. I hope i can provide more with the next crashes. Tell me if you need any configuration files, I'm happy to provide them.
Am 01.06.2015 um 23:22 schrieb Michael Biebl: > Am 01.06.2015 um 23:13 schrieb Tino: >> Package: systemd >> Version: 215-17 >> Severity: critical >> Justification: breaks the whole system >> >> Dear Maintainer, >> >> systemd doesn't survive two days on my bare minimal headless NAS >> installation. I already purged all unused packages, reinstalled systemd >> and reverted all config files to factory default, reconfiguring >> everything i need. I upgraded from wheezy some time ago. >> This time it segfaulted while adding a job that should restart journald. > When and how is this job triggered? The systemd package itself doesn't > ship any units which restart journald. Do you have any custom units? > Does this happen for arbitrary services? > Can you provide us with steps to reproduce the issue? > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
