AEMaaCS: my publisher does not run after a computer restart | Community
Skip to main content
jayv25585659
jayv25585659
Level 8
September 30, 2025
Question

AEMaaCS: my publisher does not run after a computer restart

  • September 30, 2025
  • 2 replies
  • 404 views

so I have initially run the publisher using this command (I'm on Linux using JDK11)

java -jar aem-publish-p4503.jar

I installed the content and code packages and I can browser the custom pages without any issues.

 

My problem started after I restarted my PC.  To start AEM publish I tried

  • java -jar aem-publish-p4503.jar
  • crx-quickstart/bin/start (I had to change the port number as the default is 4502)

I tried to browser localhost:4503, but all I get is a 404. I then checked error.log and I don't see any new entries.

 

I encountered something similar when I setup author the first time and the fix was to delete

./crx-quickstart/launchpad/config/org/apache/sling/jcr/repoinit/RepositoryInitializer*.config

I tried the same trick in my publisher but it does not work.

 

If I start from the beginning again (rm -fr crx-quickstart), AEM will start working again.

 

Any ideas on how to fix or perhaps a workaround?

2 replies

giuseppebaglio
giuseppebaglio
Level 10
September 30, 2025

hi @jayv25585659, 

Could you please check the contents of both the stdout.log and stderr.log files? 

Additionally, could you verify if any other services are using port 4503?:

netstat -tul | grep 4503

 

Sometimes, there may be issues with the repository. In such cases, running an Offline Revision Cleanup might help. I can't guarantee that it will solve the problem, but in my experience, it has been helpful most of the time.

    jayv25585659
    jayv25585659Author
    Level 8
    October 1, 2025

    Apologies. I should have mentioned that I'm on AEMaaCS. Reading the linked Adobe page, revision cleanup only applies to 6.5?

     

    In any case...

    - no other port uses 4503

    - When I tried to tail error.log, stderr.log and stdout.log, I do not see errors.

    Syed_Shaik
    Syed_Shaik
    Level 3
    October 1, 2025

    Hi @jayv25585659,

     

    • Stop AEM

    • Remove any repo.lock file under segmentstore

    • Ensure port 4503 is free

    • Start again with:

       
      ./crx-quickstart/bin/start
      ================================================================================
      When working with the AEM as a Cloud Service SDK (Quickstart), there are a couple of important differences compared to on-prem AEM:

      1. Startup method

        • The first time you run:

           
          java -jar aem-publish-p4503.jar

          it unpacks the crx-quickstart directory.

        • After that, always use the startup script:

           
          ./crx-quickstart/bin/start
           

          Running the JAR directly again after initialization can break the repository startup.

      2. Check the right logs
        Besides the error.log Please also look at:

         
        crx-quickstart/logs/stdout.log crx-quickstart/logs/stderr.log crx-quickstart/logs/startup.log

        These usually show the real cause if AEM is not starting.

      3. Port conflicts
        Make sure nothing else is bound to port 4503. You can check with:

         
        netstat -tulnp | grep 4503

      4. Repository locks/corruption
        If AEM was not shut down cleanly, a stale lock file may prevent startup. Stop AEM and remove:

         
        crx-quickstart/repository/segmentstore/repo.lock

        If the repository is corrupted, try running an Offline Revision Cleanup as described in Adobe’s documentation.

      5. Persistence expectation in SDK
        The SDK is ephemeral by design—it’s not guaranteed to keep content/code across system restarts. If you need persistence, the best workaround is

        • Stop AEM cleanly with ./crx-quickstart/bin/stop

        • Zip or back up the crx-quickstart folder

        • Restore it after reboot instead of deleting it every time.

     

      Terms & ConditionsAccessibility statement

      Loading footer...