Re: [CentOS] NFS help

2016-10-26 Thread Larry Martell 
On Wed, Oct 26, 2016 at 9:35 AM, Matt Garman  wrote:
> On Tue, Oct 25, 2016 at 7:22 PM, Larry Martell  
> wrote:
>> Again, no machine on the internal network that my 2 CentOS hosts are
>> on are connected to the internet. I have no way to download anything.,
>> There is an onerous and protracted process to get files into the
>> internal network and I will see if I can get netperf in.
>
> Right, but do you have physical access to those machines?  Do you have
> physical access to the machine which on which you use PuTTY to connect
> to those machines?  If yes to either question, then you can use
> another system (that does have Internet access) to download the files
> you want, put them on a USB drive (or burn to a CD, etc), and bring
> the USB/CD to the C6/C7/PuTTY machines.

This site is locked down like no other I have ever seen. You cannot
bring anything into the site - no computers, no media, no phone. You
have to empty your pockets and go through an airport type naked body
scan.

> There's almost always a technical way to get files on to (or out of) a
> system.  :)  Now, your company might have *policies* that forbid
> skirting around the technical measures that are in place.

This is my client's client, and even if I could circumvent their
policy I would not do that. They have a zero tolerance policy and if
you are caught violating it you are banned for life from the company.
And that would not make my client happy.

> Here's another way you might be able to test network connectivity
> between C6 and C7 without installing new tools: see if both machines
> have "nc" (netcat) installed.  I've seen this tool referred to as "the
> swiss army knife of network testing tools", and that is indeed an apt
> description.  So if you have that installed, you can hit up the web
> for various examples of its use.  It's designed to be easily scripted,
> so you can write your own tests, and in theory implement something
> similar to netperf.
>
> OK, I just thought of another "poor man's" way to at least do some
> sanity testing between C6 and C7: scp.  First generate a huge file.
> General rule of thumb is at least 2x the amount of RAM in the C7 host.
> You could create a tarball of /usr, for example (e.g. "tar czvf
> /tmp/bigfile.tar.gz /usr" assuming your /tmp partition is big enough
> to hold this).  Then, first do this: "time scp /tmp/bigfile.tar.gz
> localhost:/tmp/bigfile_copy.tar.gz".  This will literally make a copy
> of that big file, but will route through most of of the network stack.
> Make a note of how long it took.  And also be sure your /tmp partition
> is big enough for two copies of that big file.
>
> Now, repeat that, but instead of copying to localhost, copy to the C6
> box.  Something like: "time scp /tmp/bigfile.tar.gz  host>:/tmp/".  Does the time reported differ greatly from when you
> copied to localhost?  I would expect them to be reasonably close.
> (And this is another reason why you want a fairly large file, so the
> transfer time is dominated by actual file transfer, rather than the
> overhead.)
>
> Lastly, do the reverse test: log in to the C6 box, and copy the file
> back to C7, e.g. "time scp /tmp/bigfile.tar.gz  host>:/tmp/bigfile_copy2.tar.gz".  Again, the time should be
> approximately the same for all three transfers.  If either or both of
> the latter two copies take dramatically longer than the first, then
> there's a good chance something is askew with the network config
> between C6 and C7.
>
> Oh... all this time I've been jumping to fancy tests.  Have you tried
> the simplest form of testing, that is, doing by hand what your scripts
> do automatically?  In other words, simply try copying files between C6
> and C7 using the existing NFS config?  Can you manually trigger the
> errors/timeouts you initially posted?  Is it when copying lots of
> small files?  Or when you copy a single huge file?  Any kind of file
> copying "profile" you can determine that consistently triggers the
> error?  That could be another clue.

These are all good debugging techniques, and I have tried some of
them, but I think the issue is load related. There are 50 external
machines ftp-ing to the C7 server, 24/7, thousands of files a day. And
on the C6 client the script that processes them is running
continuously. It will sometimes run for 7 hours then hang, but it has
run for as long as 3 days before hanging. I have never been able to
reproduce the errors/hanging situation manually.

And again, this is only at this site. We have the same software
deployed at 10 different sites all doing the same thing, and it all
works fine at all of those.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] NFS help

2016-10-26 Thread Larry Martell 
On Mon, Oct 24, 2016 at 7:51 AM, mark  wrote:
> On 10/24/16 03:52, Larry Martell wrote:
>>
>> On Fri, Oct 21, 2016 at 11:42 AM,   wrote:
>>>
>>> Larry Martell wrote:

 On Fri, Oct 21, 2016 at 11:21 AM,   wrote:
>
> Larry Martell wrote:
>>
>> We have 1 system ruining Centos7 that is the NFS server. There are 50
>> external machines that FTP files to this server fairly continuously.
>>
>> We have another system running Centos6 that mounts the partition the
>> files are FTP-ed to using NFS.
>
> 
>
> What filesystem?
>
> 
>>>
>>> cat /etc/fstab on the systems, and see what they are. If either is xfs,
>>> and assuming that the systems are on UPSes, then the fstab which controls
>>> drive mounting on a system should have, instead of "defaults",
>>> nobarrier,inode64.
>>
>>
>> The server is xfs (the client is nfs). The server does have inode64
>> specified, but not nobarrier.
>>
>>> Note that the inode64 is relevant if the filesystem is > 2TB.
>>
>>
>> The file system is 51TB.
>>
>>> The reason I say this is that we we started rolling out CentOS 7, we
>>> tried
>>> to put one of our user's home directory on one, and it was a disaster.
>>> 100% repeatedly, untarring a 100M tarfile onto an nfs-mounted drive took
>>> seven minutes, where before, it had taken 30 seconds. Timed. It took us
>>> months to discover that NFS 4 tries to make transactions atomic, which is
>>> fine if you're worrying about losing power or connectivity. If you're on
>>> a
>>> UPS, and hardwired, adding the nobarrier immediately brought it down to
>>> 40
>>> seconds or so.
>>
>>
>> We are not seeing a performance issue - do you think nobarrier would
>> help with our lock up issue? I wanted to try it but my client did not
>> want me to make any changes until we got the bad disk replaced.
>> Unfortunately that will not happen until Wednesday.
>
>
> Absolutely add nobarrier, and see what happens.

Finally got to add nobarrier (I'll skip why it took so long), and it
looks like this just caused the problem to morph a bit.

On the C7 NFS server, besides having 50 external machines ftp-ing
files to it, we run 2 jobs: 1 that moves files around (called
image_mover) and one that changes perms on some files (called
chmod_job).

And on the C6 NFS client, besides the job that was hanging (called the
importer), we also run a another job (called ftp_job) that ftps files
to the C6 machine. The ftp_job had never hung before, but now the
importer that used to hang has not (yet) hung, and the ftp_job that
had not hung before now is hanging.

But the system messages are different.

On the C7 server there is a series of messages of the form 'task
blocked for >120 seconds' with a stack trace. There is one for each of
the following:

nfsd, chmod_job, kworker, pure_ftpd, image_mover

In each of the stack traces they are blocked on either nfs_write or nfs_flush

And on the C6 client there is a similar blocked message for the ftp
job, blocked on nfs_flush, then the bad sequence number message I had
seen before, and at that point the ftp_job hung.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [OT] How to recover data from an IDE drive

2016-10-26 Thread TE Dukes 


> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of John R Pierce
> Sent: Wednesday, October 26, 2016 9:12 PM
> To: centos@centos.org
> Subject: Re: [CentOS] [OT] How to recover data from an IDE drive
> 
> On 10/26/2016 6:01 PM, TE Dukes wrote:
> > As some may recall, I suffered a hardware failure of a 10 yr old IBM
> > Netvista back in January. I was backing up my personal data, 'My
> > Documents', to my CentOS server but I apparently didn't get my emails.
> >
> > It was a main board failure and I believe the data is still good on
> > the hard drive. Only problem, its an IDE drive and my server and new
> > PC have SATA drives.
> >
> > Is it possible to install the old drive as a secondary drive into a
> > newer PC with SATA drives? If so, how do I do this? I need to access the
> emails.
> >
> > This was a Windows XP machine using Outlook as the mail client.
> 
> you would need an IDE controller to do that.   I have one that is
> external and connects via USB, also came with a drive power supply...
> 
> something like this,
> https://www.amazon.com/Vantec-CB-ISATAU2-Supports-2-5-Inch-5-25-
> Inch/dp/B000J01I1G
> (works with SATA, 3.5 and 2.5" IDE, and has power supply connectors for
> both SATA and IDE style power)
> 
> 
> --
> john r pierce, recycling bits in santa cruz
> 

WOW!! Thanks!!

Didn't know there was something like that!

Thought I was going to have to buy an older PC on eBay or something.

I have tons of stuff over the years that I would like to retrieve off old
hard drives. I junked the old PCs but not the HDs.

You guys are awesome!!

Thanks!!

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

Re: [CentOS] [OT] How to recover data from an IDE drive

2016-10-26 Thread Digimer 
On 26/10/16 09:11 PM, John R Pierce wrote:
> On 10/26/2016 6:01 PM, TE Dukes wrote:
>> As some may recall, I suffered a hardware failure of a 10 yr old IBM
>> Netvista back in January. I was backing up my personal data, 'My
>> Documents',
>> to my CentOS server but I apparently didn't get my emails.
>>
>> It was a main board failure and I believe the data is still good on
>> the hard
>> drive. Only problem, its an IDE drive and my server and new PC have SATA
>> drives.
>>
>> Is it possible to install the old drive as a secondary drive into a
>> newer PC
>> with SATA drives? If so, how do I do this? I need to access the emails.
>>
>> This was a Windows XP machine using Outlook as the mail client.
> 
> you would need an IDE controller to do that.   I have one that is
> external and connects via USB, also came with a drive power supply...
> 
> something like this,
> https://www.amazon.com/Vantec-CB-ISATAU2-Supports-2-5-Inch-5-25-Inch/dp/B000J01I1G
> (works with SATA, 3.5 and 2.5" IDE, and has power supply connectors for
> both SATA and IDE style power)

I had this specific one and it worked fine in linux.

-- 
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [OT] How to recover data from an IDE drive

2016-10-26 Thread John R Pierce 

On 10/26/2016 6:01 PM, TE Dukes wrote:

As some may recall, I suffered a hardware failure of a 10 yr old IBM
Netvista back in January. I was backing up my personal data, 'My Documents',
to my CentOS server but I apparently didn't get my emails.

It was a main board failure and I believe the data is still good on the hard
drive. Only problem, its an IDE drive and my server and new PC have SATA
drives.

Is it possible to install the old drive as a secondary drive into a newer PC
with SATA drives? If so, how do I do this? I need to access the emails.

This was a Windows XP machine using Outlook as the mail client.


you would need an IDE controller to do that.   I have one that is 
external and connects via USB, also came with a drive power supply...


something like this, 
https://www.amazon.com/Vantec-CB-ISATAU2-Supports-2-5-Inch-5-25-Inch/dp/B000J01I1G 
(works with SATA, 3.5 and 2.5" IDE, and has power supply connectors for 
both SATA and IDE style power)



--
john r pierce, recycling bits in santa cruz

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

Re: [CentOS] [OT] How to recover data from an IDE drive

2016-10-26 Thread Digimer 
On 26/10/16 09:01 PM, TE Dukes wrote:
> Hello,
> 
> As some may recall, I suffered a hardware failure of a 10 yr old IBM
> Netvista back in January. I was backing up my personal data, 'My Documents',
> to my CentOS server but I apparently didn't get my emails.
> 
> It was a main board failure and I believe the data is still good on the hard
> drive. Only problem, its an IDE drive and my server and new PC have SATA
> drives.
> 
> Is it possible to install the old drive as a secondary drive into a newer PC
> with SATA drives? If so, how do I do this? I need to access the emails.
> 
> This was a Windows XP machine using Outlook as the mail client.
> 
> TIA!!

There are plenty of IDE to USB adapters out there, so one of those is
probably best. Here's what amazon has when searching for 'ide to usb':

https://www.amazon.ca/s/ref=nb_sb_noss_1?url=search-alias%3Daps=ide+to+usb

Most should work fine in Linux, but if you narrow down a specific
make/model, a quick google search should confirm linux support.

-- 
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [OT] How to recover data from an IDE drive

2016-10-26 Thread Hal Wigoda 
It can be mounted as an external or secondary drive.
However, it is more likely not to work.

If you really have to recover data from the drive,
it will have to betaken to a data recover company.

They look at the drive,
find out its geometries and hardware configuration.

Then the data surfaces, platters, or whatever are removed delicately
will have to be removed and mounted in a drive that exactly matches
the original drive electronic configuration and geometries.

And its not cheap or guaranteed to work.

I have numerous old drives that quite working.

You just say goodbye to those bits and bytes.

On Wed, Oct 26, 2016 at 8:01 PM, TE Dukes 
wrote:

> Hello,
>
> As some may recall, I suffered a hardware failure of a 10 yr old IBM
> Netvista back in January. I was backing up my personal data, 'My
> Documents',
> to my CentOS server but I apparently didn't get my emails.
>
> It was a main board failure and I believe the data is still good on the
> hard
> drive. Only problem, its an IDE drive and my server and new PC have SATA
> drives.
>
> Is it possible to install the old drive as a secondary drive into a newer
> PC
> with SATA drives? If so, how do I do this? I need to access the emails.
>
> This was a Windows XP machine using Outlook as the mail client.
>
> TIA!!
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>



-- 
-
Hal Wigoda
Chicago
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] [OT] How to recover data from an IDE drive

2016-10-26 Thread TE Dukes 
Hello,

As some may recall, I suffered a hardware failure of a 10 yr old IBM
Netvista back in January. I was backing up my personal data, 'My Documents',
to my CentOS server but I apparently didn't get my emails.

It was a main board failure and I believe the data is still good on the hard
drive. Only problem, its an IDE drive and my server and new PC have SATA
drives.

Is it possible to install the old drive as a secondary drive into a newer PC
with SATA drives? If so, how do I do this? I need to access the emails.

This was a Windows XP machine using Outlook as the mail client.

TIA!!


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

Re: [CentOS] rpmbuild question

2016-10-26 Thread Gordon Messmer 

On 10/26/2016 10:07 AM, m.r...@5-cent.us wrote:

Trying to build a package from a gzipped tarball of a python package.
I'm trying to build it in /root/rpmbuild.


To echo Frank's advice: don't do that.  Build rpms as a non-root user.  
Consider using "mock", especially if you intend to distribute your packages.



Python has a way to build it,
but it creates its own tree, with a clone of the rpmbuild tree under
*that*.


It sounds like you're using "setup.py bdist_rpm".  When you do that, 
python's setuptools will create a temporary rpm build environment in 
./build/.  You should also get the src.rpm in ./dist/


If you want to build the package in your own rpmroot, just take the 
src.rpm from ./dist/ and rebuild it.


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

Re: [CentOS] SElinux suggestions needed: migrating backup service

2016-10-26 Thread Gordon Messmer 

On 10/24/2016 04:43 PM, Leon Fauster wrote:

Using rsync -aHA (without X) circumvent the output but its still unclear what 
exactly triggers
the above output.



The '-X' flag attempts to make attributes match on the source and 
destination files.  Since the source files have no SELinux attribute, 
rsync will try to remove it from the destination, where an attribute has 
been inherited.


I'm not entirely certain why a file couldn't have no SELinux label, but 
since you don't have any extended attributes to preserve, the simple 
solution would be to stop telling rsync to preserve extended attributes.


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

Re: [CentOS] Anyone know anything about slurm on CentOS 7?

2016-10-26 Thread Troels Arvin 
m.roth-x6lchVBUigD1P9xLtpHBDw wrote:
> why /var/log/messages is getting flooded with
> Oct 26 11:01:06  kernel: type=1105 audit
> (1477494066.569:642430): pid=108551 uid=0
[...]

Is your auditd service running? I believe I've seen cases where auditd 
was not running, leading to audit-stuff showing up in /var/log/messages

-- 
Regards,
Troels Arvin

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

Re: [CentOS] Anyone know anything about slurm on CentOS 7?

2016-10-26 Thread m . roth 
Eero Volotinen wrote:
> looks like auditd logging is a bit tweaked.
>
As far as I know, it's selinux-policy-targeted out of the box. (And yes,
we do have it in permissive mode.)

Any thoughts on how to tweak that?

  mark
>
> 26.10.2016 6.11 ip.  kirjoitti:
>
>> The recently-left programmer did *something*, and he didn't know what,
>> and
>> the guy who picked it up is working with me to find out why
>> /var/log/messages is getting flooded with
>> Oct 26 11:01:06  kernel: type=1105
>> audit(1477494066.569:642430): pid=108551 uid=0 auid=4294967295
>> ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0
>> msg='op=PAM:session_open
>> grantors=pam_keyinit,pam_keyinit,pam_limits,pam_
>> systemd,pam_unix,pam_krb5,pam_xauth
>> acct="" exe="/usr/bin/su" hostname=? addr=? terminal=?
>> res=success'
>> Oct 26 11:01:06  kernel: type=1106
>> audit(1477494066.620:642431): pid=108548 uid=0 auid=4294967295
>> ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0
>> msg='op=PAM:session_close
>> grantors=pam_keyinit,pam_keyinit,pam_limits,pam_
>> systemd,pam_unix,pam_krb5,pam_xauth
>> acct="" exe="/usr/bin/su" hostname=? addr=? terminal=?
>> res=success'
>> Oct 26 11:01:06  kernel: type=1104
>> audit(1477494066.620:642432): pid=108548 uid=0 auid=4294967295
>> ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0
>> msg='op=PAM:setcred grantors=pam_rootok acct="" exe="/usr/bin/su"
>> hostname=? addr=? terminal=? res=success'
>>
>> Oct 26 11:01:11  su: (to ) root on none
>> Oct 26 11:01:11  su: (to ) root on none
>> Oct 26 11:01:11  systemd: Started Session c21839 of user
>> .
>>
>> Other folks can submit jobs to slurm, and we don't get anything like
>> this.
>>
>> Feel free to contact me offlist
>>
>>   mark
>> Oct 26 11:01:11  systemd: Starting Session c21839 of user
>> .
>>
>>
>> ___
>> 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] Anyone know anything about slurm on CentOS 7?

2016-10-26 Thread Andrew Holway 
You might have some luck on the beowulf mailing list - http://beowulf.org/
There are quite a few slurmy types kicking around there.

On 26 October 2016 at 22:09, Eero Volotinen  wrote:

> looks like auditd logging is a bit tweaked.
>
> eero
>
> 26.10.2016 6.11 ip.  kirjoitti:
>
> > The recently-left programmer did *something*, and he didn't know what,
> and
> > the guy who picked it up is working with me to find out why
> > /var/log/messages is getting flooded with
> > Oct 26 11:01:06  kernel: type=1105
> > audit(1477494066.569:642430): pid=108551 uid=0 auid=4294967295
> > ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0
> > msg='op=PAM:session_open
> > grantors=pam_keyinit,pam_keyinit,pam_limits,pam_
> > systemd,pam_unix,pam_krb5,pam_xauth
> > acct="" exe="/usr/bin/su" hostname=? addr=? terminal=? res=success'
> > Oct 26 11:01:06  kernel: type=1106
> > audit(1477494066.620:642431): pid=108548 uid=0 auid=4294967295
> > ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0
> > msg='op=PAM:session_close
> > grantors=pam_keyinit,pam_keyinit,pam_limits,pam_
> > systemd,pam_unix,pam_krb5,pam_xauth
> > acct="" exe="/usr/bin/su" hostname=? addr=? terminal=? res=success'
> > Oct 26 11:01:06  kernel: type=1104
> > audit(1477494066.620:642432): pid=108548 uid=0 auid=4294967295
> > ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0
> > msg='op=PAM:setcred grantors=pam_rootok acct="" exe="/usr/bin/su"
> > hostname=? addr=? terminal=? res=success'
> >
> > Oct 26 11:01:11  su: (to ) root on none
> > Oct 26 11:01:11  su: (to ) root on none
> > Oct 26 11:01:11  systemd: Started Session c21839 of user
> > .
> >
> > Other folks can submit jobs to slurm, and we don't get anything like
> this.
> >
> > Feel free to contact me offlist
> >
> >   mark
> > Oct 26 11:01:11  systemd: Starting Session c21839 of user
> > .
> >
> >
> > ___
> > 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] Anyone know anything about slurm on CentOS 7?

2016-10-26 Thread Eero Volotinen 
looks like auditd logging is a bit tweaked.

eero

26.10.2016 6.11 ip.  kirjoitti:

> The recently-left programmer did *something*, and he didn't know what, and
> the guy who picked it up is working with me to find out why
> /var/log/messages is getting flooded with
> Oct 26 11:01:06  kernel: type=1105
> audit(1477494066.569:642430): pid=108551 uid=0 auid=4294967295
> ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0
> msg='op=PAM:session_open
> grantors=pam_keyinit,pam_keyinit,pam_limits,pam_
> systemd,pam_unix,pam_krb5,pam_xauth
> acct="" exe="/usr/bin/su" hostname=? addr=? terminal=? res=success'
> Oct 26 11:01:06  kernel: type=1106
> audit(1477494066.620:642431): pid=108548 uid=0 auid=4294967295
> ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0
> msg='op=PAM:session_close
> grantors=pam_keyinit,pam_keyinit,pam_limits,pam_
> systemd,pam_unix,pam_krb5,pam_xauth
> acct="" exe="/usr/bin/su" hostname=? addr=? terminal=? res=success'
> Oct 26 11:01:06  kernel: type=1104
> audit(1477494066.620:642432): pid=108548 uid=0 auid=4294967295
> ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0
> msg='op=PAM:setcred grantors=pam_rootok acct="" exe="/usr/bin/su"
> hostname=? addr=? terminal=? res=success'
>
> Oct 26 11:01:11  su: (to ) root on none
> Oct 26 11:01:11  su: (to ) root on none
> Oct 26 11:01:11  systemd: Started Session c21839 of user
> .
>
> Other folks can submit jobs to slurm, and we don't get anything like this.
>
> Feel free to contact me offlist
>
>   mark
> Oct 26 11:01:11  systemd: Starting Session c21839 of user
> .
>
>
> ___
> 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] rpmbuild question

2016-10-26 Thread James Hogarth 
On 26 Oct 2016 6:17 pm, "Frank Cox"  wrote:
>
> On Wed, 26 Oct 2016 13:07:43 -0400
> m.r...@5-cent.us wrote:
>
> > I'm trying to build it in /root/rpmbuild.
>
> Don't do that.  Install rpmdevtools so you build it under your home
directory and avoid blowing up your system if there's an error.
>

First of all read up on how to properly build an RPM:

https://www.hogarthuk.com/?q=node/11

Since this is python look up the Fedora python guidelines and follow those.

Here's the spec for a recent python library I packaged:

https://pkgs.fedoraproject.org/cgit/rpms/python-ntlm3.git/tree/python-ntlm3.spec

If you don't need python3 you can strip that stuff out ...

The Fedora python guidelines have a decent spec template you can crib, keep
in mind the el6 caveats if you need to build for that with regards to macro
definitions
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] rpmbuild question

2016-10-26 Thread Frank Cox 
On Wed, 26 Oct 2016 13:07:43 -0400
m.r...@5-cent.us wrote:

> I'm trying to build it in /root/rpmbuild. 

Don't do that.  Install rpmdevtools so you build it under your home directory 
and avoid blowing up your system if there's an error.

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

[CentOS] rpmbuild question

2016-10-26 Thread m . roth 
Hi, folks,

   Trying to build a package from a gzipped tarball of a python package.
I'm trying to build it in /root/rpmbuild. Python has a way to build it,
but it creates its own tree, with a clone of the rpmbuild tree under
*that*.

   So, from the specfile, I'm trying to understand, after much googling,
what I need to change the Source and BuildRoot to. My latest try for
the latter is
BuildRoot: %{_builddir}/BUILD/%{name}-%{version}-%{release}
For Source0, I want to use the file in SOURCES.

   Anyone got a better example than what I've been googling?

   mark

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

Re: [CentOS] CVE-2016-5195 DirtyCOW : Critical Linux Kernel Flaw

2016-10-26 Thread Peter Kjellström 
On Wed, 26 Oct 2016 06:30:45 -0500
Johnny Hughes  wrote:

> On 10/26/2016 05:56 AM, Peter Kjellström wrote:
> > On Tue, 25 Oct 2016 17:21:54 -0700
> > Akemi Yagi  wrote:
> >   
> >> On Tue, Oct 25, 2016 at 10:26 AM, Leon Fauster
> >>  wrote:  
> >>> Am 25.10.2016 um 15:39 schrieb Peter Kjellström
> >>> :
>  On Tue, 25 Oct 2016 10:06:12 +0200
>  Christian Anthon  wrote:
> 
> > What is the best approach on centos 6 to mitigate the problem is
> > officially patched? As far as I can tell Centos 6 is vulnerable
> > to attacks using ptrace.
> 
>  I can confirm that c6 is vulnerable, we're running a patched
>  kernel (local build) using a rhel6 adaptation of the upstream
>  fix.
> 
>  Ask off-list if you want an src.rpm
> >>>
> >>>
> >>> Hi Peter, can you confirm that its this?
> >>>
> >>> http://pastebin.centos.org/56391/
> >>
> >> That is for the EL-7.2 kernel. Peter was offering a patch for
> >> CentOS 6.
> >>
> >> RH released the patched kernel for EL-6.8 today. I have attached
> >> the diff file between 2.6.32-642.6.1.el6 and 2.6.32-642.6.2.el6.
> >> It is more complex because the 6 kernel is older, so required more
> >> mods, I suppose. Maybe that was the reason why the EL-6 update
> >> took longer than EL-7.  
> > 
> > We also did a quick diff for the official c6 patch and it's almost
> > but not quite what we were using as a quick fix.
> > 
> > /Peter  
> 
> The 6 kernel is released now  ..  Use that :)

You misunderstood me. I was referring to the difference between the
quick fix initially deployed by us and the now released fix. We're
almost completely updated from quick fix to official fix by now.

/Peter


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

[CentOS] Anyone know anything about slurm on CentOS 7?

2016-10-26 Thread m . roth 
The recently-left programmer did *something*, and he didn't know what, and
the guy who picked it up is working with me to find out why
/var/log/messages is getting flooded with
Oct 26 11:01:06  kernel: type=1105
audit(1477494066.569:642430): pid=108551 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0
msg='op=PAM:session_open
grantors=pam_keyinit,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_krb5,pam_xauth
acct="" exe="/usr/bin/su" hostname=? addr=? terminal=? res=success'
Oct 26 11:01:06  kernel: type=1106
audit(1477494066.620:642431): pid=108548 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0
msg='op=PAM:session_close
grantors=pam_keyinit,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_krb5,pam_xauth
acct="" exe="/usr/bin/su" hostname=? addr=? terminal=? res=success'
Oct 26 11:01:06  kernel: type=1104
audit(1477494066.620:642432): pid=108548 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0
msg='op=PAM:setcred grantors=pam_rootok acct="" exe="/usr/bin/su"
hostname=? addr=? terminal=? res=success'

Oct 26 11:01:11  su: (to ) root on none
Oct 26 11:01:11  su: (to ) root on none
Oct 26 11:01:11  systemd: Started Session c21839 of user .

Other folks can submit jobs to slurm, and we don't get anything like this.

Feel free to contact me offlist

  mark
Oct 26 11:01:11  systemd: Starting Session c21839 of user .


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

Re: [CentOS] NFS help

2016-10-26 Thread Boris Epstein 
I am sorry, I am stepping into the conversation late and may not fully
understand all aspects of the situation but I wonder if it may make sense
to set up a server process on the NFS server machine that simply listens
for incoming requests to perform a file copy and then does so as requested
- only locally. If files in question are large - which I suspect they may
be, given the timeouts becoming an issue - that may resolve the issue and
help speed things up at the same time.

Cheers,

Boris.


On Wed, Oct 26, 2016 at 9:35 AM, Matt Garman 
wrote:

> On Tue, Oct 25, 2016 at 7:22 PM, Larry Martell 
> wrote:
> > Again, no machine on the internal network that my 2 CentOS hosts are
> > on are connected to the internet. I have no way to download anything.,
> > There is an onerous and protracted process to get files into the
> > internal network and I will see if I can get netperf in.
>
> Right, but do you have physical access to those machines?  Do you have
> physical access to the machine which on which you use PuTTY to connect
> to those machines?  If yes to either question, then you can use
> another system (that does have Internet access) to download the files
> you want, put them on a USB drive (or burn to a CD, etc), and bring
> the USB/CD to the C6/C7/PuTTY machines.
>
> There's almost always a technical way to get files on to (or out of) a
> system.  :)  Now, your company might have *policies* that forbid
> skirting around the technical measures that are in place.
>
> Here's another way you might be able to test network connectivity
> between C6 and C7 without installing new tools: see if both machines
> have "nc" (netcat) installed.  I've seen this tool referred to as "the
> swiss army knife of network testing tools", and that is indeed an apt
> description.  So if you have that installed, you can hit up the web
> for various examples of its use.  It's designed to be easily scripted,
> so you can write your own tests, and in theory implement something
> similar to netperf.
>
> OK, I just thought of another "poor man's" way to at least do some
> sanity testing between C6 and C7: scp.  First generate a huge file.
> General rule of thumb is at least 2x the amount of RAM in the C7 host.
> You could create a tarball of /usr, for example (e.g. "tar czvf
> /tmp/bigfile.tar.gz /usr" assuming your /tmp partition is big enough
> to hold this).  Then, first do this: "time scp /tmp/bigfile.tar.gz
> localhost:/tmp/bigfile_copy.tar.gz".  This will literally make a copy
> of that big file, but will route through most of of the network stack.
> Make a note of how long it took.  And also be sure your /tmp partition
> is big enough for two copies of that big file.
>
> Now, repeat that, but instead of copying to localhost, copy to the C6
> box.  Something like: "time scp /tmp/bigfile.tar.gz  host>:/tmp/".  Does the time reported differ greatly from when you
> copied to localhost?  I would expect them to be reasonably close.
> (And this is another reason why you want a fairly large file, so the
> transfer time is dominated by actual file transfer, rather than the
> overhead.)
>
> Lastly, do the reverse test: log in to the C6 box, and copy the file
> back to C7, e.g. "time scp /tmp/bigfile.tar.gz  host>:/tmp/bigfile_copy2.tar.gz".  Again, the time should be
> approximately the same for all three transfers.  If either or both of
> the latter two copies take dramatically longer than the first, then
> there's a good chance something is askew with the network config
> between C6 and C7.
>
> Oh... all this time I've been jumping to fancy tests.  Have you tried
> the simplest form of testing, that is, doing by hand what your scripts
> do automatically?  In other words, simply try copying files between C6
> and C7 using the existing NFS config?  Can you manually trigger the
> errors/timeouts you initially posted?  Is it when copying lots of
> small files?  Or when you copy a single huge file?  Any kind of file
> copying "profile" you can determine that consistently triggers the
> error?  That could be another clue.
>
> Good luck!
> ___
> 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] NFS help

2016-10-26 Thread Matt Garman 
On Tue, Oct 25, 2016 at 7:22 PM, Larry Martell  wrote:
> Again, no machine on the internal network that my 2 CentOS hosts are
> on are connected to the internet. I have no way to download anything.,
> There is an onerous and protracted process to get files into the
> internal network and I will see if I can get netperf in.

Right, but do you have physical access to those machines?  Do you have
physical access to the machine which on which you use PuTTY to connect
to those machines?  If yes to either question, then you can use
another system (that does have Internet access) to download the files
you want, put them on a USB drive (or burn to a CD, etc), and bring
the USB/CD to the C6/C7/PuTTY machines.

There's almost always a technical way to get files on to (or out of) a
system.  :)  Now, your company might have *policies* that forbid
skirting around the technical measures that are in place.

Here's another way you might be able to test network connectivity
between C6 and C7 without installing new tools: see if both machines
have "nc" (netcat) installed.  I've seen this tool referred to as "the
swiss army knife of network testing tools", and that is indeed an apt
description.  So if you have that installed, you can hit up the web
for various examples of its use.  It's designed to be easily scripted,
so you can write your own tests, and in theory implement something
similar to netperf.

OK, I just thought of another "poor man's" way to at least do some
sanity testing between C6 and C7: scp.  First generate a huge file.
General rule of thumb is at least 2x the amount of RAM in the C7 host.
You could create a tarball of /usr, for example (e.g. "tar czvf
/tmp/bigfile.tar.gz /usr" assuming your /tmp partition is big enough
to hold this).  Then, first do this: "time scp /tmp/bigfile.tar.gz
localhost:/tmp/bigfile_copy.tar.gz".  This will literally make a copy
of that big file, but will route through most of of the network stack.
Make a note of how long it took.  And also be sure your /tmp partition
is big enough for two copies of that big file.

Now, repeat that, but instead of copying to localhost, copy to the C6
box.  Something like: "time scp /tmp/bigfile.tar.gz :/tmp/".  Does the time reported differ greatly from when you
copied to localhost?  I would expect them to be reasonably close.
(And this is another reason why you want a fairly large file, so the
transfer time is dominated by actual file transfer, rather than the
overhead.)

Lastly, do the reverse test: log in to the C6 box, and copy the file
back to C7, e.g. "time scp /tmp/bigfile.tar.gz :/tmp/bigfile_copy2.tar.gz".  Again, the time should be
approximately the same for all three transfers.  If either or both of
the latter two copies take dramatically longer than the first, then
there's a good chance something is askew with the network config
between C6 and C7.

Oh... all this time I've been jumping to fancy tests.  Have you tried
the simplest form of testing, that is, doing by hand what your scripts
do automatically?  In other words, simply try copying files between C6
and C7 using the existing NFS config?  Can you manually trigger the
errors/timeouts you initially posted?  Is it when copying lots of
small files?  Or when you copy a single huge file?  Any kind of file
copying "profile" you can determine that consistently triggers the
error?  That could be another clue.

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

[CentOS] CentOS-announce Digest, Vol 140, Issue 9

2016-10-26 Thread centos-announce-request 
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

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

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

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


Today's Topics:

   1. CESA-2016:2098 Important CentOS 7 kernel Security Update
  (Johnny Hughes)
   2. CESA-2016:2105 Important CentOS 6 kernel Security Update
  (Johnny Hughes)


--

Message: 1
Date: Tue, 25 Oct 2016 11:17:10 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2016:2098 Important CentOS 7 kernel
SecurityUpdate
Message-ID: <20161025111710.ga35...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2016:2098 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-2098.html

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

x86_64:
afb7e2a7c3a38185b99f092b70ec274888a5beb136a7e5077559cbd29b3f55d7  
kernel-3.10.0-327.36.3.el7.x86_64.rpm
1b33324ee4de14c03dde2eefb91bdee83082dd4ced6c0b94f5ab3253690bce38  
kernel-abi-whitelists-3.10.0-327.36.3.el7.noarch.rpm
000ccd89b45a28645202add878b5e37d9a482df68fd5cf12914611098724eea7  
kernel-debug-3.10.0-327.36.3.el7.x86_64.rpm
430e59db8a03d01f25ff602e766b96b06157fb881db68ca0cb81f229ec2609d6  
kernel-debug-devel-3.10.0-327.36.3.el7.x86_64.rpm
5522697d3b016509dd3744e714d61e5d177921d2a045588730c1cd41713ba2c1  
kernel-devel-3.10.0-327.36.3.el7.x86_64.rpm
b3fb9f23b5a2427d90e286350b1e7ded8ce6c3c2c5f7e191ee15bb8a70c981aa  
kernel-doc-3.10.0-327.36.3.el7.noarch.rpm
ad0006f10828ff8890c5599982c57a5ed75a9fdc9aab90e0c8cba6422eb766ea  
kernel-headers-3.10.0-327.36.3.el7.x86_64.rpm
3639553b0daacf8b577a5576d732eadae1aeef30cf61ca15dd755e439b5a8578  
kernel-tools-3.10.0-327.36.3.el7.x86_64.rpm
b66a1c39f21081605dc3f19afc73236b5cb23a1de8d1bd1b14718165663de7ac  
kernel-tools-libs-3.10.0-327.36.3.el7.x86_64.rpm
97f1708f020dc0c19c9abead5cabdf813aa56ffdf6f8956811669019d74980d8  
kernel-tools-libs-devel-3.10.0-327.36.3.el7.x86_64.rpm
6101abe377f9c3f96f9a0b32840ccde2d60835af96ffbb1c787841e0a98bb755  
perf-3.10.0-327.36.3.el7.x86_64.rpm
cd55f641ed83faeb33d35a7915c78f85f58a237612ffebdfd5f41e652472ce7b  
python-perf-3.10.0-327.36.3.el7.x86_64.rpm

Source:
fc7d9058db4d12308f80993c446175e0fd45e413ffafa7b9b2b0c38a432a4a3c  
kernel-3.10.0-327.36.3.el7.src.rpm



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



--

Message: 2
Date: Wed, 26 Oct 2016 07:33:13 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2016:2105 Important CentOS 6 kernel
SecurityUpdate
Message-ID: <20161026073313.ga49...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2016:2105 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-2105.html

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

i386:
accab5355c8df90d69b9c0a510de38c8169f1ad3f68fb90a281a380bda814508  
kernel-2.6.32-642.6.2.el6.i686.rpm
34f0fb180eb6366cfe4921bb2754cc5e1a71c653b4c8295f0d7c55b8fc2c5f22  
kernel-abi-whitelists-2.6.32-642.6.2.el6.noarch.rpm
f5ee02aae55cd82ffb76592f075ae17b867e45719664c0fbba58c2ddaaef42e5  
kernel-debug-2.6.32-642.6.2.el6.i686.rpm
bef23a94d5d10cbc9781973ccab1017608bc6fd4aaea4580e733291b4b1e5c0f  
kernel-debug-devel-2.6.32-642.6.2.el6.i686.rpm
c174e85e65af3f6f3e58c91d5496ba442fce86a2069b67e888290ac4bb5ab979  
kernel-devel-2.6.32-642.6.2.el6.i686.rpm
a9b70c9690cd9cf1b3a5d8daf6405355d2fe036909702744a13c23aa6dadab24  
kernel-doc-2.6.32-642.6.2.el6.noarch.rpm
a718ceea93ff199e1be06ccbbaee1f9904185350d4c3dde7d5efddee95a8e17f  
kernel-firmware-2.6.32-642.6.2.el6.noarch.rpm
a1390897ac937dfdc103e496723b3b46130d44b65f03661a9da7d923875d70ae  
kernel-headers-2.6.32-642.6.2.el6.i686.rpm
522934abb31cdcf2527d6be98e15c57f2d0449f3cb822d6f51fa8ab0ff802563  
perf-2.6.32-642.6.2.el6.i686.rpm
8d26ca9e0f4274066d6f47a6444e53266398d1e2785c2ca7c30e782a930474a7  
python-perf-2.6.32-642.6.2.el6.i686.rpm

x86_64:
e03a46c4ad13964946f4a0132514dd784718e64224318481449a9bac96c8a133  
kernel-2.6.32-642.6.2.el6.x86_64.rpm
34f0fb180eb6366cfe4921bb2754cc5e1a71c653b4c8295f0d7c55b8fc2c5f22  
kernel-abi-whitelists-2.6.32-642.6.2.el6.noarch.rpm
756b7fdf4e4c305ed0bcd5258b78333f2bd1dc0cc6183fcc7b49146237e50d6d  
kernel-debug-2.6.32-642.6.2.el6.x86_64.rpm

Re: [CentOS] CVE-2016-5195 DirtyCOW : Critical Linux Kernel Flaw

2016-10-26 Thread Johnny Hughes 
On 10/26/2016 05:56 AM, Peter Kjellström wrote:
> On Tue, 25 Oct 2016 17:21:54 -0700
> Akemi Yagi  wrote:
> 
>> On Tue, Oct 25, 2016 at 10:26 AM, Leon Fauster
>>  wrote:
>>> Am 25.10.2016 um 15:39 schrieb Peter Kjellström :  
 On Tue, 25 Oct 2016 10:06:12 +0200
 Christian Anthon  wrote:
  
> What is the best approach on centos 6 to mitigate the problem is
> officially patched? As far as I can tell Centos 6 is vulnerable to
> attacks using ptrace.  

 I can confirm that c6 is vulnerable, we're running a patched kernel
 (local build) using a rhel6 adaptation of the upstream fix.

 Ask off-list if you want an src.rpm  
>>>
>>>
>>> Hi Peter, can you confirm that its this?
>>>
>>> http://pastebin.centos.org/56391/  
>>
>> That is for the EL-7.2 kernel. Peter was offering a patch for CentOS
>> 6.
>>
>> RH released the patched kernel for EL-6.8 today. I have attached the
>> diff file between 2.6.32-642.6.1.el6 and 2.6.32-642.6.2.el6. It is
>> more complex because the 6 kernel is older, so required more mods, I
>> suppose. Maybe that was the reason why the EL-6 update took longer
>> than EL-7.
> 
> We also did a quick diff for the official c6 patch and it's almost but
> not quite what we were using as a quick fix.
> 
> /Peter

The 6 kernel is released now  ..  Use that :)




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

Re: [CentOS] CVE-2016-5195 DirtyCOW : Critical Linux Kernel Flaw

2016-10-26 Thread Peter Kjellström 
On Tue, 25 Oct 2016 17:21:54 -0700
Akemi Yagi  wrote:

> On Tue, Oct 25, 2016 at 10:26 AM, Leon Fauster
>  wrote:
> > Am 25.10.2016 um 15:39 schrieb Peter Kjellström :  
> >> On Tue, 25 Oct 2016 10:06:12 +0200
> >> Christian Anthon  wrote:
> >>  
> >>> What is the best approach on centos 6 to mitigate the problem is
> >>> officially patched? As far as I can tell Centos 6 is vulnerable to
> >>> attacks using ptrace.  
> >>
> >> I can confirm that c6 is vulnerable, we're running a patched kernel
> >> (local build) using a rhel6 adaptation of the upstream fix.
> >>
> >> Ask off-list if you want an src.rpm  
> >
> >
> > Hi Peter, can you confirm that its this?
> >
> > http://pastebin.centos.org/56391/  
> 
> That is for the EL-7.2 kernel. Peter was offering a patch for CentOS
> 6.
> 
> RH released the patched kernel for EL-6.8 today. I have attached the
> diff file between 2.6.32-642.6.1.el6 and 2.6.32-642.6.2.el6. It is
> more complex because the 6 kernel is older, so required more mods, I
> suppose. Maybe that was the reason why the EL-6 update took longer
> than EL-7.

We also did a quick diff for the official c6 patch and it's almost but
not quite what we were using as a quick fix.

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

Re: [CentOS] Ordering rich rules with firewalld

2016-10-26 Thread lejeczek 

i'm on
CentOS Linux release 7.2.1511 (Core) and firewalld 0.3.9
and it works, has been for a few months, perfectly fine.

On 26/08/16 23:46, Jonathan Billings wrote:

I believe the priority feature is introduced in a version  later than what is 
in CentOS 7. However, I believe the 7.3 update (in beta now for RHEL) has a 
version that supports priority.


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

[CentOS-announce] CESA-2016:2105 Important CentOS 6 kernel Security Update

2016-10-26 Thread Johnny Hughes 

CentOS Errata and Security Advisory 2016:2105 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-2105.html

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

i386:
accab5355c8df90d69b9c0a510de38c8169f1ad3f68fb90a281a380bda814508  
kernel-2.6.32-642.6.2.el6.i686.rpm
34f0fb180eb6366cfe4921bb2754cc5e1a71c653b4c8295f0d7c55b8fc2c5f22  
kernel-abi-whitelists-2.6.32-642.6.2.el6.noarch.rpm
f5ee02aae55cd82ffb76592f075ae17b867e45719664c0fbba58c2ddaaef42e5  
kernel-debug-2.6.32-642.6.2.el6.i686.rpm
bef23a94d5d10cbc9781973ccab1017608bc6fd4aaea4580e733291b4b1e5c0f  
kernel-debug-devel-2.6.32-642.6.2.el6.i686.rpm
c174e85e65af3f6f3e58c91d5496ba442fce86a2069b67e888290ac4bb5ab979  
kernel-devel-2.6.32-642.6.2.el6.i686.rpm
a9b70c9690cd9cf1b3a5d8daf6405355d2fe036909702744a13c23aa6dadab24  
kernel-doc-2.6.32-642.6.2.el6.noarch.rpm
a718ceea93ff199e1be06ccbbaee1f9904185350d4c3dde7d5efddee95a8e17f  
kernel-firmware-2.6.32-642.6.2.el6.noarch.rpm
a1390897ac937dfdc103e496723b3b46130d44b65f03661a9da7d923875d70ae  
kernel-headers-2.6.32-642.6.2.el6.i686.rpm
522934abb31cdcf2527d6be98e15c57f2d0449f3cb822d6f51fa8ab0ff802563  
perf-2.6.32-642.6.2.el6.i686.rpm
8d26ca9e0f4274066d6f47a6444e53266398d1e2785c2ca7c30e782a930474a7  
python-perf-2.6.32-642.6.2.el6.i686.rpm

x86_64:
e03a46c4ad13964946f4a0132514dd784718e64224318481449a9bac96c8a133  
kernel-2.6.32-642.6.2.el6.x86_64.rpm
34f0fb180eb6366cfe4921bb2754cc5e1a71c653b4c8295f0d7c55b8fc2c5f22  
kernel-abi-whitelists-2.6.32-642.6.2.el6.noarch.rpm
756b7fdf4e4c305ed0bcd5258b78333f2bd1dc0cc6183fcc7b49146237e50d6d  
kernel-debug-2.6.32-642.6.2.el6.x86_64.rpm
bef23a94d5d10cbc9781973ccab1017608bc6fd4aaea4580e733291b4b1e5c0f  
kernel-debug-devel-2.6.32-642.6.2.el6.i686.rpm
06d0b2dbfe10f04f636faf37fd907111777ead7c406c386eeef4a7dc96a8896b  
kernel-debug-devel-2.6.32-642.6.2.el6.x86_64.rpm
0b8195fa45b0dff3af0a7bf6b77e0e320b4674aaf4b57cecc726457f02f208d7  
kernel-devel-2.6.32-642.6.2.el6.x86_64.rpm
a9b70c9690cd9cf1b3a5d8daf6405355d2fe036909702744a13c23aa6dadab24  
kernel-doc-2.6.32-642.6.2.el6.noarch.rpm
a718ceea93ff199e1be06ccbbaee1f9904185350d4c3dde7d5efddee95a8e17f  
kernel-firmware-2.6.32-642.6.2.el6.noarch.rpm
f3f772ca476017a40222059108c2d2801ba6ea5ad3351cf03207fa2c99ce26f2  
kernel-headers-2.6.32-642.6.2.el6.x86_64.rpm
a817b22e777013c4757d8d27dbbc12478bca40b04ddfebc7129ea030870faa0d  
perf-2.6.32-642.6.2.el6.x86_64.rpm
49d01cc50bde501b650b9d50c4ae0da5a9a53c6e588531a0c4699c21f11ad643  
python-perf-2.6.32-642.6.2.el6.x86_64.rpm

Source:
c53ef890315b8699634652e8520af16805ea4b9da607d336d22a7a971ecf486d  
kernel-2.6.32-642.6.2.el6.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] CVE-2016-5195 DirtyCOW : Critical Linux Kernel Flaw

2016-10-26 Thread Johnny Hughes 
On 10/25/2016 03:37 PM, m.r...@5-cent.us wrote:
> Phelps, Matthew wrote:
>> On Tue, Oct 25, 2016 at 2:18 PM,  wrote:
>>
>>> My manager just told me that upstream has released a patched kernel for
>>> 7:
>>> CentOS package kernel-3.10.0-327.36.3.el7.x86_64.rpm
>>> see http://rhn.redhat.com/errata/RHSA-2016-2098.html
>>>
>>> I'm hoping Johnny can get us that, hopefully before the end of the week.
>>>
>> That came out this morning:
>>
> Didn't see the announcement here, but I found it a bit after I posted.
> 
> Thank you, Johnny, and the whole team.
> 

You are welcome.

The CentOS-6 kernel with the CVE-2016-5195 is finished, passed our CI
suite tests, and is now pushed to our master mirror
(kernel-2.6.32-642.6.2.el6)

It should be installable from mirror.centos.org in an hour or so.
External mirrors should also be able to start syncing to get it in about
and hour as well.

Still no upstream EL5 release.  We will get that one released as soon as
we have the source code for it.

Thanks,
Johnny Hughes




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

Re: [CentOS] CVE-2016-5195

2016-10-26 Thread Johnny Hughes 
On 10/25/2016 03:19 AM, aswathi...@accenture.com wrote:
> Hi Team,
> 
> Could you please help us to know about the CVE-2016-5195 on CentOs.
> 
> 
> I have server running with CentOS Linux release 7.2.1511 (Core)  , will this 
> be effected?
> 

It is affected .. and CentOS has released and update for this for
CentOS-7 already:

https://lists.centos.org/pipermail/centos-announce/2016-October/022133.html

If you run 'yum update', you should get kernel-3.10.0-327.36.3.el7




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

Re: [CentOS] "Shortcut" for creating a software RAID 60?

2016-10-26 Thread Sorin Srbu 
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of Gordon Messmer
> Sent: den 26 oktober 2016 08:25
> To: CentOS mailing list 
> Subject: Re: [CentOS] "Shortcut" for creating a software RAID 60?
> 
> On 10/25/2016 10:41 PM, Sorin Srbu wrote:
> > Never mind. Found this to start with.
> 
> 
> Additionally, see the man page for "md".

Gotcha'. Thanks.

-- 
//Sorin

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

Re: [CentOS] "Shortcut" for creating a software RAID 60?

2016-10-26 Thread Gordon Messmer 

On 10/25/2016 10:41 PM, Sorin Srbu wrote:

Never mind. Found this to start with.



Additionally, see the man page for "md".

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

Re: [CentOS] "Shortcut" for creating a software RAID 60?

2016-10-26 Thread Sorin Srbu 
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of John R Pierce
> Sent: den 26 oktober 2016 07:42
> To: centos@centos.org
> Subject: Re: [CentOS] "Shortcut" for creating a software RAID 60?
> 
> On 10/25/2016 11:54 AM, Gordon Messmer wrote:
> > If you built a RAID0 array of RAID6 arrays, then you'd fail a disk by
> > marking it failed and removing it from whichever RAID6 array it was a
> > member of, in the same fashion as you'd remove it from any other array
> > type.
> 
> FWIW, what I've done in the past is build the raid 6's with mdraid, then
> use LVM to stripe them into a volume group.

What's the advantage doing it that way?

Ease of maintenance maybe?

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