which log4j.properties contains the right variables for RationalReporting
After a few days of operation, probably in order to extend the file system, the RRDI was stopped and when I try to start it now, I get an error:
[9/9/13 0:31:21:658 PDT] 00000000 ModelMgr I WSVR0801I: Initializing all server configuration models
[9/9/13 0:31:24:208 PDT] 00000000 WorkSpaceMana A WKSP0500I: Workspace configuration consistency check is disabled.
[9/9/13 0:31:24:428 PDT] 00000000 AdminTool A ADMU3200I: Server launched. Waiting for initialization status.
[9/9/13 0:31:26:791 PDT] 00000000 AdminTool A ADMU3011E: Server launched but failed initialization. Server logs, startServer.log, and other log files under /opt/IBM/WebSphere/AppServer/profiles/RationalReporting/logs/RationalReportingServer should contain failure information.
What I paste here is already the content of the startServer.log. I get a PID but the initialization fails. In order to have a better log I wanted to update the log4j.properties file, but there are too many and it is had to decide which one would be in charge of giving me the exact information.
Although the process is out there, I cannot connect to reporting.
[9/9/13 0:31:21:658 PDT] 00000000 ModelMgr I WSVR0801I: Initializing all server configuration models
[9/9/13 0:31:24:208 PDT] 00000000 WorkSpaceMana A WKSP0500I: Workspace configuration consistency check is disabled.
[9/9/13 0:31:24:428 PDT] 00000000 AdminTool A ADMU3200I: Server launched. Waiting for initialization status.
[9/9/13 0:31:26:791 PDT] 00000000 AdminTool A ADMU3011E: Server launched but failed initialization. Server logs, startServer.log, and other log files under /opt/IBM/WebSphere/AppServer/profiles/RationalReporting/logs/RationalReportingServer should contain failure information.
What I paste here is already the content of the startServer.log. I get a PID but the initialization fails. In order to have a better log I wanted to update the log4j.properties file, but there are too many and it is had to decide which one would be in charge of giving me the exact information.
Although the process is out there, I cannot connect to reporting.
Accepted answer
You can go the WAS Admin Console page to change the log level of the WAS server. The page is always on the
Troubleshooting > Logging and tracing > server1.
Troubleshooting > Logging and tracing > server1.