Debian - ssh Does Not Run On Boot












0















All in the title.



I'm finding this by using the command systemctl status ssh, and I get a report of (dead). My networking seems to be fine as ping 8.8.8.8 gets responses. Somewhere online I saw a similar problem where it was suggested to try grep sshd /var/log/auth.log. The logs for today are as follows:



Jan 25 20:28:48 RTIBUSDock sudo: root : TTY=unknown ; PWD=/home/scripts ; USER=root ; COMMAND=/usr/sbin/service ssh start
Jan 25 20:28:49 RTIBUSDock sshd[580]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Jan 25 20:28:49 RTIBUSDock sshd[580]: error: Bind to port 22 on :: failed: Address already in use.
Jan 25 20:28:49 RTIBUSDock sshd[580]: fatal: Cannot bind any address.
Jan 25 20:49:23 RTIBUSDock sshd[1255]: Server listening on 0.0.0.0 port 22.
Jan 25 20:49:23 RTIBUSDock sshd[1255]: Server listening on :: port 22.
Jan 25 20:54:20 RTIBUSDock sudo: root : TTY=ttySAC2 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl enable ssh
Jan 25 20:54:30 RTIBUSDock sshd[1255]: Received signal 15; terminating.
Jan 25 20:56:04 RTIBUSDock sudo: root : TTY=ttySAC2 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl enable ssh.socket
Jan 25 21:00:52 RTIBUSDock sshd[1020]: Server listening on 0.0.0.0 port 22.
Jan 25 21:00:52 RTIBUSDock sshd[1020]: Server listening on :: port 22.
Jan 25 21:01:08 RTIBUSDock sshd[1020]: Received signal 15; terminating.
Jan 25 21:58:01 RTIBUSDock sshd[826]: Server listening on 0.0.0.0 port 22.
Jan 25 21:58:01 RTIBUSDock sshd[826]: Server listening on :: port 22.



If it's relevant, this all started happening after moving the boot volume (on an SD card) from one computer to another. I'm very new to Linux stuff so if there are any other logs to check I don't know about them. All input welcome.









share







New contributor




Bo Thompson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    0















    All in the title.



    I'm finding this by using the command systemctl status ssh, and I get a report of (dead). My networking seems to be fine as ping 8.8.8.8 gets responses. Somewhere online I saw a similar problem where it was suggested to try grep sshd /var/log/auth.log. The logs for today are as follows:



    Jan 25 20:28:48 RTIBUSDock sudo: root : TTY=unknown ; PWD=/home/scripts ; USER=root ; COMMAND=/usr/sbin/service ssh start
    Jan 25 20:28:49 RTIBUSDock sshd[580]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
    Jan 25 20:28:49 RTIBUSDock sshd[580]: error: Bind to port 22 on :: failed: Address already in use.
    Jan 25 20:28:49 RTIBUSDock sshd[580]: fatal: Cannot bind any address.
    Jan 25 20:49:23 RTIBUSDock sshd[1255]: Server listening on 0.0.0.0 port 22.
    Jan 25 20:49:23 RTIBUSDock sshd[1255]: Server listening on :: port 22.
    Jan 25 20:54:20 RTIBUSDock sudo: root : TTY=ttySAC2 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl enable ssh
    Jan 25 20:54:30 RTIBUSDock sshd[1255]: Received signal 15; terminating.
    Jan 25 20:56:04 RTIBUSDock sudo: root : TTY=ttySAC2 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl enable ssh.socket
    Jan 25 21:00:52 RTIBUSDock sshd[1020]: Server listening on 0.0.0.0 port 22.
    Jan 25 21:00:52 RTIBUSDock sshd[1020]: Server listening on :: port 22.
    Jan 25 21:01:08 RTIBUSDock sshd[1020]: Received signal 15; terminating.
    Jan 25 21:58:01 RTIBUSDock sshd[826]: Server listening on 0.0.0.0 port 22.
    Jan 25 21:58:01 RTIBUSDock sshd[826]: Server listening on :: port 22.



    If it's relevant, this all started happening after moving the boot volume (on an SD card) from one computer to another. I'm very new to Linux stuff so if there are any other logs to check I don't know about them. All input welcome.









    share







    New contributor




    Bo Thompson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0








      All in the title.



      I'm finding this by using the command systemctl status ssh, and I get a report of (dead). My networking seems to be fine as ping 8.8.8.8 gets responses. Somewhere online I saw a similar problem where it was suggested to try grep sshd /var/log/auth.log. The logs for today are as follows:



      Jan 25 20:28:48 RTIBUSDock sudo: root : TTY=unknown ; PWD=/home/scripts ; USER=root ; COMMAND=/usr/sbin/service ssh start
      Jan 25 20:28:49 RTIBUSDock sshd[580]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
      Jan 25 20:28:49 RTIBUSDock sshd[580]: error: Bind to port 22 on :: failed: Address already in use.
      Jan 25 20:28:49 RTIBUSDock sshd[580]: fatal: Cannot bind any address.
      Jan 25 20:49:23 RTIBUSDock sshd[1255]: Server listening on 0.0.0.0 port 22.
      Jan 25 20:49:23 RTIBUSDock sshd[1255]: Server listening on :: port 22.
      Jan 25 20:54:20 RTIBUSDock sudo: root : TTY=ttySAC2 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl enable ssh
      Jan 25 20:54:30 RTIBUSDock sshd[1255]: Received signal 15; terminating.
      Jan 25 20:56:04 RTIBUSDock sudo: root : TTY=ttySAC2 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl enable ssh.socket
      Jan 25 21:00:52 RTIBUSDock sshd[1020]: Server listening on 0.0.0.0 port 22.
      Jan 25 21:00:52 RTIBUSDock sshd[1020]: Server listening on :: port 22.
      Jan 25 21:01:08 RTIBUSDock sshd[1020]: Received signal 15; terminating.
      Jan 25 21:58:01 RTIBUSDock sshd[826]: Server listening on 0.0.0.0 port 22.
      Jan 25 21:58:01 RTIBUSDock sshd[826]: Server listening on :: port 22.



      If it's relevant, this all started happening after moving the boot volume (on an SD card) from one computer to another. I'm very new to Linux stuff so if there are any other logs to check I don't know about them. All input welcome.









      share







      New contributor




      Bo Thompson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      All in the title.



      I'm finding this by using the command systemctl status ssh, and I get a report of (dead). My networking seems to be fine as ping 8.8.8.8 gets responses. Somewhere online I saw a similar problem where it was suggested to try grep sshd /var/log/auth.log. The logs for today are as follows:



      Jan 25 20:28:48 RTIBUSDock sudo: root : TTY=unknown ; PWD=/home/scripts ; USER=root ; COMMAND=/usr/sbin/service ssh start
      Jan 25 20:28:49 RTIBUSDock sshd[580]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
      Jan 25 20:28:49 RTIBUSDock sshd[580]: error: Bind to port 22 on :: failed: Address already in use.
      Jan 25 20:28:49 RTIBUSDock sshd[580]: fatal: Cannot bind any address.
      Jan 25 20:49:23 RTIBUSDock sshd[1255]: Server listening on 0.0.0.0 port 22.
      Jan 25 20:49:23 RTIBUSDock sshd[1255]: Server listening on :: port 22.
      Jan 25 20:54:20 RTIBUSDock sudo: root : TTY=ttySAC2 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl enable ssh
      Jan 25 20:54:30 RTIBUSDock sshd[1255]: Received signal 15; terminating.
      Jan 25 20:56:04 RTIBUSDock sudo: root : TTY=ttySAC2 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl enable ssh.socket
      Jan 25 21:00:52 RTIBUSDock sshd[1020]: Server listening on 0.0.0.0 port 22.
      Jan 25 21:00:52 RTIBUSDock sshd[1020]: Server listening on :: port 22.
      Jan 25 21:01:08 RTIBUSDock sshd[1020]: Received signal 15; terminating.
      Jan 25 21:58:01 RTIBUSDock sshd[826]: Server listening on 0.0.0.0 port 22.
      Jan 25 21:58:01 RTIBUSDock sshd[826]: Server listening on :: port 22.



      If it's relevant, this all started happening after moving the boot volume (on an SD card) from one computer to another. I'm very new to Linux stuff so if there are any other logs to check I don't know about them. All input welcome.







      debian ssh





      share







      New contributor




      Bo Thompson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.










      share







      New contributor




      Bo Thompson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      share



      share






      New contributor




      Bo Thompson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 2 mins ago









      Bo ThompsonBo Thompson

      1




      1




      New contributor




      Bo Thompson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Bo Thompson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Bo Thompson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          0






          active

          oldest

          votes











          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
          });


          }
          });






          Bo Thompson is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f496789%2fdebian-ssh-does-not-run-on-boot%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          Bo Thompson is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          Bo Thompson is a new contributor. Be nice, and check out our Code of Conduct.













          Bo Thompson is a new contributor. Be nice, and check out our Code of Conduct.












          Bo Thompson is a new contributor. Be nice, and check out our Code of Conduct.
















          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














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f496789%2fdebian-ssh-does-not-run-on-boot%23new-answer', 'question_page');
          }
          );

          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