Unable to retrieve package information.

[hamed_forum]

2.4.4-RELEASE-p3 on this version i cant update to 2.5
what must do ?how to can find where is problm?

Version 2.4.4-RELEASE-p3 (amd64)
built on Wed May 15 18:53:44 EDT 2019
FreeBSD 11.2-RELEASE-p10
The system is on the latest version.
and install package
Unable to retrieve package information.

[viragomann]

Is pfSense able to resolve public host names?
You can check that with Diagnostic > DNS lookup.

[johnpoz]

https://docs.netgate.com/pfsense/en/latest/install/upgrade-troubleshooting.html

[hamed_forum]

@viragomann yes it can
Hostname
google.com
Results
Result Record type
216.58.208.78 A
2a00:1450:4018:802::200e AAAA
Timings
Name server Query time
8.8.8.8 48 msec
5.239.242.5 14 msec
5.239.242.3 15 msec
4.2.2.4 114 msec

host -t srv _https._tcp.pkg.pfsense.org
_https._tcp.pkg.pfsense.org has SRV record 10 10 443 files00.netgate.com.
_https._tcp.pkg.pfsense.org has SRV record 10 10 443 files01.netgate.com.

host files01.netgate.com.
files01.netgate.com has address 162.208.119.40
files01.netgate.com has IPv6 address 2607:ee80:10::119:40
/root: host files00.netgate.com.
files00.netgate.com has address 162.208.119.41
files00.netgate.com has IPv6 address 2607:ee80:10::119:41

root: curl --output /dev/null --silent --head --fail "https://files00.netgate.com/pfSense_v2_4_4_amd64-core/meta.txz"
root: echo $?
0

pkg upgrade
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

set type=srv
_https._tcp.pkg.pfsense.org
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
_https._tcp.pkg.pfsense.org service = 10 10 443 files00.netgate.com.
_https._tcp.pkg.pfsense.org service = 10 10 443 files01.netgate.com.

Authoritative answers can be found from:

pkg upgrade
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: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-core/meta.txz: Operation timed out
repository pfSense-core has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-core/packagesite.txz: Operation timed out
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: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-pfSense_v2_4_4/meta.txz: Operation timed out
repository pfSense has no meta file, using default settings

[hamed_forum]

@hamed_forum ]/conf: pkg-static update -f
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

pkg-static: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-core/meta.txz: Operation timed out
repository pfSense-core has no meta file, using default settings
pkg-static: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-core/packagesite.txz: Operation timed out
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
pkg-static: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-pfSense_v2_4_4/meta.txz: Operation timed out
repository pfSense has no meta file, using default settings
pkg-static: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-pfSense_v2_4_4/packagesite.txz: Operation timed out
Unable to update repository pfSense
Error updating repositories!

[hamed_forum]

@johnpoz plz help me tanks

[pat2634]

@hamed_forum I'm encountering the same issue also. have you figured this out yet?

[Gertjan]

@pat2634 said in Unable to retrieve package information.:

have you figured this out yet?

Was resolved last 15th august.

I checked just now, today, September 7th, 2h41 PM :

Enter an option: 13

>>> Creating automatic rollback boot environment... done.
>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: . done
Processing entries: .. done
pfSense-core repository update completed. 14 packages processed.
Updating pfSense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
pfSense repository update completed. 542 packages processed.
All repositories are up to date.
>>> Setting vital flag on pkg... done.
Your packages are up to date

It's true, once in a while, there is actually an issue with the Netgate's packet and update servers. So, not your side, but their side.
When that happens, there is no need to do anything, as it would impact us all.
Among the 100 000+ pfSEnse users, there will be always one who grabs the phone and call jimp, stephenw10 or who ever work at Netgate, and it will get fixed moments later.

Most often, like
99 %, it's a local fckd up DNS. Call your admin ;)
0,9 % : your ISP is definitely not expensive enough.
0,09 % : the peering to Netgate went dark (peering == the connection from your ISP to the Netgate server farm)
0,001 : That will be the Netgate servers ....like this (15/08) time.

And yeah, these things happen.
Even Facebook disappeared from the Internet, no so long ago.