1 2 Previous Next 15 Replies Latest reply on May 12, 2015 3:01 PM by Bill Robinson

    NSH Here in 8.5 BSA console does not open NSH shell window

    S Crawford

      In the BladeLogic Server Automation Console 8.5.01.96 on RHEL 6.x, whenever I try to open an NSH session using the NSH Here custom command, nothing happens.  I looked at the console error log, and there is the following entry created from doing this:

       

      java.lang.UnsatisfiedLinkError: /opt/bmc/BladeLogic/8.5/NSH/lib/libXJNIService.so.1.0: libxerces-c-3.1.so: cannot open shared object file: No such file or directory

       

      I've attached the full stack error in this thread.  I checked to see if that library file existed, and it does:

       

      [root@client1_rhel lib]$ pwd

      /opt/bmc/BladeLogic/8.5/NSH/lib

      [root@client1_rhel lib]$ ls -al libX*

      lrwxrwxrwx. 1 root root         53 Jan 21 19:37 libXJNIService.so -> /opt/bmc/BladeLogic/8.5/NSH/lib/libXJNIService.so.1.0

      -rwxrwxr-x. 1 root bladmin 1028032 Jun 26  2014 libXJNIService.so.1.0

       

      I searched on kb.bmc.com but did not find any articles related to libXJNIService.so.  Has anyone encountered this before?

       

      Thanks

        • 1. Re: NSH Here in 8.5 BSA console does not open NSH shell window
          Bill Robinson

          ldd libXJNIService.so

          ...

            libxerces-c-3.1.so => /lib64/libxerces-c-3.1.so (0x00002ba9db026000)

          ...

           

          ls -la /lib64 | grep libxerces

          lrwxrwxrwx 1 root root 46 Oct 30 16:42 libxerces-c-3.1.so -> /opt/bmc/bladelogic/NSH/lib/libxerces-c-3.1.so

           

          so is that file there (the symlink and the actual file) ?

          • 2. Re: NSH Here in 8.5 BSA console does not open NSH shell window
            S Crawford

            It doesn't exist on the client with the 8.5 console:

             

            [root@client1_rhel ~]# cd /opt/bmc/BladeLogic/8.5/NSH/lib

            [root@client1_rhel lib]# ldd libXJNIService.so

                    linux-vdso.so.1 =>  (0x00007fff43fda000)

                    libblsrp.so => /lib64/libblsrp.so (0x00007f9c06db8000)

                    libnc.so => /lib64/libnc.so (0x00007f9c06b1b000)

                    libdl.so.2 => /lib64/libdl.so.2 (0x00007f9c06916000)

                    liblog4c.so => /lib64/liblog4c.so (0x00007f9c067b4000)

                    libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f9c06597000)

                    libBlAsJni.so => /lib64/libBlAsJni.so (0x00007f9c06435000)

                    libbrapi.so => /lib64/libbrapi.so (0x00007f9c0631a000)

                    libBlMessage.so => /lib64/libBlMessage.so (0x00007f9c06215000)

                    libBLCfgParser.so => /lib64/libBLCfgParser.so (0x00007f9c060b2000)

                    libhsreg.so => /lib64/libhsreg.so (0x00007f9c05fa2000)

                    libxerces-c-3.1.so => not found

                    libm.so.6 => /lib64/libm.so.6 (0x00007f9c05d1d000)

                    libc.so.6 => /lib64/libc.so.6 (0x00007f9c0598a000)

                    libblssl.so.0.9.8 => /lib64/libblssl.so.0.9.8 (0x00007f9c0583b000)

                    libblcrypto.so.0.9.8 => /lib64/libblcrypto.so.0.9.8 (0x00007f9c055d9000)

                    libacl.so.1 => /lib64/libacl.so.1 (0x00007f9c053d1000)

                    /lib64/ld-linux-x86-64.so.2 (0x00000036fac00000)

                    libBLerrors.so => /lib64/libBLerrors.so (0x00007f9c0528c000)

                    libbladmin.so => /lib64/libbladmin.so (0x00007f9c05110000)

                    libxerces-c-3.1.so => not found

                    libxerces-c-3.1.so => not found

                    libutil.so.1 => /lib64/libutil.so.1 (0x00007f9c04f0c000)

                    libblinexclude.so => /lib64/libblinexclude.so (0x00007f9c04e0a000)

                    libxerces-c-3.1.so => not found

                    libattr.so.1 => /lib64/libattr.so.1 (0x00007f9c04c04000)

                    libxerces-c-3.1.so => not found

            [root@client1_rhel lib]# ls -la /lib64 | grep libxerces

            [root@client1_rhel lib]#

             

            On a RHEL 6.x machine with the 8.2 BL console, libxerces-c-3.1.so doesn't exist either but the libXJNIService.so doesn't seem to require it:

             

            [root@client2_rhel ~]# cd /opt/bmc/BladeLogic/8.2/NSH/lib

            [root@client2_rhel lib]# ldd libXJNIService.so

                    linux-vdso.so.1 =>  (0x00007fff8d0e8000)

                    libblsrp.so => /lib64/libblsrp.so (0x00007fcc091f0000)

                    libnc.so => /lib64/libnc.so (0x00007fcc08f7b000)

                    libdl.so.2 => /lib64/libdl.so.2 (0x00007fcc08d76000)

                    liblog4c.so => /lib64/liblog4c.so (0x00007fcc08c14000)

                    libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fcc089f8000)

                    libBlAsJni.so => /lib64/libBlAsJni.so (0x00007fcc08896000)

                    libbrapi.so => /lib64/libbrapi.so (0x00007fcc0877c000)

                    libBlMessage.so => /lib64/libBlMessage.so (0x00007fcc08677000)

                    libBLCfgParser.so => /lib64/libBLCfgParser.so (0x00007fcc08137000)

                    libhsreg.so => /lib64/libhsreg.so (0x00007fcc08027000)

                    libm.so.6 => /lib64/libm.so.6 (0x00007fcc07da3000)

                    libc.so.6 => /lib64/libc.so.6 (0x00007fcc07a12000)

                    libblssl.so.0.9.8 => /lib64/libblssl.so.0.9.8 (0x00007fcc078c3000)

                    libblcrypto.so.0.9.8 => /lib64/libblcrypto.so.0.9.8 (0x00007fcc0763d000)

                    /lib64/ld-linux-x86-64.so.2 (0x0000003dd2600000)

                    libBLerrors.so => /lib64/libBLerrors.so (0x00007fcc074f7000)

                    libbladmin.so => /lib64/libbladmin.so (0x00007fcc07380000)

                    libutil.so.1 => /lib64/libutil.so.1 (0x00007fcc0717d000)

                    libblinexclude.so => /lib64/libblinexclude.so (0x00007fcc0707a000)

            [root@client2_rhel lib]# ls -la /lib64 | grep libxerces

            [root@client2_rhel lib]#

            • 3. Re: NSH Here in 8.5 BSA console does not open NSH shell window
              Bill Robinson

              Does the libxerces exist in the NSH/lib directory ?

              • 4. Re: NSH Here in 8.5 BSA console does not open NSH shell window
                Rajeev Gupta

                make sure the console version is same as your app server version.

                • 5. Re: NSH Here in 8.5 BSA console does not open NSH shell window
                  Bill Robinson

                  That won’t matter here if he’s missing files…

                  • 6. Re: NSH Here in 8.5 BSA console does not open NSH shell window
                    S Crawford

                    No, libxerces doesn't exist in NSH/lib either.  Is there a particular RHEL RPM that the console is expecting to be there during install that would've added this library file to /lib64?  If there is, I guess the console install isn't checking for it and/or isn't adding it.

                     

                    The console and app server versions are both 8.5.01.96.

                    • 7. Re: NSH Here in 8.5 BSA console does not open NSH shell window
                      Bill Robinson

                      That library should be part of the bsa console installer.  so this is a workstation – no other bsa components on it ?

                      • 8. Re: NSH Here in 8.5 BSA console does not open NSH shell window
                        S Crawford

                        Yes, this is a workstation, no other BSA programs or components (agent, app server, reporting server, etc).  It only has the BSA console on it.  It is running RHEL 6.4.  Is this a coding change from 8.2 since the libXJNIService.so file in the 8.2 console doesn't seem to reference libxerces?

                        • 9. Re: NSH Here in 8.5 BSA console does not open NSH shell window
                          Bill Robinson

                          Ok…i’ll spin up a vm and test.  You could try a re-install just to see if you want.

                          • 10. Re: NSH Here in 8.5 BSA console does not open NSH shell window
                            S Crawford

                            Thanks... hopefully you're getting the same results as me.  I just installed on another workstation (RHEL 6.2 this time) and am having the same issue.

                            • 11. Re: NSH Here in 8.5 BSA console does not open NSH shell window
                              Bill Robinson

                              Yeah – i have the same issue, it looks like the file is missing from the install.  also in patch4.

                               

                              For now you could probably copy it from an appserver that’s the same bsa version and drop it in NSH/lib.  But it’s possible there are other missing libs here.

                               

                              I’d open a ticket for this and we can get it fixed.

                              1 of 1 people found this helpful
                              • 12. Re: NSH Here in 8.5 BSA console does not open NSH shell window
                                S Crawford

                                Thanks Bill.  I tried copying the file from an 8.5 appserver to the NSH/lib directory, and also made a link to that file in the /lib64 directory, and once I did this, the NSH Here function worked again.

                                 

                                We opened ticket ISS04416941 to get an official fix created for this one.  In the mean time, I will probably have that library file added as part of our custom install, knowing there could be other library files missing as well. 

                                • 13. Re: NSH Here in 8.5 BSA console does not open NSH shell window
                                  Newton Nyante

                                  Defect QM001870903 has been created covering this problem.

                                  • 14. Re: NSH Here in 8.5 BSA console does not open NSH shell window

                                    Two ways to quasi get this to work.  At least, you'll be able to execute a few commands.

                                     

                                    yum install xerces-c

                                    ln -s /lib64/libxerces-c-3.1.so /lib64/libblxerces-c-3.1.so

                                     

                                    Note you'll have to tweak that a bit.  That gets at least the console to pop up for me (whereupon I do nexec -e 'sudo -i'

                                     

                                    But still seeing this defect in 8.6 SP1.  I've NOT tried getting the libtermcap.so.2 dependency working though. (e.g. do an ls on a host and you get ls: error while loading shared libraries: libtermcap.so.2: cannot open shared object file: No such file or directory)

                                    1 2 Previous Next