Hi All,
I have dispatcher on two servers Server A and Server B. On Server A it is running fine but whenever I start it on server B, any report that goes through this dispatcher just seems hanged up there:
Below is the message from cogserver.log file
015-02-05 16:44:27.007 -6 shutdown na na 0 main DISP 5004 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StopService BUX Service Success
10.45.110.55:9400 23527748 2015-02-05 16:44:27.175 -6 rsProcessStarter na 0 warptaskmta-ProcessManager-ProcessMgrThread DISP 5004 1 Audit.Other.dispatcher.DISP.pogo pogo com.cognos.pogo.reportservice.ProcessManager Failure <messages><message><messageString>DPR-DPR-1035 Dispatcher detected an error.</messageString></message><message><messageString>Process BIBusTKServerMain failed to start properly.</messageString></message></messages> External Report Server process BIBusTKServerMain cannot be startedProcess BIBusTKServerMain failed to start properly.java.io.IOException: Process BIBusTKServerMain failed to start properly. at com.cognos.pogo.reportservice.ReportServerProcess.getProcessOutput(ReportServerProcess.java:182) at com.cognos.pogo.reportservice.ReportServerProcess.start(ReportServerProcess.java:125) at com.cognos.pogo.reportservice.ProcessFacade.createServerProcess(ProcessFacade.java:275) at com.cognos.pogo.reportservice.ProcessFacade.<init>(ProcessFacade.java:158) at com.cognos.pogo.reportservice.ProcessFacade.<init>(ProcessFacade.java:117) at com.cognos.pogo.reportservice.RSComponentFactory.newProcessFacade(RSComponentFactory.java:76) at com.cognos.pogo.reportservice.ProcessManager.createProcessFacade(ProcessManager.java:516) at com.cognos.pogo.reportservice.ProcessManager.startProcess(ProcessManager.java:492) at com.cognos.pogo.reportservice.ProcessManager.startProcessesDueToCapacity(ProcessManager.java:387) at com.cognos.pogo.reportservice.ProcessManager.safeRun(ProcessManager.java:345) at com.cognos.pogo.util.threads.SafeThread.run(SafeThread.java:61)
10.45.110.55:9400 23527748 2015-02-05 16:44:26.998 -6 stopper-idVizService ATHENA 5000 1 Audit.RTUsage.idViz.ATHENA.core.qls StopService QLSService Success
10.45.110.55:9400 23527748 2015-02-05 16:44:27.913 -6 rsProcessStarter na 0 warptaskmta-ProcessManager-ProcessMgrThread DISP 5004 1 Audit.Other.dispatcher.DISP.pogo pogo com.cognos.pogo.reportservice.ProcessManager Failure <messages><message><messageString>DPR-DPR-1035 Dispatcher detected an error.</messageString></message><message><messageString>Process BIBusTKServerMain failed to start properly.</messageString></message></messages> External Report Server process BIBusTKServerMain cannot be startedProcess BIBusTKServerMain failed to start properly.java.io.IOException: Process BIBusTKServerMain failed to start properly. at com.cognos.pogo.reportservice.ReportServerProcess.getProcessOutput(ReportServerProcess.java:182) at com.cognos.pogo.reportservice.ReportServerProcess.start(ReportServerProcess.java:125) at com.cognos.pogo.reportservice.ProcessFacade.createServerProcess(ProcessFacade.java:275) at com.cognos.pogo.reportservice.ProcessFacade.<init>(ProcessFacade.java:158) at com.cognos.pogo.reportservice.ProcessFacade.<init>(ProcessFacade.java:117) at com.cognos.pogo.reportservice.RSComponentFactory.newProcessFacade(RSComponentFactory.java:76) at com.cognos.pogo.reportservice.ProcessManager.createProcessFacade(ProcessManager.java:516) at com.cognos.pogo.reportservice.ProcessManager.startProcess(ProcessManager.java:492) at com.cognos.pogo.reportservice.ProcessManager.startProcessesDueToCapacity(ProcessManager.java:387) at com.cognos.pogo.reportservice.ProcessManager.safeRun(ProcessManager.java:345) at com.cognos.pogo.util.threads.SafeThread.run(SafeThread.java:61)
10.45.110.55:9400 23527748 2015-02-05 16:44:28.638 -6 rsProcessStarter na 0 warptaskmta-ProcessManager-ProcessMgrThread DISP 5004 1 Audit.Other.dispatcher.DISP.pogo
I checked the LIBPATH is correct and other environment variables are also set correctly.
Any suggestions.
got the issue fixed guys.
Just for an update. We had an upgrade to AIX recently and in that case, cognos 10.2.1 needs to have below variable set in environment which was not done and hence the dispatcher was not able to get sufficient memory.
MALLOCTYPE=watson