SCIENTIFIC-LINUX-USERS Archives

July 2016

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
SCHAER Frederic <[log in to unmask]>
Reply To:
SCHAER Frederic <[log in to unmask]>
Date:
Thu, 28 Jul 2016 07:36:58 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (1 lines)
Probably...



So.

I took the SL SRPM (http://ftp.scientificlinux.org/linux/scientific/6.8/SRPMS/vendor/libcgroup-0.40.rc1-18.el6_8.src.rpm) , rebuilt it and ... 



[root@dev7247 libcgroup]# cp rebuilt/lib64/libcgroup.so.1.0.40 /lib64/

cp: overwrite `/lib64/libcgroup.so.1.0.40'? y

[root@dev7247 libcgroup]# service cgconfig restart

Stopping cgconfig service:                                 [  OK  ]

Starting cgconfig service:                                 [  OK  ]



... ? uncaught IO errors at build time ?



-----Message d'origine-----

De : [log in to unmask] [mailto:[log in to unmask]] De la part de Steven Haigh

Envoyé : jeudi 28 juillet 2016 09:00

À : [log in to unmask]

Cc : Connie Sieh <[log in to unmask]>

Objet : Re: sl6.8 libcgroup -- bug



That could probably be Connie atm.



CC'ed into this thread.



On 2016-07-28 16:08, Stijn De Weirdt wrote:

> hi fredric,

> 

> i confirm, things seem ok with the centos rpm

> 

> quick inspection of the rpms also does not show something obviously

> wrong (both rpms ship same files with same sizes).

> 

> i took the centos rpms, modified the release using rpmrebuild

> (rpmrebuild --release=18.el6_8.0.fromcentos -p thecentosrpms) for all

> libcgroup rpms and added them to one of our local repos. yum is happy 

> again.

> 

> how do we report this to the SL packagers? (or do we just assume they

> read all these mails?)

> 

> stijn

> 

> On 07/27/2016 05:22 PM, SCHAER Frederic wrote:

>> Same here.

>> Hey ! This seems SL specific... !?

>> 

>> I installed this one manually : 

>> CentOS/6.8/updates/x86_64/Packages/libcgroup-0.40.rc1-18.el6_8.x86_64.rpm

>> 

>> [root@dev7247 ~]# cat /etc/redhat-release

>> Scientific Linux release 6.8 (Carbon)

>> 

>> [root@dev7247 ~]# rpm -qi libcgroup

>> Name        : libcgroup                    Relocations: (not 

>> relocatable)

>> Version     : 0.40.rc1                          Vendor: CentOS

>> Release     : 18.el6_8                      Build Date: Tue 12 Jul 

>> 2016 06:27:20 PM CEST

>> Install Date: Wed 27 Jul 2016 05:15:28 PM CEST      Build Host: 

>> worker1.bsys.centos.org

>> (...)

>> 

>> And cgroups seem to still work whereas they failed with the SL RPM :

>> [root@dev7247 ~]# service cgconfig restart

>> Stopping cgconfig service:                                 [  OK  ]

>> Starting cgconfig service:                                 [  OK  ]

>> 

>> ?

>> 

>> Regards

>> 

>> -----Message d'origine-----

>> De : [log in to unmask] 

>> [mailto:[log in to unmask]] De la part de 

>> ~Stack~

>> Envoyé : mercredi 27 juillet 2016 12:59

>> À : Stijn De Weirdt <[log in to unmask]>; 

>> [log in to unmask]

>> Objet : Re: sl6.8 libcgroup

>> 

>> On 07/27/2016 03:53 AM, Stijn De Weirdt wrote:

>>> hi all,

>>> 

>>> 

>>> we have a update an sl67 node to sl68 (but not yet updated the 

>>> kernel),

>>> and this updates

>>> libcgroup-0.40.rc1-17.el6_7.x86_64

>>> to

>>> libcgroup-0.40.rc1-18.el6_8.x86_64

>>> 

>>> however, it now seems that the cgonfigparser even fails to validate 

>>> the

>>> distributed /etc/cgconfig.conf

>>> 

>>>> [root@test2802 ~]# /sbin/cgconfigparser -l /etc/cgconfig.conf

>>>> error at line number 17 at {:syntax error

>>>> Error: failed to parse file /etc/cgconfig.conf

>>>> /sbin/cgconfigparser; error loading /etc/cgconfig.conf: Have 

>>>> multiple paths for the same namespace

>>> 

>>> 

>>> the /etc/cgconfig.conf is the same in both rpms

>>> 

>>> anyone seeing this? or knows how to fix?

>> 

>> Greetings,

>> 

>> I discovered the exact same thing. I fully updated to 6.8 and rebooted

>> into the new kernel. I haven't filed a bug report against it yet as I

>> didn't have time yesterday to really dig into it. My "workaround" was 

>> to

>> "yum downgrade libcgroup" on all my hosts until I could figure it out.

>> 

>> ~Stack~

>> 

>> 



-- 

Steven Haigh



Email: [log in to unmask]

Web: https://www.crc.id.au

Phone: (03) 9001 6090 - 0412 935 897


ATOM RSS1 RSS2