Support Article
Logs can't be viewed from Pega
SA-4467
Summary
Pega is not writing anything to logs and the logs are not available to view.
Error Messages
R log4j:ERROR setFile(null,true) call failed.
[11/4/14 16:03:56:081 EST] 00000015 SystemErr R java.io.FileNotFoundException: /PegaRULES-ALERT.log (The file access permissions do not allow the specified action.)
[11/4/14 16:03:56:082 EST] 00000015 SystemErr R at java.io.FileOutputStream.<init>(FileOutputStream.java:203)
[11/4/14 16:03:56:082 EST] 00000015 SystemErr R at java.io.FileOutputStream.<init>(FileOutputStream.java:127)
[11/4/14 16:03:56:082 EST] 00000015 SystemErr R at com.pega.apache.log4j.FileAppender.setFile(FileAppender.java:298)
[11/4/14 16:03:56:082 EST] 00000015 SystemErr R at com.pega.apache.log4j.RollingFileAppender.setFile(RollingFileAppender.java:168)
[11/4/14 16:03:56:082 EST] 00000015 SystemErr R at com.pega.apache.log4j.FileAppender.activateOptions(FileAppender.java:172)
[11/4/14 16:03:56:082 EST] 00000015 SystemErr R at com.pega.apache.log4j.config.PropertySetter.activate(PropertySetter.java:257)
[11/4/14 16:03:56:082 EST] 00000015 SystemErr R at com.pega.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:262)
[11/4/14 16:03:56:083 EST] 00000015 SystemErr R at com.pega.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:166)
[11/4/14 16:03:56:083 EST] 00000015 SystemErr R at com.pega.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:179)
[11/4/14 16:03:56:083 EST] 00000015 SystemErr R at com.pega.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:253)
[11/4/14 16:03:56:083 EST] 00000015 SystemErr R at com.pega.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:166)
[11/4/14 16:03:56:083 EST] 00000015 SystemErr R at com.pega.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:179)
[11/4/14 16:03:56:083 EST] 00000015 SystemErr R at com.pega.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:253)
[11/4/14 16:03:56:083 EST] 00000015 SystemErr R at com.pega.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:166)
[11/4/14 16:03:56:084 EST] 00000015 SystemErr R at com.pega.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:179)
[11/4/14 16:03:56:084 EST] 00000015 SystemErr R at com.pega.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:467)
[11/4/14 16:03:56:084 EST] 00000015 SystemErr R at com.pega.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:436)
[11/4/14 16:03:56:084 EST] 00000015 SystemErr R at com.pega.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:922)
[11/4/14 16:03:56:084 EST] 00000015 SystemErr R at com.pega.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:796)
[11/4/14 16:03:56:084 EST] 00000015 SystemErr R at com.pega.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:723)
[11/4/14 16:03:56:084 EST] 00000015 SystemErr R at com.pega.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:507)
[11/4/14 16:03:56:085 EST] 00000015 SystemErr R at com.pega.apache.log4j.LogManager.initializeConfig(LogManager.java:163)
[11/4/14 16:03:56:085 EST] 00000015 SystemErr R at com.pega.pegarules.priv.LogHelper._initLogging_privact(LogHelper.java:662)
[11/4/14 16:03:56:085 EST] 00000015 SystemErr R at com.pega.pegarules.priv.LogHelper.init(LogHelper.java:646)
[11/4/14 16:03:56:085 EST] 00000015 SystemErr R at com.pega.pegarules.priv.LogHelper.<init>(LogHelper.java:259)
[11/4/14 16:03:56:085 EST] 00000015 SystemErr R at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:192)
[11/4/14 16:03:56:085 EST] 00000015 SystemErr R at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:167)
[11/4/14 16:03:56:085 EST] 00000015 SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[11/4/14 16:03:56:086 EST] 00000015 SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
[11/4/14 16:03:56:086 EST] 00000015 SystemErr R at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
[11/4/14 16:03:56:086 EST] 00000015 SystemErr R at java.lang.reflect.Method.invoke(Method.java:611)
[11/4/14 16:03:56:086 EST] 00000015 SystemErr R at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
[11/4/14 16:03:56:086 EST] 00000015 SystemErr R at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
[11/4/14 16:03:56:086 EST] 00000015 SystemErr R at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
[11/4/14 16:03:56:086 EST] 00000015 SystemErr R at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)
[11/4/14 16:03:56:086 EST] 00000015 SystemErr R at com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:1680)
[11/4/14 16:03:56:087 EST] 00000015 SystemErr R at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:410)
[11/4/14 16:03:56:087 EST] 00000015 SystemErr R at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:88)
[11/4/14 16:03:56:087 EST] 00000015 SystemErr R at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:169)
[11/4/14 16:03:56:087 EST] 00000015 SystemErr R at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:749)
[11/4/14 16:03:56:087 EST] 00000015 SystemErr R at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:634)
[11/4/14 16:03:56:087 EST] 00000015 SystemErr R at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:422)
[11/4/14 16:03:56:088 EST] 00000015 SystemErr R at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:714)
[11/4/14 16:03:56:088 EST] 00000015 SystemErr R at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1160)
[11/4/14 16:03:56:088 EST] 00000015 SystemErr R at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1369)
[11/4/14 16:03:56:088 EST] 00000015 SystemErr R at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:639)
[11/4/14 16:03:56:088 EST] 00000015 SystemErr R at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:967)
[11/4/14 16:03:56:088 EST] 00000015 SystemErr R at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:766)
[11/4/14 16:03:56:088 EST] 00000015 SystemErr R at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2153)
[11/4/14 16:03:56:088 EST] 00000015 SystemErr R at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:445)
[11/4/14 16:03:56:089 EST] 00000015 SystemErr R at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)
[11/4/14 16:03:56:089 EST] 00000015 SystemErr R at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:388)
[11/4/14 16:03:56:089 EST] 00000015 SystemErr R at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$500(CompositionUnitMgrImpl.java:116)
[11/4/14 16:03:56:089 EST] 00000015 SystemErr R at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:994)
[11/4/14 16:03:56:089 EST] 00000015 SystemErr R at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:349)
[11/4/14 16:03:56:089 EST] 00000015 SystemErr R at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1690)
Steps to Reproduce
unknown
Root Cause
The root cause of this problem is defect/misconfiguration in the PRPC operating environment. The custom property pega.logdir was defined in prlogging.xml, but the property didn't exist under Process Definition > Java Virtual Machine > Custom Properties.
Resolution
This issue is resolved through the following local change: The pega.logdir was re-added as a custom property and system restarted. Log files are now generating properly.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.