Re: [CentOS] OT Hardware Forum

[Fred Smith]

On Tue, May 15, 2018 at 06:51:42PM -0400, Mark LaPierre wrote:
> Hey Y'all,
> 
> Is there a forum where I can discuss hardware and CentOS 7?  I'm
> considering building a new desktop system specifically designed for
> CentOS 7 and the Folding At Home project.
> 
> This mail list seams to be oriented toward CentOS software issues
> not hardware discussions.

Mark:

Perhaps that is a fair question to post on one of the FAH fora?

I ran FAH on my desktop Linux system for some years, mostly as
CPU only. The last couple years I ran it it had enough GPU to run
the GPU client. I had an old Nvidia card, upgraded to a newer one
(but still not near top'o'the line), a GTX-750 ti, which did 2 or
3 times the folding performance of the old one, for less power usage.

however, there was enough load from the process(es) that served the
GPU that I became really annoyed by the very laggy desktop performance
of my home computer system, plus our electricity consumption or rather
the size of our electricity bill, has caused me to stop folding.

I like what they do and liked participating for many years, but
other things got in the way enough for me to quit.

But I digress... Are you on the Centos team? If so you'll probably
see me near the top, even though I haven't folded for some time.

Good luck!

Fred
-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
   I can do all things through Christ 
  who strengthens me.
-- Philippians 4:13 ---
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] OT Hardware Forum

[Mark LaPierre]

Hey Y'all,

Is there a forum where I can discuss hardware and CentOS 7?  I'm 
considering building a new desktop system specifically designed for 
CentOS 7 and the Folding At Home project.


This mail list seams to be oriented toward CentOS software issues not 
hardware discussions.


--
_
   °v°
  /(_)\
   ^ ^  Mark LaPierre
Registered Linux user No #267004
https://linuxcounter.net/

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-es] Problema al acceder a sitio mediante squid

[Efrain Dector]

Buen día.

Por medio de ACLs puedes configurar dominios para que estos no pasen por el
proxy.

Una vez configurado, crea una ACL para que un equipo de tu red acceda a
través del proxy a esa página, con esto podrás revisar los logs y ver si te
cuentan algo extraño.

Saludos

El 15 de mayo de 2018, 16:21, Ramón Macías Zamora <
ramon.mac...@raykasolutions.com> escribió:

> Estimados Amigos,
>
> Estoy teniendo un comportamiento raro de squid, cuando un cliente tiene
> configurado el proxy por medio de squid y se accede al sitio
> http://www.boattrader.com, se muestra una pantalla en blanco. Sin embargo
> cuando se accede directamente por medio de nateo por medio de iptables, se
> puede acceder normalmente.
>
> Hice una análisis del tráfico (con Firefox) y lo extraño que veo es que
> cuando se accede por medio del proxy se devuelve el Content-Length: 0
>
>
> --
>
>
>
> Ramón Macías Zamora
> Tecnología, Investigación y Desarrollo
> Guayaquil - Ecuador
> msn:ramon_mac...@hotmail.com
> skype:  ramon_macias
> UserLinux# 180926 (http://counter.li.org)
> Cel:593-8-0192238
> Tel:593 4 6044566
> ___
> CentOS-es mailing list
> CentOS-es@centos.org
> https://lists.centos.org/mailman/listinfo/centos-es
>
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS-es] Pregunta bloqueo sitios https

[César Martinez M .]

Gracias Angel estoy investigando para ver si con squidguard puedo llegar 
al objetivo de bloquear sitios https de forma transparente, he buscado y 
re buscado por la red y no hay otra alternativa rápida.


Imagínate ingresar CIDR no termino nunca porque son miles de sitios, la 
idea es poder filtrar solo con acl una que tenga palabras pornografía 
etc etc y así bloquear de forma rápida y efectiva como squid lo hace 
pero no con sitios https.


--
|Saludos Cordiales
|César Martínez M. | Ingeniero de Sistemas
|Consultor & Proyectos Software Libre| SERVICOM
|Teléfono: (593-2)554-271 2221-386 | Ext 4501
|Celular:593 999374317 |Skype servicomecuador
|Web www.servicomecuador.com Síguenos en:
|Twitter: @servicomecuador |Facebook: servicomec
|Zona Clientes: www.servicomecuador.com/billing
|Blog: http://servicomecuador.com/blog
|Dir. Av. 10 de Agosto N29-140 Entre
|Acuña y  Cuero y Caicedo
|Quito - Ecuador - Sudamérica

El 15/05/18 a las 14:01, angel jauregui escribió:

@Ricardo de hecho no necesitaban hacer eso en tu caso, podrian redirigir
ese trafico y evitar configurar cada equipo.

@Cesar la verdad seria paranoico configurar cada navegador, en ambiente
corporativo o de Mediana/Grande Empresa lo mas coherente es buscar una
alternativa, ademas colocarlo como intermediatio (es un MITM), y tendrias
un 2do vector de ataque. Yo te recomendaria sacar el CIDR y hacer ese
proceso manual la primera vez.

Saludos

El 15 de mayo de 2018, 10:22, Ricardo J. Barberis 
escribió:


En $TRABAJO directamente bloqueamos el puerto 443 y configuramos el proxy
HTTPS en los navegadores, de esta forma el filtrado en squid sigue
funcionando igual que para HTTP (que sigue pasando por squid pero de forma
transparente).

El Martes 15/05/2018 a las 10:14, César Martinez M. escribió:

Buen día amigos espero todos se encuentren bien, como saben varios
sitios han implementado ya certificados ssl para sus sitios gratuitos o
pagados para dar mejor seo a los mismos, esto a perjudicado el bloqueo
que se realizaba con squid ya que squid no filtra este tipo de sitios.

He estado usando iptables para bloquear ciertos sitios https pero se
vuelve una tarea complicada filtrar todos los sitios de pornografía,
descargas y más ya que antes con squid solo al crear una acl con
palabras filtraba esto.

La pregunta es alguien tiene alguna sugerencia o solución para este
cambio drástico de filtrado.

--
Ricardo J. Barberis
Usuario Linux Nº 250625: http://counter.li.org/
Usuario LFS Nº 5121: http://www.linuxfromscratch.org/
Senior SysAdmin / IT Architect - www.DonWeb.com
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es






___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

[CentOS-es] Problema al acceder a sitio mediante squid

[Ramón Macías Zamora]

Estimados Amigos,

Estoy teniendo un comportamiento raro de squid, cuando un cliente tiene
configurado el proxy por medio de squid y se accede al sitio
http://www.boattrader.com, se muestra una pantalla en blanco. Sin embargo
cuando se accede directamente por medio de nateo por medio de iptables, se
puede acceder normalmente.

Hice una análisis del tráfico (con Firefox) y lo extraño que veo es que
cuando se accede por medio del proxy se devuelve el Content-Length: 0


--



Ramón Macías Zamora
Tecnología, Investigación y Desarrollo
Guayaquil - Ecuador
msn:ramon_mac...@hotmail.com
skype:  ramon_macias
UserLinux# 180926 (http://counter.li.org)
Cel:593-8-0192238
Tel:593 4 6044566
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS-es] Pregunta bloqueo sitios https

[Ricardo J. Barberis]

El Martes 15/05/2018 a las 16:01, angel jauregui escribió:
> @Ricardo de hecho no necesitaban hacer eso en tu caso, podrian redirigir
> ese trafico y evitar configurar cada equipo.

No, si rediriges HTTPS al proxy se rompe el protocolo SSL, y no tenemos CA 
propia para interceptar tráfico HTTPS (e igual tendríamos que instalar el 
certificado raiz de nuestra CA en todos los navegadores).

Para HTTP plano sí interceptamos todo el tráfico y lo pasamos a squid de forma 
transparente.

> @Cesar la verdad seria paranoico configurar cada navegador, en ambiente
> corporativo o de Mediana/Grande Empresa lo mas coherente es buscar una
> alternativa, ademas colocarlo como intermediatio (es un MITM), y tendrias
> un 2do vector de ataque. Yo te recomendaria sacar el CIDR y hacer ese
> proceso manual la primera vez.
>
> Saludos
>
> El 15 de mayo de 2018, 10:22, Ricardo J. Barberis 
>
> escribió:
> > En $TRABAJO directamente bloqueamos el puerto 443 y configuramos el proxy
> > HTTPS en los navegadores, de esta forma el filtrado en squid sigue
> > funcionando igual que para HTTP (que sigue pasando por squid pero de
> > forma transparente).
> >
> > El Martes 15/05/2018 a las 10:14, César Martinez M. escribió:
> > > Buen día amigos espero todos se encuentren bien, como saben varios
> > > sitios han implementado ya certificados ssl para sus sitios gratuitos o
> > > pagados para dar mejor seo a los mismos, esto a perjudicado el bloqueo
> > > que se realizaba con squid ya que squid no filtra este tipo de sitios.
> > >
> > > He estado usando iptables para bloquear ciertos sitios https pero se
> > > vuelve una tarea complicada filtrar todos los sitios de pornografía,
> > > descargas y más ya que antes con squid solo al crear una acl con
> > > palabras filtraba esto.
> > >
> > > La pregunta es alguien tiene alguna sugerencia o solución para este
> > > cambio drástico de filtrado.
> >
> > --
> > Ricardo J. Barberis
> > Usuario Linux Nº 250625: http://counter.li.org/
> > Usuario LFS Nº 5121: http://www.linuxfromscratch.org/
> > Senior SysAdmin / IT Architect - www.DonWeb.com
> > ___
> > CentOS-es mailing list
> > CentOS-es@centos.org
> > https://lists.centos.org/mailman/listinfo/centos-es



-- 
Ricardo J. Barberis
Usuario Linux Nº 250625: http://counter.li.org/
Usuario LFS Nº 5121: http://www.linuxfromscratch.org/
Senior SysAdmin / IT Architect - www.DonWeb.com
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS-es] Pregunta bloqueo sitios https

[angel jauregui]

@Ricardo de hecho no necesitaban hacer eso en tu caso, podrian redirigir
ese trafico y evitar configurar cada equipo.

@Cesar la verdad seria paranoico configurar cada navegador, en ambiente
corporativo o de Mediana/Grande Empresa lo mas coherente es buscar una
alternativa, ademas colocarlo como intermediatio (es un MITM), y tendrias
un 2do vector de ataque. Yo te recomendaria sacar el CIDR y hacer ese
proceso manual la primera vez.

Saludos

El 15 de mayo de 2018, 10:22, Ricardo J. Barberis 
escribió:

> En $TRABAJO directamente bloqueamos el puerto 443 y configuramos el proxy
> HTTPS en los navegadores, de esta forma el filtrado en squid sigue
> funcionando igual que para HTTP (que sigue pasando por squid pero de forma
> transparente).
>
> El Martes 15/05/2018 a las 10:14, César Martinez M. escribió:
> > Buen día amigos espero todos se encuentren bien, como saben varios
> > sitios han implementado ya certificados ssl para sus sitios gratuitos o
> > pagados para dar mejor seo a los mismos, esto a perjudicado el bloqueo
> > que se realizaba con squid ya que squid no filtra este tipo de sitios.
> >
> > He estado usando iptables para bloquear ciertos sitios https pero se
> > vuelve una tarea complicada filtrar todos los sitios de pornografía,
> > descargas y más ya que antes con squid solo al crear una acl con
> > palabras filtraba esto.
> >
> > La pregunta es alguien tiene alguna sugerencia o solución para este
> > cambio drástico de filtrado.
>
> --
> Ricardo J. Barberis
> Usuario Linux Nº 250625: http://counter.li.org/
> Usuario LFS Nº 5121: http://www.linuxfromscratch.org/
> Senior SysAdmin / IT Architect - www.DonWeb.com
> ___
> CentOS-es mailing list
> CentOS-es@centos.org
> https://lists.centos.org/mailman/listinfo/centos-es
>



-- 
M.S.I. Angel Haniel Cantu Jauregui.

Celular: (011-52-1)-899-871-17-22
E-Mail: angel.ca...@sie-group.net
Web: http://www.sie-group.net/
Cd. Reynosa Tamaulipas.
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

[CentOS-announce] CESA-2018:1453 Critical CentOS 7 dhcp Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2018:1453 Critical

Upstream details at : https://access.redhat.com/errata/RHSA-2018:1453

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
d8016005508135f34e59a890a4f189d5d63c1ae90647dc5cf292a58efa1ad281  
dhclient-4.2.5-68.el7.centos.1.x86_64.rpm
87c6a692dca9eeae9c5bffed9aec1209570ad6d4ef2235dcd8d4e9aba92bea28  
dhcp-4.2.5-68.el7.centos.1.x86_64.rpm
362140e6e05c70c91c4dd4f24d244b808173a2bc155712e0f921230bd139806d  
dhcp-common-4.2.5-68.el7.centos.1.x86_64.rpm
e807c98666a5a90388c1013e8bd4001dafdb4ddc769b2de8679683600995ce47  
dhcp-devel-4.2.5-68.el7.centos.1.i686.rpm
c0b4af7a8bae02b00407f37283356085c7316a533196615c3f1dfffa6bb8a35a  
dhcp-devel-4.2.5-68.el7.centos.1.x86_64.rpm
1090e35b58f6eefc7d262df1e9d3e1afc5ebb7b86f7664bee8efd4fed5b0c6f7  
dhcp-libs-4.2.5-68.el7.centos.1.i686.rpm
79fe00ee01d3087ca9384f639eec607b0d190007c68fab64da5f0e5c6b77d388  
dhcp-libs-4.2.5-68.el7.centos.1.x86_64.rpm

Source:
fe5f91adcebb9edf7333af7a645d682919c6823d8d93f91d289c4f6da4d73df4  
dhcp-4.2.5-68.el7.centos.1.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

[CentOS-announce] CESA-2018:1454 Critical CentOS 6 dhcp Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2018:1454 Critical

Upstream details at : https://access.redhat.com/errata/RHSA-2018:1454

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
e7b038ec6216dd9c84a4b2736a650df51c24837311786160402603a1d611d1e1  
dhclient-4.1.1-53.P1.el6.centos.4.i686.rpm
56a47d731986deb59119fbde6bd8997f3d95ebc1023a9fd40d266af715bd  
dhcp-4.1.1-53.P1.el6.centos.4.i686.rpm
f5abe8bcbe57a59102bfa875985c65f8ef11725d8d5cbba363a9af43b5c5b53e  
dhcp-common-4.1.1-53.P1.el6.centos.4.i686.rpm
7aac0528855e392838d05ed6040828f725fa53617e1a075263509a29ad6b4741  
dhcp-devel-4.1.1-53.P1.el6.centos.4.i686.rpm

x86_64:
274cc0f07e56546c3be18acc23696b63b83cbeb31d047132f1963b40f8e70eaa  
dhclient-4.1.1-53.P1.el6.centos.4.x86_64.rpm
34b6034b5152b0db167fb649c9d8d32f23ce6317b571d9a06af5176b0ab33a6a  
dhcp-4.1.1-53.P1.el6.centos.4.x86_64.rpm
ab0da4ab9234f2b9c36251c970880804e4ec9cb6baa1e7a32e50b2e8655a4dc5  
dhcp-common-4.1.1-53.P1.el6.centos.4.x86_64.rpm
7aac0528855e392838d05ed6040828f725fa53617e1a075263509a29ad6b4741  
dhcp-devel-4.1.1-53.P1.el6.centos.4.i686.rpm
d2d2344fd4076e12450ef5ca37ea2139a049166b6b2059b0ecc007fa1b892212  
dhcp-devel-4.1.1-53.P1.el6.centos.4.x86_64.rpm

Source:
d30ede6d503154811891158c268f0b80a892c925662f0b8914d90d437392b42c  
dhcp-4.1.1-53.P1.el6.centos.4.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

Re: [CentOS] Persisting Routes In A Routing Table Other Than The Default

[Chris Adams]

Once upon a time, Adam Tauno Williams  said:
> Rules load automatically via the /etc/sysconfig/network-scripts/rules-
> {interface} files.  Routes added to /etc/sysconfig/network-
> scripts/routes-{interface} are always added to the default policy.

What are you putting in the routes- file?  I just put something
like:

table 200 default via 192.168.41.1 dev eth1

-- 
Chris Adams 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Persisting Routes In A Routing Table Other Than The Default

[Adam Tauno Williams]

I need to add persistent routes to a policy routing table.  I can add
rules to an IP policy table after installing  NetworkManager-config-
routing-rules;  but I have not found how to add routes to a table other
than the specific table.

Manually I do a: 
  ip route add default via 192.168.1.6 dev ens192 table pods

Rules load automatically via the /etc/sysconfig/network-scripts/rules-
{interface} files.  Routes added to /etc/sysconfig/network-
scripts/routes-{interface} are always added to the default policy.

[root@aqueduct rc.d]# ip rule
0:  from all lookup local 
32763:  from 192.168.65.0/24 lookup pods 
32764:  from 192.168.41.0/24 lookup pods 
32765:  from 192.168.43.0/24 lookup pods 
32766:  from all lookup main 
32767:  from all lookup default 

-- 
Adam Tauno Williams  GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] could not resolve mirrorlist.centos.org

[m . roth]

Richard wrote:
>> Date: Tuesday, May 15, 2018 12:01:59 -0400
>> From: m.r...@5-cent.us
>>
>>I've got managers on me, I'm rebuilding this system as C 7...
>> and I'm getting the above. No idea. It pings, but pointing a
>> browser to  there gives me "invalid release".
>>
>>Anyone else having trouble?

> If you want a list of the mirrors, go to:
>
>

Never mind. I'd installed a minimal basic system, and had added our local
repo, and then went to run a large script... and somewhere, for no reason
I know, it had shut down the NIC-formerly-known-as-eth0. I brought that
up,  and all was well.

   mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-es] Pregunta bloqueo sitios https

[César Martinez M .]

Gracias amigos de todas las opciones que han mencionado voy a probar con 
dnsguardian ya que siempre uso proxy transparente, ponerse a sacar host 
es interminable existen muchos sitios que no se sabe ni los nombres por 
eso imposible hacer de uno en uno, voy a buscar un manual por la red 
centos 7 mas dns guardian para hacer un laboratorio y probar, de pronto 
si alguien tiene por ahí uno bueno se los agradecería.


Gracias nuevamente a todos por su tiempo y respuestas.

--
|Saludos Cordiales
|César Martínez M. | Ingeniero de Sistemas
|Consultor & Proyectos Software Libre| SERVICOM
|Teléfono: (593-2)554-271 2221-386 | Ext 4501
|Celular:593 999374317 |Skype servicomecuador
|Web www.servicomecuador.com Síguenos en:
|Twitter: @servicomecuador |Facebook: servicomec
|Zona Clientes: www.servicomecuador.com/billing
|Blog: http://servicomecuador.com/blog
|Dir. Av. 10 de Agosto N29-140 Entre
|Acuña y  Cuero y Caicedo
|Quito - Ecuador - Sudamérica

El 15/05/18 a las 08:17, Anthony Mogrovejo escribió:

Alguna vez quice poner una entidad certificadora de por medio y vía dns
hacer bloqueos ... Quizás te sirva la idea ...

Sls

El mar., 15 may. 2018 8:14 a. m., César Martinez M. <
cmarti...@servicomecuador.com> escribió:


Buen día amigos espero todos se encuentren bien, como saben varios
sitios han implementado ya certificados ssl para sus sitios gratuitos o
pagados para dar mejor seo a los mismos, esto a perjudicado el bloqueo
que se realizaba con squid ya que squid no filtra este tipo de sitios.

He estado usando iptables para bloquear ciertos sitios https pero se
vuelve una tarea complicada filtrar todos los sitios de pornografía,
descargas y más ya que antes con squid solo al crear una acl con
palabras filtraba esto.

La pregunta es alguien tiene alguna sugerencia o solución para este
cambio drástico de filtrado.

--
|Saludos Cordiales
|César Martínez M. | Ingeniero de Sistemas
|Consultor & Proyectos Software Libre| SERVICOM
|Teléfono: (593-2)554-271 2221-386 | Ext 4501
|Celular:593 999374317 |Skype servicomecuador
|Web www.servicomecuador.com Síguenos en:
|Twitter: @servicomecuador |Facebook: servicomec
|Zona Clientes: www.servicomecuador.com/billing
|Blog: http://servicomecuador.com/blog
|Dir. Av. 10 de Agosto N29-140 Entre
|Acuña y  Cuero y Caicedo
|Quito - Ecuador - Sudamérica

___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es


___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es



___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS] could not resolve mirrorlist.centos.org

[Richard]

> Date: Tuesday, May 15, 2018 12:01:59 -0400
> From: m.r...@5-cent.us
>
> Hi, folks,
> 
>I've got managers on me, I'm rebuilding this system as C 7...
> and I'm getting the above. No idea. It pings, but pointing a
> browser to  there gives me "invalid release".
> 
>Anyone else having trouble?
> 
>  mark

If you want a list of the mirrors, go to:

   


If you want to go to http://mirrorlist.centos.org, then you have to
fill in the parameters that you see in a yum .repo file, e.g.,

   

otherwise you do indeed get the "invalid release" response.



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] could not resolve mirrorlist.centos.org

[m . roth]

Hi, folks,

   I've got managers on me, I'm rebuilding this system as C 7... and I'm
getting the above. No idea. It pings, but pointing a browser to  there
gives me "invalid release".

   Anyone else having trouble?

 mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 7.5 (1804) and NetworkManager

[Michael Lampe]

Gnome's control-center now requires NetworkManager-wifi. But it's only a 
soft requirement, no shared libs involved.


To keep your workstation NM-free, you want to install a dummy package 
that provides NetworkManager-wifi but actually contains nothing, ideally 
before updating to 7.5. Here's a script to create such a dummy: 
https://github.com/larsks/fakeprovide


If you do this, control-center shows a sad face and some text (Oops, 
blah, blah, ...) in the WiFi tab. Just the same you always got in the 
network tab without NM. That's all.


-M.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-es] Pregunta bloqueo sitios https

[Ricardo J. Barberis]

En $TRABAJO directamente bloqueamos el puerto 443 y configuramos el proxy 
HTTPS en los navegadores, de esta forma el filtrado en squid sigue 
funcionando igual que para HTTP (que sigue pasando por squid pero de forma 
transparente).

El Martes 15/05/2018 a las 10:14, César Martinez M. escribió:
> Buen día amigos espero todos se encuentren bien, como saben varios
> sitios han implementado ya certificados ssl para sus sitios gratuitos o
> pagados para dar mejor seo a los mismos, esto a perjudicado el bloqueo
> que se realizaba con squid ya que squid no filtra este tipo de sitios.
>
> He estado usando iptables para bloquear ciertos sitios https pero se
> vuelve una tarea complicada filtrar todos los sitios de pornografía,
> descargas y más ya que antes con squid solo al crear una acl con
> palabras filtraba esto.
>
> La pregunta es alguien tiene alguna sugerencia o solución para este
> cambio drástico de filtrado.

-- 
Ricardo J. Barberis
Usuario Linux Nº 250625: http://counter.li.org/
Usuario LFS Nº 5121: http://www.linuxfromscratch.org/
Senior SysAdmin / IT Architect - www.DonWeb.com
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS] CentOS 7.5 (1804) and NetworkManager

[Nicolas Kovacs]

Le 15/05/2018 à 17:01, Jonathan Billings a écrit :
> On a server, who cares if you remove GDM, you aren't running X
> anyway.  If you are, it's a workstation really, and the following
> applies. 

On servers, I always install all NetworkManager-related packages.

My question was about my workstation with KDE/GDM. Here's how I did
things until now, and apparently I can't do that anymore:

https://blog.microlinux.fr/poste-de-travail-centos-7/#reseau-pc

Niki

-- 
Microlinux - Solutions informatiques durables
7, place de l'église - 30730 Montpezat
Site : https://www.microlinux.fr
Blog : https://blog.microlinux.fr
Mail : i...@microlinux.fr
Tél. : 04 66 63 10 32
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 7.5 (1804) and NetworkManager

[Jonathan Billings]

On Tue, May 15, 2018 at 12:40:06PM +0200, Nicolas Kovacs wrote:
> [..] On servers and desktop clients, I usually remove
> it and configure the network "traditionally" by simply editing
> /etc/sysconfig/network-scripts/ifcfg-whatever, /etc/resolv.conf,
> /etc/hosts, /etc/hostname and /etc/sysconfig/network. Running
> NetworkManager on anything else than a laptop has never made any sense
> to me, since it's basically an extra layer of abstraction.

On a server, who cares if you remove GDM, you aren't running X
anyway.  If you are, it's a workstation really, and the following
applies. 

On a Workstation, it's part of the GNOME environment.  I'm not
surprised it is required if you want GNOME.  If you don't want NM, I
suggest using something other than GNOME (which requires gdm on
workstations, otherwise you don't get a screen lock).  Workstations
need the ability to manage things like VPNs and ephemeral network
devices like bluetooth, so you'll need a GUI interface, which talks
with NetworkManager.

However, I've always used NM on servers in C7.  The old 'network'
service tries once to set up the network when the system boots, and
doesn't handle network outages well at all.  With NM, it can detect
media coming up and restore networking.  It can be set up with
dispatchers to run commands when the network goes up and down (fix the
clock and restart remote syslog, for example).

A lot of these are also the case for Workstations (maybe even more
so).  You need something to be able to handle a changing network
environment during the daily utilization of a system.

NM in CentOS 7 is a different beast than it was in C6.  If you were
burned by NM in C6, give it a try in C7, you might find it
acceptable. 

-- 
Jonathan Billings 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Issue with private mirror

[Eric Germann]

Which data?  the repo directory.

FWIW, I tried several mirrors.

EKG


> On May 15, 2018, at 10:04 AM, Nux!  wrote:
> 
> Hi,
> 
> To me it looks like you are getting incomplete content from your rsync 
> source. Try to sync from another mirror.
> 
> hth
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> - Original Message -
>> From: "Eric Germann" 
>> To: "CentOS mailing list" 
>> Sent: Tuesday, 15 May, 2018 12:58:21
>> Subject: [CentOS] Issue with private mirror
> 
>> Hello all, long time lurker, first time poster.
>> 
>> I have a situation that has been confounding me for the better part of a 
>> week.
>> 
>> I run an internal mirror of a Centos mirror, mainly because I have lots of 
>> hosts
>> and low bandwidth.
>> 
>> For my 7.x hosts, since 7.5.1804 was released, when I do a “yum update”, I 
>> get
>> the following errors on a number of files.
>> 
>> "Package does not match intended download. Suggestion: run yum 
>> --enablerepo=base
>> clean metadata”
>> 
>> I’ve done that.
>> 
>> I’ve done “yum clean all”.  I’ve done “yum clean all && rm -rf /var/cacheyum”
>> 
>> I’ve blown away the 7.5.1804 tree in my mirror and resync’d it and it still 
>> does
>> it.
>> 
>> If I change the 7 -> 7.5.1804 symlink to 7.4, yum update runs fine.
>> 
>> I’m confounded.
>> 
>> How can I check the repo data files on my copy against the tree to see where 
>> or
>> if it’s blowing up.
>> 
>> Oddly, if I point the host I’m updating at the SAME server I’m mirroring from
>> and do a yum update, it works fine.  Using rsync to update.
>> 
>> Out of Ideas,
>> 
>> EKG
>> 
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-es] Pregunta bloqueo sitios https

[angel jauregui]

Debes seguirlo haciendo igual, con iptables.
Porque si configuras a squid para filtrar el HTTPs estarias ocacionando en
MITM y los usuarios obtendrian una advertencia de que su conexion fue
comprometida.

Como consejo, busca el CIDR del sitio web y listo...

Saludos !

El 15 de mayo de 2018, 8:14, César Martinez M. <
cmarti...@servicomecuador.com> escribió:

> Buen día amigos espero todos se encuentren bien, como saben varios sitios
> han implementado ya certificados ssl para sus sitios gratuitos o pagados
> para dar mejor seo a los mismos, esto a perjudicado el bloqueo que se
> realizaba con squid ya que squid no filtra este tipo de sitios.
>
> He estado usando iptables para bloquear ciertos sitios https pero se
> vuelve una tarea complicada filtrar todos los sitios de pornografía,
> descargas y más ya que antes con squid solo al crear una acl con palabras
> filtraba esto.
>
> La pregunta es alguien tiene alguna sugerencia o solución para este cambio
> drástico de filtrado.
>
> --
> |Saludos Cordiales
> |César Martínez M. | Ingeniero de Sistemas
> |Consultor & Proyectos Software Libre| SERVICOM
> |Teléfono: (593-2)554-271 2221-386 | Ext 4501
> |Celular:593 999374317 |Skype servicomecuador
> |Web www.servicomecuador.com Síguenos en:
> |Twitter: @servicomecuador |Facebook: servicomec
> |Zona Clientes: www.servicomecuador.com/billing
> |Blog: http://servicomecuador.com/blog
> |Dir. Av. 10 de Agosto N29-140
> 
> Entre
> |Acuña y  Cuero y Caicedo
> |Quito - Ecuador - Sudamérica
>
> ___
> CentOS-es mailing list
> CentOS-es@centos.org
> https://lists.centos.org/mailman/listinfo/centos-es
>



-- 
M.S.I. Angel Haniel Cantu Jauregui.

Celular: (011-52-1)-899-871-17-22
E-Mail: angel.ca...@sie-group.net
Web: http://www.sie-group.net/
Cd. Reynosa Tamaulipas.
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS-es] Pregunta bloqueo sitios https

[Ricky Gutierrez]

Necesitas dansguardian que se complemente con squid.

El mar., 15 may. 2018 7:14, César Martinez M. 
escribió:

> Buen día amigos espero todos se encuentren bien, como saben varios
> sitios han implementado ya certificados ssl para sus sitios gratuitos o
> pagados para dar mejor seo a los mismos, esto a perjudicado el bloqueo
> que se realizaba con squid ya que squid no filtra este tipo de sitios.
>
> He estado usando iptables para bloquear ciertos sitios https pero se
> vuelve una tarea complicada filtrar todos los sitios de pornografía,
> descargas y más ya que antes con squid solo al crear una acl con
> palabras filtraba esto.
>
> La pregunta es alguien tiene alguna sugerencia o solución para este
> cambio drástico de filtrado.
>
> --
> |Saludos Cordiales
> |César Martínez M. | Ingeniero de Sistemas
> |Consultor & Proyectos Software Libre| SERVICOM
> |Teléfono: (593-2)554-271 2221-386 | Ext 4501
> |Celular:593 999374317 |Skype servicomecuador
> |Web www.servicomecuador.com Síguenos en:
> |Twitter: @servicomecuador |Facebook: servicomec
> |Zona Clientes: www.servicomecuador.com/billing
> |Blog: http://servicomecuador.com/blog
> |Dir. Av. 10 de Agosto N29-140 Entre
> |Acuña y  Cuero y Caicedo
> |Quito - Ecuador - Sudamérica
>
> ___
> CentOS-es mailing list
> CentOS-es@centos.org
> https://lists.centos.org/mailman/listinfo/centos-es
>
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS] Issue with private mirror

[Nux!]

Hi,

To me it looks like you are getting incomplete content from your rsync source. 
Try to sync from another mirror.

hth

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Eric Germann" 
> To: "CentOS mailing list" 
> Sent: Tuesday, 15 May, 2018 12:58:21
> Subject: [CentOS] Issue with private mirror

> Hello all, long time lurker, first time poster.
> 
> I have a situation that has been confounding me for the better part of a week.
> 
> I run an internal mirror of a Centos mirror, mainly because I have lots of 
> hosts
> and low bandwidth.
> 
> For my 7.x hosts, since 7.5.1804 was released, when I do a “yum update”, I get
> the following errors on a number of files.
> 
> "Package does not match intended download. Suggestion: run yum 
> --enablerepo=base
> clean metadata”
> 
> I’ve done that.
> 
> I’ve done “yum clean all”.  I’ve done “yum clean all && rm -rf /var/cacheyum”
> 
> I’ve blown away the 7.5.1804 tree in my mirror and resync’d it and it still 
> does
> it.
> 
> If I change the 7 -> 7.5.1804 symlink to 7.4, yum update runs fine.
> 
> I’m confounded.
> 
> How can I check the repo data files on my copy against the tree to see where 
> or
> if it’s blowing up.
> 
> Oddly, if I point the host I’m updating at the SAME server I’m mirroring from
> and do a yum update, it works fine.  Using rsync to update.
> 
> Out of Ideas,
> 
> EKG
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-es] Pregunta bloqueo sitios https

[Anthony Mogrovejo]

Alguna vez quice poner una entidad certificadora de por medio y vía dns
hacer bloqueos ... Quizás te sirva la idea ...

Sls

El mar., 15 may. 2018 8:14 a. m., César Martinez M. <
cmarti...@servicomecuador.com> escribió:

> Buen día amigos espero todos se encuentren bien, como saben varios
> sitios han implementado ya certificados ssl para sus sitios gratuitos o
> pagados para dar mejor seo a los mismos, esto a perjudicado el bloqueo
> que se realizaba con squid ya que squid no filtra este tipo de sitios.
>
> He estado usando iptables para bloquear ciertos sitios https pero se
> vuelve una tarea complicada filtrar todos los sitios de pornografía,
> descargas y más ya que antes con squid solo al crear una acl con
> palabras filtraba esto.
>
> La pregunta es alguien tiene alguna sugerencia o solución para este
> cambio drástico de filtrado.
>
> --
> |Saludos Cordiales
> |César Martínez M. | Ingeniero de Sistemas
> |Consultor & Proyectos Software Libre| SERVICOM
> |Teléfono: (593-2)554-271 2221-386 | Ext 4501
> |Celular:593 999374317 |Skype servicomecuador
> |Web www.servicomecuador.com Síguenos en:
> |Twitter: @servicomecuador |Facebook: servicomec
> |Zona Clientes: www.servicomecuador.com/billing
> |Blog: http://servicomecuador.com/blog
> |Dir. Av. 10 de Agosto N29-140 Entre
> |Acuña y  Cuero y Caicedo
> |Quito - Ecuador - Sudamérica
>
> ___
> CentOS-es mailing list
> CentOS-es@centos.org
> https://lists.centos.org/mailman/listinfo/centos-es
>
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

[CentOS-es] Pregunta bloqueo sitios https

[César Martinez M .]

Buen día amigos espero todos se encuentren bien, como saben varios 
sitios han implementado ya certificados ssl para sus sitios gratuitos o 
pagados para dar mejor seo a los mismos, esto a perjudicado el bloqueo 
que se realizaba con squid ya que squid no filtra este tipo de sitios.


He estado usando iptables para bloquear ciertos sitios https pero se 
vuelve una tarea complicada filtrar todos los sitios de pornografía, 
descargas y más ya que antes con squid solo al crear una acl con 
palabras filtraba esto.


La pregunta es alguien tiene alguna sugerencia o solución para este 
cambio drástico de filtrado.


--
|Saludos Cordiales
|César Martínez M. | Ingeniero de Sistemas
|Consultor & Proyectos Software Libre| SERVICOM
|Teléfono: (593-2)554-271 2221-386 | Ext 4501
|Celular:593 999374317 |Skype servicomecuador
|Web www.servicomecuador.com Síguenos en:
|Twitter: @servicomecuador |Facebook: servicomec
|Zona Clientes: www.servicomecuador.com/billing
|Blog: http://servicomecuador.com/blog
|Dir. Av. 10 de Agosto N29-140 Entre
|Acuña y  Cuero y Caicedo
|Quito - Ecuador - Sudamérica

___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS-virt] centos-qemu-ev repository not work for x86_64 arch on CentOS 7.5

[Sandro Bonazzola]

2018-05-15 15:08 GMT+02:00 Nerijus Baliunas :

> On Tue, 15 May 2018 14:48:13 +0200 Sandro Bonazzola 
> wrote:
>
> > > > Also, can you share your anaconda logs?
> > > > Maybe some package installation order issue prevents /usr/bin/uname
> -m |
> > > > grep -q 'x86_64' to properly execute.
> > >
> > > In packaging.log:
> > > 14:38:25,111 INFO packaging: centos-release-7-5.1804.el7.centos.x86_64
> > > (43/296)
> > > 14:38:25,111 INFO packaging: /var/tmp/rpm-tmp.Zk5yvn: line 1:
> > > /usr/bin/uname: No such file or directory
> >
> > So this is a requirements error in the spec file.
> >
> > centos-release should have:
> >
> > Requires(post): coreutils
>
> rpm -q --requires centos-release
> /bin/sh
> config(centos-release) = 7-5.1804.el7.centos
> coreutils
>
> I assume it is not enough?
>

Correct, that's not enough. It should have:
Requires(post): coreutils




>
> Regards,
> Nerijus
>



-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R

Red Hat EMEA 

sbona...@redhat.com


___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] centos-qemu-ev repository not work for x86_64 arch on CentOS 7.5

[Nerijus Baliunas]

On Tue, 15 May 2018 14:48:13 +0200 Sandro Bonazzola  wrote:

> > > Also, can you share your anaconda logs?
> > > Maybe some package installation order issue prevents /usr/bin/uname -m |
> > > grep -q 'x86_64' to properly execute.
> >
> > In packaging.log:
> > 14:38:25,111 INFO packaging: centos-release-7-5.1804.el7.centos.x86_64
> > (43/296)
> > 14:38:25,111 INFO packaging: /var/tmp/rpm-tmp.Zk5yvn: line 1:
> > /usr/bin/uname: No such file or directory
> 
> So this is a requirements error in the spec file.
> 
> centos-release should have:
> 
> Requires(post): coreutils

rpm -q --requires centos-release
/bin/sh
config(centos-release) = 7-5.1804.el7.centos
coreutils

I assume it is not enough?

Regards,
Nerijus
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] centos-qemu-ev repository not work for x86_64 arch on CentOS 7.5

[Sandro Bonazzola]

2018-05-15 14:39 GMT+02:00 Nerijus Baliunas :

> On Tue, 15 May 2018 14:18:08 +0200 Sandro Bonazzola 
> wrote:
>
> > >> I have freshly installed CentOS 7.5 on a Dell server, and
> > >> /etc/yum/vars/contentdir
> > >> contains 'altarch' too. CentOS 7.4->7.5 upgraded servers have
> 'centos'.
> > >
> > > I see in %post:
> > > /usr/bin/uname -m | grep -q 'x86_64' && echo 'centos'
> > > >/etc/yum/vars/contentdir || echo 'altarch' > /etc/yum/vars/contentdir
> > >
> > > can you please check
> > >
> > > /usr/bin/uname -m
> > >
> > > on your system?
>
> # /usr/bin/uname -m
> x86_64
>
> > Also, can you share your anaconda logs?
> > Maybe some package installation order issue prevents /usr/bin/uname -m |
> > grep -q 'x86_64' to properly execute.
>
> In packaging.log:
> 14:38:25,111 INFO packaging: centos-release-7-5.1804.el7.centos.x86_64
> (43/296)
> 14:38:25,111 INFO packaging: /var/tmp/rpm-tmp.Zk5yvn: line 1:
> /usr/bin/uname: No such file or directory
>

So this is a requirements error in the spec file.

centos-release should have:

Requires(post): coreutils



>
> Logs are at http://sat.lt/anaconda.tgz
>
> Regards,
> Nerijus
> ___
> CentOS-virt mailing list
> CentOS-virt@centos.org
> https://lists.centos.org/mailman/listinfo/centos-virt
>



-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R

Red Hat EMEA 

sbona...@redhat.com


___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] centos-qemu-ev repository not work for x86_64 arch on CentOS 7.5

[Nerijus Baliunas]

On Tue, 15 May 2018 14:18:08 +0200 Sandro Bonazzola  wrote:

> >> I have freshly installed CentOS 7.5 on a Dell server, and
> >> /etc/yum/vars/contentdir
> >> contains 'altarch' too. CentOS 7.4->7.5 upgraded servers have 'centos'.
> >
> > I see in %post:
> > /usr/bin/uname -m | grep -q 'x86_64' && echo 'centos'
> > >/etc/yum/vars/contentdir || echo 'altarch' > /etc/yum/vars/contentdir
> >
> > can you please check
> >
> > /usr/bin/uname -m
> >
> > on your system?

# /usr/bin/uname -m
x86_64

> Also, can you share your anaconda logs?
> Maybe some package installation order issue prevents /usr/bin/uname -m |
> grep -q 'x86_64' to properly execute.

In packaging.log:
14:38:25,111 INFO packaging: centos-release-7-5.1804.el7.centos.x86_64 (43/296)
14:38:25,111 INFO packaging: /var/tmp/rpm-tmp.Zk5yvn: line 1: /usr/bin/uname: 
No such file or directory

Logs are at http://sat.lt/anaconda.tgz

Regards,
Nerijus
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

[CentOS] CentOS 7.5 and GPU memory

[Jerry Geis]

Is there a way to "control" how much GPU memory the OS uses ?
Back on CentOS 7.4 it "seemed" to use less. I want / need to tell 7.5 to
use less.\ or no GPU memory.  I have a video application that needs more of
the GPU memory and not so much the OS taking that memory.

How do I do that?

Thanks,

Jerry
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 7.5 (1804) and NetworkManager

[Stephen John Smoogen]

On 15 May 2018 at 06:40, Nicolas Kovacs  wrote:
> Hi,
>
> I'm running CentOS on all kinds of setups: servers, workstations,
> desktops and laptops.
>
> Up until now, I'm only using NetworkManager on laptops, since it makes
> sense to use it there. On servers and desktop clients, I usually remove
> it and configure the network "traditionally" by simply editing
> /etc/sysconfig/network-scripts/ifcfg-whatever, /etc/resolv.conf,
> /etc/hosts, /etc/hostname and /etc/sysconfig/network. Running
> NetworkManager on anything else than a laptop has never made any sense
> to me, since it's basically an extra layer of abstraction.
>
> With the latest update, the removal of NetworkManager on a desktop
> client isn't possible anymore, since 'yum remove NetworkManager' also
> tries to remove 'gdm', and disabling it on startup spews back all sorts
> of errors.
>
> If you folks at Red Hat are reading this, I have one question: WHY ?
>

The latest RHEL releases are getting rebased with newer Gnome and
other components. Those are more interlinked with NetworkManager and
other helper tools to work towards a less bag of potatoes and other
junk approach.

This isn't to say this is the right thing. It is just a statement of
why things are and where they seem to be going.

> Niki Kovacs
> --
> Microlinux - Solutions informatiques durables
> 7, place de l'église - 30730 Montpezat
> Site : https://www.microlinux.fr
> Blog : https://blog.microlinux.fr
> Mail : i...@microlinux.fr
> Tél. : 04 66 63 10 32
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos



-- 
Stephen J Smoogen.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Squid and log files

[Pete Biggs]

> I don't know if the compressed and archived *.gz log files are supposed
> to be erased some time. Anyway, I'd like to make sure they are kept at
> least for one full year.
> 
> Where is this defined ?
> 

It's the logrotate system.  Look in /etc/logrotate.conf and
/etc/logrotate.d/ and 'man logrotate'.

P.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-virt] centos-qemu-ev repository not work for x86_64 arch on CentOS 7.5

[Sandro Bonazzola]

2018-05-15 14:16 GMT+02:00 Sandro Bonazzola :

>
>
> 2018-05-15 13:53 GMT+02:00 Nerijus Baliunas  >:
>
>> On Tue, 15 May 2018 14:45:23 +0300 Gena Makhomed  wrote:
>>
>> > >> Something wrong with $contentdir variable,
>> > >> it points to altarch for x86_64 $basearch.
>> > >
>> > > can't reproduce on a fresh x86_64 installation. Adding Brian in case
>> he has
>> > > a clue for this.
>> >
>> > I use fresh installed x86_64 CentOS 7.5 via VNC
>> > with partially filled config anaconda-ks.cfg
>> >
>> > And I can see in /etc/yum/vars/contentdir:
>> >
>> > # cat /etc/yum/vars/contentdir
>> > altarch
>> >
>> > As I understand, on the fresh x86_64 installation
>> > file /etc/yum/vars/contentdir should have centos value.
>> >
>> > P.S.
>> >
>> > I will report this issue to my hoster (hetzner.com)
>> > may be this is hoster issue and not CentOS issue ?
>> >
>> > But I am not sure what this is hoster bug,
>> > it may be CentOS 7.5 anaconda installer bug.
>> >
>> > I delete after installation all anaconda configs and all anaconda
>> > log files, so now I can't debug this issue more deeply, sorry.
>>
>> I have freshly installed CentOS 7.5 on a Dell server, and
>> /etc/yum/vars/contentdir
>> contains 'altarch' too. CentOS 7.4->7.5 upgraded servers have 'centos'.
>>
>
> I see in %post:
> /usr/bin/uname -m | grep -q 'x86_64' && echo 'centos'
> >/etc/yum/vars/contentdir || echo 'altarch' > /etc/yum/vars/contentdir
>
> can you please check
>
> /usr/bin/uname -m
>
> on your system?
>

Also, can you share your anaconda logs?
Maybe some package installation order issue prevents /usr/bin/uname -m |
grep -q 'x86_64' to properly execute.



>
>
>
>
>>
>> Regards,
>> Nerijus
>> ___
>> CentOS-virt mailing list
>> CentOS-virt@centos.org
>> https://lists.centos.org/mailman/listinfo/centos-virt
>>
>
>
>
> --
>
> SANDRO BONAZZOLA
>
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> 
> 
>



-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R

Red Hat EMEA 

sbona...@redhat.com


___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] centos-qemu-ev repository not work for x86_64 arch on CentOS 7.5

[Sandro Bonazzola]

2018-05-15 13:53 GMT+02:00 Nerijus Baliunas :

> On Tue, 15 May 2018 14:45:23 +0300 Gena Makhomed  wrote:
>
> > >> Something wrong with $contentdir variable,
> > >> it points to altarch for x86_64 $basearch.
> > >
> > > can't reproduce on a fresh x86_64 installation. Adding Brian in case
> he has
> > > a clue for this.
> >
> > I use fresh installed x86_64 CentOS 7.5 via VNC
> > with partially filled config anaconda-ks.cfg
> >
> > And I can see in /etc/yum/vars/contentdir:
> >
> > # cat /etc/yum/vars/contentdir
> > altarch
> >
> > As I understand, on the fresh x86_64 installation
> > file /etc/yum/vars/contentdir should have centos value.
> >
> > P.S.
> >
> > I will report this issue to my hoster (hetzner.com)
> > may be this is hoster issue and not CentOS issue ?
> >
> > But I am not sure what this is hoster bug,
> > it may be CentOS 7.5 anaconda installer bug.
> >
> > I delete after installation all anaconda configs and all anaconda
> > log files, so now I can't debug this issue more deeply, sorry.
>
> I have freshly installed CentOS 7.5 on a Dell server, and
> /etc/yum/vars/contentdir
> contains 'altarch' too. CentOS 7.4->7.5 upgraded servers have 'centos'.
>

I see in %post:
/usr/bin/uname -m | grep -q 'x86_64' && echo 'centos'
>/etc/yum/vars/contentdir || echo 'altarch' > /etc/yum/vars/contentdir

can you please check

/usr/bin/uname -m

on your system?




>
> Regards,
> Nerijus
> ___
> CentOS-virt mailing list
> CentOS-virt@centos.org
> https://lists.centos.org/mailman/listinfo/centos-virt
>



-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R

Red Hat EMEA 

sbona...@redhat.com


___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

[CentOS] Issue with private mirror

[Eric Germann]

Hello all, long time lurker, first time poster.

I have a situation that has been confounding me for the better part of a week.

I run an internal mirror of a Centos mirror, mainly because I have lots of 
hosts and low bandwidth.

For my 7.x hosts, since 7.5.1804 was released, when I do a “yum update”, I get 
the following errors on a number of files.

"Package does not match intended download. Suggestion: run yum 
--enablerepo=base clean metadata”

I’ve done that.  

I’ve done “yum clean all”.  I’ve done “yum clean all && rm -rf /var/cacheyum”

I’ve blown away the 7.5.1804 tree in my mirror and resync’d it and it still 
does it.

If I change the 7 -> 7.5.1804 symlink to 7.4, yum update runs fine.

I’m confounded.

How can I check the repo data files on my copy against the tree to see where or 
if it’s blowing up.

Oddly, if I point the host I’m updating at the SAME server I’m mirroring from 
and do a yum update, it works fine.  Using rsync to update.

Out of Ideas,

EKG

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-virt] centos-qemu-ev repository not work for x86_64 arch on CentOS 7.5

[Nerijus Baliunas]

On Tue, 15 May 2018 14:45:23 +0300 Gena Makhomed  wrote:

> >> Something wrong with $contentdir variable,
> >> it points to altarch for x86_64 $basearch.
> > 
> > can't reproduce on a fresh x86_64 installation. Adding Brian in case he has
> > a clue for this.
> 
> I use fresh installed x86_64 CentOS 7.5 via VNC
> with partially filled config anaconda-ks.cfg
> 
> And I can see in /etc/yum/vars/contentdir:
> 
> # cat /etc/yum/vars/contentdir
> altarch
> 
> As I understand, on the fresh x86_64 installation
> file /etc/yum/vars/contentdir should have centos value.
> 
> P.S.
> 
> I will report this issue to my hoster (hetzner.com)
> may be this is hoster issue and not CentOS issue ?
> 
> But I am not sure what this is hoster bug,
> it may be CentOS 7.5 anaconda installer bug.
> 
> I delete after installation all anaconda configs and all anaconda
> log files, so now I can't debug this issue more deeply, sorry.

I have freshly installed CentOS 7.5 on a Dell server, and 
/etc/yum/vars/contentdir
contains 'altarch' too. CentOS 7.4->7.5 upgraded servers have 'centos'.

Regards,
Nerijus
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

[CentOS] Squid and log files

[Nicolas Kovacs]

Hi,

I have Squid running on several CentOS proxy servers. Here's what the
Squid log file directory looks like on my own server:

access.log
access.log-20180311.gz
access.log-20180319.gz
access.log-20180429.gz
access.log-20180506.gz
access.log-20180514.gz
cache.log
cache.log-20180416.gz
cache.log-20180422.gz
cache.log-20180430.gz
cache.log-20180506.gz
cache.log-20180514.gz
squidGuard.log

I don't know if the compressed and archived *.gz log files are supposed
to be erased some time. Anyway, I'd like to make sure they are kept at
least for one full year.

Where is this defined ?

Niki
-- 
Microlinux - Solutions informatiques durables
7, place de l'église - 30730 Montpezat
Site : https://www.microlinux.fr
Blog : https://blog.microlinux.fr
Mail : i...@microlinux.fr
Tél. : 04 66 63 10 32
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-virt] centos-qemu-ev repository not work for x86_64 arch on CentOS 7.5

[Gena Makhomed]

On 15.05.2018 13:52, Sandro Bonazzola wrote:


failure: repodata/repomd.xml from centos-qemu-ev: [Errno 256] No more

mirrors to try.
http://mirror.centos.org/altarch/7/virt/x86_64/kvm-common/
repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found



Something wrong with $contentdir variable,
it points to altarch for x86_64 $basearch.


can't reproduce on a fresh x86_64 installation. Adding Brian in case he has
a clue for this.


I use fresh installed x86_64 CentOS 7.5 via VNC
with partially filled config anaconda-ks.cfg

And I can see in /etc/yum/vars/contentdir:

# cat /etc/yum/vars/contentdir
altarch

As I understand, on the fresh x86_64 installation
file /etc/yum/vars/contentdir should have centos value.

P.S.

I will report this issue to my hoster (hetzner.com)
may be this is hoster issue and not CentOS issue ?

But I am not sure what this is hoster bug,
it may be CentOS 7.5 anaconda installer bug.

I delete after installation all anaconda configs and all anaconda
log files, so now I can't debug this issue more deeply, sorry.

--
Best regards,
 Gena
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS] CentOS 7.5 (1804) and NetworkManager

[Gianluca Cecchi]

On Tue, May 15, 2018 at 12:40 PM, Nicolas Kovacs  wrote:

> Hi,
>
> I'm running CentOS on all kinds of setups: servers, workstations,
> desktops and laptops.
>
> Up until now, I'm only using NetworkManager on laptops, since it makes
> sense to use it there. On servers and desktop clients, I usually remove
> it and configure the network "traditionally" by simply editing
> /etc/sysconfig/network-scripts/ifcfg-whatever, /etc/resolv.conf,
> /etc/hosts, /etc/hostname and /etc/sysconfig/network. Running
> NetworkManager on anything else than a laptop has never made any sense
> to me, since it's basically an extra layer of abstraction.
>
> With the latest update, the removal of NetworkManager on a desktop
> client isn't possible anymore, since 'yum remove NetworkManager' also
> tries to remove 'gdm', and disabling it on startup spews back all sorts
> of errors.
>
> If you folks at Red Hat are reading this, I have one question: WHY ?
>
> Niki Kovacs
>

Disclosure:
I'm not a folk at Red Hat ;-)

In CentOS / Fedora I simply disable NetworkManager service and put into
ifcfg-xxx (eg ifcfg-eth0) the line

NM_CONTROLLED=no

The network service is enabled by default, so this should be sufficient to
keep NetworkManager installed but not inerfering with your classic network
configuration.

On a just updated c7test vm

[root@c7test ~]# uptime
 13:19:51 up 2 min,  1 user,  load average: 0.10, 0.15, 0.07
[root@c7test ~]#

[root@c7test ~]# cat /etc/centos-release
CentOS Linux release 7.5.1804 (Core)
[root@c7test ~]#

[root@c7test ~]# systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service;
disabled; vendor preset: enabled)
   Active: inactive (dead)
 Docs: man:NetworkManager(8)

[root@c7test ~]# systemctl status network -l
● network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
   Active: active (exited) since Tue 2018-05-15 13:17:27 CEST; 15s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 700 ExecStart=/etc/rc.d/init.d/network start (code=exited,
status=0/SUCCESS)

May 15 13:17:21 c7test.mydomain systemd[1]: Starting LSB: Bring up/down
networking...
May 15 13:17:23 c7test.mydomain network[700]: Bringing up loopback
interface:  [  OK  ]
May 15 13:17:27 c7test.mydomain NET[1001]:
/etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf
May 15 13:17:27 c7test.mydomain network[700]: Bringing up interface eth0:
[  OK  ]
May 15 13:17:27 c7test.mydomain systemd[1]: Started LSB: Bring up/down
networking.


[root@c7test ~]# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc pfifo_fast state
UP group default qlen 1000
link/ether 00:1a:4a:16:01:00 brd ff:ff:ff:ff:ff:ff
inet 10.4.4.33/24 brd 10.4.4.255 scope global eth0
   valid_lft forever preferred_lft forever
inet6 fe80::21a:4aff:fe16:100/64 scope link
   valid_lft forever preferred_lft forever
[root@c7test ~]#


HOIH,
Gianluca
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-virt] centos-qemu-ev repository not work for x86_64 arch on CentOS 7.5

[Phill Bandelow]

Yep. We are seeing the same thing.

http://mirror.centos.org/altarch/7/virt/x86_64/kvm-
common/repodata/repomd.xml:

[Errno 14] HTTP Error 404 - Not Found

On 15 May 2018 at 11:52, Sandro Bonazzola  wrote:

>
>
> 2018-05-15 12:38 GMT+02:00 Gena Makhomed :
>
>> Hello, Sandro!
>>
>> On 15.05.2018 13:24, Gena Makhomed wrote:
>>
>> failure: repodata/repomd.xml from centos-qemu-ev: [Errno 256] No more
>>> mirrors to try.
>>> http://mirror.centos.org/altarch/7/virt/x86_64/kvm-common/re
>>> podata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
>>>
>>
>> I found workaround:
>>
>> # diff -u CentOS-QEMU-EV.repo.old CentOS-QEMU-EV.repo
>> --- CentOS-QEMU-EV.repo.old 2018-05-15 13:30:27.500156416 +0300
>> +++ CentOS-QEMU-EV.repo 2018-05-15 13:30:38.980208715 +0300
>> @@ -5,7 +5,7 @@
>>
>>  [centos-qemu-ev]
>>  name=CentOS-$releasever - QEMU EV
>> -baseurl=http://mirror.centos.org/$contentdir/$releasever/vi
>> rt/$basearch/kvm-common/
>> +baseurl=http://mirror.centos.org/centos/$releasever/virt/$b
>> asearch/kvm-common/
>>  gpgcheck=1
>>  enabled=1
>>  gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization
>>
>> 
>> =
>>
>> now all works fine.
>>
>> But as I understand, this is bug and it should be fixed.
>>
>> Something wrong with $contentdir variable,
>> it points to altarch for x86_64 $basearch.
>
>
>
> can't reproduce on a fresh x86_64 installation. Adding Brian in case he
> has a clue for this.
>
>
>
>
>
>>
>>
>> --
>> Best regards,
>>  Gena
>> ___
>> CentOS-virt mailing list
>> CentOS-virt@centos.org
>> https://lists.centos.org/mailman/listinfo/centos-virt
>>
>
>
>
> --
>
> SANDRO BONAZZOLA
>
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> 
> 
>
> ___
> CentOS-virt mailing list
> CentOS-virt@centos.org
> https://lists.centos.org/mailman/listinfo/centos-virt
>
>


-- 
Regards,
Phill Bandelow
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] centos-qemu-ev repository not work for x86_64 arch on CentOS 7.5

[Sandro Bonazzola]

2018-05-15 12:38 GMT+02:00 Gena Makhomed :

> Hello, Sandro!
>
> On 15.05.2018 13:24, Gena Makhomed wrote:
>
> failure: repodata/repomd.xml from centos-qemu-ev: [Errno 256] No more
>> mirrors to try.
>> http://mirror.centos.org/altarch/7/virt/x86_64/kvm-common/
>> repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
>>
>
> I found workaround:
>
> # diff -u CentOS-QEMU-EV.repo.old CentOS-QEMU-EV.repo
> --- CentOS-QEMU-EV.repo.old 2018-05-15 13:30:27.500156416 +0300
> +++ CentOS-QEMU-EV.repo 2018-05-15 13:30:38.980208715 +0300
> @@ -5,7 +5,7 @@
>
>  [centos-qemu-ev]
>  name=CentOS-$releasever - QEMU EV
> -baseurl=http://mirror.centos.org/$contentdir/$releasever/vi
> rt/$basearch/kvm-common/
> +baseurl=http://mirror.centos.org/centos/$releasever/virt/$b
> asearch/kvm-common/
>  gpgcheck=1
>  enabled=1
>  gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization
>
> 
> =
>
> now all works fine.
>
> But as I understand, this is bug and it should be fixed.
>
> Something wrong with $contentdir variable,
> it points to altarch for x86_64 $basearch.



can't reproduce on a fresh x86_64 installation. Adding Brian in case he has
a clue for this.





>
>
> --
> Best regards,
>  Gena
> ___
> CentOS-virt mailing list
> CentOS-virt@centos.org
> https://lists.centos.org/mailman/listinfo/centos-virt
>



-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R

Red Hat EMEA 

sbona...@redhat.com


___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

[CentOS] CentOS 7.5 (1804) and NetworkManager

[Nicolas Kovacs]

Hi,

I'm running CentOS on all kinds of setups: servers, workstations,
desktops and laptops.

Up until now, I'm only using NetworkManager on laptops, since it makes
sense to use it there. On servers and desktop clients, I usually remove
it and configure the network "traditionally" by simply editing
/etc/sysconfig/network-scripts/ifcfg-whatever, /etc/resolv.conf,
/etc/hosts, /etc/hostname and /etc/sysconfig/network. Running
NetworkManager on anything else than a laptop has never made any sense
to me, since it's basically an extra layer of abstraction.

With the latest update, the removal of NetworkManager on a desktop
client isn't possible anymore, since 'yum remove NetworkManager' also
tries to remove 'gdm', and disabling it on startup spews back all sorts
of errors.

If you folks at Red Hat are reading this, I have one question: WHY ?

Niki Kovacs
-- 
Microlinux - Solutions informatiques durables
7, place de l'église - 30730 Montpezat
Site : https://www.microlinux.fr
Blog : https://blog.microlinux.fr
Mail : i...@microlinux.fr
Tél. : 04 66 63 10 32
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-virt] centos-qemu-ev repository not work for x86_64 arch on CentOS 7.5

[Gena Makhomed]

Hello, Sandro!

On 15.05.2018 13:24, Gena Makhomed wrote:

failure: repodata/repomd.xml from centos-qemu-ev: [Errno 256] No more 
mirrors to try.
http://mirror.centos.org/altarch/7/virt/x86_64/kvm-common/repodata/repomd.xml: 
[Errno 14] HTTP Error 404 - Not Found


I found workaround:

# diff -u CentOS-QEMU-EV.repo.old CentOS-QEMU-EV.repo
--- CentOS-QEMU-EV.repo.old 2018-05-15 13:30:27.500156416 +0300
+++ CentOS-QEMU-EV.repo 2018-05-15 13:30:38.980208715 +0300
@@ -5,7 +5,7 @@

 [centos-qemu-ev]
 name=CentOS-$releasever - QEMU EV
-baseurl=http://mirror.centos.org/$contentdir/$releasever/virt/$basearch/kvm-common/
+baseurl=http://mirror.centos.org/centos/$releasever/virt/$basearch/kvm-common/
 gpgcheck=1
 enabled=1
 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization

=

now all works fine.

But as I understand, this is bug and it should be fixed.

Something wrong with $contentdir variable,
it points to altarch for x86_64 $basearch.

--
Best regards,
 Gena
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt