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:
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.
Hi there,
yesterday new “locking” on updates.
So I did same procedure: remove the metalink old repo index (“updates” was the culprit) and relaunch of updates.
All working now, but I think I found a new problem:
in one of my fedora templates there are rpmfusion-* repo, that I cannot find in present metalinks…
Is there a limitation in cacher that skip all non standard repo?
Thanks.
M.
There isn’t such a limitation.
I’m not clear what you mean: can you post an example of part of the repo
definition from /etc/yum.repos.d - just the lines for metalink= will do
Hi there,
I’ve created a clone of tetmplate and installed firefox onto it.
I’ve just expired / cleaned all cache and relaunched update.
Still fails.
Following logs.
PLease let me know if You need anything else.
Thanks,
M.
in rpmfusion-free.repo and rpmfusion-nonfree.repo
I’ve removed the http forwarder added by cacher, to see if there’s any differences with other ones
(You can see in next repo list that is there a backup of original ones)
This is the complete list of repo in /etc/yum.repos.d of my fedora modded template:
adobe-linux-x86_64.repo
fedora-cisco-openh264.repo
fedora-updates-testing.repo
fedora-updates.repo
fedora.repo
google-chrome.repo
qubes-r4.repo
rpmfusion-free-updates-testing.repo
rpmfusion-free-updates.repo
rpmfusion-free.repo
rpmfusion-free.repo.bck
rpmfusion-nonfree-updates-testing.repo
rpmfusion-nonfree-updates.repo
rpmfusion-nonfree.repo
rpmfusion-nonfree.repo.bck
I can tell you that this isnt going to work.
That means that dnf will try to access the repository using https.
When that request gets to cacher, cacher has no idea what it means
because it is encrypted.
as there is no special treatment for https traffic, the request will fail
Can you please give me the line I asked for before?
The metalink data in the repo definitions.