SSH Daemon doesn't start normally way
I use Ubuntu server 16.04.1 LTS (Kernel 4.4.0-38-generic x86_64).
And Install openssh-server(1:7.2p2-4ubuntu2.1).
At first, I use below.
sudo systemctl enable ssh.service
But sshd doesn't start in boot process.
So, I check this Questions -> (SSH Daemon does not autostart)
And try this article -> (http://blog.roberthallam.org/2010/06/sshd-not-running-at-startup)
However, sshd doesn't start. (sudo service ssh status is dead.)
Of course, I check symbolic link of /etc/rc*.d/S**ssh is created.
Then I added below to /etc/rc.local.
/etc/init.d/ssh start
Finally, sshd does start on boot, but I wonder why normally process doesn't work.
It might be because using usb wireless adapter, but I cannot be sure that.
Please tell me what do you think.
server ssh autostart
edited Apr 13 '17 at 12:25
Community♦
1
asked Sep 27 '16 at 11:19
MAD_PEPPERMAD_PEPPER
1113
add a comment |
I use Ubuntu server 16.04.1 LTS (Kernel 4.4.0-38-generic x86_64).
And Install openssh-server(1:7.2p2-4ubuntu2.1).
At first, I use below.
sudo systemctl enable ssh.service
But sshd doesn't start in boot process.
So, I check this Questions -> (SSH Daemon does not autostart)
And try this article -> (http://blog.roberthallam.org/2010/06/sshd-not-running-at-startup)
However, sshd doesn't start. (sudo service ssh status is dead.)
Of course, I check symbolic link of /etc/rc*.d/S**ssh is created.
Then I added below to /etc/rc.local.
/etc/init.d/ssh start
Finally, sshd does start on boot, but I wonder why normally process doesn't work.
It might be because using usb wireless adapter, but I cannot be sure that.
Please tell me what do you think.
server ssh autostart
edited Apr 13 '17 at 12:25
Community♦
1
asked Sep 27 '16 at 11:19
MAD_PEPPERMAD_PEPPER
1113
I have no direct experience with this, but reading around it seems likely that the "right" approach is to tell sshd to start onnetwork-online.targetinstead ofnetwork.target- see Linux tip: Force systemd networkd to wait for DHCP - but note that you are probably using NetworkManager not networkd - so the enable command would besystemctl enable NetworkManager-wait-online.serviceRunning Services After the Network is up
– steeldriver
Sep 27 '16 at 13:09
Thanks. I didn't understand well about "ssh daemon needs specific IP." I didn't setListenAddressofsshd_config. So I thought sshd doesn't need specific IP to start service. I thought device initialization is only needed by ssh daemon.
– MAD_PEPPER
Sep 28 '16 at 13:06
I triednetwork-online.targetapproach, but failed to start sshd. And I don't use NetworkManager, but networking daemon. This may be because of version of systemd. systemd message isDependency failed for Wait for Network to be Configured. systemd-networkd-wait-online.service: Job systemd-networkd-wait-online.service/start failed with result 'dependency'
– MAD_PEPPER
Sep 28 '16 at 15:39
I re-install "ubuntu server", and I checked option of "open-ssh" install in dialogue. This works well, and sshd is start automatically. After all, I don't understand cause of this problem.
– MAD_PEPPER
Oct 1 '16 at 21:13
add a comment |
I use Ubuntu server 16.04.1 LTS (Kernel 4.4.0-38-generic x86_64).
And Install openssh-server(1:7.2p2-4ubuntu2.1).
At first, I use below.
sudo systemctl enable ssh.service
But sshd doesn't start in boot process.
So, I check this Questions -> (SSH Daemon does not autostart)
And try this article -> (http://blog.roberthallam.org/2010/06/sshd-not-running-at-startup)
However, sshd doesn't start. (sudo service ssh status is dead.)
Of course, I check symbolic link of /etc/rc*.d/S**ssh is created.
Then I added below to /etc/rc.local.
/etc/init.d/ssh start
Finally, sshd does start on boot, but I wonder why normally process doesn't work.
It might be because using usb wireless adapter, but I cannot be sure that.
Please tell me what do you think.
server ssh autostart
edited Apr 13 '17 at 12:25
Community♦
1
asked Sep 27 '16 at 11:19
MAD_PEPPERMAD_PEPPER
1113
I use Ubuntu server 16.04.1 LTS (Kernel 4.4.0-38-generic x86_64).
And Install openssh-server(1:7.2p2-4ubuntu2.1).
At first, I use below.
sudo systemctl enable ssh.service
But sshd doesn't start in boot process.
So, I check this Questions -> (SSH Daemon does not autostart)
And try this article -> (http://blog.roberthallam.org/2010/06/sshd-not-running-at-startup)
However, sshd doesn't start. (sudo service ssh status is dead.)
Of course, I check symbolic link of /etc/rc*.d/S**ssh is created.
Then I added below to /etc/rc.local.
/etc/init.d/ssh start
Finally, sshd does start on boot, but I wonder why normally process doesn't work.
It might be because using usb wireless adapter, but I cannot be sure that.
Please tell me what do you think.
server ssh autostart
server ssh autostart
edited Apr 13 '17 at 12:25
Community♦
1
asked Sep 27 '16 at 11:19
MAD_PEPPERMAD_PEPPER
1113
edited Apr 13 '17 at 12:25
Community♦
1
asked Sep 27 '16 at 11:19
MAD_PEPPERMAD_PEPPER
1113
edited Apr 13 '17 at 12:25
Community♦
1
edited Apr 13 '17 at 12:25
Community♦
1
edited Apr 13 '17 at 12:25
Community♦
1
1
asked Sep 27 '16 at 11:19
MAD_PEPPERMAD_PEPPER
1113
asked Sep 27 '16 at 11:19
MAD_PEPPERMAD_PEPPER
1113
asked Sep 27 '16 at 11:19
MAD_PEPPERMAD_PEPPER
1113
1113
I have no direct experience with this, but reading around it seems likely that the "right" approach is to tell sshd to start onnetwork-online.targetinstead ofnetwork.target- see Linux tip: Force systemd networkd to wait for DHCP - but note that you are probably using NetworkManager not networkd - so the enable command would besystemctl enable NetworkManager-wait-online.serviceRunning Services After the Network is up
– steeldriver
Sep 27 '16 at 13:09
Thanks. I didn't understand well about "ssh daemon needs specific IP." I didn't setListenAddressofsshd_config. So I thought sshd doesn't need specific IP to start service. I thought device initialization is only needed by ssh daemon.
– MAD_PEPPER
Sep 28 '16 at 13:06
I triednetwork-online.targetapproach, but failed to start sshd. And I don't use NetworkManager, but networking daemon. This may be because of version of systemd. systemd message isDependency failed for Wait for Network to be Configured. systemd-networkd-wait-online.service: Job systemd-networkd-wait-online.service/start failed with result 'dependency'
– MAD_PEPPER
Sep 28 '16 at 15:39
I re-install "ubuntu server", and I checked option of "open-ssh" install in dialogue. This works well, and sshd is start automatically. After all, I don't understand cause of this problem.
– MAD_PEPPER
Oct 1 '16 at 21:13
add a comment |
I have no direct experience with this, but reading around it seems likely that the "right" approach is to tell sshd to start onnetwork-online.targetinstead ofnetwork.target- see Linux tip: Force systemd networkd to wait for DHCP - but note that you are probably using NetworkManager not networkd - so the enable command would besystemctl enable NetworkManager-wait-online.serviceRunning Services After the Network is up
– steeldriver
Sep 27 '16 at 13:09
Thanks. I didn't understand well about "ssh daemon needs specific IP." I didn't setListenAddressofsshd_config. So I thought sshd doesn't need specific IP to start service. I thought device initialization is only needed by ssh daemon.
– MAD_PEPPER
Sep 28 '16 at 13:06
I triednetwork-online.targetapproach, but failed to start sshd. And I don't use NetworkManager, but networking daemon. This may be because of version of systemd. systemd message isDependency failed for Wait for Network to be Configured. systemd-networkd-wait-online.service: Job systemd-networkd-wait-online.service/start failed with result 'dependency'
– MAD_PEPPER
Sep 28 '16 at 15:39
I re-install "ubuntu server", and I checked option of "open-ssh" install in dialogue. This works well, and sshd is start automatically. After all, I don't understand cause of this problem.
– MAD_PEPPER
Oct 1 '16 at 21:13
I have no direct experience with this, but reading around it seems likely that the "right" approach is to tell sshd to start on
network-online.target instead of network.target - see Linux tip: Force systemd networkd to wait for DHCP - but note that you are probably using NetworkManager not networkd - so the enable command would be systemctl enable NetworkManager-wait-online.service Running Services After the Network is up– steeldriver
Sep 27 '16 at 13:09
I have no direct experience with this, but reading around it seems likely that the "right" approach is to tell sshd to start on
network-online.target instead of network.target - see Linux tip: Force systemd networkd to wait for DHCP - but note that you are probably using NetworkManager not networkd - so the enable command would be systemctl enable NetworkManager-wait-online.service Running Services After the Network is up– steeldriver
Sep 27 '16 at 13:09
Thanks. I didn't understand well about "ssh daemon needs specific IP." I didn't set
ListenAddress of sshd_config . So I thought sshd doesn't need specific IP to start service. I thought device initialization is only needed by ssh daemon.– MAD_PEPPER
Sep 28 '16 at 13:06
Thanks. I didn't understand well about "ssh daemon needs specific IP." I didn't set
ListenAddress of sshd_config . So I thought sshd doesn't need specific IP to start service. I thought device initialization is only needed by ssh daemon.– MAD_PEPPER
Sep 28 '16 at 13:06
I tried
network-online.target approach, but failed to start sshd. And I don't use NetworkManager, but networking daemon. This may be because of version of systemd. systemd message is Dependency failed for Wait for Network to be Configured. systemd-networkd-wait-online.service: Job systemd-networkd-wait-online.service/start failed with result 'dependency'– MAD_PEPPER
Sep 28 '16 at 15:39
I tried
network-online.target approach, but failed to start sshd. And I don't use NetworkManager, but networking daemon. This may be because of version of systemd. systemd message is Dependency failed for Wait for Network to be Configured. systemd-networkd-wait-online.service: Job systemd-networkd-wait-online.service/start failed with result 'dependency'– MAD_PEPPER
Sep 28 '16 at 15:39
I re-install "ubuntu server", and I checked option of "open-ssh" install in dialogue. This works well, and sshd is start automatically. After all, I don't understand cause of this problem.
– MAD_PEPPER
Oct 1 '16 at 21:13
I re-install "ubuntu server", and I checked option of "open-ssh" install in dialogue. This works well, and sshd is start automatically. After all, I don't understand cause of this problem.
– MAD_PEPPER
Oct 1 '16 at 21:13
add a comment |
1 Answer
1
active
oldest
votes
Well make sure openssh-server is installed. If installed already try reinstalling as follows :
sudo apt-get remove --purge openssh-server
sudo apt-get install openssh-server
For Ubuntu 16.04 LTS , there isn't any issue with 4.4 kernel and Linux kernel 4.6 is also compatible as well. If you still have the problem then I recommend you to upgrade your kernel or recompile your kernel.
edited Sep 27 '16 at 11:47
edwinksl
16.8k125387
answered Sep 27 '16 at 11:47
SAGAR NairSAGAR Nair
1,046612
I didn't write in question, but I already re-installed openssh-server. But nothing changed. No one else seems to have same problem, I think this is my environmental problem.
– MAD_PEPPER
Sep 28 '16 at 11:23
Linux image 4.6 don't seems to provide withapt. I think manually upgrade of linux kernel isn't recommended. I'm unwilling to.
– MAD_PEPPER
Sep 28 '16 at 12:19
I didn't say thanks! sorry! Thanks a lot!
– MAD_PEPPER
Sep 28 '16 at 12:54
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f830278%2fssh-daemon-doesnt-start-normally-way%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Well make sure openssh-server is installed. If installed already try reinstalling as follows :
sudo apt-get remove --purge openssh-server
sudo apt-get install openssh-server
For Ubuntu 16.04 LTS , there isn't any issue with 4.4 kernel and Linux kernel 4.6 is also compatible as well. If you still have the problem then I recommend you to upgrade your kernel or recompile your kernel.
edited Sep 27 '16 at 11:47
edwinksl
16.8k125387
answered Sep 27 '16 at 11:47
SAGAR NairSAGAR Nair
1,046612
I didn't write in question, but I already re-installed openssh-server. But nothing changed. No one else seems to have same problem, I think this is my environmental problem.
– MAD_PEPPER
Sep 28 '16 at 11:23
Linux image 4.6 don't seems to provide withapt. I think manually upgrade of linux kernel isn't recommended. I'm unwilling to.
– MAD_PEPPER
Sep 28 '16 at 12:19
I didn't say thanks! sorry! Thanks a lot!
– MAD_PEPPER
Sep 28 '16 at 12:54
add a comment |
Well make sure openssh-server is installed. If installed already try reinstalling as follows :
sudo apt-get remove --purge openssh-server
sudo apt-get install openssh-server
For Ubuntu 16.04 LTS , there isn't any issue with 4.4 kernel and Linux kernel 4.6 is also compatible as well. If you still have the problem then I recommend you to upgrade your kernel or recompile your kernel.
edited Sep 27 '16 at 11:47
edwinksl
16.8k125387
answered Sep 27 '16 at 11:47
SAGAR NairSAGAR Nair
1,046612
I didn't write in question, but I already re-installed openssh-server. But nothing changed. No one else seems to have same problem, I think this is my environmental problem.
– MAD_PEPPER
Sep 28 '16 at 11:23
Linux image 4.6 don't seems to provide withapt. I think manually upgrade of linux kernel isn't recommended. I'm unwilling to.
– MAD_PEPPER
Sep 28 '16 at 12:19
I didn't say thanks! sorry! Thanks a lot!
– MAD_PEPPER
Sep 28 '16 at 12:54
add a comment |
Well make sure openssh-server is installed. If installed already try reinstalling as follows :
sudo apt-get remove --purge openssh-server
sudo apt-get install openssh-server
For Ubuntu 16.04 LTS , there isn't any issue with 4.4 kernel and Linux kernel 4.6 is also compatible as well. If you still have the problem then I recommend you to upgrade your kernel or recompile your kernel.
edited Sep 27 '16 at 11:47
edwinksl
16.8k125387
answered Sep 27 '16 at 11:47
SAGAR NairSAGAR Nair
1,046612
Well make sure openssh-server is installed. If installed already try reinstalling as follows :
sudo apt-get remove --purge openssh-server
sudo apt-get install openssh-server
For Ubuntu 16.04 LTS , there isn't any issue with 4.4 kernel and Linux kernel 4.6 is also compatible as well. If you still have the problem then I recommend you to upgrade your kernel or recompile your kernel.
edited Sep 27 '16 at 11:47
edwinksl
16.8k125387
answered Sep 27 '16 at 11:47
SAGAR NairSAGAR Nair
1,046612
edited Sep 27 '16 at 11:47
edwinksl
16.8k125387
edited Sep 27 '16 at 11:47
edwinksl
16.8k125387
edited Sep 27 '16 at 11:47
edwinksl
16.8k125387
16.8k125387
answered Sep 27 '16 at 11:47
SAGAR NairSAGAR Nair
1,046612
answered Sep 27 '16 at 11:47
SAGAR NairSAGAR Nair
1,046612
answered Sep 27 '16 at 11:47
SAGAR NairSAGAR Nair
1,046612
1,046612
I didn't write in question, but I already re-installed openssh-server. But nothing changed. No one else seems to have same problem, I think this is my environmental problem.
– MAD_PEPPER
Sep 28 '16 at 11:23
Linux image 4.6 don't seems to provide withapt. I think manually upgrade of linux kernel isn't recommended. I'm unwilling to.
– MAD_PEPPER
Sep 28 '16 at 12:19
I didn't say thanks! sorry! Thanks a lot!
– MAD_PEPPER
Sep 28 '16 at 12:54
add a comment |
I didn't write in question, but I already re-installed openssh-server. But nothing changed. No one else seems to have same problem, I think this is my environmental problem.
– MAD_PEPPER
Sep 28 '16 at 11:23
Linux image 4.6 don't seems to provide withapt. I think manually upgrade of linux kernel isn't recommended. I'm unwilling to.
– MAD_PEPPER
Sep 28 '16 at 12:19
I didn't say thanks! sorry! Thanks a lot!
– MAD_PEPPER
Sep 28 '16 at 12:54
I didn't write in question, but I already re-installed openssh-server. But nothing changed. No one else seems to have same problem, I think this is my environmental problem.
– MAD_PEPPER
Sep 28 '16 at 11:23
I didn't write in question, but I already re-installed openssh-server. But nothing changed. No one else seems to have same problem, I think this is my environmental problem.
– MAD_PEPPER
Sep 28 '16 at 11:23
Linux image 4.6 don't seems to provide with
apt . I think manually upgrade of linux kernel isn't recommended. I'm unwilling to.– MAD_PEPPER
Sep 28 '16 at 12:19
Linux image 4.6 don't seems to provide with
apt . I think manually upgrade of linux kernel isn't recommended. I'm unwilling to.– MAD_PEPPER
Sep 28 '16 at 12:19
I didn't say thanks! sorry! Thanks a lot!
– MAD_PEPPER
Sep 28 '16 at 12:54
I didn't say thanks! sorry! Thanks a lot!
– MAD_PEPPER
Sep 28 '16 at 12:54
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f830278%2fssh-daemon-doesnt-start-normally-way%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I have no direct experience with this, but reading around it seems likely that the "right" approach is to tell sshd to start on
network-online.targetinstead ofnetwork.target- see Linux tip: Force systemd networkd to wait for DHCP - but note that you are probably using NetworkManager not networkd - so the enable command would besystemctl enable NetworkManager-wait-online.serviceRunning Services After the Network is up– steeldriver
Sep 27 '16 at 13:09
Thanks. I didn't understand well about "ssh daemon needs specific IP." I didn't set
ListenAddressofsshd_config. So I thought sshd doesn't need specific IP to start service. I thought device initialization is only needed by ssh daemon.– MAD_PEPPER
Sep 28 '16 at 13:06
I tried
network-online.targetapproach, but failed to start sshd. And I don't use NetworkManager, but networking daemon. This may be because of version of systemd. systemd message isDependency failed for Wait for Network to be Configured. systemd-networkd-wait-online.service: Job systemd-networkd-wait-online.service/start failed with result 'dependency'– MAD_PEPPER
Sep 28 '16 at 15:39
I re-install "ubuntu server", and I checked option of "open-ssh" install in dialogue. This works well, and sshd is start automatically. After all, I don't understand cause of this problem.
– MAD_PEPPER
Oct 1 '16 at 21:13