ViPR SRM 4.2.1: MySQL-client will not launch during upgrade to 4.2.1[7]

           

   Article Number:     520696                                   Article Version: 4     Article Type:    Break Fix 
   

 


Product:

 

ViPR SRM 4.2,ViPR SRM 4.2 SP1

 

Issue:

 

 

The embedded mysql-client will not allow login access on the Primary or Additional Backend servers and reports the following error:   
   
    /opt/APG/../mysql: error while loading shared libraries: libtinfo,so,5: cannot open shared object file: No such file or directory   
   
    Tests were performed with the following:   
    Enter username: [apg] both root and apg   
    Enter database: [apg] attempted connection to apg, compliance and events   
     
                                                           

 

 

Cause:

 

 

The soft-link is missing to the newly added library that was deployed during the update of the MySQL database. The SRM 4.2.1 has an update SLES OS that is missing the libtinfo.so.5 file and will cause the mysql-client to fail.                                                           

 

 

Change:

 

 

Create the soft link to the new library file.                                                           

 

 

Resolution:

 

 

To resolve this issue a soft link needs to be added with a pointer to the new library. This link needs to be added on all database Servers in the SRM installation.   
   
    To add the soft link you will need to login to the applicable server and use the following command:   
   
    ln -s /lib64/libncurses.so.5.6 /lib64/libtinfo.so.5    
   
    NOTE: if you are not logged in as root you may need to use sudo to run the command   
     
                                                           

 

 

Notes:

 

 

Please review Knowledgebase Article 520855 if there are any other library issues with MySQL during the SRM update.