hwcap index 1 already defined as nosegneg

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • amintaheri1
    Junior Member
    Forum Explorer
    • Mar 2021
    • 10
    #1

    hwcap index 1 already defined as nosegneg

    Is this all normal and ok?
    I know it says non fatal, but since it happened on almost every package I wanted to double check this isnt a problem.

    > Transaction Test Succeeded
    > Running Transaction
    > Updating : net-snmp-libs 1/22
    > Updating : net-snmp 2/22
    > Updating : postgresql-libs 3/22
    > Installing : kernel-xen 4/22
    > /sbin/ldconfig: /etc/ld.so.conf.d/kernelcap-2.6.18-408.el5.lve0.8.61.1.conf:6: hwcap index 1 already defined as nosegneg
    > Non-fatal POSTIN scriptlet failure in rpm package kernel-xen-2.6.18-408.el5.lve0.8.61.1.x86_64
    > error: %post(kernel-xen-2.6.18-408.el5.lve0.8.61.1.x86_64) scriptlet failed, exit status 1
    > Updating : lve 5/22
    > Updating : liblve 6/22
    > /sbin/ldconfig: /etc/ld.so.conf.d/kernelcap-2.6.18-408.el5.lve0.8.61.1.conf:6: hwcap index 1 already defined as nosegneg
    > Non-fatal POSTIN scriptlet failure in rpm package liblve-0.8-56.el5.cloudlinux.x86_64
    > error: %post(liblve-0.8-56.el5.cloudlinux.x86_64) scriptlet failed, exit status 1
    > Updating : net-snmp-devel 7/22
    > Installing : kernel-devel 8/22
    > Updating : tzdata 9/22
    > Installing : kernel-xen-devel 10/22
    > Updating : postgresql-libs 11/22
    > /sbin/ldconfig: /etc/ld.so.conf.d/kernelcap-2.6.18-408.el5.lve0.8.61.1.conf:6: hwcap index 1 already defined as nosegneg
    > Non-fatal POSTIN scriptlet failure in rpm package postgresql-libs-8.1.23-4.el5_8.i386
    > error: %post(postgresql-libs-8.1.23-4.el5_8.i386) scriptlet failed, exit status 1
    > Cleanup : kernel-xen 12/22
    > Cleanup : lve 13/22
    > Cleanup : net-snmp 14/22
    > Cleanup : liblve 15/22
    > /sbin/ldconfig: /etc/ld.so.conf.d/kernelcap-2.6.18-408.el5.lve0.8.61.1.conf:6: hwcap index 1 already defined as nosegneg
    > Non-fatal POSTUN scriptlet failure in rpm package l
    > Cleanup : net-snmp-devel 16/22
    > error: %postun(liblve-0.8-41.el5.cloudlinux.x86_64) scriptlet failed, exit status 1
    > Cleanup : tzdata 17/22
    > Cleanup : net-snmp-libs 18/22
    > /sbin/ldconfig: /etc/ld.so.conf.d/kernelcap-2.6.18-408.el5.lve0.8.61.1.conf:6: hwcap index 1 already defined as nosegneg
    > Non-fatal POSTUN scriptlet failure in rpm package n
    > Cleanup : kernel-devel 19/22
    > error: %postun(net-snmp-libs-5.3.2.2-17.el5.x86_64) scriptlet failed, exit status 1
    > Cleanup : postgresql-libs 20/22
    > /sbin/ldconfig: /etc/ld.so.conf.d/kernelcap-2.6.18-408.el5.lve0.8.61.1.conf:6: hwcap index 1 already defined as nosegneg
    > Non-fatal POSTUN scriptlet failure in rpm package p
    > Cleanup : kernel-xen-devel 21/22
    > error: %postun(postgresql-libs-8.1.23-1.el5_7.3.x86_64) scriptlet failed, exit status 1
    > /sbin/ldconfig: /etc/ld.so.conf.d/kernelcap-2.6.18-408.el5.lve0.8.61.1.conf:6: hwcap index 1 already defined as nosegneg
    > Non-fatal POSTTRANS scriptlet failure in rpm package liblve-0.8-56.el5.cloudlinux.x86_64
    > error: %posttrans(liblve-0.8-56.el5.cloudlinux.x86_64) scriptlet failed, exit status 1
    >
    > Removed:
    > kernel-devel.x86_64 0:2.6.18-374.12.1.el5.lve0.8.54 kernel-xen.x86_64 0:2.6.18-374.12.1.el5.lve0.8.54 kernel-xen-devel.x86_64 0:2.6.18-374.12.1.el5.lve0.8.54
    >
    > Installed:
    > kernel-devel.x86_64 0:2.6.18-408.el5.lve0.8.61.1 kernel-xen.x86_64 0:2.6.18-408.el5.lve0.8.61.1 kernel-xen-devel.x86_64 0:2.6.18-408.el5.lve0.8.61.1
    >
    > Updated:
    > liblve.x86_64 0:0.8-56.el5.cloudlinux lve.x86_64 0:0.8-56.el5.cloudlinux net-snmp.x86_64 1:5.3.2.2-17.el5_8.1 net-snmp-devel.x86_64 1:5.3.2.2-17.el5_8.1 net-snmp-libs.x86_64 1:5.3.2.2-17.el5_8.1
    > postgresql-libs.i386 0:8.1.23-4.el5_8 postgresql-libs.x86_64 0:8.1.23-4.el5_8 tzdata.x86_64 0:2012c-1.el5
    >
    > Complete!
    Tags: None
    • amintaheri1
      Junior Member
      Forum Explorer
      • Mar 2021
      • 10
      #2
      This happens on every yum update, even ones taht have nothing to do with the kernel

      > Running Transaction
      > Updating : expat 1/8
      > /sbin/ldconfig: /etc/ld.so.conf.d/kernelcap-2.6.18-408.el5.lve0.8.61.1.conf:6: hwcap index 1 already defined as nosegneg
      > Non-fatal POSTIN scriptlet failure in rpm package expat-1.95.8-11.el5_8.x86_64
      > error: %post(expat-1.95.8-11.el5_8.x86_64) scriptlet failed, exit status 1
      > Updating : expat 2/8
      > /sbin/ldconfig: /etc/ld.so.conf.d/kernelcap-2.6.18-408.el5.lve0.8.61.1.conf:6: hwcap index 1 already defined as nosegneg
      > Non-fatal POSTIN scriptlet failure in rpm package expat-1.95.8-11.el5_8.i386
      > error: %post(expat-1.95.8-11.el5_8.i386) scriptlet failed, exit status 1
      > Updating : expat-devel 3/8
      > Updating : gawk 4/8
      > Cleanup : expat-devel 5/8
      > Cleanup : expat 6/8
      > /sbin/ldconfig: /etc/ld.so.conf.d/kernelcap-2.6.18-408.el5.lve0.8.61.1.conf:6: hwcap index 1 already defined as nosegneg
      > Non-fatal POSTUN scriptlet failure in rpm package e
      > Cleanup : gawk 7/8
      > error: %postun(expat-1.95.8-8.3.el5_5.3.x86_64) scriptlet failed, exit status 1
      >
      > Updated:
      > expat.i386 0:1.95.8-11.el5_8 expat.x86_64 0:1.95.8-11.el5_8 expat-devel.x86_64 0:1.95.8-11.el5_8 gawk.x86_64 0:3.1.5-16.el5
      >
      > Complete!

      please advise.

        Comment

        • lkanter
          Member
          • Nov 2016
          • 34
          #3
          Please provide output of

          grep ^hwcap /etc/ld.so.conf.d/*

            Comment

            • amintaheri1
              Junior Member
              Forum Explorer
              • Mar 2021
              • 10
              #4
              Hi Leonid,

              Thanks for your reply, here is the output of the command as requested.

              > # grep ^hwcap /etc/ld.so.conf.d/*
              > /etc/ld.so.conf.d/kernelcap-2.6.18-374.18.1.el5.lve0.8.57.conf:hwcap 1 nosegneg
              > /etc/ld.so.conf.d/kernelcap-2.6.18-408.el5.lve0.8.58.conf:hwcap 1 nosegneg
              > /etc/ld.so.conf.d/kernelcap-2.6.18-408.el5.lve0.8.61.1.conf:hwcap 0 nosegneg
              >
              > # uname -r
              > 2.6.18-408.el5.lve0.8.58xen

              We haven rebooted into the newest kernel yet on all boxes.

                Comment

                • lkanter
                  Member
                  • Nov 2016
                  • 34
                  #5
                  Please remove two old files /etc/ld.so.conf.d/kernelcap-2.6.18-374.18.1.el5.lve0.8.57.conf and /etc/ld.so.conf.d/kernelcap-2.6.18-408.el5.lve0.8.58.conf and run ldconfig. With future kernel updates it should not happen.

                    Comment

                    • amintaheri1
                      Junior Member
                      Forum Explorer
                      • Mar 2021
                      • 10
                      #6
                      Thanks, that seemed to have solved it. Ill report back if I find otherwise but for now please consider this closed with my thanks!

                        Comment

                        • amintaheri1
                          Junior Member
                          Forum Explorer
                          • Mar 2021
                          • 10
                          #7
                          Just as a follow up, this continues to happen, we install new kernels and this keeps happening. Can you please update your kernel installation process to remove the older files and fix the ldconfig on your own? Ive never in my life had this happen so many times until we started using CL.

                            Comment

                            • amintaheri1
                              Junior Member
                              Forum Explorer
                              • Mar 2021
                              • 10
                              #8
                              Just wanted to mention that this is still happening a year later.

                              # rpm -e apr-1.2.7-11.el5_6.5.cloudlinux.5.x86_64
                              /sbin/ldconfig: /etc/ld.so.conf.d/kernelcap-2.6.18-448.4.1.el5.lve0.8.69.1.conf:6: hwcap index 1 already defined as nosegneg
                              error: %postun(apr-1.2.7-11.el5_6.5.cloudlinux.5.x86_64) scriptlet failed, exit status 1

                              # grep ^hwcap /etc/ld.so.conf.d/*
                              /etc/ld.so.conf.d/kernelcap-2.6.18-408.8.2.el5.lve0.8.61.3.conf:hwcap 1 nosegneg
                              /etc/ld.so.conf.d/kernelcap-2.6.18-448.4.1.el5.lve0.8.69.1.conf:hwcap 0 nosegneg

                              # uname -r
                              2.6.18-408.8.2.el5.lve0.8.61.3xen

                                Comment

                                • iseletsk
                                  Senior Member
                                  • Dec 2017
                                  • 1199
                                  #9
                                  That is because you still have a kernel from a year ago. The bug was fixed in lve 0.8.61.3 kernel. Remove old kernel, and you will not see it any more.

                                    Comment

                                    • dmelnik3289
                                      Junior Member
                                      • Sep 2021
                                      • 6
                                      #10
                                      Thanks for sharing this information. I really like your blog post very much. You have really shared an informative and interesting blog always, Keep it up!!!!

                                        Comment

                                        Previous template Next
                                        Working...

                                        We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

                                        By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

                                        I Agree