Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • 2
    "delayed" is different from "in some cases I had to start them manually"; what exactly is happening with their startup sequence? Commented Feb 12, 2019 at 14:06
  • sometimes they start with long delay, sometimes they don't start at all so I need to login, check the services status with the command service --status-all (to exclude network problem), if they are off i run the command systemctl start apache2 or ssh. before the upgrade everything was ok without delay or without the necessity to login Commented Feb 12, 2019 at 14:31
  • Have you looked at the log files ? Commented Feb 13, 2019 at 15:29
  • 1
    my guess: the newer kernel delays /dev/(u)random initial read operations: Feb 13 21:57:59 vm-debian-buster kernel: random: crng init done and ssh starts right after. Commented Feb 13, 2019 at 23:05
  • 1
    haveged solved the problem on the 'broken machine' with kernel 4.19.0-1-amd64, but on the machine with 'clean install' the kernel has been updated to 4.19.0-2-amd64. kernel problem? apt update can solve the problem on the 'broken machine' too. Commented Feb 14, 2019 at 0:25