[CentOS] CentOS-announce Digest, Vol 130, Issue 2

[centos-announce-request]

Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. CESA-2015:2549 Moderate CentOS 6 libxml2 Security Update
  (Johnny Hughes)


--

Message: 1
Date: Mon, 7 Dec 2015 13:26:33 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2015:2549 Moderate CentOS 6 libxml2
SecurityUpdate
Message-ID: <20151207132633.ga36...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2015:2549 Moderate

Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-2549.html

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

i386:
ef6fc5b110883e8b85e6e0aadb0dece190506569ba1c25247b612ffee5e10e7c  
libxml2-2.7.6-20.el6_7.1.i686.rpm
02e4ba1fea746762064a0fc7ba37d9fa1626cefd43257360db633fb23007c1d7  
libxml2-devel-2.7.6-20.el6_7.1.i686.rpm
d45068dcb62936bfd95e45182c807339dc060963d97adeae4d7717943a0107df  
libxml2-python-2.7.6-20.el6_7.1.i686.rpm
3c14ee97b4f56ede803f59fcdadb4786e3e4ab6792d68e7b509e7a346973b363  
libxml2-static-2.7.6-20.el6_7.1.i686.rpm

x86_64:
ef6fc5b110883e8b85e6e0aadb0dece190506569ba1c25247b612ffee5e10e7c  
libxml2-2.7.6-20.el6_7.1.i686.rpm
6c42e07b5804dc8c346d5fa29755a515e8338618fc2b228959e4449e0d7b3227  
libxml2-2.7.6-20.el6_7.1.x86_64.rpm
02e4ba1fea746762064a0fc7ba37d9fa1626cefd43257360db633fb23007c1d7  
libxml2-devel-2.7.6-20.el6_7.1.i686.rpm
46fa4d9f942837bb4dc48907578ed4e12ca6a830b61719c649ff2b7ac5292bbf  
libxml2-devel-2.7.6-20.el6_7.1.x86_64.rpm
248032ec39a9aa0964763fa824604bc696dc54b59adaaac6b9e7c54f76137518  
libxml2-python-2.7.6-20.el6_7.1.x86_64.rpm
67315973b872c5fdfc8656df43af9d21bd9a881e4c20d1bff3f53db1def4022b  
libxml2-static-2.7.6-20.el6_7.1.x86_64.rpm

Source:
647b02b23b0fc8a0cb8d0821279cb4600f130b3776e345e91dee342f8df4  
libxml2-2.7.6-20.el6_7.1.src.rpm



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



--

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


End of CentOS-announce Digest, Vol 130, Issue 2
***
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-virt] Xen build with XSAs through 163 in progress

[George Dunlap]

Just a heads-up: A Xen package with XSAs through 163 is on its way
through the build system.  I'll send an announcement when I've tagged
it as ready to be propagated to the mirrors.

As with the last XSA update, it will depend on having manually updated
to the new Virt SIG repository layout.  If you haven't already please
run the following in preparation:

yum install 
http://buildlogs.centos.org/centos/6/virt/x86_64/xen/centos-release-xen-7-11.el6.x86_64.rpm

(And note that this package depends on a package from centos-extras,
so if you have that repo disabled by default you'll need to enable it
to perform the above command.)

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

Re: [CentOS-es] Inicia con fallos el Samba4

[Fermin Francisco]

Buenas noches!!
Esta noche resolví el problema.
El problema estaba en el script de inicio de samba4.
Los sustituí por el que aparece en la web oficial de samba.
https://wiki.samba.org/index.php/Samba4/InitScript

Aquí les presento el script que se encuentra en la web oficial:
#!/bin/bash
#
# samba4This shell script takes care of starting and stopping
#   samba4 daemons.
#
# chkconfig: - 58 74
# description: Samba 4.0 will be the next version of the Samba suite
# and incorporates all the technology found in both the Samba4 alpha
# series and the stable 3.x series. The primary additional features
# over Samba 3.6 are support for the Active Directory logon protocols
# used by Windows 2000 and above.

### BEGIN INIT INFO
# Provides: samba4
# Required-Start: $network $local_fs $remote_fs
# Required-Stop: $network $local_fs $remote_fs
# Should-Start: $syslog $named
# Should-Stop: $syslog $named
# Short-Description: start and stop samba4
# Description: Samba 4.0 will be the next version of the Samba suite
# and incorporates all the technology found in both the Samba4 alpha
# series and the stable 3.x series. The primary additional features
# over Samba 3.6 are support for the Active Directory logon protocols
# used by Windows 2000 and above.
### END INIT INFO

# Source function library.
. /etc/init.d/functions


# Source networking configuration.
. /etc/sysconfig/network


prog=samba
prog_dir=/usr/local/samba/sbin/
lockfile=/var/lock/subsys/$prog


start() {
[ "$NETWORKING" = "no" ] && exit 1
#   [ -x /usr/sbin/ntpd ] || exit 5

# Start daemons.
echo -n $"Starting samba4: "
daemon $prog_dir/$prog -D
RETVAL=$?
echo
[ $RETVAL -eq 0 ] && touch $lockfile
return $RETVAL
}


stop() {
[ "$EUID" != "0" ] && exit 4
echo -n $"Shutting down samba4: "
killproc $prog_dir/$prog
RETVAL=$?
echo
[ $RETVAL -eq 0 ] && rm -f $lockfile
return $RETVAL
}


# See how we were called.
case "$1" in
start)
start
    ;;
stop)
stop
    ;;
status)
status $prog
    ;;
restart)
stop
start
    ;;
reload)
echo "Not implemented yet."
exit 3
    ;;
*)
echo $"Usage: $0 {start|stop|status|restart|reload}"
exit 2
esac

Despues de reiniciar el equipo y ejecutar el comando:
systemctl status samba4.service
Obtengo lo siguiente:
[root@servidor ~]# systemctl status samba4.servicesamba4.service - LSB: start 
and stop samba4   Loaded: loaded (/etc/rc.d/init.d/samba4)   Active: active 
(running) since Tue 2015-12-08 00:05:51 AST; 36s ago  Process: 1074 
ExecStart=/etc/rc.d/init.d/samba4 start (code=exited, status=0/SUCCESS)   
CGroup: /system.slice/samba4.service           ├─1497 
/usr/local/samba/sbin//samba -D           ├─2119 /usr/local/samba/sbin//samba 
-D           ├─2120 /usr/local/samba/sbin//samba -D           ├─2121 
/usr/local/samba/sbin//samba -D           ├─2122 /usr/local/samba/sbin//samba 
-D           ├─2123 /usr/local/samba/sbin//samba -D           ├─2124 
/usr/local/samba/sbin/smbd -D --option=server role check:inhibit=yes 
--foreground           ├─2125 /usr/local/samba/sbin//samba -D           ├─2126 
/usr/local/samba/sbin//samba -D           ├─2127 /usr/local/samba/sbin//samba 
-D           ├─2128 /usr/local/samba/sbin//samba -D           ├─2129 
/usr/local/samba/sbin//samba -D           ├─2130 /usr/local/samba/sbin//samba 
-D           ├─2131 /usr/local/samba/sbin//samba -D           ├─2132 
/usr/local/samba/sbin/winbindd -D --option=server role check:inhibit=yes 
--foreground           ├─2136 /usr/local/samba/sbin/winbindd -D --option=server 
role check:inhibit=yes --foreground           ├─2137 /usr/local/samba/sbin/smbd 
-D --option=server role check:inhibit=yes --foreground           ├─2138 
/usr/local/samba/sbin/smbd -D --option=server role check:inhibit=yes 
--foreground           └─2141 /usr/local/samba/sbin/smbd -D --option=server 
role check:inhibit=yes --foreground
Dec 08 00:05:54 servidor samba[1497]: [2015/12/08 00:05:54.327969,  0] 
../source4/smbd/server.c:484(binary_smbd_main)Dec 08 00:05:54 servidor 
samba[1497]: samba: using 'standard' process modelDec 08 00:05:54 servidor 
samba[1497]: [2015/12/08 00:05:54.437017,  0] 
../lib/util/become_daemon.c:124(daemon_ready)Dec 08 00:05:54 servidor 
samba[1497]: STATUS=daemon 'samba' finished starting up and ready to serve 
connectionsDec 08 00:05:55 servidor winbindd[2132]: [2015/12/08 
00:05:55.418842,  0] 
../source3/winbindd/winbindd_cache.c:3245(initialize_winbindd_cache)Dec 08 
00:05:55 servidor winbindd[2132]: initialize_winbindd_cache: clearing cache and 
re-creating with version number 2Dec 08 00:05:56 servidor winbindd[2132]: 
[2015/12/08 00:05:56.574831,  0] 
../lib/util/become_daemon.c:124(daemon_ready)Dec 08 00:05:56 servidor 
winbindd[2132]: STATUS=daemon 'winbindd' finished starting up and 

Re: [CentOS] yum errors

[Wes James]

> On Dec 8, 2015, at 7:45 AM, Johnny Hughes  wrote:
> 
> On 12/07/2015 11:50 PM, Wes James wrote:
>> 
>>> On Dec 7, 2015, at 10:02 PM, Jake Shipton  wrote:
>>> 
>>> Wes James wrote:
 
> On Dec 7, 2015, at 8:37 PM, Wes James  wrote:
> 
>> 
>> On Dec 7, 2015, at 8:23 PM, Wes James > > wrote:
>> 
>> 
>>> On Dec 7, 2015, at 8:03 PM, Wes James  wrote:
>>> 
>> 
>> 
>> 
>>> I finally just did yum update on this box (actually 6.3) and now it is 
>>> 6.7.  During the update it created a CentOS-Base.repo.rpmnew file.  I 
>>> renamed my current one and this one to just .repo and  now I again get:
>>> 
>>> 
>>> 
>>> yum update
>>> Loaded plugins: fastestmirror, presto
>>> Setting up Update Process
>>> Loading mirror speeds from cached hostfile
>>> Could not retrieve mirrorlist 
>>> http://mirrorlist.centos.org/?release=6=x86_64=os=stock 
>>> >>  
>>> >
>>>  error was
>>> 12: Timeout on 
>>> http://mirrorlist.centos.org/?release=6=x86_64=os=stock:
>>>  
>>> >>  
>>> >
>>>  (28, 'connect() timed out!')
>>> Error: Cannot find a valid baseurl for repo: base
>>> 
>>> ——
>>> 
>>> I thought updating to 6.7 might fix something, but it didn’t help.  Any 
>>> ideas why it is doing this?
>>> 
>>> If I go to:
>>> 
>>> http://mirrorlist.centos.org/?release=6=x86_64=os=stock 
>>> 
>>>  
>>> >>  
>>> >
>>>  
>>> >>  
>>> 
>>>  
>>> >>  
>>> >>
>>> 
>>> in a browser, it shows a list of repos.
>>> 
>> 
>> I just noticed on a stock install of 6.7 (from 6.4 doing a test), doing 
>> yum update shows this:
>> 
>> Loaded plugins: fastestmirror, refresh-packagekit, security
>> 
>> But on the box I just updated it shows:
>> 
>> Loaded plugins: fastestmirror, presto
>> 
>> So maybe the presto plugin is causing the problem.  Anyone else using 
>> presto plugin??
>> 
>> -wes
> 
> 
> That wasn’t it.  I disabled presto then both with (and got the following 
> error):
> 
> yum update --disableplugin=presto,fast*
> Setting up Update Process
> Could not retrieve mirrorlist 
> http://mirrorlist.centos.org/?release=6=x86_64=os=stock 
>  
> error was
> 12: Timeout on 
> http://mirrorlist.centos.org/?release=6=x86_64=os=stock: 
> 
>  (28, 'connect() timed out!')
> Error: Cannot retrieve repository metadata (repomd.xml) for repository: 
> base. Please verify its path and try again
> 
> 
> —
> 
> 
> Not sure what to try next.  Other than my previous fix of not using a 
> mirror list, but a known local repo that works fine for updates.
> 
> -wes
 
 Poking around I found:
 
 /etc/yum/pluginconf.d and now I see where presto comes from.  I noticed in 
 the fastmirror.conf there is a line
 
 hostfile-timedhosts.txt
 
 On my test box it has several lines of hosts with a number.
 
 On the box I’m have yum update issues, it is blank.  ??
 
 -wes
 
 ___
 CentOS mailing list
 CentOS@centos.org
 https://lists.centos.org/mailman/listinfo/centos
 
>>> 
>>> Hi,
>>> 
>>> I wasn't sure if I should reply to you as you seem to be doing a pretty
>>> good job of helping your self here :-D.
>>> 
>>> But jokes aside, can you do a couple of checks?
>>> 
>>> Firstly, let's make sure this machine actually has a network connection
>>> I've actually seen people spend hours trying to fix issues like yours
>>> only to find they had no outside network connection..
>>> 
>>> $ ping 8.8.8.8
>>> 
>>> Do you get a ping response? If not, check network settings. If you do,
>>> move on..
>>> 
>>> $ ping google.com
>>> 
>>> Does the domain resolve correctly? If not, check DNS settings. If you
>>> 

Re: [CentOS] Version numbering vis a vis CentOS and RHEL

[Phelps, Matthew]

On Tue, Dec 8, 2015 at 2:42 AM, James Hogarth 
wrote:

> On 7 Dec 2015 23:43, "J Martin Rushton" 
> wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On 07/12/15 22:37, Warren Young wrote:
> > > On Dec 7, 2015, at 1:52 PM, Greg Lindahl  wrote:
> > >>
> > >> On Mon, Dec 07, 2015 at 08:57:01PM +0100, Zdenek Sedlak wrote:
> > >>
> > >>> AFAIK, the 7(1503) format is used only on the websites, and
> > >>> internally CentOS uses 7.1.1503. Do you see this as an issue?
> > >>
> > >> Yes. It confuses humans. There have been a bunch of examples
> > >> given of how it confuses humans. A simple fix for this human
> > >> issue is to use 7.1.1503 on the website, here on the mailing
> > >> list, etc.
> > >
> > > And then we’re right back in the same old boat: With every new
> > > release, the same old thread will pop up, “How do I make my servers
> > > stay on CentOS 7.1?”
> > >
> > > Give up on the point release idea.  It’s CentOS 7; there is no
> > > CentOS 7.1.  The only reason there’s a YYMM part is that it’s a
> > > media respin.  Best ignore that wherever practical.
> >
> > So if we are to give up on the point release does that mean I don't
> > have to update my machines until CentOS 8 comes along? ;-)
> >
> > Seriously though, since I have to build my own repos (air gap) and
> > build the images for the diskless machines the point releases are
> > important in tracking roughly which version particular nodes are on.
> > Running yum update on a regular basis is just not an option.
>
> You should be updating during the lifecycle to each milestone though... To
> not do so is to leave yourself open to numerous bugs and attacks.
>
> As it is, as pointed out, you can still check the installed files from the
> centos-release package for the upstream it's based on and the YYMM respin
> date...
>
> Common configuration management systems (you should be using one of these
> given you say you have many systems) will also report the relevant details
> correctly.
>
> On top of this if you are maintaining your own internal air gapped repo you
> should be paying attention to announcements which will inform you at these
> milestone points...
>
> Given the workflow you state nothing has changed for you with the EL7.X
> releases...
>
>
What I want to know is, why is CentOS doing things differently than RedHat?
Who made this decision, and was there any consideration given to making
such a highly visible departure? When did CentOS decide to fork away from
RHEL? It doesn't matter if this is truly the case, or not. Perception is
reality here; CentOS is now no longer "the same" as RHEL and this turns it
into a whole different, new, distro of Linux. That affects things like
software certification, hardware support, security certification, etc. etc.
It is now a stupendous burden on those of us who chose to implement it
because it was "the same" as RHEL.

Was this an edict resulting from the RedHat acquisition of CentOS?

I can hear people saying, "Well, why don't you just use RedHat then?" I
probably will have to now. But, we chose CentOS because it *was* RHEL, but
it gave us more control (the ease of air-gapped repositories is a good
example).

I just think this whole thing was a highly unnecessary, and bad idea. And
it has a lot of really serious repercussions that nobody seems to have
thought of before plowing ahead.

And, obviously, that angers me. I am asking for more than just consistency
between the web site and /etc/centos-release, I am asking that, starting
with RHEL 7.3, that CentOS stop using YYMM in its version numbers
completely.



-- 
Matt Phelps
System Administrator, Computation Facility
Harvard - Smithsonian Center for Astrophysics
mphe...@cfa.harvard.edu, http://www.cfa.harvard.edu
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum errors

[Johnny Hughes]

On 12/07/2015 11:50 PM, Wes James wrote:
> 
>> On Dec 7, 2015, at 10:02 PM, Jake Shipton  wrote:
>>
>> Wes James wrote:
>>>
 On Dec 7, 2015, at 8:37 PM, Wes James  wrote:

>
> On Dec 7, 2015, at 8:23 PM, Wes James  > wrote:
>
>
>> On Dec 7, 2015, at 8:03 PM, Wes James  wrote:
>>
>
> 
>
>> I finally just did yum update on this box (actually 6.3) and now it is 
>> 6.7.  During the update it created a CentOS-Base.repo.rpmnew file.  I 
>> renamed my current one and this one to just .repo and  now I again get:
>>
>> 
>>
>> yum update
>> Loaded plugins: fastestmirror, presto
>> Setting up Update Process
>> Loading mirror speeds from cached hostfile
>> Could not retrieve mirrorlist 
>> http://mirrorlist.centos.org/?release=6=x86_64=os=stock 
>> >  
>> >
>>  error was
>> 12: Timeout on 
>> http://mirrorlist.centos.org/?release=6=x86_64=os=stock: 
>> >  
>> >
>>  (28, 'connect() timed out!')
>> Error: Cannot find a valid baseurl for repo: base
>>
>> ——
>>
>> I thought updating to 6.7 might fix something, but it didn’t help.  Any 
>> ideas why it is doing this?
>>
>> If I go to:
>>
>> http://mirrorlist.centos.org/?release=6=x86_64=os=stock 
>> 
>>  
>> > >
>>  
>> > 
>>  
>> > >>
>>
>> in a browser, it shows a list of repos.
>>
>
> I just noticed on a stock install of 6.7 (from 6.4 doing a test), doing 
> yum update shows this:
>
> Loaded plugins: fastestmirror, refresh-packagekit, security
>
> But on the box I just updated it shows:
>
> Loaded plugins: fastestmirror, presto
>
> So maybe the presto plugin is causing the problem.  Anyone else using 
> presto plugin??
>
> -wes


 That wasn’t it.  I disabled presto then both with (and got the following 
 error):

 yum update --disableplugin=presto,fast*
 Setting up Update Process
 Could not retrieve mirrorlist 
 http://mirrorlist.centos.org/?release=6=x86_64=os=stock 
  
 error was
 12: Timeout on 
 http://mirrorlist.centos.org/?release=6=x86_64=os=stock: 
  
 (28, 'connect() timed out!')
 Error: Cannot retrieve repository metadata (repomd.xml) for repository: 
 base. Please verify its path and try again


 —


 Not sure what to try next.  Other than my previous fix of not using a 
 mirror list, but a known local repo that works fine for updates.

 -wes
>>>
>>> Poking around I found:
>>>
>>> /etc/yum/pluginconf.d and now I see where presto comes from.  I noticed in 
>>> the fastmirror.conf there is a line
>>>
>>> hostfile-timedhosts.txt
>>>
>>> On my test box it has several lines of hosts with a number.
>>>
>>> On the box I’m have yum update issues, it is blank.  ??
>>>
>>> -wes
>>>
>>> ___
>>> CentOS mailing list
>>> CentOS@centos.org
>>> https://lists.centos.org/mailman/listinfo/centos
>>>
>>
>> Hi,
>>
>> I wasn't sure if I should reply to you as you seem to be doing a pretty
>> good job of helping your self here :-D.
>>
>> But jokes aside, can you do a couple of checks?
>>
>> Firstly, let's make sure this machine actually has a network connection
>> I've actually seen people spend hours trying to fix issues like yours
>> only to find they had no outside network connection..
>>
>> $ ping 8.8.8.8
>>
>> Do you get a ping response? If not, check network settings. If you do,
>> move on..
>>
>> $ ping google.com
>>
>> Does the domain resolve correctly? If not, check DNS settings. If you
>> do, move on..
>>
>> Assuming both of those have worked, can you do the following:
>>
>> $ mkdir temporary
>> $ cd temporary
>> $ wget
>> "http://mirrorlist.centos.org/?release=6=x86_64=os=stock;
>>
>> (Don't miss those quotes on the url, they are needed to ensure the &'s
>> do not confuse BASH/ZSH)
>>

Re: [CentOS] yum errors

[Scott Robbins]

On Mon, Dec 07, 2015 at 08:23:29PM -0700, Wes James wrote:
> 
> > On Dec 7, 2015, at 8:03 PM, Wes James  wrote:
> > 
> 
> 
> > I finally just did yum update on this box (actually 6.3) and now it is 6.7. 
> >  During the update it created a CentOS-Base.repo.rpmnew file.  I renamed my 
> > current one and this one to just .repo and  now I again get:
> > 
> > 
> > 
> > yum update
> > Loaded plugins: fastestmirror, presto
> > Setting up Update Process
> > Loading mirror speeds from cached hostfile
> > Could not retrieve mirrorlist 
> > http://mirrorlist.centos.org/?release=6=x86_64=os=stock 
> >  
> > error was
> > 12: Timeout on 
> > http://mirrorlist.centos.org/?release=6=x86_64=os=stock: 
> >  
> > (28, 'connect() timed out!')
> > Error: Cannot find a valid baseurl for repo: base
> > 

> 
> Loaded plugins: fastestmirror, presto
> 
> So maybe the presto plugin is causing the problem.  Anyone else using presto 
> plugin??

I use presto without problems.  You can try disabling any plugin by going
to /etc/yum/pluginconf.d and in the files there, change enabled from 1 to 0

-- 
Scott Robbins
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

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

Re: [CentOS] Version numbering vis a vis CentOS and RHEL

[Karanbir Singh]

On 07/12/15 23:42, J Martin Rushton wrote:
> So if we are to give up on the point release does that mean I don't
> have to update my machines until CentOS 8 comes along? ;-)

on the flip side, ignore the point in time, assume you run /7/ and need
to update as you go along, with the YYmm telling you how far adrift you
are... in workloads where there is no real update in place ( think
cloud, container, atomic etc ), its the only reference you get to a
single package set.


-- 
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum errors

[Wes James]

> On Dec 7, 2015, at 10:57 PM, Rob Kampen  wrote:



>> 
>> [base]
>> name=CentOS-$releasever - Base
>> #mirrorlist=http://mirrorlist.centos.org/?release=$releasever=$basearch=os=$infra
> finally something I can check for you
> my 6.x machine does not have the trailing =$infra
> suggest you remove and try again

That didn’t help.  FYI, My virtualbox stock centos 6.x install has the infra= 
stuff. 

>> baseurl=http://some.mirror.in.my.state/centos/$releasever/os/$basearch/
>> gpgcheck=1
>> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6 
>> 
>> 
>> it works to do updates (and the other baseurl lines in that file).  It fails 
>> with the mirror list option.
>> 
>> I have a centos 6.2 box here that is working just fine with updates and it 
>> looks very similar to this 6.7 box - updated from 6.3).  I even tried going 
>> from static IP to dhcp assigned IP but no go.
>> 
>> I just check /var/log/yum.log, but that doesn’t show any errors, just 
>> successful updates.
>> 
>> -wes

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

Re: [CentOS] yum errors

[Wes James]

Another option I tried was

service iptables stop

just to see if there was a firewall rule causing an issue.  But yum update 
still fails:


yum update
Loaded plugins: fastestmirror, presto
Setting up Update Process
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist 
http://mirrorlist.centos.org/?release=6=x86_64=os=stock error 
was
12: Timeout on 
http://mirrorlist.centos.org/?release=6=x86_64=os=stock: (28, 
'connect() timed out!')
Error: Cannot find a valid baseurl for repo: base

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

Re: [CentOS] Version numbering vis a vis CentOS and RHEL

[Jonathan Billings]

On Tue, Dec 08, 2015 at 08:45:10AM -0500, Phelps, Matthew wrote:
> What I want to know is, why is CentOS doing things differently than RedHat?
> Who made this decision, and was there any consideration given to making
> such a highly visible departure? When did CentOS decide to fork away from
> RHEL? It doesn't matter if this is truly the case, or not. Perception is
> reality here; CentOS is now no longer "the same" as RHEL and this turns it
> into a whole different, new, distro of Linux. That affects things like
> software certification, hardware support, security certification, etc. etc.
> It is now a stupendous burden on those of us who chose to implement it
> because it was "the same" as RHEL.

CentOS has always been different than Red Hat Enterprise Linux,
because Red Hat is willing to support older point releases of RHEL
(for a price), while CentOS only supports the latest release.  You
might be running RHEL 7.1 Extended Update Support for another year or
so, while the rest of the world has updated to RHEL 7.2.
(see https://access.redhat.com/support/policy/updates/errata)

I believe (although I was not involved with the choice) the new naming
scheme reflects a need to advertise to the end user that there is only
one supported release of each major version of CentOS, with a regular
release of installation medium that coincides with the feature
updates that come out with each RHEL point release.

So often, I see people come on mailing lists and the IRC channels
saying "I'm running CentOS 6.1 and I can't get PHP to work" and we
have to ask why they aren't running a supported release of CentOS 6.
A lot of people seem genuinely surprised that you can't just keep
running some point release of CentOS and expect any kind of support.

I'll admit, the use of 7.2.1511 is *helpful* because then I know what
upstream version of RHEL it is based on, however, I'm also using RHEL7
along side CentOS7.  But in terms of naming the install medium, it
makes sense to just put a monotonically increasing number that
reflects a timestamp.

This is just my opinion, as both someone who tries to be helpful to
CentOS users, as well as a sysadmin in a large institution.

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

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[James B. Byrne]

On Mon, December 7, 2015 13:41, Matthew Miller wrote:
> On Fri, Dec 04, 2015 at 09:03:50AM -0500, James B. Byrne wrote:
>> On Thu, Dec 03, 2015 at 02:50:38PM -0500, m.r...@5-cent.us wrote:
>> > For laptops, great. For anything else, not so much. For example,
>> > it's supposed to be an *ENTERPRISE* o/s... why does it
>> > automatically, without ever asking, install anything wifi? I'm
> [...]
>> The short answer:  Because RHEL is based on Fedora development.
>
>
> This is roughly true, although "downstream" RHEL makes its own
> decisions about many things. If you (Mark, or anyone else) would like
> to make this different in the future, getting involved with Fedora
> Server is a good way to do so.
>

I subscribe to the Fedora Server list digest. Which form also is how I
get this list's messages. Thus the delay in my responses.

However, to describe the Server List as an active forum for discussion
would be somewhat overstating things.  I have not received anything
from it as yet in December and the total volume of traffic on that
list in November was very light.  I am not sure in what way you
envisage additional involvement is to take place.

I have been bitten by things done in Fedora that only have any use on
a laptop and that should never have been allowed into a server
distribution.  But I cannot see how I would have been aware of them
until they manifested themselves on equipment under my care.  By which
time it is rather too late to influence the decision to include them. 
Automatically powering down NICs comes to my mind; due the rather
nasty consequences that resulted.

The difficulty is that with Free and Open Source Software you are only
going to see features that are of some immediate use to the writers;
or whose value has already been entrenched such that it is difficult
if not impossible to dispense with. Clearly, power saving features are
of some interest to people that run their systems on batteries.

However, there are batteries, and then there are batteries.  We
occasionally run run on batteries too. It is just that ours are
measured in kilovolt-amp hours.  Having a server distro configured by
default to turn off a NIC because it has not had traffic for fifteen
minutes is not going to save us enough power from now to the end of
eternity to warrant the disruption that little 'feature' cost us when
it was first encountered.

The move to Systemd, and all the controversy that decision has
generated, also provides 'features' whose benefits appear to me be be
aimed principally at users who shut their systems off every day. These
benefits are of far less value to people who measure uptime in months
or years, while the discomfort, and expense, of this change must be
borne regardless.

Systemd will eventually be accepted or rejected on its own merits.  I
am not interested in debating them here since I have nothing upon
which to base an opinion one way or the other.  But it can hardly be
denied that forcing highly qualified people to expend time, a very
limited resource in my experience, to learn yet another way to start a
computer system, without providing any readily discernible benefit to
them, is not likely to engender much in the way of sympathy.

We went to RedHat and ended up on CentOS because of its server
orientation.  Which to us implied something more than simple
compatibility of the software components.  If RedHats's intent is to
end up as a laptop distro then we will probably part ways at some
point.  We have a laptop distro that works well for us. It is called
OSX.  And the hardware is pretty good too.


-- 
***  e-Mail is NOT a SECURE channel  ***
Do NOT transmit sensitive data via e-Mail
James B. Byrnemailto:byrn...@harte-lyne.ca
Harte & Lyne Limited  http://www.harte-lyne.ca
9 Brockley Drive  vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada  L8E 3C3

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

Re: [CentOS] yum errors

[Tru Huynh]

Hi,


On Tue, Dec 08, 2015 at 08:24:34AM -0700, Wes James wrote:
> 

...
> 
> nslookup works:
> 
> Non-authoritative answer:
> Name: mirrorlist.centos.org
> Address: 108.61.16.227
> Name: mirrorlist.centos.org
> Address: 84.22.180.89
> Name: mirrorlist.centos.org
> Address: 88.150.173.218
> 
> but wget fails??
> 
> $ wget 
> "http://mirrorlist.centos.org/?release=6=x86_64=os=stock;
> --2015-12-08 08:04:15--  
> http://mirrorlist.centos.org/?release=6=x86_64=os=stock
> Resolving mirrorlist.centos.org... 199.187.126.90
> Connecting to mirrorlist.centos.org|199.187.126.90|:80... 
> failed: Connection timed out.
> Retrying.
why does your wget hit 199.187.126.90 when your DNS says
108.61.16.227|84.22.180.89|88.150.173.218 ?

Bad http proxy in the way?

Tru

-- 
Tru Huynh 
http://pgp.mit.edu:11371/pks/lookup?op=get=0xBEFA581B


pgpU5AaknTmdV.pgp
Description: PGP signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum errors

[Wes James]

> On Dec 8, 2015, at 9:03 AM, Tru Huynh  wrote:
> 
> Hi,
> 
> 
> On Tue, Dec 08, 2015 at 08:24:34AM -0700, Wes James wrote:
>> 
> 
> ...
>> 
>> nslookup works:
>> 
>> Non-authoritative answer:
>> Name:mirrorlist.centos.org
>> Address: 108.61.16.227
>> Name:mirrorlist.centos.org
>> Address: 84.22.180.89
>> Name:mirrorlist.centos.org
>> Address: 88.150.173.218
>> 
>> but wget fails??
>> 
>> $ wget 
>> "http://mirrorlist.centos.org/?release=6=x86_64=os=stock;
>> --2015-12-08 08:04:15--  
>> http://mirrorlist.centos.org/?release=6=x86_64=os=stock
>> Resolving mirrorlist.centos.org... 199.187.126.90
>> Connecting to mirrorlist.centos.org|199.187.126.90|:80... 
>> failed: Connection timed out.
>> Retrying.
> why does your wget hit 199.187.126.90 when your DNS says
> 108.61.16.227|84.22.180.89|88.150.173.218 ?
> 
> Bad http proxy in the way?
> 


I just tried wget on my virtual box vm and it shows:

wget "http://mirrorlist.centos.org/?release=6=x86_64=os;
--2015-12-08 09:12:33--  
http://mirrorlist.centos.org/?release=6=x86_64=os
Resolving mirrorlist.centos.org... 108.61.16.227, 84.22.180.89, 88.150.173.218, 
...
Connecting to mirrorlist.centos.org|108.61.16.227|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: “index.html?release=6=x86_64=os”

[ <=> ] 
512 --.-K/s   in 0s  

2015-12-08 09:12:34 (96.8 MB/s) - “index.html?release=6=x86_64=os” 
saved [512]



Why is wget resolving to 199.187….. on these other systems?

and nslookup shows the correct host resolution:

$ nslookup mirrorlist.centos.org

Non-authoritative answer:
Name:   mirrorlist.centos.org
Address: 88.150.173.218
Name:   mirrorlist.centos.org
Address: 84.22.180.89
Name:   mirrorlist.centos.org
Address: 108.61.16.227

Thanks,

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

Re: [CentOS] yum errors

[Wes James]

> On Dec 8, 2015, at 9:03 AM, Tru Huynh  wrote:
> 
> Hi,
> 
> 
> On Tue, Dec 08, 2015 at 08:24:34AM -0700, Wes James wrote:
>> 
> 
> ...
>> 
>> nslookup works:
>> 
>> Non-authoritative answer:
>> Name:mirrorlist.centos.org
>> Address: 108.61.16.227
>> Name:mirrorlist.centos.org
>> Address: 84.22.180.89
>> Name:mirrorlist.centos.org
>> Address: 88.150.173.218
>> 
>> but wget fails??
>> 
>> $ wget 
>> "http://mirrorlist.centos.org/?release=6=x86_64=os=stock;
>> --2015-12-08 08:04:15--  
>> http://mirrorlist.centos.org/?release=6=x86_64=os=stock
>> Resolving mirrorlist.centos.org... 199.187.126.90
>> Connecting to mirrorlist.centos.org|199.187.126.90|:80... 
>> failed: Connection timed out.
>> Retrying.
> why does your wget hit 199.187.126.90 when your DNS says
> 108.61.16.227|84.22.180.89|88.150.173.218 ?
> 
> Bad http proxy in the way?
> 
> Tru


I also checked to see if I had a .wgetrc - nope and the /etc/wgetrc file, all 
the lines are commented out.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum errors

[Wes James]

> On Dec 8, 2015, at 9:03 AM, Tru Huynh  wrote:
> 
> Hi,
> 
> 
> On Tue, Dec 08, 2015 at 08:24:34AM -0700, Wes James wrote:
>> 
> 
> ...
>> 
>> nslookup works:
>> 
>> Non-authoritative answer:
>> Name:mirrorlist.centos.org
>> Address: 108.61.16.227
>> Name:mirrorlist.centos.org
>> Address: 84.22.180.89
>> Name:mirrorlist.centos.org
>> Address: 88.150.173.218
>> 
>> but wget fails??
>> 
>> $ wget 
>> "http://mirrorlist.centos.org/?release=6=x86_64=os=stock;
>> --2015-12-08 08:04:15--  
>> http://mirrorlist.centos.org/?release=6=x86_64=os=stock
>> Resolving mirrorlist.centos.org... 199.187.126.90
>> Connecting to mirrorlist.centos.org|199.187.126.90|:80... 
>> failed: Connection timed out.
>> Retrying.
> why does your wget hit 199.187.126.90 when your DNS says
> 108.61.16.227|84.22.180.89|88.150.173.218 ?
> 
> Bad http proxy in the way?
> 
> Tru
> 

I started poking around in /etc/resolve.conf, /etc/nsswitch.conf and /etc/hosts 
and guess what I found in /etc/hosts?


199.187.126.90 mirrorlist.centos.org 


Not sure why the previous admin did this.  Is it an old mirror IP??  

I commented that line out and now yum update is working.

Insanity reigns…..

Thanks for everyones help :)

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

Re: [CentOS] yum errors

[Wes James]

> On Dec 8, 2015, at 9:21 AM, Richard  
> wrote:
> 
> 
> 
>> Date: Tuesday, December 08, 2015 09:17:20 -0700
>> From: Wes James 
>> 



> 
> You wouldn't happen to have an entry for mirrorlist.centos.org in
> your /etc/hosts file for some reason?
> 
> Also, what is on the line for the (uncommented out) "hosts:" entry
> in your /etc/nsswitch.conf file?
> 


That was it.  Your email arrived in my head before I got it here on the list :)

Thanks!

-wes

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

Re: [CentOS] yum errors

[Richard]

> Date: Tuesday, December 08, 2015 09:17:20 -0700
> From: Wes James 
> 
>> On Dec 8, 2015, at 9:03 AM, Tru Huynh  wrote:
>> 
>> Hi,
>> 
>> 
>> On Tue, Dec 08, 2015 at 08:24:34AM -0700, Wes James wrote:
>>> 
>> 
>> ...
>>> 
>>> nslookup works:
>>> 
>>> Non-authoritative answer:
>>> Name:   mirrorlist.centos.org
>>> Address: 108.61.16.227
>>> Name:   mirrorlist.centos.org
>>> Address: 84.22.180.89
>>> Name:   mirrorlist.centos.org
>>> Address: 88.150.173.218
>>> 
>>> but wget fails??
>>> 
>>> $ wget
>>> "http://mirrorlist.centos.org/?release=6=x86_64=os
>>> ra=stock" --2015-12-08 08:04:15--
>>> http://mirrorlist.centos.org/?release=6=x86_64=os
>>> a=stock Resolving mirrorlist.centos.org... 199.187.126.90
>>> Connecting to mirrorlist.centos.org|199.187.126.90|:80... 
>>> failed: Connection timed out.
>>> Retrying.
>> why does your wget hit 199.187.126.90 when your DNS says
>> 108.61.16.227|84.22.180.89|88.150.173.218 ?
>> 
>> Bad http proxy in the way?
>> 
> 
> 
> I just tried wget on my virtual box vm and it shows:
> 
> wget "http://mirrorlist.centos.org/?release=6=x86_64=os;
> --2015-12-08 09:12:33--
> http://mirrorlist.centos.org/?release=6=x86_64=os
> Resolving mirrorlist.centos.org... 108.61.16.227, 84.22.180.89,
> 88.150.173.218, ... Connecting to
> mirrorlist.centos.org|108.61.16.227|:80... connected. HTTP request
> sent, awaiting response... 200 OK
> Length: unspecified [text/plain]
> Saving to: “index.html?release=6=x86_64=os”
> 
> [ <=>
> ] 512 --.-K/s   in 0s  
> 
> 2015-12-08 09:12:34 (96.8 MB/s) -
> “index.html?release=6=x86_64=os” saved [512]
> 
> 
> 
> Why is wget resolving to 199.187….. on these other systems?
> 
> and nslookup shows the correct host resolution:
> 
> $ nslookup mirrorlist.centos.org
> 
> Non-authoritative answer:
> Name: mirrorlist.centos.org
> Address: 88.150.173.218
> Name: mirrorlist.centos.org
> Address: 84.22.180.89
> Name: mirrorlist.centos.org
> Address: 108.61.16.227
> 
> Thanks,
> 
> -wes

You wouldn't happen to have an entry for mirrorlist.centos.org in
your /etc/hosts file for some reason?

Also, what is on the line for the (uncommented out) "hosts:" entry
in your /etc/nsswitch.conf file?


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

Re: [CentOS] yum errors

[Wes James]

> On Dec 8, 2015, at 9:03 AM, Tru Huynh  wrote:
> 
> Hi,
> 
> 
> On Tue, Dec 08, 2015 at 08:24:34AM -0700, Wes James wrote:
>> 
> 
> ...
>> 
>> nslookup works:
>> 
>> Non-authoritative answer:
>> Name:mirrorlist.centos.org
>> Address: 108.61.16.227
>> Name:mirrorlist.centos.org
>> Address: 84.22.180.89
>> Name:mirrorlist.centos.org
>> Address: 88.150.173.218
>> 
>> but wget fails??
>> 
>> $ wget 
>> "http://mirrorlist.centos.org/?release=6=x86_64=os=stock;
>> --2015-12-08 08:04:15--  
>> http://mirrorlist.centos.org/?release=6=x86_64=os=stock
>> Resolving mirrorlist.centos.org... 199.187.126.90
>> Connecting to mirrorlist.centos.org|199.187.126.90|:80... 
>> failed: Connection timed out.
>> Retrying.
> why does your wget hit 199.187.126.90 when your DNS says
> 108.61.16.227|84.22.180.89|88.150.173.218 ?
> 
> Bad http proxy in the way?
> 
> Tru
> 
> -

Good point.  When I do wget on a working repo (a working local repo in a US 
state), it works fine, but it errors out on the mirrorlist.centos.org, which is 
odd.

I don’t need a proxy for this box, but is there a proxy file for wget that is 
fouling things up?  I’ll check.

Thanks,

-wes

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

[CentOS-virt] new install of Xen 4.6 hangs on Loading initial ramdisk

[President]

Not sure if this actually made it to the list the first time.  



Here is the SERIAL output (bottom of message after your questions).  Googling 
the error indicates it's something people ran into a few years back but was 
supposedly fixed.  Any ideas?



I can verify that if I REMOVE the second CPU, it boots into Xen kernel no 
problem.  The CPU itself doesn't matter, as I can swap either CPU into the 
first slot, and it boots.  Only if there is a second CPU does it fail.



-Original message-
From: George Dunlap 
Sent: Monday 30th November 2015 6:00
To: Discussion about the virtualization on CentOS 
Subject: Re: [CentOS-virt] new install of Xen 4.6 hangs on Loading initial 
ramdisk



On Fri, Nov 27, 2015 at 11:18 PM, Craig Thompson  > wrote:
First post to this list.  I would appreciate some help on this issue.

As background, I installed CentOS 7 on a Dell server, and then ran the 
following commands:

yum update 
http://buildlogs.centos.org/centos/7/virt/x86_64/xen/centos-release-xen-7-11.el7.x86_64.rpm
 

 
yum --enablerepo=centos-virt-xen-testing update
yum --enablerepo=centos-virt-xen-testing install xen

Doing that, I was able to successfully install Xen, create a virtual machine 
with its own HVM setup, logical volume, etc. and boot it just fine.

I then tried to do the same on an IBM x3550 server I’m trying to install with 
CentOS 7.  The CentOS 7 install went just fine.  I can boot into the standard 
kernel and have a working machine.  But after running the commands above to 
install the Xen hypervisor, the machine hangs on boot for a few moments after 
displaying the lines below and then reboots in a loop over and over and over:

Loading Xen 4.6.0-2.el7 …
Loading Linux 3.18.21-16.el7.x86_64 …
Loading initial ramdisk …

It never gets beyond that.  If I choose the stock kernel (no Xen) from the Grub 
menu, it will continue to boot into that just fine.

My grub.cfg file has these entries of note:

 multiboot /xen-4.6.0-2.el7.gz placeholder  dom0_mem=1024M,max:1024M cpuinfo 
com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all ${xen_rm_opts}
        echo    'Loading Linux 3.18.21-16.el7.x86_64 ...'
        module  /vmlinuz-3.18.21-16.el7.x86_64 placeholder 
root=UUID=9dc18146-f9b3-41cc-ba9c-7314689abcde ro crashkernel=auto debug 
irqpoll ipv6.disable=1 console=hvc0 earlyprintk=xen nomodeset
        echo    'Loading initial ramdisk ...'
        module  --nounzip   /initramfs-3.18.21-16.el7.x86_64.img


What I have tried:

1) adding debug into the vmlinuz line
2) disabling ipv6 in that line
3) adding root=UUID=9dc18146-f9b3-41cc-ba9c-7314689abcde to the last line AFTER 
/initramfs ….

Nothing so far has made any difference.  Obviously the process works, as it 
works for me just fine on the Dell server.

Underlying this machine is a SATA RAID 1 PCI card with two SSD drives attached 
in a RAID 1 mirror.  Not that that should matter, but I’m including it for 
reference. As noted previously, it boots into the stock kernel just fine.

Any help would be appreciated.

Thanks for the testing and the report.

Have you tried booting the Xen4CentOS kernel (Linux-3.18.21-16) by itself 
(i.e., not under Xen)?

Also, is there any chance you could get the output of a serial console?  That's 
pretty critical for debugging this sort of thing.
CentOS-virt mailing list


###  No such file or directory opening port
(XEN) Bad console= option 'tty'
 Xen 4.6.0-2.el7
(XEN) Xen version 4.6.0-2.el7 (mockbu...@centos.org) (gcc (GCC) 4.8.3 20140911 
(Red Hat 4.8.3-9)) debug=n Tue Nov  3 17:23:39 UTC 2015
(XEN) Latest ChangeSet: Mon Oct 19 12:05:21 2015 +0100 git:36b6fe9-dirty
(XEN) Bootloader: GRUB 2.02~beta2
(XEN) Command line: placeholder dom0_mem=1024M,max:1024M cpuinfo 
com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 2 seconds
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)   - 0009c800 (usable)
(XEN)  0009c800 - 000a (reserved)
(XEN)  000e - 0010 (reserved)
(XEN)  0010 - bffcba40 (usable)
(XEN)  bffcba40 - bffcee00 (ACPI data)
(XEN)  bffcee00 - c000 (reserved)
(XEN)  fec0 - 0001 (reserved)
(XEN)  0001 - 0001fee0 (usable)
(XEN)  0001fee0 - 0001fef0 (reserved)
(XEN)  0001fef0 - 0002fee0 (usable)
(XEN)  0002fee0 - 0002fef0 (reserved)
(XEN)  0002fef0 - 0003fee0 (usable)
(XEN)  0003fee0 - 0003fef0 (reserved)
(XEN)  0003fef0 - 00084000 (usable)

Re: [CentOS-virt] Xen build with XSAs through 163 in progress

[George Dunlap]

On Tue, Dec 8, 2015 at 12:23 PM, George Dunlap  wrote:
> Just a heads-up: A Xen package with XSAs through 163 is on its way
> through the build system.  I'll send an announcement when I've tagged
> it as ready to be propagated to the mirrors.
>
> As with the last XSA update, it will depend on having manually updated
> to the new Virt SIG repository layout.  If you haven't already please
> run the following in preparation:
>
> yum install 
> http://buildlogs.centos.org/centos/6/virt/x86_64/xen/centos-release-xen-7-11.el6.x86_64.rpm
>
> (And note that this package depends on a package from centos-extras,
> so if you have that repo disabled by default you'll need to enable it
> to perform the above command.)

...and the updated packages have now been signed and pushed to
mirror.centos.org.

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

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[Matthew Miller]

On Tue, Dec 08, 2015 at 10:46:58AM -0500, James B. Byrne wrote:
> > This is roughly true, although "downstream" RHEL makes its own
> > decisions about many things. If you (Mark, or anyone else) would like
> > to make this different in the future, getting involved with Fedora
> > Server is a good way to do so.
> However, to describe the Server List as an active forum for discussion
> would be somewhat overstating things.  I have not received anything

I didn't describe in that way. In fact, it *isn't* that. It's a mailing
list for working on the Fedora Server edition.

> from it as yet in December and the total volume of traffic on that
> list in November was very light.

I'm sure it will pick up as we get further into the Fedora 24 cycle.

> I am not sure in what way you envisage additional involvement is to
> take place.

It's an open source project. There are a lot of ways to be involved.
From your concerns, doing early testing and providing feedback on
system-wide features from a server perspective is one way. Or simply
doing QA in general. You could also help develop server roles matching
needs in your environment — that's a particular feature I'm hoping will
come from Fedora through RHEL to CentOS.


> I have been bitten by things done in Fedora that only have any use on
> a laptop and that should never have been allowed into a server
> distribution.  But I cannot see how I would have been aware of them
> until they manifested themselves on equipment under my care.  By which

^ right, this.

> time it is rather too late to influence the decision to include them. 

Well, not if you get involved early. That's the point.

If you don't *want* to, that's fine, but there's only so much complainy
cake that you can have and eat at the same time.

-- 
Matthew Millermat...@mattdm.org 
Fedora Project Leader  mat...@fedoraproject.org   
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS 6 pci audio card not enabled

[cl...@west.net]

CentOS 6 up-to-date 2.6.32-573.8.1.el6.x86_64
Gigabyte GA-Z68P-DS3
on-board audio BIOS disabled.
Intel I5
Pny 550Ti video
Envy 24HT pci audio module

I want to use the fiber in/out of the audio card, but it is not listed 
in System/Preferences/Sound/Hardware, only the HDMI is available.


It was installed in the pci slot when the system CentOS 6.0 was installed.

I have searched all over Google, but can't find a solution.

Does anyone have a solution for this problem ?

Advice will be appreciated. thanks in advance!




[mumbles@120db ~]$ aplay -l
 List of PLAYBACK Hardware Devices 
card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 7: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 8: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 9: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0


[mumbles@120db ~]$ lspci | grep -i audio
01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio 
Controller (rev a1)
05:00.0 Multimedia audio controller: VIA Technologies Inc. VT1720/24 
[Envy24PT/HT] PCI Multi-Channel Audio Controller (rev 01)


[mumbles@120db ~]$ lspci -k


01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio 
Controller (rev a1)

Subsystem: Device 196e:089c
Kernel driver in use: snd_hda_intel
Kernel modules: snd-hda-intel


05:00.0 Multimedia audio controller: VIA Technologies Inc. VT1720/24 
[Envy24PT/HT] PCI Multi-Channel Audio Controller (rev 01)

Subsystem: VIA Technologies Inc. Albatron PX865PE 7.1
Kernel modules: snd-ice1724


[mumbles@120db ~]$ lspci -n | grep 05:00.0
05:00.0 0401: 1412:1724 (rev 01)
[mumbles@120db ~]$ grep 1724 /lib/modules/$(uname -r)/modules.pcimap
snd-ice1724 0x1412 0x1724 0x 0x 0x 
0x 0x0


[mumbles@120db ~]$ modinfo snd-ice1724
filename: 
/lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/sound/pci/ice1712/snd-ice1724.ko

license: GPL
description: VIA ICEnsemble ICE1724/1720 (Envy24HT/PT)
author: Jaroslav Kysela 
srcversion: 4159E44B9111EFB98548209
alias: pci:v1412d1724sv*sd*bc*sc*i*
depends: 
snd,snd-ac97-codec,snd-pcm,snd-i2c,snd-ice17xx-ak4xxx,snd-rawmidi,snd-pt2258,snd-ak4xxx-adda,snd-ak4114

vermagic: 2.6.32-573.8.1.el6.x86_64 SMP mod_unload modversions
parm: index:Index value for ICE1724 soundcard. (array of int)
parm: id:ID string for ICE1724 soundcard. (array of charp)
parm: enable:Enable ICE1724 soundcard. (array of bool)
parm: model:Use the given board model. (array of charp)
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] openvpn + routing

[Helmut Drodofsky]

default route normally is

0.0.0.0/0

to overwrite default you can
- erase the existing an add the new one: this change is to do vice 
versa: an start up and shut down; so you need an installation dependend 
information about the default Gateway.


Alternativly you can add two routes:
0.0.0.0 netmask 128.0.0.0 and
128.0.0.0 netmask 128.0.0.0

then you have routes, that overwrites the existing default. You have 
only to add this specific routes on openvpn up and delete on openvpn down.



--
Viele Grüße
Helmut Drodofsky
 
Internet XS Service GmbH

Heßbrühlstraße 15
70565 Stuttgart
  Geschäftsführung
Dr.-Ing. Roswitha Hahn-Drodofsky
HRB 21091 Stuttgart
USt.ID: DE190582774
Tel. 0711 781941 0
Fax: 0711 781941 79
Mail: i...@internet-xs.de
www.internet-xs.de

Am 07.12.2015 um 18:29 schrieb John R Pierce:

On 12/7/2015 8:40 AM, m.r...@5-cent.us wrote:

>there is one route missing:
>
>128.0.0.0/1.
>

Did you mean 127.0.0.0?


and I hope not /1 or that would encompass all networks with the first 
octet from 128-255






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

Re: [CentOS-virt] How to manually add a new interface to a bridge device?

[Zoltan Frombach]

I would stop the VM, edit its definition file (that's an XML file) and then
start it up. But be careful: After you edit the XML file, you need to
execute a command so KVM re-reads that file. I forgot that command, but you
can look it up on Google.
On Dec 9, 2015 7:52 AM, "Howard Leadmon"  wrote:

>
>
> Maybe my google-fu is failing me, but I have spent the past couple hours
> looking at how to add a vnet? Device to my KVM host running CentOS 6, and
> for the life of me I can’t get this going.
>
>
>
> From all my research if I want to add a device I should just do ‘brctl
> addif br1 vnet14’ if I want to add a vnet14 to bridge br1.   When I do
> this, I get:
>
>
>
> # brctl addif br0 vnet14
>
> interface vnet14 does not exist!
>
>
>
>
>
> If I run a ‘brctl show’ I get the following:
>
>
>
> # brctl show
>
> bridge name bridge id   STP enabled interfaces
>
> br0 8000.00237dd22a4c   no  eth0
>
> vnet0
>
> vnet10
>
> vnet11
>
> vnet13
>
> vnet2
>
>vnet3
>
> vnet4
>
> vnet6
>
> vnet8
>
> br1 8000.00237dd22a50   no  eth1
>
> vnet1
>
> vnet12
>
> vnet5
>
> vnet7
>
> vnet9
>
>
>
>
>
> Needless to say the existing vnet?? Devices are in use on guest VM’s
> currently.
>
>
>
> When I create a new VM using virt-install, I usually add the following to
> my command line:
>
>
>
> --network=bridge:br0 --network=bridge:br1
>
>
>
> I messed up building a new VM, and only added the br0 interface to the VM,
> but need the br1 interface as well.  So my question is, or a pointer to how
> I can add that br1 interface to my existing VM, and create the needed
> vnet14 interface for it to attach to?
>
>
>
> If anyone can explain how to do this, or give me a good pointer on where
> the info is on how to do this, it would sure be a huge help..
>
>
>
> Thanks…
>
>
>
>
>
> ---
>
> Howard Leadmon
>
>
>
> ___
> CentOS-virt mailing list
> CentOS-virt@centos.org
> https://lists.centos.org/mailman/listinfo/centos-virt
>
>
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

[CentOS] tsocks or equivalent for CentOS 7

[Leroy Tennison]

Does such exist? I looked for dante and couldn't find that. I found and tried 
using a version from CentOS 6 but it didn't work. If anyone can point me to an 
rpm (or set of same) I would most certainly appreciate it. Thanks. 


Confidentiality Notice | This email and any included attachments may be 
privileged, confidential and/or otherwise protected from disclosure.  Access to 
this email by anyone other than the intended recipient is unauthorized.  If you 
believe you have received this email in error, please contact the sender 
immediately and delete all copies.  If you are not the intended recipient, you 
are notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] tsocks or equivalent for CentOS 7

[John R Pierce]

On 12/8/2015 2:56 PM, Leroy Tennison wrote:

Does such exist? I looked for dante and couldn't find that. I found and tried 
using a version from CentOS 6 but it didn't work. If anyone can point me to an 
rpm (or set of same) I would most certainly appreciate it. Thanks.


this?  http://tsocks.sourceforge.net/

not updated since 2002 as 'beta 5'  ?!?sounds like abandonware.



--
john r pierce, recycling bits in santa cruz

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

Re: [CentOS-virt] win2008r2 update on centos 6 host made system unbootable

[Dennis Jacobfeuerborn]

On 09.12.2015 00:39, NightLightHosts Admin wrote:
> On Tue, Dec 8, 2015 at 5:26 PM, Dennis Jacobfeuerborn
>  wrote:
>> Hi,
>> today we ran into a strange problem: When performing a regular Windows
>> 2008r2 update apparently among other things the following was installed:
>> "SUSE - Storage Controller - SUSE Block Driver for Windows"
>>
>> Previously the disk drive was using the Red Hat virtio drivers which
>> worked just fine but after the reboot after the update I just get a blue
>> screen indicating that Windows cannot find a boot device.
>>
>> Does anyone understand what is going on here? Why is the windows update
>> installing a Suse driver that overrides the Red Hat driver even though
>> it is apparently incompatible with the system?
>>
>> Regards,
>>   Dennis
> 
> Did you roll back the driver and did it work after that?

I can't roll back the driver for that device because I can't boot the
system. The only way I can boot into the system is by changing the disk
type to IDE but then I cannot roll back the driver because the entire
device changed. As far as I can tell the Suse version of the virtio
block driver is incompatible with the incompatible with the system but
right now I see no way to tell windows "Uninstall the driver completely
for the entire system" so that on the next boot it would fall back to
the old virtio driver from Red Hat.
I tried installing the current stable drivers from this URL:
https://fedoraproject.org/wiki/Windows_Virtio_Drivers

But Windows refuses and says the driver is already up-to-date.

What worries me is that I want to update other win2008r2 guests as well
but now fear that they will all be rendered unbootable by such an update.

Regards,
  Dennis

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

Re: [CentOS-virt] win2008r2 update on centos 6 host made system unbootable

[NightLightHosts Admin]

On Tue, Dec 8, 2015 at 5:26 PM, Dennis Jacobfeuerborn
 wrote:
> Hi,
> today we ran into a strange problem: When performing a regular Windows
> 2008r2 update apparently among other things the following was installed:
> "SUSE - Storage Controller - SUSE Block Driver for Windows"
>
> Previously the disk drive was using the Red Hat virtio drivers which
> worked just fine but after the reboot after the update I just get a blue
> screen indicating that Windows cannot find a boot device.
>
> Does anyone understand what is going on here? Why is the windows update
> installing a Suse driver that overrides the Red Hat driver even though
> it is apparently incompatible with the system?
>
> Regards,
>   Dennis

Did you roll back the driver and did it work after that?
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

[CentOS-virt] How to manually add a new interface to a bridge device?

[Howard Leadmon]

 

Maybe my google-fu is failing me, but I have spent the past couple hours
looking at how to add a vnet? Device to my KVM host running CentOS 6, and
for the life of me I can't get this going.

 

>From all my research if I want to add a device I should just do 'brctl addif
br1 vnet14' if I want to add a vnet14 to bridge br1.   When I do this, I
get:

 

# brctl addif br0 vnet14

interface vnet14 does not exist!

 

 

If I run a 'brctl show' I get the following:

 

# brctl show

bridge name bridge id   STP enabled interfaces

br0 8000.00237dd22a4c   no  eth0

vnet0

vnet10

vnet11

vnet13

vnet2

   vnet3

vnet4

vnet6

vnet8

br1 8000.00237dd22a50   no  eth1

vnet1

vnet12

vnet5

vnet7

vnet9

 

 

Needless to say the existing vnet?? Devices are in use on guest VM's
currently.

 

When I create a new VM using virt-install, I usually add the following to my
command line:

 

--network=bridge:br0 --network=bridge:br1

 

I messed up building a new VM, and only added the br0 interface to the VM,
but need the br1 interface as well.  So my question is, or a pointer to how
I can add that br1 interface to my existing VM, and create the needed vnet14
interface for it to attach to?

 

If anyone can explain how to do this, or give me a good pointer on where the
info is on how to do this, it would sure be a huge help..

 

Thanks.

 

 

---

Howard Leadmon 

 

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