22.01.a.20211203.0600 update failing - packagesite URL error...pkg+:// implies SRV mirror type

luckman212 · Dec 3, 2021, 1:12 PM

Not sure if this is a temporary DNS error or something but, this morning I checked for updates on my 22.01 test box (6100) which currently has 22.01.a.20211130.0600 installed, and get this:

Dropped to the console to check:

[22.01-DEVELOPMENT][root@pfSense.home.arpa]/root: pkg update
Updating pfSense-core repository catalogue...
pkg: packagesite URL error for pkg+https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-core/meta.conf -- pkg+:// implies SRV mirror type
pkg: packagesite URL error for pkg+https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-core/meta.txz -- pkg+:// implies SRV mirror type
repository pfSense-core has no meta file, using default settings
pkg: packagesite URL error for pkg+https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-core/packagesite.pkg -- pkg+:// implies SRV mirror type
pkg: packagesite URL error for pkg+https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-core/packagesite.txz -- pkg+:// implies SRV mirror type
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: packagesite URL error for pkg+https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-pfSense_plus_devel/meta.conf -- pkg+:// implies SRV mirror type
pkg: packagesite URL error for pkg+https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-pfSense_plus_devel/meta.txz -- pkg+:// implies SRV mirror type
repository pfSense has no meta file, using default settings
pkg: packagesite URL error for pkg+https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-pfSense_plus_devel/packagesite.pkg -- pkg+:// implies SRV mirror type
pkg: packagesite URL error for pkg+https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-pfSense_plus_devel/packagesite.txz -- pkg+:// implies SRV mirror type
Unable to update repository pfSense
Error updating repositories!

(pkg-static update -f gives the same output)

Here's pkg -vv

[22.01-DEVELOPMENT][root@pfSense.home.arpa]/root: pkg -vv
Version                 : 1.17.2
PKG_DBDIR = "/var/db/pkg";
PKG_CACHEDIR = "/var/cache/pkg";
PORTSDIR = "/usr/ports";
INDEXDIR = "";
INDEXFILE = "INDEX-12";
HANDLE_RC_SCRIPTS = false;
DEFAULT_ALWAYS_YES = false;
ASSUME_ALWAYS_YES = false;
REPOS_DIR [
    "/etc/pkg/",
    "/usr/local/etc/pkg/repos/",
]
PLIST_KEYWORDS_DIR = "";
SYSLOG = true;
ABI = "FreeBSD:12:amd64";
ALTABI = "freebsd:12:x86:64";
DEVELOPER_MODE = false;
VULNXML_SITE = "http://vuxml.freebsd.org/freebsd/vuln.xml.xz";
FETCH_RETRY = 3;
PKG_PLUGINS_DIR = "/usr/local/lib/pkg/";
PKG_ENABLE_PLUGINS = true;
PLUGINS [
]
DEBUG_SCRIPTS = false;
PLUGINS_CONF_DIR = "/usr/local/etc/pkg/";
PERMISSIVE = false;
REPO_AUTOUPDATE = true;
NAMESERVER = "";
HTTP_USER_AGENT = "pkg/1.17.2";
EVENT_PIPE = "";
FETCH_TIMEOUT = 30;
UNSET_TIMESTAMP = false;
SSH_RESTRICT_DIR = "";
PKG_ENV {
}
PKG_SSH_ARGS = "";
DEBUG_LEVEL = 0;
ALIAS {
}
CUDF_SOLVER = "";
SAT_SOLVER = "";
RUN_SCRIPTS = true;
CASE_SENSITIVE_MATCH = false;
LOCK_WAIT = 1;
LOCK_RETRIES = 5;
SQLITE_PROFILE = false;
WORKERS_COUNT = 0;
READ_LOCK = false;
PLIST_ACCEPT_DIRECTORIES = false;
IP_VERSION = 0;
AUTOMERGE = true;
VERSION_SOURCE = "";
CONSERVATIVE_UPGRADE = true;
PKG_CREATE_VERBOSE = false;
AUTOCLEAN = false;
DOT_FILE = "";
REPOSITORIES {
}
VALID_URL_SCHEME [
    "pkg+http",
    "pkg+https",
    "https",
    "http",
    "file",
    "ssh",
    "ftp",
    "ftps",
    "pkg+ssh",
    "pkg+ftp",
    "pkg+ftps",
]
ALLOW_BASE_SHLIBS = false;
WARN_SIZE_LIMIT = 1048576;
METALOG = "";
OSVERSION = 1202508;
IGNORE_OSVERSION = false;
BACKUP_LIBRARIES = false;
BACKUP_LIBRARY_PATH = "/usr/local/lib/compat/pkg";
PKG_TRIGGERS_DIR = "/usr/local/share/pkg/triggers";
PKG_TRIGGERS_ENABLE = true;
AUDIT_IGNORE_GLOB [
]
AUDIT_IGNORE_REGEX [
    "NULL",
]
COMPRESSION_LEVEL = -1;
ARCHIVE_SYMLINK = false;
REPO_ACCEPT_LEGACY_PKG = false;


Repositories:
  pfSense-core: {
    url             : "pkg+https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-core",
    enabled         : yes,
    priority        : 0,
    fingerprints    : "/usr/local/share/pfSense/keys/pkg"
  }
  pfSense: {
    url             : "pkg+https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-pfSense_plus_devel",
    enabled         : yes,
    priority        : 0,
    fingerprints    : "/usr/local/share/pfSense/keys/pkg"
  }

Tried switching branches to stable and back—didn't work either.

Saw this mentioned in another thread so I checked DNS from the unit:

# dig _http._tcp.pkg.pfsense.org SRV

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

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

;; ANSWER SECTION:
_http._tcp.pkg.pfsense.org. 60	IN	SRV	10 10 80 files01.netgate.com.
_http._tcp.pkg.pfsense.org. 60	IN	SRV	10 10 80 files00.netgate.com.

;; Query time: 174 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Dec 03 13:11:55 UTC 2021
;; MSG SIZE  rcvd: 133

Any ideas?

NRgia · Dec 3, 2021, 2:18 PM

@luckman212
It's not just you, I'm on CE 2.6.0-development and I see the same as you.

It's good that you reported this though.

luckman212 · Dec 3, 2021, 4:12 PM

@nrgia The fix is in https://forum.netgate.com/topic/168280/are-the-repos-down/

NRgia · Dec 3, 2021, 5:10 PM

@luckman212
Thanks,
I fixed the issue with what @stephenw10 posted