Page 1 of 1

Fail to do UPDATE

PostPosted: Sat Jul 13, 2019 11:44 am
by gequiros
Hello everyone

I try to do an update and i got as far as:

Dialer01:~ # zypper up -y
File '/repodata/repomd.xml' not found on medium 'http://download.opensuse.org/repositories/server:database/openSUSE_Leap_42.3/'
Abort, retry, ignore? [a/r/i/...? shows all options] (a): a
ABORT request: Aborting requested by user


That i got on all 14 servers

Thanks for any suggestion !!

Re: Fail to do UPDATE

PostPosted: Sun Jul 14, 2019 7:17 pm
by ambiorixg12
System is trying to update from a repo that it is not available, you will need to update the repo list for a valid one

Re: Fail to do UPDATE

PostPosted: Mon Jul 15, 2019 9:44 am
by gequiros
can you let me know how to solve it ? which one is the correct repository to be used and so on?

Re: Fail to do UPDATE

PostPosted: Mon Jul 15, 2019 9:21 pm
by williamconley
1) WHY are you trying to update? Please don't say "because updates are a good thing, I learned this from Microsoft Windows forcing updates on me for 15 years."

2) Repos are often down. Repos also have security, if someone from your IP range has a bad reputation, you can be blacklisted and thus blocked from that repo. However, there are mirros for OpenSuSE repos all over the world so you can find another one and switch to it. That would be an OpenSuSE issue, not related to Vicidial. OpenSuSE is a Very Large project and has many more users than this site does. There is a lot of support available for how to manage the OpenSuSE OS, much more than this site has to offer. I don't have time right now or I'd request your IP and find you a closer repo after checking to see if the primary repos are presently up from where I am. 8-)

Re: Fail to do UPDATE

PostPosted: Tue Jul 16, 2019 8:18 am
by areon
Hello,

We have some problem on OpenSuse Leap 42.3:
http://download.opensuse.org/repositori ... Leap_42.3/
Resource is no longer available!

Сan anyone tell the repository address where database packets for Suse 42.3 available now?

Re: Fail to do UPDATE

PostPosted: Tue Jul 16, 2019 10:03 am
by williamconley
disable that repo. You don't need to update that one anyway.

Re: Fail to do UPDATE

PostPosted: Wed Jul 17, 2019 8:11 am
by gequiros
Thanks so much for the advise !!

Ps:
Yeah, i learned it the microsoft way, and here a few times i update all the "SERVERS on the CLUSTER" disappear from DB, but, a quick one to fix

Re: Fail to do UPDATE

PostPosted: Wed Jul 17, 2019 8:32 pm
by williamconley
In that case, I'll repeat for emphasis: Do not update your server without a reason. "Cuz it's safer" is not a reason.

Whitelist lockdown your server and the world has no access. None of the exploits for any Linux OS will work without first having access through the firewall. Don't give anyone access through your firewall. Don't update without a need for a feature not available in your present version. We have clients who update regularly, and we have clients who have NEVER updated after many years, and we have some clients (my favorites) who update annually during whatever their Seasonal Downtime happens (like ... Christmas).