Control: tag -1 confirmed Control: severity -1 grave Control: fixed -1 219-1
Hello Faidon, Faidon Liambotis [2015-03-26 19:48 +0200]: > Well, this does makes the whole system break (the system needs a reboot > to properly function again; daemon-reexec didn't work). I was about to > deploy this to a large fleet of machines and having to reboot all of > them would be quite catastrophic. I think it deserves to at least be RC. OK, bumped again, I don't mind that much. > I haven't been able to reproduce it again :/ I must be missing > something, as I was able to reproduce it multiple times on two different > servers yesterday. "systemctl restart strongswan" does not leave any > processes behind in my runs (I wrote something to do the same sequence > of events in a loop). It does here. > Can you confirm that in your case "systemctl restart strongswan" leaves > unmanageable processes behind (i.e. the ipsec binaries you see do *not* > have --nofork as an argument)? Yes, exactly. It seems like these processes were started by the init.d script, not the .service. > If so, a mere "ipsec stop" after that should be able to crash > systemd. Not that, it just marks the unit as stopped but keeps the processes running. But killing the two daemons manually makes the cgroup empty and I get that very exception. Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: 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
