AEM Replication Queue Blocked on One Publisher | Community
Skip to main content
Singaiah_Chintalapudi
Singaiah_Chintalapudi
Level 7
Jul 6, 2018 2:21 PM UTC

AEM Replication Queue Blocked on One Publisher

Hi,

The replication queue is blocked on one of the publishers and I see the below message in the logs:

error: com.day.cq.replication.ReplicationException: Repository error during node import: java.io.IOException: Read-only file system

Message sent.

But the test connection is successful. This publisher is up and running and all the bundles are active.

Can you please let me know how to fix this issue.

We are using admin credentials in the replication agent.

Thanks.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

joerghoh
joerghoh
Employee
Jul 7, 2018 5:24 PM UTC

This error message should be quite descriptive: java.io.IOException: Read-only file system

Regarding the "Test connection": Test connection does just what it says: It tests the connection. It doesn't do actual imports or writes to the repository, so it's very obvious that you don't get any errors in that case.

Jörg

Translate
Singaiah_Chintalapudi
Singaiah_ChintalapudiAuthor
Level 7
Jul 6, 2018 4:09 PM UTC

Thanks. I've tried these options.

- Permissions looks fine

- Restarted the bundle

- Deleted one of the item from the queue

- Setup a debug log already

I still see the same errors in the debug log. It is throwing the 400.

Our disk went to read only mode for some reason. We just changed it and everything is working.

Translate
    user05162
    Employee
    Jul 6, 2018 3:38 PM UTC

    - Try to clear one or two items from the queue.

    - Check permissions for "replication-service" and "replication-receiver" on both author and publisher and compare it with a working setup.

    - Try to restart "com.day.cq.cq-replication" bundle

    - Setup a DEBUG logger on com.day.cq.replication and it will provide more details on what process is triggering that error.

    Translate
      Terms & ConditionsAccessibility statement

      Loading footer...