PfSense Repository "broken"



  • there is no ip for pkg.pfsense.org.
    I have checked several dns servers, none gives an ip.



  • It's not supposed to



  • @FuriousRage:

    there is no ip for pkg.pfsense.org.
    I have checked several dns servers, none gives an ip.

    Question already treated several times.
    It starts with "pkg.pfsense.org" hasn't no A records.
    It has SRV records, etc etc  ;)



  • @Gertjan:

    @FuriousRage:

    there is no ip for pkg.pfsense.org.
    I have checked several dns servers, none gives an ip.

    Question already treated several times.
    It starts with "pkg.pfsense.org" hasn't no A records.
    It has SRV records, etc etc  ;)

    And because of this, i cannot even view my local installed packages.

    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
    pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-core/meta.txz: No address record
    repository pfSense-core has no meta file, using default settings
    pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-core/packagesite.txz: No address record
    Unable to update repository pfSense-core
    Updating pfSense repository catalogue...
    pkg: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
    pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/meta.txz: No address record
    repository pfSense has no meta file, using default settings
    pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/packagesite.txz: No address record
    Unable to update repository pfSense
    Error updating repositories!
    

  • Rebel Alliance Global Moderator

    "access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory"

    This is your issue - has zero to do with pkg.pfsense.org being a SRV..

    You seem to have lots of issues going on - failure to be able to resolve is just one of them..

    dig  _https._tcp.pkg.pfsense.org SRV

    ; <<>> DiG 9.11.2 <<>> _https._tcp.pkg.pfsense.org SRV
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7146
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 1

    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;_https._tcp.pkg.pfsense.org.  IN      SRV

    ;; ANSWER SECTION:
    _https._tcp.pkg.pfsense.org. 3588 IN    SRV    10 10 443 files01.netgate.com.
    _https._tcp.pkg.pfsense.org. 3588 IN    SRV    10 10 443 files00.netgate.com.

    ;; AUTHORITY SECTION:
    pfsense.org.            1014    IN      NS      ns1.netgate.com.
    pfsense.org.            1014    IN      NS      ns2.netgate.com.

    ;; Query time: 3 msec
    ;; SERVER: 192.168.3.10#53(192.168.3.10)
    ;; WHEN: Sun Aug 06 05:48:34 Central Daylight Time 2017
    ;; MSG SIZE  rcvd: 181



  • I use what ever is the installed DNS Resolver in pfSense 2.3.x.
    Its setup to resolve with authorative nameservers, meaning i dont have a dns server in settings.
    This is a new installation with the usb key version, installed it on saturday.

    Cant the pfSense package manager get the ip it needs to show packages?

    What i see, its not trying to resolve _https._tcp.pkg.pfsense.org but pkg.pfsense.org

    @johnpoz:

    "access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory"

    This is your issue - has zero to do with pkg.pfsense.org being a SRV..

    You seem to have lots of issues going on - failure to be able to resolve is just one of them..

    dig  _https._tcp.pkg.pfsense.org SRV

    ; <<>> DiG 9.11.2 <<>> _https._tcp.pkg.pfsense.org SRV
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7146
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 1

    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;_https._tcp.pkg.pfsense.org.  IN      SRV

    ;; ANSWER SECTION:
    _https._tcp.pkg.pfsense.org. 3588 IN    SRV    10 10 443 files01.netgate.com.
    _https._tcp.pkg.pfsense.org. 3588 IN    SRV    10 10 443 files00.netgate.com.

    ;; AUTHORITY SECTION:
    pfsense.org.            1014    IN      NS      ns1.netgate.com.
    pfsense.org.            1014    IN      NS      ns2.netgate.com.

    ;; Query time: 3 msec
    ;; SERVER: 192.168.3.10#53(192.168.3.10)
    ;; WHEN: Sun Aug 06 05:48:34 Central Daylight Time 2017
    ;; MSG SIZE  rcvd: 181



  • No expert, but isn't this error :-

    pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
    

    what you need to sort out first, as john has already said?



  • Suddenly….
    pkg.pfsense.org is not resolved.
    repo file (/var/db/pkg/repo-pfSense.sqlite) does not exists

    No configuration changes were made in network, DNS resolution works (includ. over TCP) works properly.

    Updating pfSense-core repository catalogue...
    pfSense-core repository is up to date.
    Updating pfSense repository catalogue...
    pkg: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
    pkg: https://pkg.pfsense.org/pfSense_v2_4_0_amd64-pfSense_devel/meta.txz: Not Found
    repository pfSense has no meta file, using default settings
    pkg: https://pkg.pfsense.org/pfSense_v2_4_0_amd64-pfSense_devel/packagesite.txz: Not Found
    Unable to update repository pfSense
    Error updating repositories!
    
    


  • As seen by others.

    Did you read https://forum.pfsense.org/index.php?topic=134764.msg738671#msg738671 and all other threads mentioned ?



  • I had a similar issue a few days ago.

    I solved my isue here
    https://forum.pfsense.org/index.php?topic=135618.msg742504#msg742504

    /Bingo



  • I had the same issue just now on a new pfsense VM, seems switching back to the stable repo fixed it, so currently development repo is broken?