Why doesn't the session manager start?

Symphony DE and grid

  • The application is configured such that preStartApplication is false (default), which means that Symphony does not attempt to start a session manager for the application until a client tries to connect to the application. Run your client and check whether a session manager is started.

  • Windows: The SSM host runs in a non-domain (WORKGROUP) environment. However, the SD host may be configured to append a domain name to hosts with DHCP. It may event try to append a domain name to a host in a non-domain environment, which results in an incorrect host name that cannot be resolved. There are two ways to resolve this problem:

    1. Configure the SD host to not append DNS suffixes.
      1. Navigate to Control Panel > Network Connections.

      2. Right click on your network connection and select Properties.

        Another dialog displays.

      3. In the scroll box, select Internet Protocol (TCP/IP) and click Properties.

      4. Click Advanced.

      5. Select the DNS tab.

      6. If possible, configure your DNS settings to not append DNS suffixes.

    2. On the SD host, edit C:\Windows\system32\drivers\etc\hosts to map the SSM host name (with the appended domain suffix) to an IP address. Add a line to the file that contains the IP address and the SSM host name with the appended domain name.

      For example, 172.17.18.35 hostA.mydomain.

Symphony DE

You have already started the maximum number of session managers that your DE cluster is configured to support. Increase the number of session managers that your DE cluster can support.

  1. Shut down your DE cluster.

  2. Modify the following file to increase the max number of SSMs the SD can start:
    • Windows: %SOAM_HOME%\conf\vem_resource.conf

    • Linux: $SOAM_HOME/conf/vem_resource.conf

      #
      # AGENT service information
      # <service name>:<port_number>:<host_name>:<max number of #SSMs SD can start>:<max number of SIMs SSM can #start>:<OS_type>:<CPU_factor>
      #
      AGENT:8000:localhost:25:2:NTX86:1
  3. Start the DE cluster.

Symphony grid

  • There are no available slots on which to run a session manager. Check that your resource plan is configured correctly.

  • The session director or other necessary cluster components may be down. Follow the Easy Cluster Verification Steps To Get Started document in the Knowledge Center for detailed information on how to troubleshoot cluster startup issues.

  • Windows: If your application's OS execution user password has expired, make sure you have set your new password with EGO. If you do not update your password, EGO may fail to start a session manager process because it is trying to start it using an invalid user name and password. Use the egosh ego execpasswd command to set your new password with EGO.