Greetings, Sorry I am late to the discussion.
I have some systems running in a VMWare infrastructure and things like ssh and puppet are not starting (puppet times out and fails) or taking a long time to start (ssh). If I install sshd, I expect it to start (somewhat quickly) not 200 seconds after boot. If I install puppet, I expect it to start - not timeout and fail. It seems installing haveged has "fixed" these issues [Thanks jim_p < pitsior...@gmail.com>] , but knowing those specific solutions remains the challenge. I've spent a lot of time debugging, reading, and researching to find these bug reports and threads. It takes a lot of time and even then I'm not certain of the appropriateness of the fix. Is installing haveged the right solution for a headless VM that needs to have ssh and puppet running? Right now systemd upstream is dubious of PR 10621 and according to Michael Biebl it will be opt-in only. PS. Thank you Michael for your work on systemd. Where do we communicate to admins that their services might be slow to start or fail to start and they need to manually install some package (haveged) or touch a systemd config (PR 10621)? Thanks everyone for their input in this discussion! It is appreciated! -m
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers