Oracle Analytics Publisher: 12C AdminServer.out is generating but logs are not writing logs to this file

AdminServer.out is of size 0 and nothing is writing to this file rather AdminServer.out00001, 000002 etc files getting created and those are getting written with server logs.

Root cause:

What was found in your setUserOverridesImpl.sh file is that you are starting the JVM with the parameter : weblogic.RotatingFileRedirector

that is causing the AdminServer.out to be empty.

This is the extract of the setUserOverridesImpl.sh file below:

# bug 30011801

#Add rotation of out files for weblogic servers

${JAVA_HOME}/bin/java -cp ${MW_HOME}/wlserver/server/lib/weblogic.jar weblogic.RotatingFileRedirector -configOverride baseLogFileName=${DOMAIN_HOME}/servers/${SERVER_NAME}/logs/${SERVER_NAME}.out -config ${MW_HOME}/bi/modules/oracle.bi.sysman/env/stdout_config.properties &

this bug 30011801 is an Oracle Business Intelligence Enterprise Edition / Analytics System Management bug, not a WebLogic Server defect.

This bug 30011801 is an Oracle Business Intelligence Enterprise Edition / Analytics System Management bug.

Solution:

Added the below mentioned parameters in stdout_config.properties

numberOfFilesLimited=false
rotationSize=5000
rotatedFileCount=10
baseLogFileName=AdminServer.out

Shutdown Adminserver

Clear all AdminServer.out files

and start the AdminServer

Error in BI Server logs-Failed to create system session due to exception: java.net.ConnectException: Connection refused

 Following is the error in BI logs:

 [2023-04-03T22:31:52.633-04:00] [bi_server1] [ERROR] [] [oracle.biee.search] [tid: BISearchSujectAreaPushCrawler-thread-1] [userId: <anonymous>] [ecid: eed40b4f-e0e5-4d62-8ab6-0cdcabc489fe-0000000d,0:776:7:39] [APP: bisearch] [partition-name: DOMAIN] [tenant-name: GLOBAL] Failed to create system session due to exception: java.net.ConnectException: Connection refused (Connection refused)[[
 javax.xml.ws.ProtocolException: java.net.ConnectException: Connection refused (Connection refused)
        at com.siebel.analytics.web.jaxwsutils.HttpTcpBridge.sendHttpRequest(HttpTcpBridge.java:105)
        at com.siebel.analytics.web.jaxwsutils.DirectSoapCaller.invokeSoapMethod(DirectSoapCaller.java:221)
        at com.siebel.analytics.web.jaxwsutils.SAWSOAPTcpConnector.invokeSoapMethod(SAWSOAPTcpConnector.java:79)
        at com.siebel.analytics.web.jaxwsutils.SOAPInterfaceProxy.invoke(SOAPInterfaceProxy.java:206)
        at com.sun.proxy.$Proxy718.logonex(Unknown Source)
        at oracle.biee.search.security.BISearchSessionManager$BIPSSoapSession.createSessionID(BISearchSessionManager.java:576)
        at oracle.biee.search.security.BISearchSessionManager$BIPSSoapSession.createSession(BISearchSessionManager.java:440)
        at oracle.biee.search.security.BISearchSessionManager$BIPSSoapSession.<init>(BISearchSessionManager.java:423)
        at oracle.biee.search.security.BISearchSessionManager$BIPSSoapSession.<init>(BISearchSessionManager.java:403)
        at oracle.biee.search.security.BISearchSessionManager.lambda$getSession$0(BISearchSessionManager.java:290)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at oracle.biee.search.security.BISearchSessionManager.getSession(BISearchSessionManager.java:301)
        at oracle.biee.search.security.BISearchSessionManager.getSystemSession(BISearchSessionManager.java:360)
        at oracle.biee.search.security.BISearchSessionManager.getSystemSession(BISearchSessionManager.java:366)
        at oracle.biee.search.services.crawl.scheduler.BISearchSubjectAreaUpdater$SubjectAreaUpdater.call(BISearchSubjectAreaUpdater.java:117)
        at oracle.biee.search.services.crawl.scheduler.BISearchSubjectAreaUpdater$SubjectAreaUpdater.call(BISearchSubjectAreaUpdater.java:72)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:750)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:476)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:218)


Solution:
Start System Components of OBIEE as following:

1. Login to EM as admin user

2. Click on Navigation Icon

3. Expand Business Intelligence

4. Click on biinstance

5. Click on Availability Tab

6.Click Start All to start the Components