Issue with checking for updates

[iammike]

When I check for updates I get this all the time

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 23.1.11 at Thu Jul 20 12:58:59 +07 2023
Fetching changelog information, please wait... fetch: transfer timed out
fetch: /usr/local/opnsense/changelog/changelog.txz appears to be truncated: 0/279964 bytes
Updating OPNsense repository catalogue...

Status keeps spinning and spinning. Doesn't matter how long I keep it running.

Any ideas?

Mirror is set to Default.
Type is set to Community

[iammike]

Did a connectivity test and that is oke. Only iPV6 failed, but that is not enabled

***GOT REQUEST TO AUDIT CONNECTIVITY***
Currently running OPNsense 23.1.11 at Thu Jul 20 13:06:12 +07 2023
Checking connectivity for host: pkg.opnsense.org -> 89.149.222.99
PING 89.149.222.99 (89.149.222.99): 1500 data bytes
1508 bytes from 89.149.222.99: icmp_seq=0 ttl=50 time=165.911 ms
1508 bytes from 89.149.222.99: icmp_seq=1 ttl=50 time=165.922 ms
1508 bytes from 89.149.222.99: icmp_seq=2 ttl=50 time=165.758 ms
1508 bytes from 89.149.222.99: icmp_seq=3 ttl=50 time=165.932 ms

--- 89.149.222.99 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 165.758/165.881/165.932/0.071 ms
Checking connectivity for repository (IPv4): https://pkg.opnsense.org/FreeBSD:13:amd64/23.1
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 835 packages processed.
Updating mimugmail repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: ........ done
Processing entries: .......... done
mimugmail repository update completed. 190 packages processed.
All repositories are up to date.
Checking connectivity for host: pkg.opnsense.org -> 2001:1af8:5300:a010:1::1
ping: UDP connect: No route to host
Checking connectivity for repository (IPv6): https://pkg.opnsense.org/FreeBSD:13:amd64/23.1
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/23.1/latest/meta.txz: Non-recoverable resolver failure
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/23.1/latest/packagesite.pkg: Non-recoverable resolver failure
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/23.1/latest/packagesite.txz: Non-recoverable resolver failure
Unable to update repository OPNsense
Updating mimugmail repository catalogue...
pkg: https://opn-repo.routerperformance.net/repo/FreeBSD:13:amd64/meta.txz: Non-recoverable resolver failure
repository mimugmail has no meta file, using default settings
pkg: https://opn-repo.routerperformance.net/repo/FreeBSD:13:amd64/packagesite.pkg: Non-recoverable resolver failure
pkg: https://opn-repo.routerperformance.net/repo/FreeBSD:13:amd64/packagesite.txz: Non-recoverable resolver failure
Unable to update repository mimugmail
Error updating repositories!
***DONE***

[franco]

I'd still try to enable "Prefer IPv4 over IPv6" under System: Settings: General.


Cheers,
Franco

[zan]

I found even with a working IPv6 updating is iffy and often get stuck, so I usually enable the "Settings>Prefer to use IPv4 even if IPv6 is available" prior updating.

Edit: franco beat me

[iammike]

@Franco

I just checked and that was already enabled

[franco]

Hmm, truncation of files can also happen when a web proxy is involved.

Can you download the file from the console via this command?

# fetch https://pkg.opnsense.org/FreeBSD:13:amd64/23.1/sets/changelog.txz


Cheers,
Franco

[iammike]

Downloads oke

#  fetch https://pkg.opnsense.org/FreeBSD:13:amd64/23.1                                                                                                                                                      /sets/changelog.txz
changelog.txz                                          276 kB  394 kBps    01s
#

[franco]

Maybe there is just a stuck pkg process:

# killall pkg
# killall pkg-static

And try the GUI again.


Cheers,
Franco

[iammike]

Thx @Franco.

# killall pkg
# killall pkg-static
No matching processes were found

Status now says this

Updated on    Wed Jul 12 09:04:58 +07 2023    
Checked on    N/A

[franco]

Ok, now let's hope the next check will not get stuck again :)


Cheers,
Franco

[iammike]

Problem remains.

I now start to think that it has to do with corruption on the DISK because I was told that yesterday we had 2 power outages and the Router is not connected yet to a UPS.

I did a fsck when in Single User mode, but would like some more guidance how to deal with this

Filesystem is UFS

[Patrick M. Hausen]

Boot to single user mode, run fsck -y, if that completes and prints something like "file system is clean" or similar in the end, all is well file system wise. Repeated runs of fsck -y might be necessary.

[iammike]

Guys,

error remains even after changing the file system to ZFS and even after a reboot and then checking for updates.

Any idea else what I can do?

[franco]

It's either ISP or configuration related. Are you using multi-WAN?


Cheers,
Franco

[iammike]

no @franco

It's a real vanilla setup, no IPv6 no Multi Wan just basic stuff (but incl AGH)

Good one on the provider, I could test it at a friends house, he has a different provider, will report back