Hi Stijn,

In some (old) forums it's stated that such things should be reported here, and 
on the SL FAQ that we might send our findings/patches to the SL-DEV mailing 
list... (I'm not subscribed on that one)
For now, I've just found that it's the shared library that's in cause :

[root@dev7247 libcgroup]# service cgconfig restart
Stopping cgconfig service:                                 [  OK  ]
Starting cgconfig service:                                 [  OK  ]
[root@dev7247 libcgroup]# cp sl/lib64/libcgroup.so.1.0.40 
/lib64/libcgroup.so.1.0.40
cp: overwrite `/lib64/libcgroup.so.1.0.40'? y
[root@dev7247 libcgroup]# service cgconfig restart
Stopping cgconfig service:                                 [  OK  ]
Starting cgconfig service: error at line number 4 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
error at line number 5 at =:syntax error
Error: failed to parse file /etc/cgconfig.d/htcondor.conf
/sbin/cgconfigparser; error loading /etc/cgconfig.d/htcondor.conf: Have 
multiple paths for the same namespace
Failed to parse /etc/cgconfig.conf or /etc/cgconfig.d      [FAILED]

Regards

-----Message d'origine-----
De : Stijn De Weirdt [mailto:[email protected]] 
Envoyé : jeudi 28 juillet 2016 08:09
À : SCHAER Frederic <[email protected]>; ~Stack~ <[email protected]>; 
[email protected]
Objet : Re: sl6.8 libcgroup -- bug

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 : [email protected] 
> [mailto:[email protected]] De la part de ~Stack~
> Envoyé : mercredi 27 juillet 2016 12:59
> À : Stijn De Weirdt <[email protected]>; [email protected]
> 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~
> 
> 

Reply via email to