Am 01.06.2015 um 23:56 schrieb Tino: > 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.
Can you rule out any hardware defects? Have you tested your RAM, file system, can you ran badblocks, fsck, debsums, etc? > 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. What are the last lines you get in the journal when it crash happens? journalctl -alb should still work, right? When systemd crashes, it freezes, so your system is still operational. You just won't be able to interact with systemd anymore. Can you attach the output of "systemd-analzye dump" and "systemd-delta" Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
