4 Replies Latest reply on Nov 23, 2016 2:51 AM by phoffmann

    Landesk 9.6 on Aix 7.1.0.0.

    Rookie

      I install all the necessary rpm files to get the agent installed but I get this when I run the installer.

       

      (server)root # /tmp/aix > ./aixagent.sh
      Mon Sep 19 09:19:03 EDT 2016
      Removing packages: vulscan ...
      Finished removal.
      Expanding baseclient64 ...
      Installing baseclient64 ...
      /tmp/aix/tmp
      setup.sh
      invperiod set to 24
      package cba8-9.6-1.1321 is already installed
      package ldiscan-9.6-1.3320 is already installed
      package sdclient-9.6-1.3320 is already installed
      Finished with baseclient64 ...
      exec(): 0509-036 Cannot load program cba because of the following errors:
      rtld: 0712-001 Symbol strcmp was referenced
            from module cba(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-001 Symbol memmove was referenced
            from module cba(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-001 Symbol strncpy was referenced
            from module cba(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-001 Symbol strcpy was referenced
            from module cba(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-001 Symbol strcat was referenced
            from module cba(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-001 Symbol X509_subject_name_hash_old was referenced
            from module cba(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-001 Symbol bcopy was referenced
            from module cba(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-002 fatal error: exiting.

      exec(): 0509-036 Cannot load program proxyhost because of the following errors:
      rtld: 0712-001 Symbol strcmp was referenced
            from module proxyhost(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-001 Symbol memmove was referenced
            from module proxyhost(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-001 Symbol strncpy was referenced
            from module proxyhost(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-001 Symbol strcpy was referenced
            from module proxyhost(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-001 Symbol strcat was referenced
            from module proxyhost(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-001 Symbol X509_subject_name_hash_old was referenced
            from module proxyhost(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-001 Symbol bcopy was referenced
            from module proxyhost(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-002 fatal error: exiting.
      map-fetchinvsettings: no header data read from proxyhost
      map-fetchinvsettings: failed to read inventory settings reply headers from core
      ldiscan: Error: Could not ping the core: INFLDMS.priv.health-first.org
      Notifying core of installation ...
      exec(): 0509-036 Cannot load program alert because of the following errors:
      rtld: 0712-001 Symbol strcmp was referenced
            from module alert(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-001 Symbol memmove was referenced
            from module alert(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-001 Symbol strncpy was referenced
            from module alert(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-001 Symbol strcpy was referenced
            from module alert(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-001 Symbol strcat was referenced
            from module alert(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-001 Symbol bcopy was referenced
            from module alert(), but a runtime definition
            of the symbol was not found.
      rtld: 0712-002 fatal error: exiting.
      Successfully finished installing client.
      Exiting with return code 0

       

      Is it some libraries? Any help would be great.

        • 1. Re: Landesk 9.6 on Aix 7.1.0.0.
          Rookie

          Landesk 9.6 sp2

          • 2. Re: Landesk 9.6 on Aix 7.1.0.0.
            phoffmann SupportEmployee

            So a couple of things here, that'll hopefully help.

             

            Disclaimer - I don't have access to an AIX system since those things can't be virtualised (without having an AIX system in the first place). So there's limited stuff I can do here.

            1. SP3 for 9.6 has been available for a while. You may want to upgrade to that? You can find a link to it here -- LANDESK Management Suite 9.6 Service Pack 3 now available
            2. Before installing the script/agent, try to run the uninstall script? That's the "rmlinux64client.sh" in "C:\Program Files\LANDesk\ManagementSuite\ldlogon\unix\" (default location). The script gets updated with the SP3 install ... older scripts (for 9.0 and 9.5) can be found here - How to manually remove the Linux/Unix agent

             

            ... a bunch of your errors read to me like there's something of an incomplete / unclean uninstall and that may cause some issues?

             

            Also - This section here:

            (...)

            map-fetchinvsettings: no header data read from proxyhost

            map-fetchinvsettings: failed to read inventory settings reply headers from core

            ldiscan: Error: Could not ping the core: INFLDMS.priv.health-first.org

            (...)

            ... seems like a networking / resolution issue to me. You may want to look into your RESOLV.CONF (or it's equivalent) and make sure you can actually talk to your Core?

             

            Also - you may want to check in to using IP-addresses for your Core in your NIX agent config, if you're having DNS issues?

             

            Hope that helps?

            • 3. Re: Landesk 9.6 on Aix 7.1.0.0.
              Rookie

              Tried and same error. Added  Landesk core server to hosts file with IP and ran uninstaller and tried to do install but get same error.

              • 4. Re: Landesk 9.6 on Aix 7.1.0.0.
                phoffmann SupportEmployee

                Just to clarify - you tried what? You tried updating to 9.6 SP3 - and/or you tried to use the uninstaller?

                 

                If you're seeing consistent issues with installing the agent (which is a bit odd, since "you had it on before"), you may want to run an STRACE (which I assume will exist on AIX?). STRACE is a NIX system tracing thing that sufficiently capable people can read to find out "what's being done / what's going on" and can give a hint as to where and why things are falling over (say - for instance - a buffer overflow happens when trying to read a value for your keyboard string).

                 

                How do you use STRACE? Well - here's a bit of a rough guide that'll get you started. You'd need to STRACE the install, obviously.

                 

                STRACE is a *-IX specific debug thing. In windows-speak, it effectively monitors API’s and resources that a process uses.

                 

                Example command:

                “”

                truss -o /tmp/ldsysscan.trace /opt/landesk/bin/map-systemscan -V255 -o /tmp/ldsysscan.out -l /tmp/ldsysscan.log

                “”

                 

                Effectively, it’s 2 parts (red and green).

                 

                The Green bit is easy – that’s just the command you’re wanting to run (in this case, map-systemscan with max verbosity and output-file & log-file option).

                 

                The red bit is you telling STRACE to actually run, and where to log its output to (so in this case - /tmp/ldsysscan.trace - ) … by and large, that’s it.

                 

                If you're not confident in reading the STRACE itself, you'd need to open up a call with support, provide them the STRACE along with a description of your problem, and they should be able to (most likely) shoot it at out devs to make sense of.

                 

                Again - since I don't have access to an AIX system, this is about the best I can offer you at the moment.