Re: [CentOS] yum errors

[Rob Kampen]

On 12/08/2015 06: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)


Now, what happened? Did it connect and download correctly? If so do the
following:

$ cat index.html\?release=6\=x86_64\=os\=stock

You should basically get the mirror list:

http://mirrors.coreix.net/centos/6.7/os/x86_64/
http://centos.serverspace.co.uk/centos/6.7/os/x86_64/
http://mirrors.melbourne.co.uk/sites/ftp.centos.org/centos/6.7/os/x86_64/
http://mirrors.vooservers.com/centos/6.7/os/x86_64/
http://mirror.mhd.uk.as44574.net/mirror.centos.org/6.7/os/x86_64/
http://www.mirrorservice.org/sites/mirror.centos.org/6.7/os/x86_64/
http://mirrors.clouvider.net/CentOS/6.7/os/x86_64/
http://mirrors.ukfast.co.uk/sites/ftp.centos.org/6.7/os/x86_64/
http://mirror.cov.ukservers.com/centos/6.7/os/x86_64/

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

[James Hogarth]

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...
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] 7.2 kernel panic on boot

[Karanbir Singh]

On 07/12/15 04:11, Greg Lindahl wrote:
> On Sun, Dec 06, 2015 at 09:22:15PM -0500, Jonathan Billings wrote:
>> On Sun, Dec 06, 2015 at 06:35:58PM +, Timothy Murphy wrote:
>>> Always Learning wrote:
>>>
 I always admire Johnny's prose, passion for Centos and his calm approach
 to everything.
>>>
>>> Agreed.
>>> But two possibly OT and probably ignorant queries:
>>>
>>> 1. I am running a standard Centos 32-bit system on my home servers.
>>> I keep them up-to-date, but have not re-booted for several months.
>>> I see from /etc/centos-release that I am running 7.1.
>>> If I re-booted would this become 7.2?
>>>
>>> 2. If so, is this kernel panic a widespread phenomenon?
>>
>> You're running the 32-bit AltArch build of CentOS?
>>
>> The /etc/centos-release is owned by the centos-release package, and
>> the contents will be updated when you update that pacakge.  A reboot
>> won't change that.  In the default x86_64 release, I think that you'd
>> need to pull updates from the CR repo to get the 7.2.1511 packages,
>> still. 
> 
> And just look at the confusion -- because the website almost never
> mentions 7.1.1053 or 7.2.1511, it can be really hard to understand
> this discussion -- one person using "7.1" and "7.2" and the other
> using "7.2.1511". Good thing the 2nd person didn't use "7 (1511)",
> like the website does.

Note that there is a /etc/centos-release-upstream as well that
identifies what ver of the upstream we are currently tracking.

> Oh, wait: CentOS, love it or leave it.

I hope its not that drastic!

There are multiple issues and fallouts etc here, start from the fact
that the point number isnt really much other than a datestamp, to who
and how it gets used and for what purpose etc. But the thing that
bothers me most is that the reason as to why we are doing this and how
its implemented isnt clear to people on this thread.

eg. when we were doing x.y, RHEL wasent. They were on a X release, and
all the other point in time data was communicated outside of that scope
( eg in EL3 / 4 etc ). I believe being pragmatic around this, and
delivering value into areas that needed it most is good thing for us and
the userbase at large - however, if we are breaking systems for existing
setup's then we should address that. I took onboard all the feedback
from 7 release time and I believe the system we have in place now should
work for most people ( no one has been able to demonstrate a problem
space in the distro as such ).

If the issue is around communication and how we export the metadata /
mindset - I totally take on board that we've had serious issues in that
space. Even the fact that there is a CR/ repo isnt something most people
understand or even know about, its something we should fix.

Greg's pointed out the website version reporting, and its a great point
- however, note that we are already working on fixing that side of
things by bringing all Download specific info into 1 place, and doing
this on the wiki ( wiki.centos.org/Download ) - we are moving all
version specific content away from the website; the net result being
that the website becomes about the project, and the wiki becomes the
defacto source for all things content ( linux distro, sig's content,
user help etc ). This is also primarily driven by the fact that we've
struggled to keep the site updated and relevant, whereas the wiki with
its much larger user base and contributor base has far better churn.

So lets workout what the tangible issues are, and then work on resolving
those.

I will end by saying that we have more than a few million monthly
instances out there now, in container space, in cloud space, in
developer instances - and all of those people have hugely benefited from
the new visioning.

I certainly dont want you to leave!

regards

-- 
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] 7.2 kernel panic on boot

[Karanbir Singh]

On 07/12/15 13:03, Johnny Hughes wrote:

> 2.  The Alternative Arches (i686, armhpc, aarch64) are not necessarily
> updated as quickly as the main arches.  That is one of the reasons they
> are AltArch and not a main arch.  However, we are working hard on all of
> those as well.

power7 and 8 ( both BE and LE ) are pretty close as well


-- 
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] Version numbering vis a vis CentOS and RHEL

[John Hodrien]

On Mon, 7 Dec 2015, Phelps, Matthew wrote:


- Coordination of other repositories (e.g. EPEL) is based on the "version",
how does that work now?


Exactly the same as it did before.  Before you'd have a $maj.$min repo, which
is the same as it is now.  maj=7 min=1.1503

You can park it there and not suffer any problems as I understand it.  At
least that's what I've done with 7.  So when 7.2 finally hits, it'll be maj=7
min=2.1512


All of these things ran in parallel with the RHEL release cycle, and the
work could be done at the same time. That was the overriding philosophy of
CentOS, "we are a recompile of RHEL." Now, the impression is (rightly or
wrongly, it doesn't matter to me) CentOS is totally becoming a separate
Linux distro, and needs to be treated as such. And that has huge
implications for system administrators in a large environment. Huge.


I don't see it as an issue.  A partially updated (without touching CR) 7.1.X
is equivalent to a partially update 7.1 RHEL.


There are answers to all these questions, but there is a lot of confusion
that's been generated by this seemingly cosmetic change in version numbers.
I've checked, and there was no,"We're considering creating this basic
difference from RHEL, how will this affect you?" on this list, or the
website, etc. From our viewpoint, it was sprung on us out of nowhere, and
now were being told "deal with it, or leave."


To me, I'm not sure I get any issues or advantages from the new scheme, but I
can't say it bothers me greatly.

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

Re: [CentOS] 7.2 kernel panic on boot

[Jonathan Billings]

On Mon, Dec 07, 2015 at 07:03:53AM -0600, Johnny Hughes wrote:
> 1.  The CentOS Release package does not get updated until the full
> release.  It will not be updated in CR repo, but will be part of the
> final rollout which includes installable ISOs, etc.  Neither will
> Anaconda, which will also be updated in the full upcoming release.
> 
> The CR repo is the rest of the updates (earlier that the final release)
> as we still to the final QA. This is all spelled out here:
> 
> https://wiki.centos.org/AdditionalResources/Repositories/CR

Ah, I didn't know that.  Makes sense.

My point was just that /etc/centos-release reflects the packages you
have installed, and not what kernel you've booted into.

However, /etc/issue is intepreted by the login service to use your
kernel release so it will reflect your kernel.


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

[CentOS] Version numbering vis a vis CentOS and RHEL

[Phelps, Matthew]

OK, I'm staring a new thread.

On Mon, Dec 7, 2015 at 9:53 AM, Timothy Murphy  wrote:

> Phelps, Matthew wrote:
>
> >> > Oh, wait: CentOS, love it or leave it.
> >>
> >> Correct.
> >>
> >> In fact, I would prefer you leave.
> >
> > Really?
> >
> > This is what we're dealing with now?
> >
> > OK. I will recommend we move away from CentOS.
>
> This seems to be raising what to me is a trivial issue
> to an absurd level of hostility.
> Johnny Hughes' comment was uncharacteristically harsh;
> and yours is even harsher.
>
> To me, CentOS is a highly stable OS for my home servers,
> and I am eternally grateful to Johnny Hughes and his colleagues
> for carrying out what looks to me like an impossibly complex task.
>
> The numbering of packages is a very small part of this.
> On the other hand, a kernel panic would be very worrying to me
> if it were in fact likely to happen.
> I am glad to hear that I have no need to worry.
>

To you, and probably a majority of CentOS users, the "version number" of
CentOS is indeed a trivial, cosmetic issue.

However, there are those of us who use CentOS in a very large enterprise
environment. That is, in fact, the intended audience of the whole distro.
When there is a "new version" of Red Hat (and I know that means nothing
with hundreds of constantly updating packages; however, my bosses don't get
that),  and hence CentOS, there is a huge amount of work that needs to be
done in a typical enterprise. These include, but are not limited to:

- setting up a new internal-only mirror of the distribution
- setting up a new tftp/PXEboot/kickstart environment for network installs.
- Editing several install scripts to match the new environment
- Testing all these changes
- Checking that all security recommendations/edicts from a higher authority
(e.g. the US Government), which are also based on the "version", are
followed
- Checking that all commercial software supports the release (most of these
use "RHEL X.y", what is that in CentOS now?)
- Trying to get support from commercial software when the "version numbers"
don't match
- Coordination of other repositories (e.g. EPEL) is based on the "version",
how does that work now?

All of these things ran in parallel with the RHEL release cycle, and the
work could be done at the same time. That was the overriding philosophy of
CentOS, "we are a recompile of RHEL." Now, the impression is (rightly or
wrongly, it doesn't matter to me) CentOS is totally becoming a separate
Linux distro, and needs to be treated as such. And that has huge
implications for system administrators in a large environment. Huge.

There are answers to all these questions, but there is a lot of confusion
that's been generated by this seemingly cosmetic change in version numbers.
I've checked, and there was no,"We're considering creating this basic
difference from RHEL, how will this affect you?" on this list, or the
website, etc. From our viewpoint, it was sprung on us out of nowhere, and
now were being told "deal with it, or leave."

It sucks.


-- 
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] 7.2 kernel panic on boot

[Timothy Murphy]

Phelps, Matthew wrote:

>> > Oh, wait: CentOS, love it or leave it.
>>
>> Correct.
>>
>> In fact, I would prefer you leave.
> 
> Really?
> 
> This is what we're dealing with now?
> 
> OK. I will recommend we move away from CentOS.

This seems to be raising what to me is a trivial issue
to an absurd level of hostility.
Johnny Hughes' comment was uncharacteristically harsh;
and yours is even harsher.

To me, CentOS is a highly stable OS for my home servers,
and I am eternally grateful to Johnny Hughes and his colleagues
for carrying out what looks to me like an impossibly complex task.

The numbering of packages is a very small part of this.
On the other hand, a kernel panic would be very worrying to me
if it were in fact likely to happen.
I am glad to hear that I have no need to worry.


-- 
Timothy Murphy  
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin


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

Re: [CentOS] 7.2 kernel panic on boot

[Akemi Yagi]

On Mon, Dec 7, 2015 at 4:45 AM, Johnny Hughes  wrote:
> On 12/06/2015 10:11 PM, Greg Lindahl wrote:
(bit snip)
>> Oh, wait: CentOS, love it or leave it.
>
> Correct.
>
> In fact, I would prefer you leave.

No, I would prefer ALL of you leave. All of you who are not addressing
the OP's issue should leave the thread. Just start a new thread, not
here. Enough is enough (/me saying in the same tone as President Obama
referring to the gun violence in the US).

Now back to the topic...

This bug report:

https://bugs.centos.org/view.php?id=9860

and its upstream (RH) reference:

https://bugzilla.redhat.com/show_bug.cgi?id=1285235

might possibly be related to the kernel panic the original poster
reported. There is a workaround that may be worth a try:

Boot with the kernel parameter :

initcall_blacklist=clocksource_done_booting

Akemi
___
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 16:17, Phelps, Matthew wrote:
> 
> IRC is not a good choice for communicating with IT admins in a large
> enterprise environment. It is usually blocked.
> 

Does google hangout work ? we might be able to also setup a phone dial
in setup

-- 
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] Version numbering vis a vis CentOS and RHEL

[Phelps, Matthew]

On Mon, Dec 7, 2015 at 11:27 AM, Karanbir Singh 
wrote:

> On 07/12/15 16:17, Phelps, Matthew wrote:
> >
> > IRC is not a good choice for communicating with IT admins in a large
> > enterprise environment. It is usually blocked.
> >
>
> Does google hangout work ? we might be able to also setup a phone dial
> in setup
>
> --
> 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
>


In my case, yes, Hangouts works.

However, in general, any time dependent method is a problem since there's
probably some fire to be put out at any given hour.

I, and I suspect others, would prefer asynchronous communications so we can
contribute when we have time.

-- 
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] openvpn + routing

[m . roth]

Helmut Drodofsky wrote:
> Hello,
>
> there is one route missing:
>
> 128.0.0.0/1.
>
Did you mean 127.0.0.0?

  mark

> config client:
> route-nopull
> redirect-gateway def1 bypass-dhcp
>
> best regards
> Helmut
>
> 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 06.12.2015 um 20:26 schrieb Axel Glienke:
>> Hello,
>>
>> i have a little question.
>>
>> My system:
>>
>> ip route:
>> 0.0.0.0/1 via 10.8.0.5 dev tun0
>> default via 192.168.2.1 dev br0  proto static  metric 425
>> 10.8.0.1 via 10.8.0.5 dev tun0
>> 10.8.0.5 dev tun0  proto kernel  scope link  src 10.8.0.6
>> 88.198.140.127 via 192.168.2.1 dev br0
>> 192.168.2.0/24 dev br0  proto kernel  scope link  src 192.168.2.101
>> metric 425
>> 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
>>
>>
>> traceroute gmx.de
>> traceroute to gmx.de (213.165.65.60), 30 hops max, 60 byte packets
>>  1  Speedport.ip (192.168.2.1)  0.578 ms  0.662 ms  0.859 ms
>> ^C
>>
>> [root@h1 ~]# traceroute spiegel.de
>> traceroute to spiegel.de (62.138.116.3), 30 hops max, 60 byte packets
>>  1  10.8.0.1 (10.8.0.1)  35.009 ms  34.982 ms  34.956 ms
>>
>> Why the routing is different, in first case over br0 in second over
>> the vpn device?
>>
>>
>> How can i disable "push default route" from the server-directive on
>> client-side in OpenVPN?
>> I want, that only traffic, incoming over tun0 routing back over tun0.
>> Is this possible with firewalld-cmd?
>>
>> Thx.
>>
>> Grüße
>>
>> Axel
>>
>> ___
>> 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] Version numbering vis a vis CentOS and RHEL

[m . roth]

1. Thank you, Matthew, for a new thread. This had nothing to do with the o/p
of the old thread.
2. I'm not sure what more can possibly be said that hasn't already. Can we
end this, unless the Board decides to solicit our opinion, and
get back to solving issues?
3. Board of CentOS: some folks don't care about the numbering, but it bothers
a *lot* of us, and at least to me, that doesn't seem like a huge deal
to change; it's not something critical to the distro. Therefore, I'm
politely asking you to revisit the issue in your meetings, and
reconsider the x.y.# (e.g., 7.1.1511).

   mark, still struggling with bareos and windows

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

Re: [CentOS] openvpn + routing

[Helmut Drodofsky]

Hello,

there is one route missing:

128.0.0.0/1.

config client:
route-nopull
redirect-gateway def1 bypass-dhcp

best regards
Helmut

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 06.12.2015 um 20:26 schrieb Axel Glienke:

Hello,

i have a little question.

My system:

ip route:
0.0.0.0/1 via 10.8.0.5 dev tun0
default via 192.168.2.1 dev br0  proto static  metric 425
10.8.0.1 via 10.8.0.5 dev tun0
10.8.0.5 dev tun0  proto kernel  scope link  src 10.8.0.6
88.198.140.127 via 192.168.2.1 dev br0
192.168.2.0/24 dev br0  proto kernel  scope link  src 192.168.2.101  
metric 425

192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1


traceroute gmx.de
traceroute to gmx.de (213.165.65.60), 30 hops max, 60 byte packets
 1  Speedport.ip (192.168.2.1)  0.578 ms  0.662 ms  0.859 ms
^C

[root@h1 ~]# traceroute spiegel.de
traceroute to spiegel.de (62.138.116.3), 30 hops max, 60 byte packets
 1  10.8.0.1 (10.8.0.1)  35.009 ms  34.982 ms  34.956 ms

Why the routing is different, in first case over br0 in second over 
the vpn device?



How can i disable "push default route" from the server-directive on 
client-side in OpenVPN?
I want, that only traffic, incoming over tun0 routing back over tun0. 
Is this possible with firewalld-cmd?


Thx.

Grüße

Axel

___
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] Version numbering vis a vis CentOS and RHEL

[Karanbir Singh]

On 07/12/15 15:52, John Hodrien wrote:

> To me, I'm not sure I get any issues or advantages from the new scheme,
> but I
> can't say it bothers me greatly.

This is the thing that bothers me most - that folks dont have a good
grasp on what / why the numbering is working like this.

We are still a small team, and all efforts are flat out on getting the
iso media and images done, out of the door - but as soon as I have this
done, I'll look at hosting some google hangouts, irc sessions and maybe
a longer email thread as well to lay out the numbering proposition.

-- 
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] Version numbering vis a vis CentOS and RHEL

[Phelps, Matthew]

On Mon, Dec 7, 2015 at 11:12 AM, Karanbir Singh 
wrote:

> On 07/12/15 15:52, John Hodrien wrote:
>
> > To me, I'm not sure I get any issues or advantages from the new scheme,
> > but I
> > can't say it bothers me greatly.
>
> This is the thing that bothers me most - that folks dont have a good
> grasp on what / why the numbering is working like this.
>
> We are still a small team, and all efforts are flat out on getting the
> iso media and images done, out of the door - but as soon as I have this
> done, I'll look at hosting some google hangouts, irc sessions and maybe
> a longer email thread as well to lay out the numbering proposition.
>
> --
> 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
>


IRC is not a good choice for communicating with IT admins in a large
enterprise environment. It is usually blocked.

-- 
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] openvpn + routing

[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



--
john r pierce, recycling bits in santa cruz

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

Re: [CentOS] 7.2 kernel panic on boot

[Johnny Hughes]

On 12/06/2015 10:11 PM, Greg Lindahl wrote:
> On Sun, Dec 06, 2015 at 09:22:15PM -0500, Jonathan Billings wrote:
>> On Sun, Dec 06, 2015 at 06:35:58PM +, Timothy Murphy wrote:
>>> Always Learning wrote:
>>>
 I always admire Johnny's prose, passion for Centos and his calm approach
 to everything.
>>>
>>> Agreed.
>>> But two possibly OT and probably ignorant queries:
>>>
>>> 1. I am running a standard Centos 32-bit system on my home servers.
>>> I keep them up-to-date, but have not re-booted for several months.
>>> I see from /etc/centos-release that I am running 7.1.
>>> If I re-booted would this become 7.2?
>>>
>>> 2. If so, is this kernel panic a widespread phenomenon?
>>
>> You're running the 32-bit AltArch build of CentOS?
>>
>> The /etc/centos-release is owned by the centos-release package, and
>> the contents will be updated when you update that pacakge.  A reboot
>> won't change that.  In the default x86_64 release, I think that you'd
>> need to pull updates from the CR repo to get the 7.2.1511 packages,
>> still. 
> 
> And just look at the confusion -- because the website almost never
> mentions 7.1.1053 or 7.2.1511, it can be really hard to understand
> this discussion -- one person using "7.1" and "7.2" and the other
> using "7.2.1511". Good thing the 2nd person didn't use "7 (1511)",
> like the website does.
> 
> Oh, wait: CentOS, love it or leave it.

Correct.

In fact, I would prefer you leave.




signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] 7.2 kernel panic on boot

[Phelps, Matthew]

On Dec 7, 2015 07:45, "Johnny Hughes"  wrote:
>
> On 12/06/2015 10:11 PM, Greg Lindahl wrote:
> > On Sun, Dec 06, 2015 at 09:22:15PM -0500, Jonathan Billings wrote:
> >> On Sun, Dec 06, 2015 at 06:35:58PM +, Timothy Murphy wrote:
> >>> Always Learning wrote:
> >>>
>  I always admire Johnny's prose, passion for Centos and his calm
approach
>  to everything.
> >>>
> >>> Agreed.
> >>> But two possibly OT and probably ignorant queries:
> >>>
> >>> 1. I am running a standard Centos 32-bit system on my home servers.
> >>> I keep them up-to-date, but have not re-booted for several months.
> >>> I see from /etc/centos-release that I am running 7.1.
> >>> If I re-booted would this become 7.2?
> >>>
> >>> 2. If so, is this kernel panic a widespread phenomenon?
> >>
> >> You're running the 32-bit AltArch build of CentOS?
> >>
> >> The /etc/centos-release is owned by the centos-release package, and
> >> the contents will be updated when you update that pacakge.  A reboot
> >> won't change that.  In the default x86_64 release, I think that you'd
> >> need to pull updates from the CR repo to get the 7.2.1511 packages,
> >> still.
> >
> > And just look at the confusion -- because the website almost never
> > mentions 7.1.1053 or 7.2.1511, it can be really hard to understand
> > this discussion -- one person using "7.1" and "7.2" and the other
> > using "7.2.1511". Good thing the 2nd person didn't use "7 (1511)",
> > like the website does.
> >
> > Oh, wait: CentOS, love it or leave it.
>
> Correct.
>
> In fact, I would prefer you leave.
>
>
>

Really?

This is what we're dealing with now?

OK. I will recommend we move away from CentOS.

Good job.
___
> 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] 7.2 kernel panic on boot

[Johnny Hughes]

On 12/06/2015 08:22 PM, Jonathan Billings wrote:
> On Sun, Dec 06, 2015 at 06:35:58PM +, Timothy Murphy wrote:
>> Always Learning wrote:
>>
>>> I always admire Johnny's prose, passion for Centos and his calm approach
>>> to everything.
>>
>> Agreed.
>> But two possibly OT and probably ignorant queries:
>>
>> 1. I am running a standard Centos 32-bit system on my home servers.
>> I keep them up-to-date, but have not re-booted for several months.
>> I see from /etc/centos-release that I am running 7.1.
>> If I re-booted would this become 7.2?
>>
>> 2. If so, is this kernel panic a widespread phenomenon?
> 
> You're running the 32-bit AltArch build of CentOS?
> 
> The /etc/centos-release is owned by the centos-release package, and
> the contents will be updated when you update that pacakge.  A reboot
> won't change that.  In the default x86_64 release, I think that you'd
> need to pull updates from the CR repo to get the 7.2.1511 packages,
> still. 
> 
> 
> 

1.  The CentOS Release package does not get updated until the full
release.  It will not be updated in CR repo, but will be part of the
final rollout which includes installable ISOs, etc.  Neither will
Anaconda, which will also be updated in the full upcoming release.

The CR repo is the rest of the updates (earlier that the final release)
as we still to the final QA. This is all spelled out here:

https://wiki.centos.org/AdditionalResources/Repositories/CR

2.  The Alternative Arches (i686, armhpc, aarch64) are not necessarily
updated as quickly as the main arches.  That is one of the reasons they
are AltArch and not a main arch.  However, we are working hard on all of
those as well.

I actually expect that I will have the CR stuff ready in the next 48
hours for i686.

I know that armhfp (that is Arm32) minimal tree is also already done and
available for 7.2.1511 (these are testing releases for Arm32):

https://lists.centos.org/pipermail/arm-dev/2015-December/001343.html

The aarch64 packages are also mostly built, but they require some more work.

3.  This kernel issue, to the best of my knowledge on this thread, is
one person who had an issue on one x86_64 install .. but it us hard to
tell as there is much discussion on the thread that has nothing to do
with that kernel ooops.







signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum errors

[Wes James]

> On Nov 20, 2015, at 11:55 AM, Wes James  wrote:
> 
>> 
>> On Nov 20, 2015, at 10:41 AM, Jim Perrin  wrote:
>> 
>> It should be looking at /6/ instead of a specific point release. We
>> (CentOS) do not provide updates for individual point releases. You are
>> several years behind in security and bug-fix updates. Once a specific
>> minor version is expired, it is moved off the main mirrors and into the
>> vault. The current iteration of the /6/ tree is 6.7, so everything below
>> that is no longer available on the mirrors. Have you modified your
>> repository files or are they stock?
>> 
>> I might suggest starting off with a 'yum clean all', then running your
>> query again.
>> 
>> 
>> 
>> On 11/20/2015 11:21 AM, Wes James wrote:
>>> I have inherited centos 6.3 and 6.2 vms in an esxi environment.  When I do
>>> 
>>> yum provides ntpd
>>> 
>>> on the 6.3 box I get a lot of errors like:
>>> 
>>> Loaded plugins: fastestmirror, presto
>>> Loading mirror speeds from cached hostfile
>>> * base: mirror.unl.edu
>>> * extras: mirrors.cmich.edu
>>> * updates: mirror.steadfast.net
>>> http://mirror.unl.edu/centos/6.4/os/x86_64/repodata/repomd.xml: [Errno 14] 
>>> PYCURL ERROR 22 
> 
> 
> I fixed the problem for now by editing /etc/yum.repos.d/CentOS-Base.repy, 
> commenting out:
> 
> mirrorlist=
> 
> then finding a local university that has /6/ repo data and uncommenting and 
> using:
> 
> baseurl=
> 
> 
> I’m not sure why this box was having issues reaching mirrorlist.centos.org 
>  or even tracerouting to it  It kept 
> getting a different trace than my 6.4 virtualbox.


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.

Thanks,

wes

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

Re: [CentOS] Centos 7 Yum conflict libicalss

[Peter]

On 07/12/15 18:55, John R Pierce wrote:
> On 12/6/2015 9:28 PM, david wrote:
>> Thanks for that.  It appears to have solved the problem.  I just
>> wonder if it should have been taken care of "automatically" without my
>> intervention, running nightly "yum -y update" commands.
> 
> epel needs to fix that package, probably.

They did, as of yesterday (when I ran into the same problem) I found it
in koji, build completed, waiting to be placed into -testing.  I
installed it directly from the koji link and it solved the issue:

http://koji.fedoraproject.org/koji/buildinfo?buildID=703093


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

[CentOS] Using typescript as a default shell?

[Benjamin Smith]

Is it possible to use 'script' command that records what happens in a session 
as the default shell? How could you deal with multiple logins at once? What 
about output from rsync and the like? 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Using typescript as a default shell?

[Frank Cox]

On Mon, 07 Dec 2015 11:21:13 -0800
Benjamin Smith wrote:

> Is it possible to use 'script' command that records what happens in a session 
> as the default shell? How could you deal with multiple logins at once? What 
> about output from rsync and the like? 

What problem are you attempting to solve?  Have you looked at the bash 
'history' command?

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Using typescript as a default shell?

[Benjamin Smith]

On Monday, December 07, 2015 01:29:54 PM Frank Cox wrote:
> Benjamin Smith wrote:
> > Is it possible to use 'script' command that records what happens in a
> > session as the default shell? How could you deal with multiple logins at
> > once? What about output from rsync and the like?
> 
> What problem are you attempting to solve?  Have you looked at the bash
> 'history' command?

We'd like to have an auditable history of what happened on production servers, 
kept for a period of time. (perhaps a week?) It's a very busy production 
environment, but the only shell-level access to the systems are 
administrative, but having a history of activity as well as the output would 
have been highly valuable this morning to verify that a mistake that might 
have been made was. (or wasn't!)

I'm familiar with `history`but it has a few problems: 

1) You only see the commands entered. 
2) You only see the commands in other shells after you log out.
3) You don't see the output from the commands. 
4) Histories can be lost altogether if the shell exits abnormally. (EG tcp 
timeout) 

I was thinking of a shell script something like (PSEUDO code) 

#! /bin/sh
LOGFILE=`date --format='Ymd:Hms'`; 
script /var/log/histories/root.$LOGFILE
exit $? 

And putting it as the shell in /etc/passwd, but this *has* to be the kind of 
thing that somebody else has done, right? 
___
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]

[m . roth]

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.

1. Ignoring the several hundred log, etc, emails I deal with at work
  every day, I'm currently on at least 5 mailing lists, including
  this one, each ranging in business from 10-30 emails/day.
2. I work full time as a sysadmin, dealing with over 178 workstations,
  servers, and clusters.
3. I actually have a life outside of computers.
4. I don't notice any response to the huge and vehement reaction to systemd.

Given all that, how much more of my life should I spend on yet *another*
busy list, esp. when I do *not* want to install fedora, and debug an o/s
at home?

   mark "had to come in an hour early to bring up servers
   in the datacenter due to power work over the weekend,
   so, yes, I *am* a bit testy"

___
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]

[m . roth]

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.

Oh, one more thing: as I posted (by request) on Bruce Schneir's blog last
week, one thing that has *always* really annoyed me is when architects or
developers DON'T TALK TO END USERS, but some manager who *knows* what
needs to happen designs the whole thing. Too many times I've seen the end
result: end users, the mass of folks who have to use it, range from
dislike to loathing, and avoid using something that *should* have made
their life easier at work, instead making it *much* harder, until they
have no choice.

I've been pleased that the folks on this list have been solicited several
times in the last six months for our opinions.

   mark

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

Re: [CentOS] 7.2 kernel panic on boot

[Gordon Messmer]

On 12/07/2015 06:31 AM, Karanbir Singh wrote:

On 07/12/15 04:11, Greg Lindahl wrote:

Oh, wait: CentOS, love it or leave it.

I hope its not that drastic!


As a member of the user community, it's hard to see it any other way.

I want to be fair to everyone, so I'll acknowledge that Greg was making 
an ass of himself.  He said so, himself.  I also think that the question 
of what release the problem occurred on is irrelevant. The relevant 
question is the version of the kernel package, not the centos-release 
package.


But that aside, I think that Greg was right in that the version notation 
used in the wiki (https://wiki.centos.org/Download) is unnecessarily 
inconsistent with older releases.  The rpm version for centos-release is 
7-1.1503.  The version reflected in /etc/centos-release is 7.1.1503.  
But text on the wiki omits a portion of that version number.  Greg was 
consistent and (in my opinion) clear that he was suggesting that the 
wiki be consistent with the numbering used elsewhere.


Johnny's response ignored that suggestion completely, and defended the 
version numbering scheme, which was not in question.  And in his very 
first response, he said, "CentOS-7 Base OS is still there, it is free 
for anyone to use ... If you don't want to use it.. That is your choice."


Can you see why that would be interpreted as "love it or leave it?"

It has been my impression for a long time that the CentOS developers are 
reluctant to engage the community in contributing to the project, and 
this is a fairly good example of why that impression endures.



There are multiple issues and fallouts etc here, start from the fact
that the point number isnt really much other than a datestamp


Arguably, that's all any version number is.  Isn't it?

But your response, like Johnny's ignores what Greg actually suggested: 
that the wiki use a version number consistent with the rpm version 
number and the content of /etc/centos-release.



Greg's pointed out the website version reporting, and its a great point
- however, note that we are already working on fixing that side of
things by bringing all Download specific info into 1 place, and doing
this on the wiki ( wiki.centos.org/Download )


Yes, the wiki is where the problem is.  That's the same URL that Greg 
mentioned originally.



This is also primarily driven by the fact that we've
struggled to keep the site updated and relevant, whereas the wiki with
its much larger user base and contributor base has far better churn.


I would interpret that as an invitation to participate in the project, 
but I created an account on the wiki and don't seem to be able to edit 
anything.


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

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

[Zdenek Sedlak]

On 12/07/2015 05:46 PM, Phelps, Matthew wrote:
> On Mon, Dec 7, 2015 at 11:27 AM, Karanbir Singh 
> wrote:
> 
>> On 07/12/15 16:17, Phelps, Matthew wrote:
>>>
>>> IRC is not a good choice for communicating with IT admins in a large
>>> enterprise environment. It is usually blocked.
>>>
>>
>> Does google hangout work ? we might be able to also setup a phone dial
>> in setup
>>
>> --
>> 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
>>
> 
> 
> In my case, yes, Hangouts works.
> 
> However, in general, any time dependent method is a problem since there's
> probably some fire to be put out at any given hour.
> 
> I, and I suspect others, would prefer asynchronous communications so we can
> contribute when we have time.
> 

Hi Matthew,

your concerns caught my attention. We are maintaining a good amount of
Linux servers, both RHEL and CentOS, and always used our own numbering
scheme in form of major.minor.patchset, where the patchset is a
sequential number telling how many times we generated the patchset, like
5.11.5, 6.7.2 and so on.

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? In that case, simply
ignore the build number in your scripts and use major.minor only as before.

Just my 2 cents...

Best regards
Zdenek Sedlak
Infrastructure Architect

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

Re: [CentOS] Using typescript as a default shell?

[Jake Shipton]

Benjamin Smith wrote:
> On Monday, December 07, 2015 01:29:54 PM Frank Cox wrote:
>> Benjamin Smith wrote:
>>> Is it possible to use 'script' command that records what happens in a
>>> session as the default shell? How could you deal with multiple logins at
>>> once? What about output from rsync and the like?
>>
>> What problem are you attempting to solve?  Have you looked at the bash
>> 'history' command?
> 
> We'd like to have an auditable history of what happened on production 
> servers, 
> kept for a period of time. (perhaps a week?) It's a very busy production 
> environment, but the only shell-level access to the systems are 
> administrative, but having a history of activity as well as the output would 
> have been highly valuable this morning to verify that a mistake that might 
> have been made was. (or wasn't!)
> 
> I'm familiar with `history`but it has a few problems: 
> 
> 1) You only see the commands entered. 
> 2) You only see the commands in other shells after you log out.
> 3) You don't see the output from the commands. 
> 4) Histories can be lost altogether if the shell exits abnormally. (EG tcp 
> timeout) 
> 
> I was thinking of a shell script something like (PSEUDO code) 
> 
> #! /bin/sh
> LOGFILE=`date --format='Ymd:Hms'`; 
> script /var/log/histories/root.$LOGFILE
> exit $? 
> 
> And putting it as the shell in /etc/passwd, but this *has* to be the kind of 
> thing that somebody else has done, right? 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
> 

Hi,

While not solving all your problems ZSH may be of help. With ZSH you can
configure it to save history immediately upon command being entered and
therefore never lose the history. Although, you can still lose it if
someone purposely deletes it. But then the same can be applied to any
shell logger.

Additionally this means recent commands will be in the history file as
soon as they run, thus you do not have to close the shell in order to
view the recent commands run.

Using .zshrc it's simply the case of using "setopts inc_appendhistory"
to get that functionality.

Although getting used to a whole new shell could be a bit of a challenge
if you are very used to BASH.

There's also many other features which may be helpful to you. Such as
time stamps and shared history.

Search "history" on this page to see more:
http://linux.die.net/man/1/zshoptions

I personally use ZSH where-ever possible as I personally find it to be
better than BASH, however this is more of a preference than anything.

Good luck though :-)

Kind Regards,
Jake Shipton (JakeMS)
Twitter: @CrazyLinuxNerd
GPG Key: 0xE3C31D8F
GPG Fingerprint: 7515 CC63 19BD 06F9 400A DE8A 1D0B A5CF E3C3 1D8F
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Using typescript as a default shell?

[Jonathan Billings]

On Mon, Dec 07, 2015 at 11:40:08AM -0800, Benjamin Smith wrote:
> We'd like to have an auditable history of what happened on production 
> servers, 
> kept for a period of time. (perhaps a week?) It's a very busy production 
> environment, but the only shell-level access to the systems are 
> administrative, but having a history of activity as well as the output would 
> have been highly valuable this morning to verify that a mistake that might 
> have been made was. (or wasn't!)

You can use auditd to do this, but it won't capture the output, just
the command and its exit code.  

To go along with the zsh suggestion, I believe that you can compile
ksh93 to include auditing, but it's not enabled on any of my systems. 

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

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

[Greg Lindahl]

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.

-- greg


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

[CentOS] A bareos question

[m . roth]

I've upgraded to 15.2, which has a webui. However, I'd like to tell it to
use kerboros, not a hard-coded password in a configuration file.

Any clues?

 mark

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

Re: [CentOS] 7.2 kernel panic on boot

[Warren Young]

On Dec 7, 2015, at 12:54 PM, Gordon Messmer  wrote:
> 
> It has been my impression for a long time that the CentOS developers are 
> reluctant to engage the community in contributing to the project

Who is “contributing” here?  Where’s the patch?  All I see is a bunch of 
bikeshedding.

The new version numbering scheme was created to solve a real problem, which 
CentOS has been fighting for years.[*]

If you change anything about the version numbering scheme within the 7 line, 
you break automated workflows that were debugged and deployed a year ago.  The 
time to make such a change is 8 at earliest, and I’d argue that switching 
*again* after the 7 effort would cause more problems than it solves.

Remember, this distro is about stability.  Changing naming/numbering schemes in 
a way that breaks scripts is about as far from stability as you can get.


[*] With every release from CentOS 3.1 through 6.7, there was always a series 
of mailing list questions of the same basic form: “FooApp is only certified for 
CentOS 6.4, but CentOS 6.7 is out, and the vendor won’t update the 
certification, so how do I keep my servers on CentOS 6.4?”   Just as there is 
no CentOS 7.2, only 7, there was no CentOS 6.4, only 6.  The new scheme tries 
to make that clear.

It would actually *be* clear if the tail (CentOS) could wag the dog (Red Hat) 
here and get them to adopt the YYMM respin scheme.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

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

[Warren Young]

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.
___
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]

[Matthew Miller]

On Mon, Dec 07, 2015 at 02:23:21PM -0500, m.r...@5-cent.us wrote:
> 1. Ignoring the several hundred log, etc, emails I deal with at work
>   every day, I'm currently on at least 5 mailing lists, including
>   this one, each ranging in business from 10-30 emails/day.

I didn't say you have to. I'm just offering a way for you to make a
difference.

> 2. I work full time as a sysadmin, dealing with over 178 workstations,
>   servers, and clusters.

Okay. 


> 3. I actually have a life outside of computers.

Yay!

> 4. I don't notice any response to the huge and vehement reaction to systemd.

Well, to be honest, probably because you weren't paying attention due
to 1, 2, and 3. :)



-- 
Matthew Miller

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

Re: [CentOS] 7.2 kernel panic on boot

[Gordon Messmer]

On 12/07/2015 02:35 PM, Warren Young wrote:

The new version numbering scheme was created to solve a real problem, which 
CentOS has been fighting for years.


I don't know how to be any more clear than I was.  Neither Greg nor I 
(as far as I can tell) were suggesting that the version numbering be 
changed, only that it be consistent with the rpm and centos-release 
files where it is used on the wiki.

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

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

[J Martin Rushton]

-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.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJWZhltAAoJEAF3yXsqtyBlyAoP/2/kIa8gzhiNKoCRPFbFW/AT
2B15B/BDdBhIYN66Ux58cScMwfBt5Z9McozvWp2yJurr5CSrxG4wywXS6sfyRrYw
7J4oplTc5lmaxZkyQIidYVJ0Rwf9h0gCPx2TW7aoPcjh9YcqtjS4zZP1AHRuMY56
Wkt2RfuAaq3LUlRD4TwPNA3UMgvR18N3L9H7p2hXxYvswmKzWzTNt0M1AD8BeLBf
S9cUSKGgAHikexjm6gmKQ2Nxb6xGcQE4lgPRCP/57cM5hX3rvhvTH4URj1+VUGw0
hd135wVk//AeK+lHXbm3ejNV/UC/sRx/JAOsaC2FYsBvfggsCuc0CUUxaGAOLZtt
cfDLJgqKQdy59XAuWjRzw3Z4m+IPqSxeBopPDTwzUOiZQYxxOq2LZO2XQHzxbO+d
VMqarwOp3n4nZvBDUeq+Q80LrrZtMGRlPtVA/YFHazVJPZ9Xo5ugV9QrdZrPO4kE
LzrwjWevRT64g1mOInSSyWrOqFbXXMrZbAeJ88csUSTAaGwVDU3vZ3tAMuar8IKa
k2IJBDBBDYQB5XZEkny5wTecS+/0B2M2ylEVyWe6GvvS5er+O6iop0Ej74O4OwGy
FA7OwV7pzmWxnyzn4L/YUxAYSsSVL5rTdEAUGpFcetDd4oQssyV0Z9OtWKNeJIkx
P+ZlCDMcxY08ajJenqm8
=SSct
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-announce] CESA-2015:2549 Moderate CentOS 6 libxml2 Security Update

[Johnny Hughes]

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-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

Re: [CentOS] 7.2 kernel panic on boot

[Duncan Brown]

On 07/12/2015 18:35, Akemi Yagi wrote:

On Mon, Dec 7, 2015 at 10:18 AM, Duncan Brown  wrote:

On 07/12/2015 14:40, Akemi Yagi wrote:

This bug report:

https://bugs.centos.org/view.php?id=9860

and its upstream (RH) reference:

https://bugzilla.redhat.com/show_bug.cgi?id=1285235

might possibly be related to the kernel panic the original poster
reported. There is a workaround that may be worth a try:

Boot with the kernel parameter :

initcall_blacklist=clocksource_done_booting

Akemi


Thanks Akemi, that worked perfectly

That is indeed good news.

Now, this is only a workaround. As seen in the RH bugzilla, the patch
is in the z-series kernel and the target is set to "7.3". That will be
CentOS 7 (1605) [or later]. At any rate it's several months from now.
If we are able to identify the patch, it will be possible to include
it in the centosplus kernel.

Akemi
___

Thats great, thank you

I'll keep an eye on the bug report

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

Re: [CentOS] 7.2 kernel panic on boot

[Duncan Brown]

On 07/12/2015 14:40, Akemi Yagi wrote:

On Mon, Dec 7, 2015 at 4:45 AM, Johnny Hughes  wrote:

On 12/06/2015 10:11 PM, Greg Lindahl wrote:

(bit snip)

Oh, wait: CentOS, love it or leave it.

Correct.

In fact, I would prefer you leave.

No, I would prefer ALL of you leave. All of you who are not addressing
the OP's issue should leave the thread. Just start a new thread, not
here. Enough is enough (/me saying in the same tone as President Obama
referring to the gun violence in the US).

Now back to the topic...

This bug report:

https://bugs.centos.org/view.php?id=9860

and its upstream (RH) reference:

https://bugzilla.redhat.com/show_bug.cgi?id=1285235

might possibly be related to the kernel panic the original poster
reported. There is a workaround that may be worth a try:

Boot with the kernel parameter :

initcall_blacklist=clocksource_done_booting

Akemi


Thanks Akemi, that worked perfectly

I've managed this twice in a week now, a simple question on the 
mythtv-users list ended up turning into a huge debate about 4k TV's


http://lists.mythtv.org/pipermail/mythtv-users/2015-December/383441.html

Still got the problem sorted though so all good I guess!

cheers

Duncan




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

Re: [CentOS] 7.2 kernel panic on boot

[Marcelo Ricardo Leitner]

Em 07-12-2015 16:35, Akemi Yagi escreveu:

On Mon, Dec 7, 2015 at 10:18 AM, Duncan Brown  wrote:

On 07/12/2015 14:40, Akemi Yagi wrote:




This bug report:

https://bugs.centos.org/view.php?id=9860

and its upstream (RH) reference:

https://bugzilla.redhat.com/show_bug.cgi?id=1285235

might possibly be related to the kernel panic the original poster
reported. There is a workaround that may be worth a try:

Boot with the kernel parameter :

initcall_blacklist=clocksource_done_booting

Akemi


Thanks Akemi, that worked perfectly


That is indeed good news.


Wow, nice one, thanks!

  Marcelo

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

Re: [CentOS] 7.2 kernel panic on boot

[Akemi Yagi]

On Mon, Dec 7, 2015 at 10:18 AM, Duncan Brown  wrote:
> On 07/12/2015 14:40, Akemi Yagi wrote:

>>
>> This bug report:
>>
>> https://bugs.centos.org/view.php?id=9860
>>
>> and its upstream (RH) reference:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1285235
>>
>> might possibly be related to the kernel panic the original poster
>> reported. There is a workaround that may be worth a try:
>>
>> Boot with the kernel parameter :
>>
>> initcall_blacklist=clocksource_done_booting
>>
>> Akemi
>>
> Thanks Akemi, that worked perfectly

That is indeed good news.

Now, this is only a workaround. As seen in the RH bugzilla, the patch
is in the z-series kernel and the target is set to "7.3". That will be
CentOS 7 (1605) [or later]. At any rate it's several months from now.
If we are able to identify the patch, it will be possible to include
it in the centosplus kernel.

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

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

[Matthew Miller]

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.


-- 
Matthew Miller

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

Re: [CentOS] About CentOS Marks

[Jake Shipton]

Takuya Yamamoto wrote:
> Hello
> 
> https://www.centos.org/legal/trademarks/
> 
> According to above, I found following message.
> --
> Notwithstanding anything to the contrary provided in these Guidelines, the 
> following are examples of unacceptable uses:
> 
> 1.Use of the CentOS Marks in connection with commercial redistribution of 
> CentOS software
> --
> 
> I have a question.
> What means "Use of the CentOS Marks"?
> 
> For example,
> While CentOS is booting up, CentOS show the CentOS logo on Full screen.
> Is it unacceptable? Or acceptable?
> If commercial redistribution of CentOS software, Developer have to hide this 
> logo?
> 
> For example,
> CentOS System is working, user can show the "CentOS" text words on console.
> Is it unacceptable? Or acceptable?
> 
> 
> ---
> Yamamoto Takuya


Hello,

I'll try to answer this for you, however please note I am not a lawyer
and do not hold an authoritative position of the CentOS distribution. I
am just a regular user like you.

I'm fairly certain in most cases that using CentOS and its trademarks
are perfectly acceptable and allowed for example if you are doing the
two options above.

However, you will run into a problem if you modify CentOS Sources, for
example making a derivative distribution (like CentOS is to RHEL) then
tried to call it "CentOS Scientific Linux" and tried to sell it as your
own work. In this case you would have to rebrand to "Scientific Linux"
and cannot (legally) use the CentOS trademarks in this case.

This is also for the same reason CentOS is called "Community Enterprise
Operating System" instead of "Red Hat Enterprise Linux Community Edition".

So if you had plans to remake or alter CentOS in major ways (Source code
editing) to redistribute as your own work, you cannot call it CentOS.

However, if you are for example working for a commercial employer you
are free to install, setup, configure and run CentOS on any commercial
or non-commercial machine at any time without risk of breaking the
trademark rules.

In the case that you need additional software included with your
installation media then a self-made repository is probably the best
option as you can legally include a "kickstart"[1] file with your
installation media to include the extra repository and install the extra
software.

I hope this is able to answer your question.

[1]
https://github.com/rhinstaller/pykickstart/blob/master/docs/kickstart-docs.rst

Kind Regards,
Jake Shipton
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum errors

[Wes James]

> 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

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

Re: [CentOS] yum errors

[Wes James]

> 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
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum errors

[Wes James]

> 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

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

[Greg Lindahl]

On Mon, Dec 07, 2015 at 03:37:27PM -0700, Warren Young wrote:
> On Dec 7, 2015, at 1:52 PM, Greg Lindahl  wrote:
> > 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?”

I'm missing the connection. That's the kind of thing that's a FAQ. If
you look back in this list archive, you'll see me answering that
question here, and pointing out that the answer is buried in the FAQ
on the website. (Never fixed despite many comments, but hey, why fix
things that are problems?)

I don't see why putting the same thing in /etc/centos-release and
the website causes this problem to be significantly worse.

I do see how the current "7 (1503)" on the website confuses many
humans, including experienced CentOS admins.


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

Re: [CentOS] yum errors

[Jake Shipton]

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)


Now, what happened? Did it connect and download correctly? If so do the
following:

$ cat index.html\?release=6\=x86_64\=os\=stock

You should basically get the mirror list:

http://mirrors.coreix.net/centos/6.7/os/x86_64/
http://centos.serverspace.co.uk/centos/6.7/os/x86_64/
http://mirrors.melbourne.co.uk/sites/ftp.centos.org/centos/6.7/os/x86_64/
http://mirrors.vooservers.com/centos/6.7/os/x86_64/

Re: [CentOS-es] Falla proxy transparente, con Centos 7

[paulcriollo]

Se descarto los dns funcionan  correctamente, se estaba usando el squid
3.38, también le puse la versión 3.4, 3.5 y hasta la 4 que es beta, pero
nada.
también como prueba adicional, probé la configuración de este howto, sigue
la falla
en los logs de squid puedo ver este error  *TCP_MISS/503* Error , cuando
deseo acceder las paginas con problemas.
Att.
PAUL CRIOLLO

El 2 de diciembre de 2015, 11:11, Pablo Alberto Flores 
escribió:

> revisa tu windows dns server, es ahí tu drama.
>
>
> El 2 de diciembre de 2015, 13:08, Ramón Macías Zamora 
> escribió:
>
> > entonces, el problema está en la resolución local de los clientes.
> >
> > Asegúrate que en el cliente se realice la resolución correctamente y ahí
> es
> > casi seguro que te funcionará.
> >
> > saludos
> >
> >
> > --
> >
> >
> >
> > Ramón Macías Zamora
> > Tecnología, Investigación y Desarrollo
> > www.rks.ec - www.raykasolutions.com
> > Guayaquil - Ecuador
> > msn:ramon_mac...@hotmail.com
> > skype:  ramon_macias
> > UserLinux# 180926 (http://counter.li.org)
> > Cel:593-8-0192238
> > Tel:593 4 6044566
> >
> > 
> >
> >
> > WEB SITES, HOSTINGS, DOMINIOS, MANTENIMIENTO DE EQUIPOS, REDES,
> SERVIDORES
> > LINUX, SOPORTE.
> >
> > 2015-12-02 10:43 GMT-05:00 :
> >
> > > desactive proxy squid transparente y solo deje el nat del firewall,
> alli
> > si
> > > funciona con todos los dns estas paginas..
> > > pero yo si deseo que funcione mi proxy
> > >
> > > El 2 de diciembre de 2015, 10:14, Pablo Alberto Flores <
> > pabfl...@uchile.cl
> > > >
> > > escribió:
> > >
> > > > el sport y dport del puerto 53 no lo bloqueas verdad.
> > > >
> > > > tcpdump que dice
> > > >
> > > >
> > > > El 2 de diciembre de 2015, 12:12,  escribió:
> > > >
> > > > > probé con los 2 dns internos y los publicos, igual se bloquea
> > > > >
> > > > > El 2 de diciembre de 2015, 10:06, Pablo Alberto Flores <
> > > > pabfl...@uchile.cl
> > > > > >
> > > > > escribió:
> > > > >
> > > > > > revisa con tcpdump los paquetes que son descartados y por quien.
> > > > > >
> > > > > > Ahora tus clientes estan configurados para utilizar el dns
> interno
> > de
> > > > > > windows server, dns de proxy o dns de ISP.
> > > > > >
> > > > > > Solo para descartar que tu wintendo sea el problema, configura el
> > > > resolv
> > > > > y
> > > > > > un cliente con los dns del IPS o google.
> > > > > >
> > > > > > el sport y dport del puerto 53 no lo bloqueas verdad.
> > > > > >
> > > > > >
> > > > > > El 2 de diciembre de 2015, 11:47, 
> > escribió:
> > > > > >
> > > > > > > tengo un dns interno en un windows server, aparte un dns
> interno
> > en
> > > > el
> > > > > > > mismo firewall linux, en el linux si resuelve esa web, pero en
> > las
> > > > pcs
> > > > > > > clientes no resuelve.
> > > > > > > att.
> > > > > > >
> > > > > > > paul criollo
> > > > > > >
> > > > > > > El 2 de diciembre de 2015, 9:35, Ramón Macías Zamora <
> > > rmac...@rks.ec
> > > > >
> > > > > > > escribió:
> > > > > > >
> > > > > > > > y si buscas la resolución desde el servidor?
> > > > > > > >
> > > > > > > > nslookup apps5.mineco.gob.pe
> > > > > > > >
> > > > > > > > Tiene configurador dentro del squid dns_nameservers ?
> > > > > > > >
> > > > > > > > Saludos
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Ramón Macías Zamora
> > > > > > > > Tecnología, Investigación y Desarrollo
> > > > > > > > www.rks.ec - www.raykasolutions.com
> > > > > > > > Guayaquil - Ecuador
> > > > > > > > msn:ramon_mac...@hotmail.com
> > > > > > > > skype:  ramon_macias
> > > > > > > > UserLinux# 180926 (http://counter.li.org)
> > > > > > > > Cel:593-8-0192238
> > > > > > > > Tel:593 4 6044566
> > > > > > > >
> > > > > > > > 
> > > > > > > >
> > > > > > > >
> > > > > > > > WEB SITES, HOSTINGS, DOMINIOS, MANTENIMIENTO DE EQUIPOS,
> REDES,
> > > > > > > SERVIDORES
> > > > > > > > LINUX, SOPORTE.
> > > > > > > >
> > > > > > > > 2015-12-02 8:37 GMT-05:00 :
> > > > > > > >
> > > > > > > > > pING SI tengo a esa web
> > > > > > > > >
> > > > > > > > > El 2 de diciembre de 2015, 8:08, Pablo Alberto Flores <
> > > > > > > > pabfl...@uchile.cl>
> > > > > > > > > escribió:
> > > > > > > > >
> > > > > > > > > > y desde el proxy puede hacer ping a la web verdad.
> > > > > > > > > > intenta con agregar los dns que ocupas en tu archivo
> > > squid.conf
> > > > > > > > > >
> > > > > > > > > > Saludos Pablo
> > > > > > > > > >
> > > > > > > > > > El 2 de diciembre de 2015, 10:00,  >
> > > > > > escribió:
> > > > > > > > > >
> > > > > > > > > > > Reporta, que no encuentra la web, como que no
> existiera.
> > > > > > > > > > >
> > > > > > > > > > > El 30 de noviembre de 2015, 10:05, Diego Chacón <
> > > > > > > > di...@gridshield.net>
> > > > > > > > > > > escribió:
> 

Re: [CentOS] yum errors

[Wes James]

> 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)
> 
> 
> Now, what happened? Did it connect and download correctly? If so do the
> following:
> 
> $ cat index.html\?release=6\=x86_64\=os\=stock
> 
> You should