BSA: java.rmi.ConnectException: Connection refused to host" when executing a job

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    TrueSight Server Automation Suite


    APPLIES TO:

    BMC BladeLogic Server Automation Suite



    PROBLEM:

     

    When running a BSA job it fails with the following errorL

    [10 Dec 2009 19:04:33,641] [Job-Execution-0] [ERROR] [BLAdmin:BLAdmins:] [Deploy] Caught exception running command - /app/nsh/bin/du -s -k //servername/app/nsh/storage/blpackages/Test-2013019.1
    Error: java.rmi.ConnectException: Connection refused to host: servername; nested exception is:
    java.net.ConnectException: Connection refused
    com.bladelogic.mfw.util.BlException: Caught exception running command - /app/nsh/bin/du -s -k //servername/app/nsh/storage/blpackages/Test-2013019.1
    Error: java.rmi.ConnectException: Connection refused to host: servername; nested exception is:
    java.net.ConnectException: Connection refused
    at com.bladelogic.app.nsh.NSHExec.exec(NSHExec.java:377)
    at com.bladelogic.model.job.deploy.BaseDeployJobExecutor.executeNSHExecCommand(BaseDeployJobExecutor.java:356)
    at com.bladelogic.model.job.deploy.BaseDeployJobExecutor.getPackageDirSize(BaseDeployJobExecutor.java:370)
    at com.bladelogic.model.job.deploy.DeployJobSequentialExecutor.startJobExecution(DeployJobSequentialExecutor.java:176)
    at com.bladelogic.app.service.job.JobExecutor.processEvent(JobExecutor.java:323)
    at com.bladelogic.app.service.job.JobExecutor.processEvents(JobExecutor.java:179)
    at com.bladelogic.app.service.job.execution.JobExecutionThread.execute(JobExecutionThread.java:97)
    at com.bladelogic.app.service.job.execution.JobExecutionThread.execute(JobExecutionThread.java:20)
    at com.bladelogic.app.service.thread.BlBlockingThread.run(BlBlockingThread.java:92)

     


    SOLUTION:

     

    The java.rmi.ConnectException text in the error message is important here. If a Connection refused message is encountered without the java.rmi.ConnectException it is not a match for this problem. 
    If the Connection refused is  seen with the java.rmi.ConnectException then it's possible there is some issue with the appserver communicating with the process spawner.  A number of things can be checked:

      
       
    • Check if the appserver is configured to use the Process Spawner:  blasadmin -s <instance name> show ProcessSpawner SpawnExternally will be true if the appserver is configured to use the process spawner.
    •  
    • Check if the Process Spawner service is running - on Windows from the Windows Services Control Panel looking for a 'blprocserv' process in the output of 'ps -ef' on a Linux appserver.  Also check the <install dir>/NSH/br/spawner.log for recent updates
    •  
    • Check the Port the appserver is configured to use (blasadmin -s <instance name> show ProcessSpawner RegistryPort) and the spawner is configured to use (blasadmin -s _spawner show app registryport).  They should be the same.
    •  
    • Confirm there is no other configuration setting in blasadmin for any instance on the system using the same port.
       
        
      
        

     


    Article Number:

    000060766


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles