[CentOS] C7 on Dell Precision 7530

2019-03-08 Thread wwp
Hello,

does anybody have experience with installing and running CentOS 7 on
Dell Precision 7530 series (w/ Intel gfx chipset if that matters)?
It can be bought w/ Ubuntu 16.04 LTS pre-installed (which doesn't
attract me at all), but prior to use such hw model at work, I'd like to
understand where I'm going to. Especially after my bad experiences
installing C7 on "modern" (read since skylake variants) hardware
whereas Ubuntu variants went better, gosh. Or maybe I should wait for
C8.

Of course I did dig the Internet for intel, found very few stuff and
this: https://access.redhat.com/ecosystem/hardware/3431551

Regards,

-- 
wwp


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


Re: [CentOS] CentOS 8 Artwork needed

2019-03-08 Thread mark
Leon Fauster via CentOS wrote:
>> Am 08.03.2019 um 15:56 schrieb Robert Moskowitz :
>> On 3/8/19 5:55 AM, J Martin Rushton via CentOS wrote:
>>> On 07/03/2019 20:45, Rich Bowen wrote:

 To all the artists and designers here, we need your help.
 With RHEL 8 beta released, we need to start producing artwork for
 CentOS
 8. It's time for the CentOS Artwork SIG, and anyone else that's
 interested in contributing to this effort, to start working on
 everything that will be needed for the new release.

 What we know we need is anaconda artwork, and new desktop
 backgrounds to replace the current '7' themed stuff.

>>
>> Perhaps avoid a blue background.
>>
>> Supposedly there is solid research now that blues are bad for our
>> eyes...
>
> https://doi.org/10.1371/journal.pone.0071398

So, you're telling us old folks that we shouldn't go outside, or look up
at the sky?

(Why, yes, since you ask, I did just have cataract surgery the beginning
of Dec, and I've been sitting at a desk job, full time, programming or
sysadmin, for a long career)

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


Re: [CentOS] CentOS 8 Artwork needed

2019-03-08 Thread Leon Fauster via CentOS


> Am 08.03.2019 um 15:56 schrieb Robert Moskowitz :
> 
> 
> 
> On 3/8/19 5:55 AM, J Martin Rushton via CentOS wrote:
>> On 07/03/2019 20:45, Rich Bowen wrote:
>>> To all the artists and designers here, we need your help.
>>> 
>>> With RHEL 8 beta released, we need to start producing artwork for CentOS
>>> 8. It's time for the CentOS Artwork SIG, and anyone else that's
>>> interested in contributing to this effort, to start working on
>>> everything that will be needed for the new release.
>>> 
>>> What we know we need is anaconda artwork, and new desktop backgrounds to
>>> replace the current '7' themed stuff.
>>> 
>>> As we dig, we may find more things that need to be updated to the new 8
>>> theme.
>>> 
>>> Additionally, we will need to update some of the assets listed here:
>>> https://wiki.centos.org/ArtWork/Identity
>>> 
>>> ... and produce new assets for 8 to be listed here:
>>> https://wiki.centos.org/ArtWork/Brand/Logo
>>> 
>>> And, finally, we need someone to step up to lead this effort.
>>> 
>>> While we don't yet know for certain when RHEL 8 will officially release,
>>> it's safe to assume that it's soon, and we need your help.
>>> 
>> I'm no artist, so I won't even attempt to actually create artwork.
>> 
>> Having said that, with the current increase in interest in space
>> activity the old Apollo 8 logo might give us some inspiration.  See
>> https://en.wikipedia.org/wiki/File:Apollo-8-patch.png for the original.
>> 
>> My initial though is for the CentOS logo where the earth is and some
>> sort of future at the Moon end.  Perhaps a star?  I'm a programmer not a
>> "creative" so I'll allow artistic types to decide.  If obscuring the
>> CentOS logo with the lower band of the "8" is unacceptable, then it
>> would be possible to keep the Earth and put the CentOS logo in place of
>> the Moon.  Not as strong a message, but still fun.
>> 
>> The three astronauts' names cound be replaced with the word "CentOS", a
>> slogan (please not "to infinity and beyond"), or simply blanked.  The
>> colour scheme will obviously depend upon corporate diktat.
> 
> Perhaps avoid a blue background.
> 
> Supposedly there is solid research now that blues are bad for our eyes...
> 

https://doi.org/10.1371/journal.pone.0071398

--
LF

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


[CentOS-announce] CESA-2019:0230 Important CentOS 7 polkit Security Update

2019-03-08 Thread Johnny Hughes


CentOS Errata and Security Advisory 2019:0230 Important

Upstream details at : https://access.redhat.com/errata/RHSA-2019:0230

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

x86_64:
0df2b8477aa99ea7221643459c947b956f387dc010c63b3f1c92ab01c01cab6a  
polkit-0.112-18.el7_6.1.i686.rpm
b7efc34c3dc4f8d6fb51b0695c4b7225a7767edf64902cacc541a65bcafb5053  
polkit-0.112-18.el7_6.1.x86_64.rpm
19d8382626658664654d7cfb84fad2020d67b1da7ed163126e53773e1cf0dd09  
polkit-devel-0.112-18.el7_6.1.i686.rpm
1c83b760d4639e6c68c8ac8ff564b83e8352967c8ca2db31694acd0f775e2299  
polkit-devel-0.112-18.el7_6.1.x86_64.rpm
4edbcd1d840915c92917faccaa72f9b6fca911abd73252b37ed8c160a86cfd1a  
polkit-docs-0.112-18.el7_6.1.noarch.rpm

Source:
72043fa864750f6491a5b9fff2bd25a13a4973a2623002caae262e3b2f3f1e45  
polkit-0.112-18.el7_6.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] CentOS 8 Artwork needed

2019-03-08 Thread Robert Moskowitz




On 3/8/19 5:55 AM, J Martin Rushton via CentOS wrote:

On 07/03/2019 20:45, Rich Bowen wrote:

To all the artists and designers here, we need your help.

With RHEL 8 beta released, we need to start producing artwork for CentOS
8. It's time for the CentOS Artwork SIG, and anyone else that's
interested in contributing to this effort, to start working on
everything that will be needed for the new release.

What we know we need is anaconda artwork, and new desktop backgrounds to
replace the current '7' themed stuff.

As we dig, we may find more things that need to be updated to the new 8
theme.

Additionally, we will need to update some of the assets listed here:
https://wiki.centos.org/ArtWork/Identity

... and produce new assets for 8 to be listed here:
https://wiki.centos.org/ArtWork/Brand/Logo

And, finally, we need someone to step up to lead this effort.

While we don't yet know for certain when RHEL 8 will officially release,
it's safe to assume that it's soon, and we need your help.


I'm no artist, so I won't even attempt to actually create artwork.

Having said that, with the current increase in interest in space
activity the old Apollo 8 logo might give us some inspiration.  See
https://en.wikipedia.org/wiki/File:Apollo-8-patch.png for the original.

My initial though is for the CentOS logo where the earth is and some
sort of future at the Moon end.  Perhaps a star?  I'm a programmer not a
"creative" so I'll allow artistic types to decide.  If obscuring the
CentOS logo with the lower band of the "8" is unacceptable, then it
would be possible to keep the Earth and put the CentOS logo in place of
the Moon.  Not as strong a message, but still fun.

The three astronauts' names cound be replaced with the word "CentOS", a
slogan (please not "to infinity and beyond"), or simply blanked.  The
colour scheme will obviously depend upon corporate diktat.


Perhaps avoid a blue background.

Supposedly there is solid research now that blues are bad for our eyes...

My $0.02 worth.


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


Re: [CentOS] elasticsearch connection refused (solved)

2019-03-08 Thread Ralf Prengel



> Am 22.02.2019 um 04:06 schrieb Keith Keller 
> :
> 
>> On 2019-02-19, Pete Biggs  wrote:
>>> On Tue, 2019-02-19 at 14:26 +, Pete Biggs wrote:
>>> 
>>> It's not a web server port - elasticsearch is a database.
>> 
>> Sorry, that was a bit abrupt - yes, it sort of looks like a web server.
> 
> It's a bit of both.  It is queryable like a database, but it answers
> requests using HTTP 


Hallo,
se-linux was active.
My automated installation in the office disables se-linux but this was a manual 
private setup.
Thanks for all hints
Ralf

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


Re: [CentOS] syslog / logstah problem with timestamp

2019-03-08 Thread Pete Biggs


> > {"index"=>{"_index"=>"%{[@metadata][comline]}-%{[@metadata][version]}",  
> > "_type"=>"doc", "_id"=>"U1XLXGkBpfl5FoHeY4J8", "status"=>400,  
> > "error"=>{"type"=>"mapper_parsing_exception", "reason"=>"failed to  
> > parse field [timestamp] of type [date]",  
> > "caused_by"=>{"type"=>"illegal_argument_exception",  
> > "reason"=>"Invalid format: \"Mar  8 11:13:54\""}
> [2019-03-08T11:13:47,125][WARN ][logstash.outputs.elasticsearch] Could  
> not index event to Elasticsearch. {:status=>400, :action=>["index",  
> {:_id=>nil,  
> :_index=>"%{[@metadata][comline]}-%{[@metadata][version]}",  
> :_type=>"doc", :routing=>nil}, #],  
> :response=>{"index"=>{"_index"=>"%{[@metadata][comline]}-%{[@metadata][version]}",
>  "_type"=>"doc", "_id"=>"VFXLXGkBpfl5FoHeY4Ly", "status"=>400, 
> "error"=>{"type"=>"mapper_parsing_exception", "reason"=>"failed to parse 
> field [timestamp] of type [date]", 
> "caused_by"=>{"type"=>"illegal_argument_exception", "reason"=>"Invalid 
> format: \"Mar  8  
> 11:13:54\""}
> [2019-03-08T11:13:47,202][WARN ][logstash.outputs.elasticsearch] Could  
> not index event to Elasticsearch. {:status=>400, :action=>["index",  
> {:_id=>nil,  
> :_index=>"%{[@metadata][comline]}-%{[@metadata][version]}",  
> :_type=>"doc", :routing=>nil}, #],  
> :response=>{"index"=>{"_index"=>"%{[@metadata][comline]}-%{[@metadata][version]}",
>  "_type"=>"doc", "_id"=>"VVXLXGkBpfl5FoHeZII_", "status"=>400, 
> "error"=>{"type"=>"mapper_parsing_exception", "reason"=>"failed to parse 
> field [timestamp] of type [date]", 
> "caused_by"=>{"type"=>"illegal_argument_exception", "reason"=>"Invalid 
> format: \"Mar  8  
> 11:13:54\""}


To be pedantic that's not a logstash error, it's an elasticsearch
error.

What logstash filters do you have for syslog messages? Make sure you
have a filter in place that does something like:

   filter {
 if [type] == "syslog" {
   grok {
 match => { "message" => "%{SYSLOGTIMESTAMP:syslog_timestamp} 
%{SYSLOGHOST:syslog_hostname} 
%{DATA:syslog_program}(?:\[%{POSINT:syslog_pid}\])?: 
%{GREEDYDATA:syslog_message}" }
 add_field => [ "received_at", "%{@timestamp}" ]
 add_field => [ "received_from", "%{host}" ]
   }
   date {
 match => [ "syslog_timestamp", "MMM  d HH:mm:ss.SSS", "MMM dd 
HH:mm:ss.SSS" ]
 timezone => "UTC"
   }
 }
   }

That will break apart the message into fields and set the correct date
format. But you will probably have to play with it to get it exactly
how you want it - the actual content of the syslog message as seen by
logstash often depends on its source (syslog, filebeat, redi etc.) -
pay particular attention to the format of the timestamps.

P.





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


Re: [CentOS-virt] Xen-kernel: Update to 4.14 or 4.19?

2019-03-08 Thread Pasi Kärkkäinen
Hi,

On Thu, Mar 07, 2019 at 05:42:13PM +, George Dunlap wrote:
> Hey all,
> 
> We've been on 4.9 for some time now, and while it's still supported, I
> think it's time to start thinking about upgrading, and I'd like input
> from the community about which version to move up to.
> 

First let's get the current 4.9.16x PR merged and kernel update pushed out.
It should fix the tty/ldisc problem causing crashes in dom0.


> 4.19 has been out for almost 5 months now.  It will include PVH domU
> support, and PVH dom0 support in what _is believed_ to be the final
> form; so when the Virt SIG moves to a version of Xen that supports PVH
> dom0, the kernel will already be in place with no need to upgrade.
> 
> The other option would be to move to 4.14: Probably more stable (as
> it's been out for over a year now), but doesn't have either PVH domU
> or PVH dom0 support.
> 
> I'd suggest 4.19. Any other opinions?
> 

+1 for 4.19 kernel as the next version.

How about blktap2 driver? In our current 4.9 kernel we have the blktap2 patch 
included. 
I think Johnny originally ported the earlier 3.18 kernel blktap2 patch to 4.9.


>  -George
>

Thanks,

-- Pasi

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


Re: [CentOS-virt] libvirt stuck when executing 2 or more parallel calls

2019-03-08 Thread Anthony PERARD
On Wed, Mar 06, 2019 at 02:47:33PM +0200, Oleksandr Panchuk wrote:
> Hello,
> 
> Recently built RPM package libvirt-4.3.0-1.xen48.el6 (
> https://cbs.centos.org/koji/buildinfo?buildID=25235 ) has following issue:
> 
> When trying to run two or more virus commands (2 or more simultaneous calls
> to libvirtd) we got virsh stuck. See attached strace log.
> 
> What could be possible cause?

I don't know, but that issue might be fix upstream. Unfortunatly newer
version requires a newer version of gnutls.

Does libvirt-4.1.0-2.xen48.el6 works better?
We could keep that version on el6, and I'll just need to rebuild it with
an extra patch to it, this one:
  libxl: don't hardcode scheduler weight
  83edaf4435f9c2d1fa5afd1dfbb1643b4f564fd1

Thanks,

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


Re: [CentOS] CentOS 8 Artwork needed

2019-03-08 Thread J Martin Rushton via CentOS
On 07/03/2019 20:45, Rich Bowen wrote:
> To all the artists and designers here, we need your help.
> 
> With RHEL 8 beta released, we need to start producing artwork for CentOS
> 8. It's time for the CentOS Artwork SIG, and anyone else that's
> interested in contributing to this effort, to start working on
> everything that will be needed for the new release.
> 
> What we know we need is anaconda artwork, and new desktop backgrounds to
> replace the current '7' themed stuff.
> 
> As we dig, we may find more things that need to be updated to the new 8
> theme.
> 
> Additionally, we will need to update some of the assets listed here:
> https://wiki.centos.org/ArtWork/Identity
> 
> ... and produce new assets for 8 to be listed here:
> https://wiki.centos.org/ArtWork/Brand/Logo
> 
> And, finally, we need someone to step up to lead this effort.
> 
> While we don't yet know for certain when RHEL 8 will officially release,
> it's safe to assume that it's soon, and we need your help.
> 
I'm no artist, so I won't even attempt to actually create artwork.

Having said that, with the current increase in interest in space
activity the old Apollo 8 logo might give us some inspiration.  See
https://en.wikipedia.org/wiki/File:Apollo-8-patch.png for the original.

My initial though is for the CentOS logo where the earth is and some
sort of future at the Moon end.  Perhaps a star?  I'm a programmer not a
"creative" so I'll allow artistic types to decide.  If obscuring the
CentOS logo with the lower band of the "8" is unacceptable, then it
would be possible to keep the Earth and put the CentOS logo in place of
the Moon.  Not as strong a message, but still fun.

The three astronauts' names cound be replaced with the word "CentOS", a
slogan (please not "to infinity and beyond"), or simply blanked.  The
colour scheme will obviously depend upon corporate diktat.

-- 
J Martin Rushton MBCS



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


[CentOS] syslog / logstah problem with timestamp

2019-03-08 Thread Ralf Prengel

Hallo,
I try to send my centos 7 logfiles to an logstsah server.
Can anyone give me an hint how to fix this problem?

Thanks

Ralf


{"index"=>{"_index"=>"%{[@metadata][comline]}-%{[@metadata][version]}",  
"_type"=>"doc", "_id"=>"U1XLXGkBpfl5FoHeY4J8", "status"=>400,  
"error"=>{"type"=>"mapper_parsing_exception", "reason"=>"failed to  
parse field [timestamp] of type [date]",  
"caused_by"=>{"type"=>"illegal_argument_exception",  
"reason"=>"Invalid format: \"Mar  8 11:13:54\""}
[2019-03-08T11:13:47,125][WARN ][logstash.outputs.elasticsearch] Could  
not index event to Elasticsearch. {:status=>400, :action=>["index",  
{:_id=>nil,  
:_index=>"%{[@metadata][comline]}-%{[@metadata][version]}",  
:_type=>"doc", :routing=>nil}, #],  
:response=>{"index"=>{"_index"=>"%{[@metadata][comline]}-%{[@metadata][version]}", "_type"=>"doc", "_id"=>"VFXLXGkBpfl5FoHeY4Ly", "status"=>400, "error"=>{"type"=>"mapper_parsing_exception", "reason"=>"failed to parse field [timestamp] of type [date]", "caused_by"=>{"type"=>"illegal_argument_exception", "reason"=>"Invalid format: \"Mar  8  
11:13:54\""}
[2019-03-08T11:13:47,202][WARN ][logstash.outputs.elasticsearch] Could  
not index event to Elasticsearch. {:status=>400, :action=>["index",  
{:_id=>nil,  
:_index=>"%{[@metadata][comline]}-%{[@metadata][version]}",  
:_type=>"doc", :routing=>nil}, #],  
:response=>{"index"=>{"_index"=>"%{[@metadata][comline]}-%{[@metadata][version]}", "_type"=>"doc", "_id"=>"VVXLXGkBpfl5FoHeZII_", "status"=>400, "error"=>{"type"=>"mapper_parsing_exception", "reason"=>"failed to parse field [timestamp] of type [date]", "caused_by"=>{"type"=>"illegal_argument_exception", "reason"=>"Invalid format: \"Mar  8  
11:13:54\""}

^C


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