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

    Resolved: The command '/usr/local/sbin/ping-auth -s > /etc/thoth/thothid 2>/dev/null' returned exit code '127', the output was ''

    Scheduled Pinned Locked Moved General pfSense Questions
    developmentcryptocryptographicfirmware
    53 Posts 3 Posters 7.9k 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.
    • JonathanLeeJ
      JonathanLee
      last edited by

      Screenshot_20231218-133414.png

      Any ideas??

      Make sure to upvote

      1 Reply Last reply Reply Quote 0
      • JonathanLeeJ
        JonathanLee
        last edited by

        I opened a TAC they just send me firmware again and closed it. Does it need a different build?

        Make sure to upvote

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by stephenw10

          Are you sure it ever showed a CryptoID? The later 2100s didn't have the chip as we moved away from that.

          Mmm, this looks like bug. Harmless but a bug.

          JonathanLeeJ J 2 Replies Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Opened an internal bug report to investigate.

            JonathanLeeJ 2 Replies Last reply Reply Quote 1
            • JonathanLeeJ
              JonathanLee @stephenw10
              last edited by

              @stephenw10

              Here is it showing in 23.05.01

              Screenshot 2023-12-18 at 2.13.40 PM.png

              Yes my SG-2100 has one, is this the same as a TPM chip for encrypting drives?

              Make sure to upvote

              1 Reply Last reply Reply Quote 0
              • JonathanLeeJ
                JonathanLee @stephenw10
                last edited by

                @stephenw10 could it be my bios that is showing? I don't know could a new SSD cause this? The cyptoID is on the pcb mainboard right?

                Make sure to upvote

                1 Reply Last reply Reply Quote 0
                • JonathanLeeJ
                  JonathanLee @stephenw10
                  last edited by

                  @stephenw10 Thanks for looking into this. I opened a TAC ticket but they just sent me firmware, when I said I installed it and it did not fix it the ticket was closed. I think he got mixed up with my ticket.

                  Make sure to upvote

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    It's not a TPM device, it doesn't have anything to do with drive encryption.

                    I wouldn't expect a driver to make any difference here. I could just about imagine causing problems communicating with the chip but that would be the same in 23.05.1.

                    I assume running ping-auth -s correctly returns the crypto ID there?

                    JonathanLeeJ 1 Reply Last reply Reply Quote 0
                    • JonathanLeeJ
                      JonathanLee @stephenw10
                      last edited by JonathanLee

                      @stephenw10 said in The command '/usr/local/sbin/ping-auth -s > /etc/thoth/thothid 2>/dev/null' returned exit code '127', the output was '':

                      ping-auth -s

                      in 23.05.01

                      Screenshot 2023-12-18 at 2.25.15 PM.png

                      So its something with that build? I also have issues with experimental ethernet rules and compex ath0 driver they no longer separate the layer 2 broadcast domains for ARP requests from LAN to Compex card, this version is prone to ARP broadcast storms across different interfaces before it broke them up I never showed traffic between the two interfaces.

                      Screenshot 2023-12-18 at 1.09.45 PM.png

                      https://forum.netgate.com/topic/184894/ethernet-rules-on-two-networks

                      Make sure to upvote

                      1 Reply Last reply Reply Quote 0
                      • JonathanLeeJ
                        JonathanLee
                        last edited by

                        https://redmine.pfsense.org/issues/15103

                        Make sure to upvote

                        1 Reply Last reply Reply Quote 0
                        • stephenw10S
                          stephenw10 Netgate Administrator
                          last edited by

                          Did you try 23.09.1 without the new SSD installed?

                          JonathanLeeJ 1 Reply Last reply Reply Quote 0
                          • JonathanLeeJ
                            JonathanLee @stephenw10
                            last edited by

                            @stephenw10 yes but I can't remember I think it also had the same issue. Could a SSD cause this?

                            Make sure to upvote

                            1 Reply Last reply Reply Quote 0
                            • stephenw10S
                              stephenw10 Netgate Administrator
                              last edited by

                              It could if, for example it somehow had the same smbus address as the crypto chip. It shouldn't but it works fine for me here in 23.09.1 without an SSD.

                              Is that test from 23.05.1 also with the SSD?

                              JonathanLeeJ 1 Reply Last reply Reply Quote 0
                              • J
                                jrey @JonathanLee
                                last edited by

                                @JonathanLee

                                So as you have already noticed, I'm guessing, what you're showing is different than the build date I'm showing and posted above

                                Curious was that image before or after TAC sent you the new image, or is/was the date the same on both.

                                Still think it is different than just a package here or there, as was discussed here.

                                https://forum.netgate.com/topic/184681/after-update-2-7-2-23-09-1?_=1702938917839

                                1 Reply Last reply Reply Quote 0
                                • J
                                  jrey @stephenw10
                                  last edited by

                                  @stephenw10 said in The command '/usr/local/sbin/ping-auth -s > /etc/thoth/thothid 2>/dev/null' returned exit code '127', the output was '':

                                  The later 2100s didn't have the chip as we moved away from that

                                  define "later" by D.O.M. - please.

                                  1 Reply Last reply Reply Quote 0
                                  • JonathanLeeJ
                                    JonathanLee @stephenw10
                                    last edited by JonathanLee

                                    @stephenw10 yes the 23.05.01 is an SSD that came with my 2100-MAX 32GB

                                    The 23.09.01 is on a KingSpec SSD it's 128GB

                                    The new SG2100MAX comes with 128GB so I wanted mine to max up to the new MAX

                                    Make sure to upvote

                                    1 Reply Last reply Reply Quote 0
                                    • stephenw10S
                                      stephenw10 Netgate Administrator
                                      last edited by

                                      Ah, but not the same one...

                                      JonathanLeeJ J 2 Replies Last reply Reply Quote 0
                                      • JonathanLeeJ
                                        JonathanLee @stephenw10
                                        last edited by JonathanLee

                                        @stephenw10 no it's a different it's a KingSpec the smart status does not show as much as the trendnet SSD. The install SSD guide for 2100 did not state any cyptoID issues also, that's why I thought it couldn't be the 128GB SSD everything works except that cryptoID is missing and it has the system errors to go with it

                                        Make sure to upvote

                                        1 Reply Last reply Reply Quote 0
                                        • J
                                          jrey @stephenw10
                                          last edited by

                                          @stephenw10

                                          So I think the only reason my system info is showing the Crypto ID is because the file with the id in it already exists and I upgraded on the existing system

                                          system_get_thothid

                                          technically if my system did not have the id already in file and got to the exec of /usr/local/sbin/ping-auth it would fail. File does not exist.

                                          ls: /usr/local/sbin/ping-auth: No such file or directory
                                          

                                          The system info has displayed this since day one, and will continue to do so, until the file is gone. Then it will error.

                                          Begs the question, @JonathanLee does the file exist on your system?

                                          @stephenw10 should it? clearly it has in the past.

                                          Clearly the dashboard is going to call system_get_thothid and if the file does not exist it is going to call ping-auth.

                                          JonathanLeeJ 1 Reply Last reply Reply Quote 1
                                          • JonathanLeeJ
                                            JonathanLee
                                            last edited by JonathanLee

                                            Can I just copy it over to the new SSD? I am confused is yours missing also as that path is invalid.

                                            I wonder what the path is to the id file. It has to match the chip each is different.

                                            I just need my top secret missing critical cryptoID file then for it to work again?

                                            Make sure to upvote

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