Is there a specific SSH boot log?

My sshd won't start at bootup. I have to type it in manually (sudo service ssh start).

I've posted a question on how to start ssh at bootup (How to start SSH daemon on boot on Linux Mint Debian v2), but, everything I've tried has not worked.

I checked /var/log/boot.log, it actually says:

[ ok ] Starting OpenBSD Secure Shell server: sshd

However, when I type ps -A | grep ssh, sshd does not show up. If I start it manually (sudo service ssh start), it does show up. Is there a specific log for SSH that I can check?

I'm using LMDE v2, 64-bit, Mate.

edited Apr 13 '17 at 12:37

Community♦

asked Jun 21 '15 at 2:58

linstar

3362415

What distro and version are you using, debian? did you try chkconfig?

– VaTo
Jun 21 '15 at 4:16

3

Have you considered looking at the logs?

– lcd047
Jun 21 '15 at 4:19

lcd047: Yes, I updated my question.

– linstar
Jun 21 '15 at 11:24

In systemd based systems, it's possible that only a socket is opened and the daemon loads on demand, when a request comes. I hope this is relevant.

– orion
Jun 21 '15 at 11:57

orion: Well, I've tried to ssh into my computer even though sshd doesn't show up with ps -A. I can't login. Once I manually start it, I can login. So, I sort of understand what you're saying, but, I think based on this scenario, I would say the daemon is not loading when the request comes in, if I'm interpreting your point correctly.

– linstar
Jun 21 '15 at 13:03

add a comment |

My sshd won't start at bootup. I have to type it in manually (sudo service ssh start).

I've posted a question on how to start ssh at bootup (How to start SSH daemon on boot on Linux Mint Debian v2), but, everything I've tried has not worked.

I checked /var/log/boot.log, it actually says:

[ ok ] Starting OpenBSD Secure Shell server: sshd

However, when I type ps -A | grep ssh, sshd does not show up. If I start it manually (sudo service ssh start), it does show up. Is there a specific log for SSH that I can check?

I'm using LMDE v2, 64-bit, Mate.

edited Apr 13 '17 at 12:37

Community♦

asked Jun 21 '15 at 2:58

linstar

3362415

What distro and version are you using, debian? did you try chkconfig?

– VaTo
Jun 21 '15 at 4:16

3

Have you considered looking at the logs?

– lcd047
Jun 21 '15 at 4:19

lcd047: Yes, I updated my question.

– linstar
Jun 21 '15 at 11:24

In systemd based systems, it's possible that only a socket is opened and the daemon loads on demand, when a request comes. I hope this is relevant.

– orion
Jun 21 '15 at 11:57

orion: Well, I've tried to ssh into my computer even though sshd doesn't show up with ps -A. I can't login. Once I manually start it, I can login. So, I sort of understand what you're saying, but, I think based on this scenario, I would say the daemon is not loading when the request comes in, if I'm interpreting your point correctly.

– linstar
Jun 21 '15 at 13:03

add a comment |

My sshd won't start at bootup. I have to type it in manually (sudo service ssh start).

I've posted a question on how to start ssh at bootup (How to start SSH daemon on boot on Linux Mint Debian v2), but, everything I've tried has not worked.

I checked /var/log/boot.log, it actually says:

[ ok ] Starting OpenBSD Secure Shell server: sshd

However, when I type ps -A | grep ssh, sshd does not show up. If I start it manually (sudo service ssh start), it does show up. Is there a specific log for SSH that I can check?

I'm using LMDE v2, 64-bit, Mate.

edited Apr 13 '17 at 12:37

Community♦

asked Jun 21 '15 at 2:58

linstar

3362415

My sshd won't start at bootup. I have to type it in manually (sudo service ssh start).

I've posted a question on how to start ssh at bootup (How to start SSH daemon on boot on Linux Mint Debian v2), but, everything I've tried has not worked.

I checked /var/log/boot.log, it actually says:

[ ok ] Starting OpenBSD Secure Shell server: sshd

However, when I type ps -A | grep ssh, sshd does not show up. If I start it manually (sudo service ssh start), it does show up. Is there a specific log for SSH that I can check?

I'm using LMDE v2, 64-bit, Mate.

ssh startup init.d

edited Apr 13 '17 at 12:37

Community♦

asked Jun 21 '15 at 2:58

linstar

3362415

edited Apr 13 '17 at 12:37

Community♦

asked Jun 21 '15 at 2:58

linstar

3362415

edited Apr 13 '17 at 12:37

Community♦

edited Apr 13 '17 at 12:37

Community♦

edited Apr 13 '17 at 12:37

Community♦

asked Jun 21 '15 at 2:58

linstar

3362415

asked Jun 21 '15 at 2:58

linstar

3362415

asked Jun 21 '15 at 2:58

linstar

3362415

What distro and version are you using, debian? did you try chkconfig?

– VaTo
Jun 21 '15 at 4:16

3

Have you considered looking at the logs?

– lcd047
Jun 21 '15 at 4:19

lcd047: Yes, I updated my question.

– linstar
Jun 21 '15 at 11:24

In systemd based systems, it's possible that only a socket is opened and the daemon loads on demand, when a request comes. I hope this is relevant.

– orion
Jun 21 '15 at 11:57

orion: Well, I've tried to ssh into my computer even though sshd doesn't show up with ps -A. I can't login. Once I manually start it, I can login. So, I sort of understand what you're saying, but, I think based on this scenario, I would say the daemon is not loading when the request comes in, if I'm interpreting your point correctly.

– linstar
Jun 21 '15 at 13:03

add a comment |

What distro and version are you using, debian? did you try chkconfig?

– VaTo
Jun 21 '15 at 4:16

3

Have you considered looking at the logs?

– lcd047
Jun 21 '15 at 4:19

lcd047: Yes, I updated my question.

– linstar
Jun 21 '15 at 11:24

In systemd based systems, it's possible that only a socket is opened and the daemon loads on demand, when a request comes. I hope this is relevant.

– orion
Jun 21 '15 at 11:57

orion: Well, I've tried to ssh into my computer even though sshd doesn't show up with ps -A. I can't login. Once I manually start it, I can login. So, I sort of understand what you're saying, but, I think based on this scenario, I would say the daemon is not loading when the request comes in, if I'm interpreting your point correctly.

– linstar
Jun 21 '15 at 13:03

What distro and version are you using, debian? did you try chkconfig?

– VaTo
Jun 21 '15 at 4:16

Have you considered looking at the logs?

– lcd047
Jun 21 '15 at 4:19

lcd047: Yes, I updated my question.

– linstar
Jun 21 '15 at 11:24

In systemd based systems, it's possible that only a socket is opened and the daemon loads on demand, when a request comes. I hope this is relevant.

– orion
Jun 21 '15 at 11:57

orion: Well, I've tried to ssh into my computer even though sshd doesn't show up with ps -A. I can't login. Once I manually start it, I can login. So, I sort of understand what you're saying, but, I think based on this scenario, I would say the daemon is not loading when the request comes in, if I'm interpreting your point correctly.

– linstar
Jun 21 '15 at 13:03

add a comment |

1 Answer
1

active

oldest

votes

I figured it out. In my auth.log file, it wasn't binding to the IP address I put in for the ListenAddress parameter in /etc/ssh/sshd_config. After I changed it back to 0.0.0.0, it starts up now. Don't quite understand, I thought I could put the IP address of my computer?

And I don't understand why it doesn't start at boot, yet, manually, it can start.

answered Jun 21 '15 at 19:12

linstar

3362415

1

Suspect sshd is starting before your specific ip address has been assigned. So it's not available when sshd tries to bind with the Listen directive

– roaima
Jun 21 '15 at 21:46

add a comment |

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f211080%2fis-there-a-specific-ssh-boot-log%23new-answer', 'question_page');

);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

And I don't understand why it doesn't start at boot, yet, manually, it can start.

answered Jun 21 '15 at 19:12

linstar

3362415

1

Suspect sshd is starting before your specific ip address has been assigned. So it's not available when sshd tries to bind with the Listen directive

– roaima
Jun 21 '15 at 21:46

add a comment |

And I don't understand why it doesn't start at boot, yet, manually, it can start.

answered Jun 21 '15 at 19:12

linstar

3362415

1

Suspect sshd is starting before your specific ip address has been assigned. So it's not available when sshd tries to bind with the Listen directive

– roaima
Jun 21 '15 at 21:46

add a comment |

And I don't understand why it doesn't start at boot, yet, manually, it can start.

answered Jun 21 '15 at 19:12

linstar

3362415

And I don't understand why it doesn't start at boot, yet, manually, it can start.

answered Jun 21 '15 at 19:12

linstar

3362415

answered Jun 21 '15 at 19:12

linstar

3362415

answered Jun 21 '15 at 19:12

linstar

3362415

answered Jun 21 '15 at 19:12

linstar

3362415

1

Suspect sshd is starting before your specific ip address has been assigned. So it's not available when sshd tries to bind with the Listen directive

– roaima
Jun 21 '15 at 21:46

add a comment |

1

Suspect sshd is starting before your specific ip address has been assigned. So it's not available when sshd tries to bind with the Listen directive

– roaima
Jun 21 '15 at 21:46

Suspect sshd is starting before your specific ip address has been assigned. So it's not available when sshd tries to bind with the Listen directive

– roaima
Jun 21 '15 at 21:46

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Unix & Linux Stack Exchange!

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.

draft saved

draft discarded

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

搜尋此網誌

mjhjmtu