Hi to all,
I try to explain what happened till now:
I’ve a test server where I had installed a subscription plan to test. After test period and changing back to community version I didn’t get any updates. This problem was solved by @giacomo
Also before this I had a yum cache error and had to rebuild the rpmbd
After these steps I could do updates at the terminal but not at softwarecenter. Softwarecenter shows yum cache error again.
Yesterday I tried to do updates and the error Giacomo solved before occurs again. After doing his steps, I could install updates at the terminal. Till today, today the same error.
After I did the steps of Giacomo again update works again.
Back to software center it shows clear yum cache, after doing this I have no entries for installed and not installed software. (Software center didn’t work in the right way before too, it has the message for a wrong repository, because of the testperiod of subscription).
Now I tried to install Nethser 7.5 from terminal with the following steps
yum clean all && yum update
yum update @nethserver-iso
and get the following message:
Warning: Group nethserver-iso does not have any packages to install.
No packages marked for update
[root@GroupwareBackup ~]# yum update
Loaded plugins: changelog, fastestmirror, nethserver_events
Loading mirror speeds from cached hostfile
https://m1.nethserver.com/stable/7.4.1708/base/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
To address this issue please refer to the below wiki article
https://wiki.centos.org/yum-errors
If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
https://m1.nethserver.com/stable/7.4.1708/centos-sclo-rh/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
One of the configured repositories failed (Stable mirror: SCLo rh 7),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=sb-centos-sclo-rh ...
4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
yum-config-manager --disable sb-centos-sclo-rh
or
subscription-manager repos --disable=sb-centos-sclo-rh
5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=sb-centos-sclo-rh.skip_if_unavailable=true
failure: repodata/repomd.xml from sb-centos-sclo-rh: [Errno 256] No more mirrors to try.
https://m1.nethserver.com/stable/7.4.1708/centos-sclo-rh/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
@giacomo How can I change to community repository not only temporarily.
Hi @giacomo,
thanks for your patience. Earlier I used the testing repo to load some modules for testing, but it’s a long time ago.
The first three commands I did everytime when it doesn’t work anymore. After these steps yum at command line works mostly for the next updates. Next time I tried, I had the same problem with the “Stable Release”.
After doing the last command I had a look to
pkginfo.conf
There is only one line with nethserver-updates, so I think I don’t have the testing repository anymore.
Basically if SystemId has a value, everything is switched to subscription repos.
We have been reworked this part for the NS release lock feature, so please be patient until the update is out.
Or you can try it from testing:
yum --enablerepo=nethserver-testing update
And then execute:
signal-event software-repos-save
If you still have problems, I’d prefer to have direct access to the machine to see what is happening.
I don’t know. Dashboard shows 7.5.1804 beta, but no updates are available. What is about the RC and the lock feature? (I don’t need it, it is only a test server, but I wanted to help with testing.)
for new nethserver release.
