On 29/08/19 9:58 PM, Gary Stainburn wrote:
One of the configured repositories failed (Unknown),
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:
Cannot retrieve metalink for repository:
On Thu, Aug 29, 2019 at 6:05 PM Valeri Galtsev
wrote:
>
>
> On 2019-08-29 10:53, Jonathan Billings wrote:
> > On Thu, Aug 29, 2019 at 10:25:50AM -0500, Valeri Galtsev wrote:
> >> root@point:/home/valeri # cd
> >> root@point:~ # whoami
> >> root
> >> root@point:~ # rm -rf /
> >> rm: "/" may not
Am 2019-08-29 18:26, schrieb Gary Stainburn:
On Thursday 29 August 2019 16:47:11 Alexander Dalloz wrote:
rpm -Vv nss
[root@stan2 ~]# rpm -Vv nss
./etc/pki/nss-legacy
. c /etc/pki/nss-legacy/nss-rhel7.config
./etc/pki/nssdb
. c /etc/pki/nssdb/cert8.db
Hola Angel,Resolviste el problema?CuRoger
Original message From: angel jauregui
Date: 2019-08-26 9:37 a.m. (GMT-05:00) To: centos-es@centos.org Subject:
[CentOS-es] Se cae Internet y no me funciona el DHCP Local !??? Buen día.Tengo
un servidor CentOS 6 el cual tiene DHCP,
On Thursday 29 August 2019 16:47:11 Alexander Dalloz wrote:
> rpm -Vv nss
[root@stan2 ~]# rpm -Vv nss
./etc/pki/nss-legacy
. c /etc/pki/nss-legacy/nss-rhel7.config
./etc/pki/nssdb
. c /etc/pki/nssdb/cert8.db
. c /etc/pki/nssdb/cert9.db
.
On 2019-08-29 10:53, Jonathan Billings wrote:
On Thu, Aug 29, 2019 at 10:25:50AM -0500, Valeri Galtsev wrote:
root@point:/home/valeri # cd
root@point:~ # whoami
root
root@point:~ # rm -rf /
rm: "/" may not be removed
Somebody is really clever in this World ;-) Well, FreeBSD folks made my
On Thu, Aug 29, 2019 at 10:25:50AM -0500, Valeri Galtsev wrote:
> root@point:/home/valeri # cd
> root@point:~ # whoami
> root
> root@point:~ # rm -rf /
> rm: "/" may not be removed
>
> Somebody is really clever in this World ;-) Well, FreeBSD folks made my day
> (again!). Note, that that I did on
Am 2019-08-29 17:36, schrieb Gary Stainburn:
On Thursday 29 August 2019 16:20:00 Alexander Dalloz wrote:
Hi,
yum uses libcurl behind the scenes and thus NSS and not OpenSSL.
Do you get something indicative when running:
URLGRABBER_DEBUG=1 yum --disablerepo=\* --enablerepo=webtatic
On Thursday 29 August 2019 16:20:00 Alexander Dalloz wrote:
> Hi,
>
> yum uses libcurl behind the scenes and thus NSS and not OpenSSL.
>
> Do you get something indicative when running:
>
> URLGRABBER_DEBUG=1 yum --disablerepo=\* --enablerepo=webtatic
> check-update
>
> Alexander
I get a lot
On 2019-08-17 08:42, Jonathan Billings wrote:
On Aug 17, 2019, at 9:25 AM, Valeri Galtsev wrote:
I like this one. Long-long ago it was one of the “tricky” questions at the UNIX
admin test (exam). Basically, no matter how devastating that may sound, the
command only will remove what is
Am 2019-08-29 16:51, schrieb Gary Stainburn:
On Thursday 29 August 2019 15:45:44 Gordon Messmer wrote:
On 8/29/19 3:03 AM, Gary Stainburn wrote:
> https://us-east.repo.webtatic.com/yum/el7/x86_64/repodata/repomd.xml: [Errno 14]
curl#60 - "Peer's Certificate issuer is not recognized."
What do
On Thursday 29 August 2019 15:45:44 Gordon Messmer wrote:
> On 8/29/19 3:03 AM, Gary Stainburn wrote:
> > https://us-east.repo.webtatic.com/yum/el7/x86_64/repodata/repomd.xml:
> > [Errno 14] curl#60 - "Peer's Certificate issuer is not recognized."
>
>
> What do you see when you run:
>
>
On 8/29/19 3:03 AM, Gary Stainburn wrote:
https://us-east.repo.webtatic.com/yum/el7/x86_64/repodata/repomd.xml: [Errno 14] curl#60
- "Peer's Certificate issuer is not recognized."
What do you see when you run:
openssl s_client -showcerts -connect us-east.repo.webtatic.com:443
Interestingly, if I try a yum update on one of my other boxes I get similar
errors. However, it then proceeds to complete the yum update successfully
[root@ollie2 ~]# yum update
Loaded plugins: fastestmirror, langpacks
Determining fastest mirrors
Could not get metalink
On Wednesday 28 August 2019 22:41:24 Jonathan Billings wrote:
> If it’s really out of date, you might need to update the ca-certificates
> package, but that’d have to be a really old system.
>
> I’d suggest by checking to make sure the clock on your computer isn’t really
> out of date. If its
On Thu, Aug 29, 2019 at 3:13 AM Jay Hart wrote:
>
> Hence why I posted this. I figured it was either an older upgrade
> procedure that worked prior to
> C7, and that someone figured it would work with C7 the same as it did
> (assuming here) with C6...
>
> Jay
>
>
>
Just to give some history,
16 matches
Mail list logo