Problem: dscontrol or lbadmin command fails

  1. The dscontrol command returns: Error: Server not responding. Or, the lbadmin command returns: Error: unable to access RMI server. These errors can result when your machine has a socksified stack. To correct this problem, edit the socks.cnf file to contain the following lines:
    EXCLUDE-MODULE java
    EXCLUDE-MODULE javaw
  2. The administration consoles for Load Balancer interfaces (command line, graphical user interface, and wizards) communicate with dsserver using remote method invocation (RMI). The default communication uses three ports; each port is set in the dsserver start script:
    • 10099 to receive commands from dscontrol
    • 10004 to send metric queries to Metric Server
    • 10199 for the RMI server port

    This can cause problems when one of the administration consoles runs on the same machine as a firewall or through a firewall. For example, when Load Balancer runs on the same machine as a firewall, and you issue dscontrol commands, you might see errors such as Error: Server not responding.

    To avoid this problem, edit the dsserver script file to set the port used by RMI for the firewall (or other application). Change the line: LB_RMISERVERPORT=10199 to LB_RMISERVERPORT=yourPort. Where yourPort is a different port.

    When complete, restart dsserver and open traffic for ports 10099, 10004, 10199, and 10100, or for the chosen port for the host address from which the administration console will be run.

  3. These errors can also occur if you have not already started dsserver.
  4. If there are multiple adapters on the machine, you must designate which adapter that dsserver is to use by adding the following in the dsserver script:java.rmi.server.hostname=<host_name or IPaddress>

    For example: java -Djava.rmi.server.hostname="10.1.1.1"



Terms and conditions for information centers | Feedback

Last updated: February 21, 2013 02:45 PM EST
File name: ttrb_crmif.html