[solved] pfSense + 25.07.1 check_upgrade: "Updating repositories metadata" returned error code 1 @ 2025-12-10 07:23:47
-
25.07.1-RELEASE (amd64)
built on Fri Aug 15 20:42:00 CEST 2025
FreeBSD 15.0-CURRENTI have an error on every reboot:
check_upgrade: "Updating repositories metadata" returned error code 1 @ 2025-12-10 07:23:47if i run
pkg -d updatei get this output
pkg -d update DBG(1)[89918]> pkg initialized Updating pfSense-core repository catalogue... DBG(1)[89918]> PkgRepo: verifying update for pfSense-core DBG(1)[89918]> Pkgrepo, begin update of '/var/db/pkg/repos/pfSense-core/db' DBG(1)[89918]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v25_07_1_amd64-core/meta.conf DBG(1)[89918]> curl_open DBG(1)[89918]> Fetch: fetcher used: pkg+https DBG(1)[89918]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v25_07_1_amd64-core/meta.conf DBG(1)[89918]> CURL> attempting to fetch from , left retry 3 * Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults * Host pfsense-plus-pkg01.atx.netgate.com:443 was resolved. * IPv6: 2610:160:11:18::209 * IPv4: 208.123.73.209 * Trying 208.123.73.209:443... * Connected to pfsense-plus-pkg01.atx.netgate.com (208.123.73.209) port 443 * ALPN: curl offers http/1.1 * CAfile: /etc/ssl/netgate-ca.pem * CApath: /etc/ssl/certs/ * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / X25519 / RSASSA-PSS * ALPN: server accepted http/1.1 * Server certificate: * subject: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=pfSense Plus; CN=pfsense-plus-pkg01.atx.netgate.com * start date: Mar 15 20:23:37 2022 GMT * expire date: Feb 19 20:23:37 2122 GMT * common name: pfsense-plus-pkg01.atx.netgate.com (matched) * issuer: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=Netgate CA; CN=Netgate CA * SSL certificate verify ok. * Certificate level 0: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 1: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption * using HTTP/1.x > GET /pfSense_plus-v25_07_1_amd64-core/meta.conf HTTP/1.1 Host: pfsense-plus-pkg01.atx.netgate.com User-Agent: pkg/1.21.3 Accept: */* If-Modified-Since: Fri, 15 Aug 2025 21:11:56 GMT * Request completely sent off < HTTP/1.1 304 Not Modified < Server: nginx < Date: Wed, 10 Dec 2025 06:32:43 GMT < Last-Modified: Fri, 15 Aug 2025 21:11:56 GMT < Connection: keep-alive < ETag: "689fa29c-b3" < * Connection #0 to host pfsense-plus-pkg01.atx.netgate.com left intact DBG(1)[89918]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v25_07_1_amd64-core/data.pkg DBG(1)[89918]> curl_open DBG(1)[89918]> Fetch: fetcher used: pkg+https DBG(1)[89918]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v25_07_1_amd64-core/data.pkg DBG(1)[89918]> CURL> attempting to fetch from , left retry 3 * Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults * Found bundle for host: 0xbec15e268a0 [serially] * Re-using existing connection with host pfsense-plus-pkg01.atx.netgate.com > GET /pfSense_plus-v25_07_1_amd64-core/data.pkg HTTP/1.1 Host: pfsense-plus-pkg01.atx.netgate.com User-Agent: pkg/1.21.3 Accept: */* If-Modified-Since: Fri, 15 Aug 2025 21:11:56 GMT * Request completely sent off < HTTP/1.1 304 Not Modified < Server: nginx < Date: Wed, 10 Dec 2025 06:32:43 GMT < Last-Modified: Fri, 15 Aug 2025 21:11:56 GMT < Connection: keep-alive < ETag: "689fa29c-6be" < * Connection #0 to host pfsense-plus-pkg01.atx.netgate.com left intact pfSense-core repository is up to date. Updating pfSense repository catalogue... DBG(1)[89918]> PkgRepo: verifying update for pfSense DBG(1)[89918]> Pkgrepo, begin update of '/var/db/pkg/repos/pfSense/db' DBG(1)[89918]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v25_07_1_amd64-pfSense_plus_v25_07_1/meta.conf DBG(1)[89918]> curl_open DBG(1)[89918]> Fetch: fetcher used: pkg+https DBG(1)[89918]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v25_07_1_amd64-pfSense_plus_v25_07_1/meta.conf DBG(1)[89918]> CURL> attempting to fetch from , left retry 3 * Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults * Host pfsense-plus-pkg01.atx.netgate.com:443 was resolved. * IPv6: 2610:160:11:18::209 * IPv4: 208.123.73.209 * Trying 208.123.73.209:443... * Connected to pfsense-plus-pkg01.atx.netgate.com (208.123.73.209) port 443 * ALPN: curl offers http/1.1 * CAfile: /etc/ssl/netgate-ca.pem * CApath: /etc/ssl/certs/ * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / X25519 / RSASSA-PSS * ALPN: server accepted http/1.1 * Server certificate: * subject: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=pfSense Plus; CN=pfsense-plus-pkg01.atx.netgate.com * start date: Mar 15 20:23:37 2022 GMT * expire date: Feb 19 20:23:37 2122 GMT * common name: pfsense-plus-pkg01.atx.netgate.com (matched) * issuer: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=Netgate CA; CN=Netgate CA * SSL certificate verify ok. * Certificate level 0: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 1: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption * using HTTP/1.x > GET /pfSense_plus-v25_07_1_amd64-pfSense_plus_v25_07_1/meta.conf HTTP/1.1 Host: pfsense-plus-pkg01.atx.netgate.com User-Agent: pkg/1.21.3 Accept: */* If-Modified-Since: Mon, 01 Dec 2025 19:15:19 GMT * Request completely sent off < HTTP/1.1 304 Not Modified < Server: nginx < Date: Wed, 10 Dec 2025 06:32:44 GMT < Last-Modified: Mon, 01 Dec 2025 19:15:19 GMT < Connection: keep-alive < ETag: "692de947-b3" < * Connection #0 to host pfsense-plus-pkg01.atx.netgate.com left intact DBG(1)[89918]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v25_07_1_amd64-pfSense_plus_v25_07_1/data.pkg DBG(1)[89918]> curl_open DBG(1)[89918]> Fetch: fetcher used: pkg+https DBG(1)[89918]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v25_07_1_amd64-pfSense_plus_v25_07_1/data.pkg DBG(1)[89918]> CURL> attempting to fetch from , left retry 3 * Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults * Found bundle for host: 0xbec15f11da0 [serially] * Re-using existing connection with host pfsense-plus-pkg01.atx.netgate.com > GET /pfSense_plus-v25_07_1_amd64-pfSense_plus_v25_07_1/data.pkg HTTP/1.1 Host: pfsense-plus-pkg01.atx.netgate.com User-Agent: pkg/1.21.3 Accept: */* If-Modified-Since: Mon, 01 Dec 2025 19:15:19 GMT * Request completely sent off < HTTP/1.1 304 Not Modified < Server: nginx < Date: Wed, 10 Dec 2025 06:32:44 GMT < Last-Modified: Mon, 01 Dec 2025 19:15:19 GMT < Connection: keep-alive < ETag: "692de947-3b117" < * Connection #0 to host pfsense-plus-pkg01.atx.netgate.com left intact pfSense repository is up to date. All repositories are up to date.WAN type is pppoe IPv4
Here my DNS settings
How do i fix this error?
-
So you only see that error once at boot?
-
@stephenw10 yes i see that only on reboot, if i mark it as read it does not appear until next reboot.
-
Check the system logs. Do you see the ppp link take some time to establish? The error is generated before it comes up?
Is this something new you're seeing in 25.07.1?
-
@stephenw10 said in pfSense + 25.07.1 check_upgrade: "Updating repositories metadata" returned error code 1 @ 2025-12-10 07:23:47:
Is this something new you're seeing in 25.07.1?
Sorry for the late reply
I do not remember ever seeing that, i am on 25.07.01 since it came out, i did NO updates recently.
I also use the new if_pppoe kernel driver since i upgraded to 25.07.01
here is the log from boot to the error, maybe you can see something here
Dec 10 08:00:00 php 11624 [pfBlockerNG] Starting cron process. Dec 10 07:32:25 sshd 69452 Accepted password for root from 10.10.10.95 port 64228 ssh2 Dec 10 07:32:25 sshd 59597 Accepted keyboard-interactive/pam for root from 10.10.10.95 port 64227 ssh2 Dec 10 07:23:47 php 72398 Standard input code: New alert found: check_upgrade: "Updating repositories metadata" returned error code 1 Dec 10 07:23:23 php-cgi 78876 servicewatchdog_cron.php: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1765347803] unbound[16014:0] error: bind: address already in use [1765347803] unbound[16014:0] fatal error: could not open ports' Dec 10 07:23:10 php-cgi 21327 haproxy: started new pid:42407 Dec 10 07:23:10 php-cgi 21327 haproxy: reload old pid:13142 Dec 10 07:23:10 php_pfb 31592 [pfBlockerNG] filterlog daemon started Dec 10 07:23:10 tail_pfb 31024 [pfBlockerNG] Firewall Filter Service started Dec 10 07:23:10 lighttpd_pfb 29088 [pfBlockerNG] DNSBL Webserver started Dec 10 07:23:10 php_pfb 26833 [pfBlockerNG] filterlog daemon stopped Dec 10 07:23:10 tail_pfb 26464 [pfBlockerNG] Firewall Filter Service stopped Dec 10 07:23:10 tail_pfb 24787 [pfBlockerNG] Firewall Filter Service started Dec 10 07:23:10 lighttpd_pfb 23493 [pfBlockerNG] DNSBL Webserver stopped Dec 10 07:23:10 php_pfb 21008 [pfBlockerNG] filterlog daemon stopped Dec 10 07:23:10 tail_pfb 18977 [pfBlockerNG] Firewall Filter Service stopped Dec 10 07:23:10 php-fpm 5597 [pfBlockerNG] Restarting firewall filter daemon Dec 10 07:23:10 php_pfb 11544 [pfBlockerNG] filterlog daemon stopped Dec 10 07:23:10 tail_pfb 11091 [pfBlockerNG] Firewall Filter Service stopped Dec 10 07:23:10 check_reload_status 640 Reloading filter Dec 10 07:23:09 php 86993 lcdproc: Start client procedure. Error counter: (0) Dec 10 07:23:08 LCDd 60097 sdeclcd: cannot release IO-permission for 0x378! Dec 10 07:23:07 lighttpd_pfb 58651 [pfBlockerNG] DNSBL Webserver started Dec 10 07:23:07 lighttpd_pfb 56694 [pfBlockerNG] DNSBL Webserver stopped Dec 10 07:23:07 lighttpd_pfb 50319 [pfBlockerNG] DNSBL Webserver stopped Dec 10 07:23:07 check_reload_status 640 Syncing firewall Dec 10 07:23:06 php-fpm 5597 /rc.start_packages: Configuration Change: (system): pfBlockerNG: saving DNSBL changes Dec 10 07:23:06 php-fpm 5597 /rc.start_packages: Restarting/Starting all packages. Dec 10 07:23:05 check_reload_status 640 Reloading filter Dec 10 07:23:05 check_reload_status 640 Reloading filter Dec 10 07:23:05 check_reload_status 640 Starting packages Dec 10 07:23:05 php-fpm 601 /rc.newwanip: Netgate pfSense Plus package system has detected an IP change or dynamic WAN reconnection - ******EDITED FOR PRIVACY****** -> ******EDITED FOR PRIVACY****** - Restarting packages. Dec 10 07:23:03 php-fpm 601 /rc.newwanip: Creating rrd update script Dec 10 07:23:00 php-cgi 78876 servicewatchdog_cron.php: Service Watchdog detected service unbound stopped. Restarting unbound (DNS Resolver) Dec 10 07:22:41 php-fpm 601 /rc.newwanip: IP Address has changed, killing states on former IP Address ******EDITED FOR PRIVACY******. Dec 10 07:22:41 php-cgi 66934 haproxy: started new pid:13142 Dec 10 07:22:40 php_pfb 85065 [pfBlockerNG] filterlog daemon started Dec 10 07:22:40 php-cgi 66934 haproxy: reload old pid:30825 Dec 10 07:22:40 php_pfb 94064 [pfBlockerNG] filterlog daemon started Dec 10 07:22:40 root 97619 Bootup complete Dec 10 07:22:40 tail_pfb 92166 [pfBlockerNG] Firewall Filter Service started Dec 10 07:22:40 tail_pfb 81574 [pfBlockerNG] Firewall Filter Service started Dec 10 07:22:40 lighttpd_pfb 82502 [pfBlockerNG] DNSBL Webserver started Dec 10 07:22:40 php_pfb 79328 [pfBlockerNG] filterlog daemon stopped Dec 10 07:22:39 tail_pfb 77444 [pfBlockerNG] Firewall Filter Service stopped Dec 10 07:22:39 lighttpd_pfb 72256 [pfBlockerNG] DNSBL Webserver stopped Dec 10 07:22:39 php_pfb 70065 [pfBlockerNG] filterlog daemon stopped Dec 10 07:22:39 tail_pfb 69286 [pfBlockerNG] Firewall Filter Service stopped Dec 10 07:22:39 php 61338 /usr/local/pkg/lcdproc_client.php: dpinger: status socket /var/run/dpinger_SKYNET_VPNV4~10.0.9.1~10.0.9.1.sock not found Dec 10 07:22:39 php-fpm 56688 [pfBlockerNG] Restarting firewall filter daemon Dec 10 07:22:39 php-fpm 601 /rc.newwanip: Removing static route for monitor 1.1.1.1 and adding a new route through pppoe0 Dec 10 07:22:39 php_pfb 46339 [pfBlockerNG] filterlog daemon stopped Dec 10 07:22:39 tail_pfb 45662 [pfBlockerNG] Firewall Filter Service stopped Dec 10 07:22:39 check_reload_status 640 Reloading filter Dec 10 07:22:37 php 61338 lcdproc: Start client procedure. Error counter: (0) Dec 10 07:22:36 php-fpm 601 /rc.newwanip: rc.newwanip: on (IP address: ******EDITED FOR PRIVACY******) (interface: PRIVADOVPN[opt6]) (real interface: ovpnc1). Dec 10 07:22:36 php-fpm 601 /rc.newwanip: rc.newwanip: Info: starting on ovpnc1. Dec 10 07:22:35 LCDd 88985 sdeclcd: cannot release IO-permission for 0x378! Dec 10 07:22:35 kernel ovpnc1: link state changed to UP Dec 10 07:22:35 check_reload_status 640 rc.newwanip starting ovpnc1 Dec 10 07:22:35 lighttpd_pfb 40793 [pfBlockerNG] DNSBL Webserver started Dec 10 07:22:35 lighttpd_pfb 37473 [pfBlockerNG] DNSBL Webserver stopped Dec 10 07:22:35 lighttpd_pfb 28487 [pfBlockerNG] DNSBL Webserver stopped Dec 10 07:22:35 check_reload_status 640 Syncing firewall Dec 10 07:22:34 php-fpm 56688 /rc.start_packages: Configuration Change: (system): pfBlockerNG: saving DNSBL changes Dec 10 07:22:34 php-fpm 56688 /rc.start_packages: Restarting/Starting all packages. Dec 10 07:22:33 kernel sonewconn: pcb 0xfffff8000a79c780 (local:/var/etc/openvpn/client1/sock): Listen queue overflow: 2 already in queue awaiting acceptance (1 occurrences), euid 0, rgid 0, jail 0 Dec 10 07:22:33 php-cgi 687 rc.bootup: API to Telegram did not return data in expected format! Dec 10 07:22:25 php-fpm 52315 /index.php: Successful login for user 'horst' from: 10.10.10.95 (Local Database) Dec 10 07:22:15 check_reload_status 640 Reloading filter Dec 10 07:22:15 sshguard 47452 Now monitoring attacks. Dec 10 07:22:15 syslogd kernel boot file is /boot/kernel/kernel Dec 10 07:22:15 syslogd exiting on signal 15 Dec 10 07:22:13 root 99579 /etc/rc.d/hostid: WARNING: hostid: unable to figure out a UUID from DMI data, generating a new one Dec 10 07:22:13 sshguard 79316 Exiting on signal. Dec 10 07:22:12 kernel done. Dec 10 07:22:12 check_reload_status 640 Reloading filter Dec 10 07:22:12 php-cgi 687 rc.bootup: miniupnpd: Starting service on interface: opt4, opt5 Dec 10 07:22:12 php-cgi 687 rc.bootup: Creating rrd update script Dec 10 07:22:12 php-fpm 52315 /rc.newwanip: Removing static route for monitor 1.1.1.1 and adding a new route through pppoe0 Dec 10 07:22:08 php-fpm 600 /rc.dyndns.update: phpDynDNS (skynet.******EDITED FOR PRIVACY******): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Dec 10 07:22:08 kernel .done. Dec 10 07:22:08 php-cgi 687 rc.bootup: The command '/usr/local/sbin/strongswanrc stop' returned exit code '1', the output was 'strongswan not running? (check /var/run/daemon-charon.pid).' Dec 10 07:22:08 kernel done. Dec 10 07:22:07 check_reload_status 640 Updating all dyndns Dec 10 07:22:07 php-cgi 2865 haproxy: startup error output!: [NOTICE] (26783) : config : config: Can't open global server state file '/tmp/haproxy_server_state': No such file or directory Dec 10 07:22:07 php-cgi 2865 haproxy: started new pid:30825 Dec 10 07:22:07 php_pfb 20886 [pfBlockerNG] filterlog daemon started Dec 10 07:22:07 php-cgi 2865 haproxy: starting old pid:none Dec 10 07:22:07 tail_pfb 20451 [pfBlockerNG] Firewall Filter Service started Dec 10 07:22:07 kernel done. Dec 10 07:22:07 lighttpd_pfb 15487 [pfBlockerNG] DNSBL Webserver started Dec 10 07:22:07 lighttpd_pfb 12804 [pfBlockerNG] DNSBL Webserver started Dec 10 07:22:07 lighttpd_pfb 9314 [pfBlockerNG] DNSBL Webserver stopped Dec 10 07:22:07 php_pfb 8196 [pfBlockerNG] filterlog daemon stopped Dec 10 07:22:07 tail_pfb 7066 [pfBlockerNG] Firewall Filter Service stopped Dec 10 07:22:07 lighttpd_pfb 1364 [pfBlockerNG] DNSBL Webserver stopped Dec 10 07:22:07 php-fpm 600 /rc.start_packages: [pfBlockerNG] Sync terminated during boot process. Dec 10 07:22:07 php 89090 lcdproc: Start client procedure. Error counter: (0) Dec 10 07:22:07 check_reload_status 640 Syncing firewall Dec 10 07:22:07 php-fpm 600 /rc.start_packages: Configuration Change: (system): pfBlockerNG: saving DNSBL changes Dec 10 07:22:06 php-fpm 600 /rc.start_packages: Restarting/Starting all packages. Dec 10 07:22:06 php-cgi 687 rc.bootup: NTPD is starting up. Dec 10 07:22:06 php-cgi 687 rc.bootup: The command '/usr/bin/timeout -k 45 30 /usr/local/sbin/ntpd -g -q -c /dev/null 216.239.35.0 216.239.35.4 216.239.35.8 216.239.35.12' returned exit code '124', the output was '10 Dec 07:21:36 ntpd[67766]: ntpd 4.2.8p18@1.4062-o Fri Jun 20 16:15:52 UTC 2025 (1): Starting 10 Dec 07:21:36 ntpd[67766]: Command line: /usr/local/sbin/ntpd -g -q -c /dev/null 216.239.35.0 216.239.35.4 216.239.35.8 216.239.35.12 10 Dec 07:21:36 ntpd[67766]: ---------------------------------------------------- 10 Dec 07:21:36 ntpd[67766]: ntp-4 is maintained by Network Time Foundation, 10 Dec 07:21:36 ntpd[67766]: Inc. (NTF), a non-profit 501(c)(3) public-benefit 10 Dec 07:21:36 ntpd[67766]: corporation. Support and training for ntp-4 are 10 Dec 07:21:36 ntpd[67766]: available at https://www.nwtime.org/support 10 Dec 07:21:36 ntpd[67766]: ---------------------------------------------------- 10 Dec 07:21:36 ntpd[67766]: proto: precision = 0.078 usec (-24) 10 Dec 07:21:36 ntpd[67766]: line 0 column 0 syntax error 10 Dec 07:21:36 ntpd[67766]: basedate set to 2025-06-08 10 Dec 07:21:36 ntpd[67766]: gps base set to 2025-06-08 (week 2370) 10 Dec 07:21:36 ntpd[67766]: Listen and drop on 0 v6wildcard [::]:123 10 Dec 07:21:36 ntpd[67766]: Listen and drop on 1 v4wildcard 0.0.0.0:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 2 igb0 [fe80::21a:8cff:fe18:9cba%1]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 3 igb0 10.10.10.1:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 4 igb0 10.10.10.253:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 5 igb1 [fe80::21a:8cff:fe18:9cbb%2]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 6 igb2 [fe80::21a:8cff:fe18:9cbc%3]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 7 igb2 10.10.20.1:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 8 igb3 [fe80::21a:8cff:fe18:9cbd%4]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 9 igb3 172.20.20.1:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 10 igb4 10.10.70.1:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 11 igb4 10.10.70.253:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 12 igb5 [fe80::21a:8cff:fe18:9cbf%6]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 13 igb5 192.168.178.2:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 14 igb5 192.168.178.100:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 15 igb6 [fe80::21a:8cff:fe18:9cc0%7]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 16 igb6 10.10.80.1:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 17 igb7 [fe80::21a:8cff:fe18:9cc1%8]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 18 igb7 10.10.99.1:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 19 lo0 [::1]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 20 lo0 [fe80::1%10]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 21 lo0 127.0.0.1:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 22 lo0 10.0.0.1:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 23 ovpns2 [fe80::21a:8cff:fe18:9cba%14]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 24 ovpns2 10.0.9.1:123 10 Dec 07:21:36 ntpd[67766]: Listening on routing socket on fd #45 for interface updates 10 Dec 07:21:41 ntpd[67766]: Listen normally on 25 igb4 [fe80::21a:8cff:fe18:9cbe%5]:123 10 Dec 07:21:41 ntpd[67766]: Listen normally on 26 pppoe0 [fe80::21a:8cff:fe18:9cba%13]:123 10 Dec 07:21:41 ntpd[67766]: Listen normally on 27 pppoe0 ******EDITED FOR PRIVACY******:123 10 Dec 07:21:41 ntpd[67766]: 216.239.35.12 local addr <null> -> ******EDITED FOR PRIVACY****** 10 Dec 07:21:41 ntpd[67766]: 216.239.35.8 local addr <null> -> ******EDITED FOR PRIVACY****** 10 Dec 07:21:41 ntpd[67766]: 216.239.35.4 local addr <null> -> ******EDITED FOR PRIVACY****** 10 Dec 07:21:41 ntpd[67766]: 216.239.35.0 local addr <null> -> ******EDITED FOR PRIVACY****** 10 Dec 07:22:06 ntpd[67766]: ntpd exiting on signal 15 (Terminated)' Dec 10 07:22:05 check_reload_status 640 Starting packages Dec 10 07:22:05 php-fpm 601 /rc.newwanip: Netgate pfSense Plus package system has detected an IP change or dynamic WAN reconnection - ******EDITED FOR PRIVACY****** -> ******EDITED FOR PRIVACY****** - Restarting packages. Dec 10 07:22:04 php-fpm 52315 /rc.newwanip: rc.newwanip: on (IP address: 10.0.9.1) (interface: SKYNET[opt8]) (real interface: ovpns2). Dec 10 07:22:04 php-fpm 52315 /rc.newwanip: rc.newwanip: Info: starting on ovpns2. Dec 10 07:22:03 php-fpm 601 /rc.newwanip: Creating rrd update script Dec 10 07:22:03 php-fpm 601 OpenVPN PID written: 97785 Dec 10 07:22:03 kernel ovpns2: link state changed to UP Dec 10 07:22:03 check_reload_status 640 rc.newwanip starting ovpns2 Dec 10 07:22:03 php-fpm 601 OpenVPN terminate old pid: 79109 Dec 10 07:22:03 php-fpm 601 OpenVPN PID written: 94919 Dec 10 07:22:03 kernel ovpns2: link state changed to DOWN Dec 10 07:22:03 check_reload_status 640 Reloading filter Dec 10 07:22:01 php-fpm 601 OpenVPN terminate old pid: 77521 Dec 10 07:22:01 php-fpm 601 /rc.newwanip: Resyncing OpenVPN instances for interface WAN. Dec 10 07:22:00 php-fpm 601 /rc.newwanip: phpDynDNS (skynet.******EDITED FOR PRIVACY******): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Dec 10 07:22:00 php-fpm 601 /rc.newwanip: sync unbound done. Dec 10 07:21:48 php-fpm 601 /rc.newwanip: Removing static route for monitor 1.1.1.1 and adding a new route through pppoe0 Dec 10 07:21:48 php-fpm 601 /rc.newwanip: GW States: Killing states for down gateway: WAN_PPPOE, ******EDITED FOR PRIVACY****** Dec 10 07:21:39 php-fpm 601 /rc.newwanip: rc.newwanip: on (IP address: ******EDITED FOR PRIVACY******) (interface: WAN[wan]) (real interface: pppoe0). Dec 10 07:21:39 php-fpm 601 /rc.newwanip: rc.newwanip: Info: starting on pppoe0. Dec 10 07:21:38 php-fpm 600 /rc.linkup: Ignoring link event during boot sequence. Dec 10 07:21:38 php-fpm 601 /rc.linkup: Ignoring link event during boot sequence. Dec 10 07:21:37 check_reload_status 640 rc.newwanip starting pppoe0 Dec 10 07:21:37 php-fpm 601 /rc.linkup: Ignoring link event during boot sequence. Dec 10 07:21:37 php-fpm 601 /rc.linkup: Ignoring link event during boot sequence. Dec 10 07:21:37 php-fpm 601 /rc.linkup: Ignoring link event during boot sequence. Dec 10 07:21:37 kernel pppoe0: link state changed to UP Dec 10 07:21:37 kernel igb6: link state changed to UP Dec 10 07:21:37 check_reload_status 640 Linkup starting igb6 Dec 10 07:21:37 php-fpm 601 /rc.linkup: Ignoring link event during boot sequence. Dec 10 07:21:37 check_reload_status 640 Linkup starting igb4 -
Remove / disable that one.
I've never seen unbound (or nginx, etc) crashing on me. If unbound crashes for you, it would do so for me, as we all share the same binary , every bit is identical (ok, risc users have other binaries).
If your RAM is bad ... servicewatchdog won't make it any better. Drive issues : same thing. Your unbound settings are wrong (fro example : you tell it to use more RAM then your system has : same thing, use the default settings and case closed. Etc.
pfSense, if it restarts a process, like unbound, it restarts it.
If you find your pfSense with a dead DNS : unbound has stopped or core dumped, then the reason why that happened has to be found, and solved. Using "servicewatchdog" is not a solution, and actually makes the problem 'worse'.Your logs clearly show that unboud was executed a controlled, ordered stop, to be started again.
During the little laps of time it wasn't running, servicewatchdog detected this, and starts unbound.
Or, another instance it was already in the process of starting.
This creates race conditions, way bigger RAM usage, failed access to files that are locked by the other instance etc etc.edit :
This :LCDd 88985 sdeclcd: cannot release IO-permission for 0x378!
I don't know who LCDd is - a LCD display driver ?
Disable it for the moment, as php isn't happy about it. -
@Gertjan said in pfSense + 25.07.1 check_upgrade: "Updating repositories metadata" returned error code 1 @ 2025-12-10 07:23:47:
I don't know who LCDd is - a LCD display driver ?
yes it is a LCD display driver for the integrated LCD, it comes with the package LDCproc
I deactivated the unbound watchdog and this seems to have resolved the problem
@Gertjan Thank you for your time and the solution!
-
Yup it's incorrectly restarting Unbound just when the update check is trying to resolve the repos.
And, yes, the service watchdog is almost always the wrong solution to issues like this.
LCDproc should be fine even with the error when it starts.
-
@stephenw10 thank you.
I have no idea why i got the unbound watchdog activated, This install is quite old and i just upgraded inplace to the new versions.
I am pretty sure i saw it on a video or something when i first installed pfsense
-
Not related, and more an optical issue :
The 'one shot ntpd call', probably to pre init the system time, is a bit messy :@HorstZimmermann said in [solved] pfSense + 25.07.1 check_upgrade: "Updating repositories metadata" returned error code 1 @ 2025-12-10 07:23:47:
Dec 10 07:22:06 php-cgi 687 rc.bootup: The command '/usr/bin/timeout -k 45 30 /usr/local/sbin/ntpd -g -q -c /dev/null 216.239.35.0 216.239.35.4 216.239.35.8 216.239.35.12' returned exit code '124', the output was '10 Dec 07:21:36 ntpd[67766]: ntpd 4.2.8p18@1.4062-o Fri Jun 20 16:15:52 UTC 2025 (1): Starting 10 Dec 07:21:36 ntpd[67766]: Command line: /usr/local/sbin/ntpd -g -q -c /dev/null 216.239.35.0 216.239.35.4 216.239.35.8 216.239.35.12 10 Dec 07:21:36 ntpd[67766]: ---------------------------------------------------- 10 Dec 07:21:36 ntpd[67766]: ntp-4 is maintained by Network Time Foundation, 10 Dec 07:21:36 ntpd[67766]: Inc. (NTF), a non-profit 501(c)(3) public-benefit 10 Dec 07:21:36 ntpd[67766]: corporation. Support and training for ntp-4 are 10 Dec 07:21:36 ntpd[67766]: available at https://www.nwtime.org/support 10 Dec 07:21:36 ntpd[67766]: ---------------------------------------------------- 10 Dec 07:21:36 ntpd[67766]: proto: precision = 0.078 usec (-24) 10 Dec 07:21:36 ntpd[67766]: line 0 column 0 syntax error 10 Dec 07:21:36 ntpd[67766]: basedate set to 2025-06-08 10 Dec 07:21:36 ntpd[67766]: gps base set to 2025-06-08 (week 2370) 10 Dec 07:21:36 ntpd[67766]: Listen and drop on 0 v6wildcard [::]:123 10 Dec 07:21:36 ntpd[67766]: Listen and drop on 1 v4wildcard 0.0.0.0:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 2 igb0 [fe80::21a:8cff:fe18:9cba%1]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 3 igb0 10.10.10.1:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 4 igb0 10.10.10.253:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 5 igb1 [fe80::21a:8cff:fe18:9cbb%2]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 6 igb2 [fe80::21a:8cff:fe18:9cbc%3]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 7 igb2 10.10.20.1:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 8 igb3 [fe80::21a:8cff:fe18:9cbd%4]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 9 igb3 172.20.20.1:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 10 igb4 10.10.70.1:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 11 igb4 10.10.70.253:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 12 igb5 [fe80::21a:8cff:fe18:9cbf%6]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 13 igb5 192.168.178.2:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 14 igb5 192.168.178.100:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 15 igb6 [fe80::21a:8cff:fe18:9cc0%7]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 16 igb6 10.10.80.1:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 17 igb7 [fe80::21a:8cff:fe18:9cc1%8]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 18 igb7 10.10.99.1:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 19 lo0 [::1]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 20 lo0 [fe80::1%10]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 21 lo0 127.0.0.1:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 22 lo0 10.0.0.1:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 23 ovpns2 [fe80::21a:8cff:fe18:9cba%14]:123 10 Dec 07:21:36 ntpd[67766]: Listen normally on 24 ovpns2 10.0.9.1:123 10 Dec 07:21:36 ntpd[67766]: Listening on routing socket on fd #45 for interface updates 10 Dec 07:21:41 ntpd[67766]: Listen normally on 25 igb4 [fe80::21a:8cff:fe18:9cbe%5]:123 10 Dec 07:21:41 ntpd[67766]: Listen normally on 26 pppoe0 [fe80::21a:8cff:fe18:9cba%13]:123 10 Dec 07:21:41 ntpd[67766]: Listen normally on 27 pppoe0 EDITED FOR PRIVACY:123 10 Dec 07:21:41 ntpd[67766]: 216.239.35.12 local addr <null> -> EDITED FOR PRIVACY 10 Dec 07:21:41 ntpd[67766]: 216.239.35.8 local addr <null> -> EDITED FOR PRIVACY 10 Dec 07:21:41 ntpd[67766]: 216.239.35.4 local addr <null> -> EDITED FOR PRIVACY 10 Dec 07:21:41 ntpd[67766]: 216.239.35.0 local addr <null> -> EDITED FOR PRIVACY 10 Dec 07:22:06 ntpd[67766]: ntpd exiting on signal 15 (Terminated)'
@HorstZimmermann : please check the line again : afaik, only RFC1918 and IPv6 comparable are listed. If this is not the case, please tell me and I'll remove your IP info.
Info like this doesn't belong in a log 'line'.[25.07.1-RELEASE][root@pfSense.bhf.tld]/etc: /usr/bin/timeout -k 45 30 /usr/local/sbin/ntpd -g -q -c /dev/null 216.239.35.0 216.239.35.4 216.239.35.8 216.239.35.12 11 Dec 13:05:02 ntpd[57103]: ntpd 4.2.8p18@1.4062-o Wed Apr 9 23:17:26 UTC 2025 (1): Starting 11 Dec 13:05:02 ntpd[57103]: Command line: /usr/local/sbin/ntpd -g -q -c /dev/null 216.239.35.0 216.239.35.4 216.239.35.8 216.239.35.12 11 Dec 13:05:02 ntpd[57103]: ---------------------------------------------------- 11 Dec 13:05:02 ntpd[57103]: ntp-4 is maintained by Network Time Foundation, 11 Dec 13:05:02 ntpd[57103]: Inc. (NTF), a non-profit 501(c)(3) public-benefit 11 Dec 13:05:02 ntpd[57103]: corporation. Support and training for ntp-4 are 11 Dec 13:05:02 ntpd[57103]: available at https://www.nwtime.org/support 11 Dec 13:05:02 ntpd[57103]: ---------------------------------------------------- 11 Dec 13:05:02 ntpd[57103]: proto: precision = 0.137 usec (-23) 11 Dec 13:05:02 ntpd[57103]: line 0 column 0 syntax error 11 Dec 13:05:02 ntpd[57103]: basedate set to 2025-03-28 11 Dec 13:05:02 ntpd[57103]: gps base set to 2025-03-30 (week 2360) 11 Dec 13:05:02 ntpd[57103]: unable to bind to wildcard address :: - another process may be running - EXITINGWay better, now the two errors show up :
[25.07.1-RELEASE][root@pfSense.bhf.tld]/etc: /usr/bin/timeout -k 45 30 /usr/local/sbin/ntpd -g -q -c /dev/null 216.239.35.0 216.239.35.4 216.239.35.8 216.239.35.12 >>/dev/null 11 Dec 13:07:14 ntpd[69623]: line 0 column 0 syntax error 11 Dec 13:07:14 ntpd[69623]: unable to bind to wildcard address :: - another process may be running - EXITINGMore better (remove the fault (?) reference to the config file option " ... -c /dev/null ..." :
[25.07.1-RELEASE][root@pfSense.bhf.tld]/etc: /usr/bin/timeout -k 45 30 /usr/local/sbin/ntpd -g -q 216.239.35.0 216.239.35.4 216.239.35.8 216.239.35.12 >> /dev/null 11 Dec 13:07:48 ntpd[5700]: unable to bind to wildcard address :: - another process may be running - EXITINGThis error is understandable as I have already a ntpd daemon running.
Maybe not at boot time, or /etc/rc.boot so nothing will be shown.
'nothing ' means : all ok. -
@Gertjan said in [solved] pfSense + 25.07.1 check_upgrade: "Updating repositories metadata" returned error code 1 @ 2025-12-10 07:23:47:
This error is understandable as I have already a ntpd daemon running.
Maybe not at boot time, or /etc/rc.boot so nothing will be shown.
'nothing ' means : all ok.[25.07.1-RELEASE][root@pfSense.bhf.tld]/etc: /usr/bin/timeout -k 45 30 /usr/local/sbin/ntpd -g -q -c /dev/null 216.239.35.0 216.239.35.4 216.239.35.8 216.239.35.12 >>/dev/nulif i understand this right then pfsense is trying to get the time on boot from google servers apparently. I have not configured any google servers in my NTP service.
so is this a baked in thing checking the time from google?
-
There are a number of ways pfSense tries to 'bootstrap' the system time and one of those is hard coded NTP servers. That's because you might have DNSSec enabled and that will fail if the system time is out by a significant amount. Thus NTP servers defined only by FQDN may result in a failure.
-
@stephenw10 thanks for clarification and yes i use DNSSec
-
To make DNSSEC work, a good if not exact system time is mandatory.
When a system starts, the first clue is : get the time from the local RTC hardware clock, if one is present. And even when it is, it could be way off-time.
This means that DNSSEC can't work / will fail.
DNS is needed so ntpd can obtain an (several) addresses of a time server.Meet the chicken-and-egg problem ^^
This line is the one and only place in pfSense where hard-coded IPs are used **, so the system time can be bootstrapped.
Ok, not entirely true. pfSense, unbound, uses also these hard-coded IPs.
-
thanks again for your time and the help
-
Hmm. I am getting this on every boot on my 25.11 release system. I don't use Service Watchdog. Is there a way to avoid this?
-
@stephenw10 and here we go again (can´t edit title anymore to remove [solved])
updated to 25.11 wit apparently no problems
25.11-RELEASE (amd64) built on Mon Dec 15 18:04:00 CET 2025 FreeBSD 16.0-CURRENTafter reboot installed patches and rebooted again now this error is back but not saying
"Updating repositories metadata"now it says"Upgrading pkg"Upgrade check_upgrade: "Upgrading pkg" returned error code 3 @ 2025-12-19 09:11:44 -
If you use IPv6 : not a solution, but a work around :
Prefer to use IPv4 even if IPv6 is available".Works for me
.edit : this setting applies only to connection origination from pfSense, not from your devices on your LANs. The IPv6 access from my LAN devices works just fine.
No "help me" PM's please. Use the forum, the community will thank you.
-
@Gertjan Thanks for the reply
i am not using IPv6 my connection is IPv4 only
-
Well, in my case:
- I do use IPv6 (but via an HENET GIF tunnel, since my ISP does not provide native v6)
- I do have "Prefer to use IPv4 even if IPv6 is available" checked
- I do have System Patches installed, and all recommended patches applied
- I don't use Service Watchdog
- I do get this error message on every boot
edit: I've been poking around in
/usr/local/libexec/pfSense-upgradeand I think I know what's going on now. Will post back shortly.
