Forecast Tab Not Working in WCC

Document ID : KB000009086
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

After a power outage, we are no longer able to generate forecasts in WCC.

 

INFO | jvm 1 | 2018/01/01 13:42:09 | 515364 | @forecast <forecast-asynch-reports> [] ERROR #AutoSysCommandClient # IclException while calling sponsor: org.apache.http.conn.HttpHostConnectException: Connection to https://rhautosys1136sp6:5250 refused  

INFO | jvm 1 | 2018/01/01 13:42:09 | 515364 | @forecast <forecast-asynch-reports> [] ERROR #ReportsCommandServiceImpl # Error occured while attempting to generate report test forecast 

INFO | jvm 1 | 2018/01/01 13:42:09 | 515364 | com.ca.uejm.command.client.common.CommandException: org.apache.http.conn.HttpHostConnectException: Connection to https://rhautosys1136sp6:5250 refused 

INFO | jvm 1 | 2018/01/01 13:42:09 | 515364 | at com.ca.uejm.command.client.autosys.AutoSysCommandClient.run(AutoSysCommandClient.java:316) 

Environment:
CA Workload Control Center r11.3.6+ CA Workload Control Center r11.4+
Cause:

1. The iGateway service for the Autosys Command Sponsor was not restarted after the power outage.

2. The iGateway service for the Autosys Command Sponsor is still running on the pid prior to the outage and has become a zombie process. 

Resolution:

On the server where Autosys is installed, do the following: 

 

1. Navigate to the $IGW_LOC directory 

2. Run the following command : ps -ef | grep igateway 

    OPTION I: If the iGateway process is NOT running, then run the following command: ./S99igateway start

    OPTION II: If the iGateway process is running, then run the following command: kill -9 <pid_of_igateway>

                     Then run the following command: ./S99igateway start