Cacher (Apt-cacher-ng): issues with fedora updates

Hi all.
I’d like to report latest malfunction, but this time it’s related to a managed one:
2 qubes-os:

  • first with cacher is unable to update fedora 36 templates, because it says there’s a unmatching sign in xml of repos
  • second without cacher updates same fedora template without any problem

Any idea?
Thanks anyway…
M.

or please copy paste exact error

Hi there,
Attaching latest ones.
Please let me know if You need other…
Thanks.
Cheers,
M.

mgmt-fedora-36_latest.log (4.0 KB)

Thanks. Can you please give us full output of, for example,

# dnf upgrade --refresh

from within fedora template?

@deeplow, @Sven
Can we split this, and replies, to a new thread named "cacher (Apt-cacher-ng), issues with fedora updates "

1 Like

Hi enmus.
Attached session log.
Please let me know if other ones are needed.
Thanks,
M.

dnf_update_full.log (3.5 KB)

what is your updateVM for fedora? Does it work with debian/whonix?

Hi,
it’s cacher for all (on first one).
And yes, of course debian and whonix are fine…
Just tested, right now and got old dear “System is already up-to-date” !
Thanks,
M.

Yes, usually it’s enough to be patient and try again every a while. It happens to me regularly.

Hi enmus,
thanks for your suggestion.
I’ll go on with it, but I’d like to let You know that’s a week it’s going in this way…
Thanks,
M.

unman already told you that in order to use cacher your repositories should be redirected to http://HTTPS///

and reading your dnf log we see

https://codecs.fedoraproject.org/openh264/36/x86_64/os/repodata/repomd.xml

For the other error:

Downloading successful, but checksum doesn’t match.

check the link to the topic I posted above.

Hi enmus.
Thanks for your help in troubleshooting my problem.

I’ve just checked back in yum.repos.d/fedora-cisco-openh264.repo because almost sure to haven’t messed them up; perhaps I think it’s exactly how salt has configured them; follows first 10 raws:

[fedora-cisco-openh264]
name=Fedora $releasever openh264 (From Cisco) - $basearch
metalink=http://HTTPS///mirrors.fedoraproject.org/metalink?repo=fedora-cisco-openh264-$releasever&arch=$basearch&protocol=http
type=rpm
enabled=1
metadata_expire=14d
repo_gpgcheck=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=True

So now?

(checking other post now…)

I think You were talking about this:

but I’ve got no luck…
dnf_update_cleaned_up.log (1.7 KB)

Thanks.
Cheers,
M.

Nope, I was talking to read all the way down from the point, meaning to try to clean cacher’s cache if nothing else helps.

Hi there,
I’ve searched a bit, but it seems to be missing the cacher “cache manager”: distkill.pl
https://www.unix-ag.uni-kl.de/~bloch/acng/html/maint.html#distkill

Do You suggest me to delete manually directory and files inside /var/cache/apt-cacher-ng ?
And in this case, only fedora directory?
Or *fedora* dirs?


Maybe something is moving… let me check…


Thanks,
M.

This is the only other thing I can suggest and I meant on

I’m sure someone else will have another suggestion.

Hi there,
probably I solved, but I’d like to have feedback from anyone else, before mark it as (possible) solution.

Briefly:
also thanks to:

I’ve searched in cache for repo references and found in mirrors.fedoraproject.org the metalink repo of my broken repositories.

So I removed by hand that (2) metalinks (all occurrences), and relauched upgrade and now it works…

Please let me know if anyone found same way to unlock fedora “not upgrading” issue…
Thanks,
M.

So doing it via webui as @Insurgo explained above didn’t help?

Please respond so it could help others too.

Hi enmus,
honestly I don’t know why, but in my cacher deploy there isn’t a browser and I haven’t installed one.
So webgui is unuseful for me…
But I can say that I runned many times acngtool, before last trick by hand, starting it from the /etc/cron.daily/<invocation> and each time I haven’t see any update working…
So I don’t think acngtool may be really useful in this matter…
Cheers,
M.

Done. Hopefully it’s as you intended.

1 Like

Thanks