Installed TSCO Gateway Server, I don't see the GeneralManagerServer process running
Legacy ID:KA426011If Gateway Server hadn't been contacted and added by the General Manager UI, the GeneralManagerServer process won't be started.
Beginning with Service Daemon version 7.5.10 a new feature was added to the Service Daemon. If General Manager UI can't contact with General Manager Server on port 10129 on the remote Gateway Server, it will try to contact Service Daemon on port 10128. If the GeneralManagerServer process was not running the Service Daemon will restart the GeneralManagerServer process on the Gateway Server.
Check if port 10129 is enabled on the Gateway server:
netstat -an |grep 10129
Check if general manager service is running or not on Gateway server, as port 10129 belongs only to this service
telnet <GW_server_Hostname> 10129
If the port 10129 is enabled try to telnet port 10129 from TSCO Application Server to check if Gateway Server is reachable from the Application Server
Try to add the new Gateway Server to the General Manager component in the TrueSight Capacity Optimization console. Check if the GeneralManager Server is started now.
If that fails, a workaround is to log into the Gateway Server as the perform user and run the following command "
nohup $BEST1_HOME/bgs/bin/GeneralManagerServer 10129 &
That should start the GeneralManagerServer process and the General Manager UI should be able to add the server correctly. In this case, you would only need to start the GeneralManagerServer manually one time. After you schedule a manager run on the Gateway server, pcron will restart the GeneralManagerServer, if it is not running.