Issue
- The Liferay log and application server log are not capturing the stack trace. And the size of these files is 0 in size with 3 to 4 lines of the log being traced.
Environment
- Liferay DXP 7.2
Resolution
Please Note: The following procedures and unofficial links involve customization, environmental changes, Please exercise appropriate discretion in the use of this information. For further assistance on the same from Liferay, please reach out to our dedicated GS team. Your sales representative is a great resource to discover the connectivity with the GS team to know more about it in detail.
- The chances of the reported case may occur with different factors like any of your custom modules may have problematic code with respect to logging configuration, or not be able to write due to the less capacity left.
- Hene cross-verify the behavior by inspecting all the custom modules to the contained log4j configuration as this way helps you to narrow down into the specific module or code to move forward with the resolution path.
- With respect to the memory and disk space, upon deployment, quite a lot may be written to the osgi /state directory. There might be having little chance getting failing to write to osgi/state due to the file system's reserve capacity not being sufficient or might be less. Hence, It might be an incomplete file or maybe result in parsing issues.
- Therefore, double-check the behavior by providing enough memory and disk space and deleting the temp directories helps to move forward. For more information, unofficial article on the same https://unix.stackexchange.com/questions/7950/reserved-space-for-root-on-a-filesystem-why