Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Sshd not working on latest RC

    Scheduled Pinned Locked Moved General pfSense Questions
    12 Posts 6 Posters 2.5k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      asterix
      last edited by

      Anyone having issues with sshd service not starting after a reboot? Tried disabling, rebooting and enabling it again… no go.

      1 Reply Last reply Reply Quote 0
      • E
        eri--
        last edited by

        Any other service with same issue.
        That has been seen when the filesystem gets orrupted and /etc/group is not with right info inside.

        1 Reply Last reply Reply Quote 0
        • C
          cmb
          last edited by

          anything related to SSH in the system log? What happens if you manually start it running '/usr/sbin/sshd'?

          1 Reply Last reply Reply Quote 0
          • A
            asterix
            last edited by

            Yes clamd (squid3) service fails to start as well. Service watchdog tries to start both but fails. clamd starts only if I issue a "clamd" command

            No info in the system logs on sshd service failiure… nor anything comes up when the service restart fails.

            1 Reply Last reply Reply Quote 0
            • A
              asterix
              last edited by

              ok so a manual start of sshd by issuing the command '/usr/sbin/sshd' worked.

              Jan 21 17:18:49 sshd[37746]: Server listening on 0.0.0.0 port 22.
              Jan 21 17:18:49 sshd[37746]: Server listening on :: port 22.

              Still on reboot it fails along with clamd

              1 Reply Last reply Reply Quote 0
              • C
                cmb
                last edited by

                Does it fail if you remove squid?

                1 Reply Last reply Reply Quote 0
                • A
                  asterix
                  last edited by

                  Didnt try that. Switched back to 2.1.5 for now.

                  1 Reply Last reply Reply Quote 0
                  • F
                    firewalluser
                    last edited by

                    @Asterix:

                    Yes clamd (squid3) service fails to start as well. Service watchdog tries to start both but fails. clamd starts only if I issue a "clamd" command

                    No info in the system logs on sshd service failiure… nor anything comes up when the service restart fails.

                    A side note about about ClamD, I've got viruses here which clamd does not recognise as a virus, but other AV software do recognise the viruses, so dont be 100% reliant on ClamD , this link will help explain why https://www.shadowserver.org/wiki/pmwiki.php/AV/Viruses

                    Capitalism, currently The World's best Entertainment Control System and YOU cant buy it! But you can buy this, or some of this or some of these

                    Asch Conformity, mainly the blind leading the blind.

                    1 Reply Last reply Reply Quote 0
                    • E
                      e3ctsc
                      last edited by

                      @cmb:

                      Does it fail if you remove squid?

                      Have the same issue since upgrading to RC *-P4 from 16.01.2015. Removing squid did not change it. Still not able to start sshd from services.

                      Additional Information:

                      • Had squid installed bevore upgrading to RC *-p4 from 16.01.2015

                      • start sshd manually (from the command line menu)

                      • once sshd is started manually it can be stopped from the services menu (but not started again)

                      • Removing squid did not change the behavior (even after restart)

                      • Nothing sshd related in system log

                      • sshd config is OK (manually started sshd uses it whithout an issue)

                      1 Reply Last reply Reply Quote 0
                      • rbgargaR
                        rbgarga Developer Netgate Administrator
                        last edited by

                        Could you guys check ownership of /usr/local/lib? I saw the same issue on a system with squid3 installed, and noted the directory ownership was changed to proxy:proxy, what caused check_reload_status not to be loaded and cause sshd not being started.

                        Renato Botelho

                        1 Reply Last reply Reply Quote 0
                        • E
                          e3ctsc
                          last edited by

                          @Renato:

                          Could you guys check ownership of /usr/local/lib? I saw the same issue on a system with squid3 installed, and noted the directory ownership was changed to proxy:proxy, what caused check_reload_status not to be loaded and cause sshd not being started.

                          It was the file permissions. I compared file ownerships with an older backup and saw following files changed

                          • complete /usr/local with all files, subdirectories and symbolic links was proxy:proxy instead of root:wheel

                          • /etc/ssl/openssl.cnf was proxy:proxy instead of root:wheel

                          • /dev/pf was root:proxy

                          After chowning them back I had to reboot to get it working again (perhaps there had been a better way than rebooting)

                          1 Reply Last reply Reply Quote 0
                          • rbgargaR
                            rbgarga Developer Netgate Administrator
                            last edited by

                            @e3ctsc:

                            @Renato:

                            Could you guys check ownership of /usr/local/lib? I saw the same issue on a system with squid3 installed, and noted the directory ownership was changed to proxy:proxy, what caused check_reload_status not to be loaded and cause sshd not being started.

                            It was the file permissions. I compared file ownerships with an older backup and saw following files changed

                            • complete /usr/local with all files, subdirectories and symbolic links was proxy:proxy instead of root:wheel

                            • /etc/ssl/openssl.cnf was proxy:proxy instead of root:wheel

                            • /dev/pf was root:proxy

                            After chowning them back I had to reboot to get it working again (perhaps there had been a better way than rebooting)

                            Thanks! I pushed a fix on squid3 package, version 0.2.6.

                            Renato Botelho

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post
                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.