Localhost for AEM 6 stopped populating crx-quickstart\logs\error.log | Community
Skip to main content
C
Clive_Stewart
Level 6
October 16, 2015
Solved

Localhost for AEM 6 stopped populating crx-quickstart\logs\error.log

  • October 16, 2015
  • 2 replies
  • 741 views

Localhost for AEM 6 stopped populating crx-quickstart\logs\error.log.

After I installed the service pack update I no longer get error.log populated if I have an error in my code I need to debug.

 

Regards

 

Clive

Best answer by Mshaji

Hi Clive,

I tested by installing fresh copy of AEM6(without sp1) and introducing an error in jsp script. I see error for my file in error.log

Then I installed SP1 and created same error in jsp file, I am able to see the error in error.log.

I suggest you to restart your AEM6 after applying SP1 update. Then test again.

If that doesn't work, create a fressh install of AEM on separate port like 6502. Then apply SP update, restart your server and test it again.

Hopefully you should see errors in the log

2 replies

M
Community Advisor
MshajiCommunity AdvisorAccepted solution
Community Advisor
October 16, 2015

Hi Clive,

I tested by installing fresh copy of AEM6(without sp1) and introducing an error in jsp script. I see error for my file in error.log

Then I installed SP1 and created same error in jsp file, I am able to see the error in error.log.

I suggest you to restart your AEM6 after applying SP1 update. Then test again.

If that doesn't work, create a fressh install of AEM on separate port like 6502. Then apply SP update, restart your server and test it again.

Hopefully you should see errors in the log

    AmitVishwakarma
    Community Advisor
    AmitVishwakarmaCommunity Advisor
    Community Advisor
    January 18, 2025

    To resolve the issue where the error.log in AEM 6 is not being populated after installing a service pack, you can try the following steps:

    1. Check Log Level Configuration:

    AEM might have updated the log level after the service pack update. To check and adjust the log level:

    • Go to the Apache Sling Logging configuration at /system/console/configuration/org.apache.sling.commons.log.LogManager.
    • Ensure that the logging level is set to ERROR or lower for the relevant loggers (like org.apache.sling or org.apache.sling.api).

    2. Check Log Appenders Configuration:

    Make sure the log appender for the error log is correctly configured. To verify or modify the logging configuration:

    • Go to /system/console/configuration/org.apache.sling.commons.log.LogManager.
    • Check if the appender (such as error.log file appender) is still configured correctly after the service pack installation.

    3. Check for Permissions:

    Ensure that the crx-quickstart/logs directory has the appropriate file permissions. If permissions were changed during the update, AEM may not be able to write to error.log.

    • Set proper file permissions so that AEM can write logs.

    4. Check AEM Logs Configuration Files:

    After updating the service pack, some configurations might have been altered. Check the logback.xml or other log configuration files in the AEM installation directory (crx-quickstart/conf) to ensure that error.log is still correctly configured to capture errors.

    5. Restart AEM:

    After making the necessary adjustments, restart AEM to ensure the changes take effect.

    6. Test Error Logging:

    Trigger an error in your code and check if it's being logged in error.log. If not, review the logs from the AEM web console under Logs in /system/console.

    If these steps do not resolve the issue, it may be beneficial to check the AEM service pack release notes for any changes to logging configurations or known issues related to logging after the update.

    Terms & ConditionsAccessibility statement

    Loading footer...