Unisphere for PowerMax: smas service does not start for new installation of Unisphere for PowerMax on RHEL platform.

           

   Article Number:     525267                                   Article Version: 3     Article Type:    Break Fix 
   

 


Product:

 

Unisphere for PowerMax,Unisphere for VMAX

 

Issue:

 

 

New installation of Unisphere for PowerMax deploys the software components and the last action is to start the smas service.   
    For installation on RHEL platform (v7.3), the smas service fails to start.   
   
    Installation screen (last part):   

      Starting SMAS Service....       
        ===============================================================================       
        Please Wait       
        -----------       
        ===============================================================================       
        Unisphere for PowerMax  Configuration Error       
        -------------------------------------------       
        SMAS Service failed to start.
   
   
    <installDir>/SMAS/installerlogs/EMC_SMAS_INSTALL_STATUS contains:   
      DEPLOY SMAS SERVICE       
        START SMAS SERVICE
   
    what is expected from a successful installation is:   
      DEPLOY SMAS SERVICE       
        START SMAS SERVICE       
        UNIVMAX INSTALLATION :SUCCESSFUL:0
   
   
    Attempt to manually check status and start smas service fails with:   
      # /etc/init.d/smas status       
        JBOSS_USER is null or not set properly . Please set it correctly to continue       
        # /etc/init.d/smas start       
        Starting smas (via systemctl):  Job for smas.service failed because the control process exited with error code. See "systemctl status smas.service" and "journalctl -xe" for details.                      
                                     
   
    /var/log/messages log contains:   
      storage-vm systemd: Starting LSB: smas service...       
        storage-vm smas: JBOSS_USER is null or not set properly . Please set it correctly to continue       
        storage-vm systemd: smas.service: control process exited, code=exited status=255       
        storage-vm systemd: Failed to start LSB: smas service.       
        storage-vm systemd: Unit smas.service entered failed state.       
        storage-vm systemd: smas.service failed.
   
   
                                                                

 

 

Cause:

 

 

The installer fails to write to /etc/init.d/smas to set the JBOSS_USER to the root account.                                                           

 

 

Resolution:

 

 

As a workaround, do the following steps to set the JBOSS_USER correctly in the smas statup script:    

      1.    cd /etc/init.d     
      2.    Edit smas file to update (and save)  placeholder "<non-root-user>" with the value root in only one place if smas file contains JBOSS_USER="<non-root-user>", for example change     
          
   
      # Set defaults.       
        #JBOSS_USER=root       
        JBOSS_USER="<non-root-user>"
   
   
     
      to:   
   
      # Set defaults.       
        #JBOSS_USER=root       
        JBOSS_USER=root
   
   
     
      3. Start the smas service with /etc/init.d/smas start and check its status with /etc/init.d/smas start