Skip to main content

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*

3
  • 1
    Indeed, there is a ssh.socket unit implemented, with a line Conflicts=ssh.service inside the definition file. So I disabled this unit, rebooted, then my sshd.service started automatically as expected. Thanks for pointing me to the culprit. Commented Nov 2, 2021 at 17:58
  • Too bad that the systemctl status ssh* returns only the ssh.service unit, not ssh.socket… Instead I would have discovered it and diagnosed the issue much earlier. Commented Nov 2, 2021 at 18:04
  • I'm getting ` failed to start (exit status 4) -- '/usr/bin/systemctl start ssh': Failed to start ssh.service: Transaction for ssh.service/start is destructive (network-online.target has 'stop' job queued, but 'start' is included in transaction). On Ubuntu Server 24.04. network-online.target` is a job that might was still in the queue, but why would ssh directly fail to start? Can't we increase the time-out or implement a retry? This is crazy. Commented Oct 25, 2024 at 20:12