Hi,
I'm updating Lumira Server for SAP BI Platform (LS4BIP) from version 1.31.1 to 1.31.2, on RedHat Linux 6.7 with SAP BusinessObjects 4.2 SP2.
But it has not been possible since it is in the message: "Starting Server Intelligence Agent .... 88%."
In reviewing the logs, the only thing unusual is identified:
598105.495: [GC (Allocation Failure) [PSYoungGen: 172034K->709K(173056K)] 431466K->260228K(522752K), 0.0185179 secs] [Times: user=0.13 sys=0.00, real=0.02 secs] 598107.707: [GC (Allocation Failure) [PSYoungGen: 172229K->773K(173056K)] 431748K->260380K(522752K), 0.0164691 secs] [Times: user=0.13 sys=0.00, real=0.02 secs] 598115.535: [GC (Allocation Failure) [PSYoungGen: 172293K->1154K(173056K)] 431900K->260962K(522752K), 0.0192403 secs] [Times: user=0.13 sys=0.00, real=0.02 secs] 598120.960: [GC (Allocation Failure) [PSYoungGen: 172674K->1186K(173056K)] 432482K->261182K(522752K), 0.0205602 secs] [Times: user=0.14 sys=0.00, real=0.02 secs] 598123.606: [GC (Allocation Failure) [PSYoungGen: 172706K->642K(173056K)] 432702K->261067K(522752K), 0.0183952 secs] [Times: user=0.13 sys=0.00, real=0.02 secs]
Anyone have any idea how to fix it, thank you very much
1. you're looking at the wrong log - the parts you posted are from garbage collection log for some java process and are irrelevant to your issue.
2. have you stopped all BOBJ processes, except CMS/FRS before running upgrade ?
3. The log you need will be in the temp directory for the user that runs this upgrade, it'll be called setupengine.log
if the setup hasn't yet finished or crashed and it'll be in the InstallData/logs directory if the setup has finished.
Search for KBA's/SAP Notes with "sia fails to start during install" - there will be many with possilble solutions
Hi Denis, attached image of the last lines of the file "setup engine.log".
In KBA's/SAP Notes I have not found anything that apply to the environment I'm working.
as I said - the SIA is not starting and setup is waiting for it...
Why it is not starting - that's the part that needs to be investigated... maybe there is more before this page (last lines is not first time its trying to start it) or there is a ccm log or sia or cms log in /logging dir with more details.
Hi Denis, effectively in the middle of the log file, the following appears:
so, the CMS is terminating. Look for CMS logs in /logging dir for details.
If you want it resolved faster and do a proper investigation - open a support Incident with SAP.
Hi, already solved by applying the technical note https://launchpad.support.sap.com/#/notes/2314588
