Yocto Project Discussions
 help / color / mirror / Atom feed
From: srijan.nandi@gmail.com
To: yocto@lists.yoctoproject.org
Subject: Re: #yocto systemd not able to start sshd after a reboot
Date: Mon, 21 Sep 2020 10:09:00 -0700	[thread overview]
Message-ID: <14779.1600708140146261109@lists.yoctoproject.org> (raw)
In-Reply-To: <CAGAf8LxAjPEwNLYGdjbPDN7uCqdGfMNZH8ar6DZmshud9NH5SQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 780 bytes --]

Seems strange to me too...I had been troubleshooting the sshd.service issue for two days. There was no logs, nothing. I was just hitting the wall. I tried a lot of combinations to get it to work but all failed.

The sshd.service was starting, if I manually did a systemctl start sshd.service. But always failed at startup. At times it would start and then get a signal 15 terminating and would close the daemon.

After not able to resolve the issue, I started checking all the other services. Every other service was starting at bootup just fine except sshd.

Not finding anything else to troubleshoot. I happened to stumble upon the sshd.socket and the Conflicts part of it. Did a hit and trial and it worked. Technically I still am not sure as to why..

-=Srijan Nandi

[-- Attachment #2: Type: text/html, Size: 812 bytes --]

  reply	other threads:[~2020-09-21 17:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 15:29 #yocto systemd not able to start sshd after a reboot srijan.nandi
2020-09-18 16:37 ` [yocto] " Khem Raj
2020-09-18 18:04   ` srijan.nandi
2020-09-19  3:10     ` [yocto] " Zoran
2020-09-19 13:12       ` srijan.nandi
2020-09-19 13:49         ` [yocto] " Zoran
2020-09-21 12:17           ` srijan.nandi
2020-09-22  6:49             ` [yocto] " Khem Raj
2020-09-21 13:22         ` Zoran
2020-09-21 17:09           ` srijan.nandi [this message]
2020-09-27 10:00 ` Zoran

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=14779.1600708140146261109@lists.yoctoproject.org \
    --to=srijan.nandi@gmail.com \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox