I’ve got a serious problem I can’t seem to solve in any way:
have got a bunch of Ubuntu machines behind a IPFire router, all physical, no VMs
IPFire was recently 2023-08-30 updated to Core-Update-Level: 178
all of my Ubuntu machines, be it 22.04 LTS or 23.04, stopped updating from archive.ubuntu.com, archive.canonical.com, so they don’t even get security updates and can’t install a thing from their repos
other repos (for example added 3rd party PPAs) do update and work just fine
tried alternative connection not using my IPFire instance, everything worked fine
tried restoring IPFire from backup /var/ipfire/backup/2023-07-12-08:44.ipf, no effect
other stuff seems to work on Ubuntu machines, “Check DNS Servers” on IPFire says all OK
Yes, let’s check the logs. First, connect to IPFire console and issue this command tail -f /var/log/messages. This command opens the kernel logs and it will display events as they happens (ctrl-c to exit). Next, start the update. Copy and paste here whatever happens to the kernel after you start the update.
You should also have a look at the apt logs on your Ubuntu machine. They should be in /var/log/apt/history.log.
Are you using IPFire proxy? As @hvacguy has already asked, what about location block and IP Address Blocklists?
If I remove IPFire from the chain, things work on all my machines (desktops, servers, phone…), so I think I’d narrowed it down to some configuration problem after the upgrade to Core 178. No clue what changed, but it all started there.
The only change in Core Update 178 was a kernel update to implement some fixes for the latest hardware vulnerabilities from Intel and AMD. There was also a fix in the kernel to workaround the bug in Hyper-V causing those vm systems to be unable to boot with Core Update 177.
There was nothing else changed. It was an interim update because of the CVE’s announced from the new hardware vulnerabilities.
Really struggle to see why the above could cause a problem to do apt-get updates.
Looking through the update code for Core Update 178 it is very simple.
Stop squid (Web Proxy) but you don’t have that running anyway.
Make sure that a kernel is actually present.
Check the disk space.
remove the old kernel.
Install the new kernel.
restart sshd, reload unbound and start squid if it is enabled.
remove lm_sensors config to force sensor update with new kernel at next reboot.
Mark that the update requires a reboot.
Update the grub config to display new core version.
and that’s it.
Can you confirm that you were running Core Update 177 before upgrading to Core Update 178.
Can other people running with Core Update 178 and using Ubuntu machines in their network confirm if they do or do not have problems trying to do updates?
You said in the earlier post that no proxy was configured but now you say that you disabled and then enabled again your web proxy and it fixed the problem.
At the time I think it was true - was trying switching things on / off, and restoring backups too.
I also state I don’t know how the Core-Update is related to the issue.
In other words: yes, it got resolved, but how exactly isn’t clear to me.
Also the Ubuntu partner repo wasn’t it, because it was configured only on one PC out of many, and all had the same problem.
I had this problem with the Ubuntu repositories, too, but not with Core Update 178. It occurred after Core Update 180. I think there may be reason not to suspect a particular update, though. This is because my attempts to remedy the problem by manipulating the enabling and/or the transparency of the Advanced Web Proxy (as described) were unsuccessful. However, the more obscure option of toggling the Clear Cache button at the bottom of that page worked.
Moreover, I had this same problem about 1 year ago, before some number of intervening Core Updates. After several days it disappeared, and I just thought that Ubuntu had somehow blocked updates as a result of difficulties associated with distributing an October release to its mirrors.
Clearing the cache may have worked, but unfortunately I don’t have a clue what was removed by that.