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

    Pkg - need to re-create database -> Segmentation fault

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    29 Posts 6 Posters 15.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.
    • D Offline
      dvl
      last edited by

      One file is there. I have removed it.

      [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: ls -l /usr/local/share/pfSense/keys/pkg/revoked/.empty
      -rw-r--r--  1 root  wheel  0 Jul 19  2016 /usr/local/share/pfSense/keys/pkg/revoked/.empty
      
      [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: ls -l /usr/local/share/pfSense/keys/pkg/trusted/.empty
      ls: /usr/local/share/pfSense/keys/pkg/trusted/.empty: No such file or directory
      [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: 
      
      

      After that, I retried the command:

       pkg-static install -f pkg
      Updating pfSense-core repository catalogue...
      pkg-static: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
      meta.txz                                 : 100%  944 B     0.9kB/s    00:01    
      pkg-static: No trusted public keys found
      repository pfSense-core has no meta file, using default settings
      packagesite.txz                          : 100%    2 KiB   2.3kB/s    00:01    
      pkg-static: No trusted public keys found
      Unable to update repository pfSense-core
      Updating pfSense repository catalogue...
      pkg-static: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
      meta.txz                                 : 100%  944 B     0.9kB/s    00:01    
      pkg-static: No trusted public keys found
      repository pfSense has no meta file, using default settings
      packagesite.txz                          : 100%  119 KiB 121.8kB/s    00:01    
      pkg-static: No trusted public keys found
      Unable to update repository pfSense
      Error updating repositories!
      
      

      What do we have there?

      [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: ls -l /var/db/pkg/
      total 4486
      -rw-r--r--  1 root  wheel      246 Mar 29 04:38 local.meta
      -rw-r--r--  1 root  wheel  4578304 Mar 29 23:03 local.sqlite
      -rw-r--r--  1 root  wheel      246 Aug  4 16:07 pfSense-core.meta
      -rw-r--r--  1 root  wheel      246 Aug  4 16:07 pfSense.meta
      [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: 
      
      

      I don't want to try anything else in case there are forensics to be used.

      1 Reply Last reply Reply Quote 0
      • jimpJ Offline
        jimp Rebel Alliance Developer Netgate
        last edited by

        Do you have key files in /usr/local/share/pfSense/keys/pkg/trusted/?

        You should have, for example, pkg.pfsense.org.20160406 and beta.pfsense.org.20151223 in there.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • D Offline
          dvl
          last edited by

          @jimp:

          Do you have key files in /usr/local/share/pfSense/keys/pkg/trusted/?

          You should have, for example, pkg.pfsense.org.20160406 and beta.pfsense.org.20151223 in there.

          [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: ls -l  /usr/local/share/pfSense/keys/pkg/trusted
          total 1
          -rw-r--r--  1 root  wheel  95 Jul 19  2016 beta.pfsense.org.20151223
          -rw-r--r--  1 root  wheel  95 Mar 30 11:34 pkg.pfsense.org.20160406
          
          1 Reply Last reply Reply Quote 0
          • rbgargaR Offline
            rbgarga Developer Netgate Administrator
            last edited by

            @dvl:

            @jimp:

            Do you have key files in /usr/local/share/pfSense/keys/pkg/trusted/?

            You should have, for example, pkg.pfsense.org.20160406 and beta.pfsense.org.20151223 in there.

            [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: ls -l  /usr/local/share/pfSense/keys/pkg/trusted
            total 1
            -rw-r--r--  1 root  wheel  95 Jul 19  2016 beta.pfsense.org.20151223
            -rw-r--r--  1 root  wheel  95 Mar 30 11:34 pkg.pfsense.org.20160406
            

            Do you see any error messages when you run 'pkg update -f'? No need to use pkg-static now since the empty file that was causing the crash was removed.

            If you see the errors, run 'pkg -dd update -f' and share the output

            Renato Botelho

            1 Reply Last reply Reply Quote 0
            • D Offline
              dvl
              last edited by

              @Renato:

              @dvl:

              @jimp:

              Do you have key files in /usr/local/share/pfSense/keys/pkg/trusted/?

              You should have, for example, pkg.pfsense.org.20160406 and beta.pfsense.org.20151223 in there.

              [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: ls -l  /usr/local/share/pfSense/keys/pkg/trusted
              total 1
              -rw-r--r--  1 root  wheel  95 Jul 19  2016 beta.pfsense.org.20151223
              -rw-r--r--  1 root  wheel  95 Mar 30 11:34 pkg.pfsense.org.20160406
              

              Do you see any error messages when you run 'pkg update -f'? No need to use pkg-static now since the empty file that was causing the crash was removed.

              If you see the errors, run 'pkg -dd update -f' and share the output

              Here we go

              [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: pkg -dd update -f
              DBG(1)[50590]> pkg initialized
              Updating pfSense-core repository catalogue...
              DBG(1)[50590]> PkgRepo: verifying update for pfSense-core
              pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
              DBG(1)[50590]> PkgRepo: need forced update of pfSense-core
              DBG(1)[50590]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
              DBG(1)[50590]> Fetch: fetching from: https://www.firmware.netgate.com/pkg/pfSense_factory-v2_3_3_amd64-core/meta.txz with opts "i"
              meta.txz                                 : 100%  944 B     0.9kB/s    00:01    
              DBG(1)[50590]> PkgRepo: extracting meta of repo pfSense-core
              DBG(1)[50716]> PkgRepo: extracting signature of repo in a sandbox
              pkg: No trusted public keys found
              repository pfSense-core has no meta file, using default settings
              DBG(1)[50590]> Fetch: fetching from: https://www.firmware.netgate.com/pkg/pfSense_factory-v2_3_3_amd64-core/packagesite.txz with opts "i"
              packagesite.txz                          : 100%    2 KiB   2.3kB/s    00:01    
              DBG(1)[50590]> PkgRepo: extracting packagesite.yaml of repo pfSense-core
              DBG(1)[50987]> PkgRepo: extracting signature of repo in a sandbox
              pkg: No trusted public keys found
              Unable to update repository pfSense-core
              Updating pfSense repository catalogue...
              DBG(1)[50590]> PkgRepo: verifying update for pfSense
              pkg: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
              DBG(1)[50590]> PkgRepo: need forced update of pfSense
              DBG(1)[50590]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
              DBG(1)[50590]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_3_amd64-pfSense_factory-v2_3_3/meta.txz with opts "i"
              meta.txz                                 : 100%  944 B     0.9kB/s    00:01    
              DBG(1)[50590]> PkgRepo: extracting meta of repo pfSense
              DBG(1)[51205]> PkgRepo: extracting signature of repo in a sandbox
              pkg: No trusted public keys found
              repository pfSense has no meta file, using default settings
              DBG(1)[50590]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_3_amd64-pfSense_factory-v2_3_3/packagesite.txz with opts "i"
              packagesite.txz                          : 100%  119 KiB 121.8kB/s    00:01    
              DBG(1)[50590]> PkgRepo: extracting packagesite.yaml of repo pfSense
              DBG(1)[51295]> PkgRepo: extracting signature of repo in a sandbox
              pkg: No trusted public keys found
              Unable to update repository pfSense
              Error updating repositories!
              [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: 
              
              
              1 Reply Last reply Reply Quote 0
              • rbgargaR Offline
                rbgarga Developer Netgate Administrator
                last edited by

                @dvl:

                @Renato:

                @dvl:

                @jimp:

                Do you have key files in /usr/local/share/pfSense/keys/pkg/trusted/?

                You should have, for example, pkg.pfsense.org.20160406 and beta.pfsense.org.20151223 in there.

                [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: ls -l  /usr/local/share/pfSense/keys/pkg/trusted
                total 1
                -rw-r--r--  1 root  wheel  95 Jul 19  2016 beta.pfsense.org.20151223
                -rw-r--r--  1 root  wheel  95 Mar 30 11:34 pkg.pfsense.org.20160406
                

                Do you see any error messages when you run 'pkg update -f'? No need to use pkg-static now since the empty file that was causing the crash was removed.

                If you see the errors, run 'pkg -dd update -f' and share the output

                Here we go

                [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: pkg -dd update -f
                DBG(1)[50590]> pkg initialized
                Updating pfSense-core repository catalogue...
                DBG(1)[50590]> PkgRepo: verifying update for pfSense-core
                pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
                DBG(1)[50590]> PkgRepo: need forced update of pfSense-core
                DBG(1)[50590]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
                DBG(1)[50590]> Fetch: fetching from: https://www.firmware.netgate.com/pkg/pfSense_factory-v2_3_3_amd64-core/meta.txz with opts "i"
                meta.txz                                 : 100%  944 B     0.9kB/s    00:01    
                DBG(1)[50590]> PkgRepo: extracting meta of repo pfSense-core
                DBG(1)[50716]> PkgRepo: extracting signature of repo in a sandbox
                pkg: No trusted public keys found
                repository pfSense-core has no meta file, using default settings
                DBG(1)[50590]> Fetch: fetching from: https://www.firmware.netgate.com/pkg/pfSense_factory-v2_3_3_amd64-core/packagesite.txz with opts "i"
                packagesite.txz                          : 100%    2 KiB   2.3kB/s    00:01    
                DBG(1)[50590]> PkgRepo: extracting packagesite.yaml of repo pfSense-core
                DBG(1)[50987]> PkgRepo: extracting signature of repo in a sandbox
                pkg: No trusted public keys found
                Unable to update repository pfSense-core
                Updating pfSense repository catalogue...
                DBG(1)[50590]> PkgRepo: verifying update for pfSense
                pkg: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
                DBG(1)[50590]> PkgRepo: need forced update of pfSense
                DBG(1)[50590]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
                DBG(1)[50590]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_3_amd64-pfSense_factory-v2_3_3/meta.txz with opts "i"
                meta.txz                                 : 100%  944 B     0.9kB/s    00:01    
                DBG(1)[50590]> PkgRepo: extracting meta of repo pfSense
                DBG(1)[51205]> PkgRepo: extracting signature of repo in a sandbox
                pkg: No trusted public keys found
                repository pfSense has no meta file, using default settings
                DBG(1)[50590]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_3_amd64-pfSense_factory-v2_3_3/packagesite.txz with opts "i"
                packagesite.txz                          : 100%  119 KiB 121.8kB/s    00:01    
                DBG(1)[50590]> PkgRepo: extracting packagesite.yaml of repo pfSense
                DBG(1)[51295]> PkgRepo: extracting signature of repo in a sandbox
                pkg: No trusted public keys found
                Unable to update repository pfSense
                Error updating repositories!
                [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: 
                
                

                Just to make sure you are using the proper keys. What is the content of /usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406 ?

                Renato Botelho

                1 Reply Last reply Reply Quote 0
                • D Offline
                  dvl
                  last edited by

                  @Renato:

                  Just to make sure you are using the proper keys. What is the content of /usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406 ?

                  [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: cat /usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406
                  function: sha256
                  fingerprint: 30be9cc2e7b2b3ba1ff3b2be1795f3f0719ab9a65322695703dc7b8f004035a8
                  
                  
                  1 Reply Last reply Reply Quote 0
                  • rbgargaR Offline
                    rbgarga Developer Netgate Administrator
                    last edited by

                    @dvl:

                    @Renato:

                    Just to make sure you are using the proper keys. What is the content of /usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406 ?

                    [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: cat /usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406
                    function: sha256
                    fingerprint: 30be9cc2e7b2b3ba1ff3b2be1795f3f0719ab9a65322695703dc7b8f004035a8
                    
                    

                    Interesting, you have CE keys but your system is configured to use factory repositories. I just don't know how this key ended up there. Did you make any custom change on this system? Is it expected to be a factory system or CE?

                    Renato Botelho

                    1 Reply Last reply Reply Quote 0
                    • D Offline
                      dvl
                      last edited by

                      @Renato:

                      @dvl:

                      @Renato:

                      Just to make sure you are using the proper keys. What is the content of /usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406 ?

                      [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: cat /usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406
                      function: sha256
                      fingerprint: 30be9cc2e7b2b3ba1ff3b2be1795f3f0719ab9a65322695703dc7b8f004035a8
                      
                      

                      Interesting, you have CE keys but your system is configured to use factory repositories. I just don't know how this key ended up there. Did you make any custom change on this system? Is it expected to be a factory system or CE?

                      CE is community edition, I'm guessing.

                      pfSense was installed when I got this box (Netgate APU2).

                      Does that answer?

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

                        @dvl:

                        @Renato:

                        @dvl:

                        @Renato:

                        Just to make sure you are using the proper keys. What is the content of /usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406 ?

                        [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: cat /usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406
                        function: sha256
                        fingerprint: 30be9cc2e7b2b3ba1ff3b2be1795f3f0719ab9a65322695703dc7b8f004035a8
                        
                        

                        Interesting, you have CE keys but your system is configured to use factory repositories. I just don't know how this key ended up there. Did you make any custom change on this system? Is it expected to be a factory system or CE?

                        CE is community edition, I'm guessing.

                        pfSense was installed when I got this box (Netgate APU2).

                        Does that answer?

                        Yes, CE is community edition.

                        If you are using Netgate hardware you are supposed to be running factory. Now the question is how the CE key ended up on your system. Did you install any package manually? changed anything while testing?

                        I'll send you factory public key.

                        Renato Botelho

                        1 Reply Last reply Reply Quote 0
                        • D Offline
                          dvl
                          last edited by

                          @Renato:

                          @dvl:

                          @Renato:

                          @dvl:

                          @Renato:

                          Just to make sure you are using the proper keys. What is the content of /usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406 ?

                          [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: cat /usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406
                          function: sha256
                          fingerprint: 30be9cc2e7b2b3ba1ff3b2be1795f3f0719ab9a65322695703dc7b8f004035a8
                          
                          

                          Interesting, you have CE keys but your system is configured to use factory repositories. I just don't know how this key ended up there. Did you make any custom change on this system? Is it expected to be a factory system or CE?

                          CE is community edition, I'm guessing.

                          pfSense was installed when I got this box (Netgate APU2).

                          Does that answer?

                          Yes, CE is community edition.

                          If you are using Netgate hardware you are supposed to be running factory. Now the question is how the CE key ended up on your system. Did you install any package manually? changed anything while testing?

                          I'll send you factory public key.

                          Yes, I know I installed at least one package (bacula-client) from my own repo. I know that was September 2016 because it was during EuroBSDCon.

                          Later, I recall some pkg update which drew down from my repo.  That messed stuff up, so I went to a backup to restore service.

                          1 Reply Last reply Reply Quote 0
                          • D Offline
                            dvl
                            last edited by

                            After replacing my CE key with the factory key:

                            [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: pkg update -f
                            Updating pfSense-core repository catalogue...
                            pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
                            meta.txz                                 : 100%  944 B     0.9kB/s    00:01    
                            packagesite.txz                          : 100%    2 KiB   2.3kB/s    00:01    
                            Processing entries: 100%
                            pfSense-core repository update completed. 15 packages processed.
                            Updating pfSense repository catalogue...
                            pkg: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
                            meta.txz                                 : 100%  944 B     0.9kB/s    00:01    
                            packagesite.txz                          : 100%  119 KiB 121.8kB/s    00:01    
                            Processing entries: 100%
                            pfSense repository update completed. 439 packages processed.
                            All repositories are up to date.
                            [2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: 
                            
                            
                            1 Reply Last reply Reply Quote 0
                            • D Offline
                              dvl
                              last edited by

                              On a side note, since correcting the key, this feature on the pfSense home page now works.  It has been broken for some time.  I think we know why.

                              Version 2.3.3_1 is available.

                              1 Reply Last reply Reply Quote 0
                              • D Offline
                                dvl
                                last edited by

                                Upgraded: 2.3.4-RELEASE-p1 (amd64)

                                1 Reply Last reply Reply Quote 0
                                • D Offline
                                  dvl
                                  last edited by

                                  All green on Nagios.  Thank you for your help.  I appreciate it.

                                  1 Reply Last reply Reply Quote 0
                                  • G Offline
                                    graysam
                                    last edited by

                                    I cannot thank you enough Renato. I've been tearing my hair out for a few months with this issue before stumbling upon your suggestion here. Sure enough, /usr/local/share/pfSense/keys/pkg/revoked/.empty was there - and the moment it was removed, presto! All I wanted to do was install man :'(.

                                    This will be pinned prominently in my notebook! (Though all other systems I manage have been upgraded past 2.3.3!)

                                    Cheers,

                                    Sam.

                                    @Renato:

                                    It's exactly what I suspected. There is a bug in pkg that causes this crash. You can see details here:

                                    https://github.com/freebsd/pkg/pull/1586

                                    We already fixed it in pfSense before submit the patch to upstream, and based on truss output we can see:

                                    The presence of the empty file /usr/local/share/pfSense/keys/pkg/revoked/.empty is the cause. I suspect there is a /usr/local/share/pfSense/keys/pkg/trusted/.empty file too. Just remove them and it will work as expected. As soon as you update pkg to latest version bug will be fixed.

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