Unable to generate Log Artifact Zip file on WebSphere and WebLogic implementations of RSA Identity Governance & Lifecycle
Originally Published: 2021-04-30
Article Number
Applies To
RSA Version/Condition: 7.1.1, 7.2.0, 7.2.1, 7.5.0
Platform/Application Server: WebSphere, WebLogic
Issue
Log Artifact Zip file (Admin > Diagnostics > Log Artifact > Generate Zip File) fails to generate on WebSphere and WebLogic deployments of RSA Identity Governance & Lifecycle.
One of the following errors may be logged in the aveksaserver.log file:
12/03/2019 12:56:35.259 ERROR (LogArtifactJob) [com.aveksa.gui.pages.admin.downloadLogs.LogArtifactJob] Insufficient Disc space on server. Cannot run the Job.Or
03/13/2020 08:52:28.102 ERROR (LogArtifactJob) [SystemErr] Exception in thread "LogArtifactJob"
Cause
- RSA Identity Governance & Lifecycle 7.1.1
- RSA Identity Governance & Lifecycle 7.2.0
- RSA Identity Governance & Lifecycle 7.2.1
- RSA Identity Governance & Lifecycle 7.5.0
Resolution
- RSA Identity Governance & Lifecycle 7.2.0 P09
- RSA Identity Governance & Lifecycle 7.2.1 P04
- RSA Identity Governance & Lifecycle 7.5.0 P01
WebSphere application server configuration:
From the WebSphere console:
1. Go to Application Servers and click on your Server name.
2. Select Process Definition under Server Infrastructure.
3. On the right, under Additional Properties click Java Virtual Machine.
4. On the right, click on Custom Properties and click New.
5. As Name, enter log.dir and as Value, add the location of the log folder.
6. Press Apply and OK and verify the setting on the summary page.
1. Go to Application Servers and click on your Server name.
2. Select Process Definition under Server Infrastructure.
3. On the right, under Additional Properties click Java Virtual Machine.
4. On the right, click on Custom Properties and click New.
5. As Name, enter log.dir and as Value, add the location of the log folder.
6. Press Apply and OK and verify the setting on the summary page.
WebLogic application server configuration:
From the WebLogic Administration Console:
1. Click Environment > Servers > Select server.
2. Click Configuration tab > Server Start tab.
3. Add the startup setting -log.dir=<directory path for logging> to the Arguments field
1. Click Environment > Servers > Select server.
2. Click Configuration tab > Server Start tab.
3. Add the startup setting -log.dir=<directory path for logging> to the Arguments field
Notes
000037307 - WorkPoint.log and heap dumps are written to the Linux root directory ( / ) on WebSphere and WebLogic implementations of RSA Identity Governance & Lifecycle
Related Articles
'Exception checking for internal table usage in collectors' and 'java.lang.NullPointerException' errors when generating a … Number of Views RSA Web Threat Detection 6.0 security scan found hard coded credentials in python.zip file Number of Views Log Artifact zip file fails to generate in RSA Governance & Lifecycle Number of Views RSA SureFile has problems opening a SureFile-zipped *.ZIP file Number of Views gpg: no valid OpenPGP data found. gpg: decrypt_message failed eof Number of Views
Trending Articles
RSA Authentication Manager Patch Updates RSA SecurID Software Token 4.1.2 and 4.2.1 for Mac OS X displays: No token storage device was detected. Verify that the de… How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows Configuring a Checkpoint firewall to work with SecurID
Don't see what you're looking for?
