Troubleshooting Startup of Workers from the Worker Agent
When the worker has successfully connected to the Worker Agent using a manual start of the worker, attempt to start it by selecting the entry in the adapter drop-down list. When the entry is selected, the menu stays selected, until the startup timeout is exceeded, or a connection from the worker is achieved.
If this fails, check to see if the command specified to execute it is in fact correct.
Local Worker on Windows – In the case of a local worker on Windows, it is worth trying to run the command using cmd.exe. For example, a Creo Parametric worker can be started as:
cmd.exe /C start "PROEWORKER" /MIN c:\ptc\program_files
\productview_adapters\proe_setup\proeworker.bat
Remote Worker on Windows – Workers that are running on a remote Windows client must be started using the Worker Daemon.
Remote Worker on UNIX – For remote UNIX workers, you must specify nohup and put the task in the background. Also, Telnet is used to connect to the remote worker. To test, use Telnet from the Worker Agent host, to the worker host. Specify the hostname, username, and password defined (in the agent.ini file) during the configuration of the worker. Assuming a successful connection, it is important that the system prompt (for that user) should not change. Manually executing the specified worker command from this environment should create a connection to the Worker Agent. If not, there is probably a difference in the environment used by Telnet and that of the default user login. Adjust the environment to ensure that the command causes a connection via Telnet, and look for things like DISPLAY, path, and shell type. The Worker Agent should then be able to start the worker.
Was this helpful?