Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

AEM Replication Queue Blocked on One Publisher

Avatar

Avatar
Validate 25
MVP
Singaiah_Chintalapudi
MVP

Likes

130 likes

Total Posts

233 posts

Correct Reply

37 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Ignite 5
Ignite 3
View profile

Avatar
Validate 25
MVP
Singaiah_Chintalapudi
MVP

Likes

130 likes

Total Posts

233 posts

Correct Reply

37 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Ignite 5
Ignite 3
View profile
Singaiah_Chintalapudi
MVP

06-07-2018

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.

Replies

Avatar

Avatar
Coach
Employee
jbrar
Employee

Likes

377 likes

Total Posts

867 posts

Correct Reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile

Avatar
Coach
Employee
jbrar
Employee

Likes

377 likes

Total Posts

867 posts

Correct Reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile
jbrar
Employee

06-07-2018

- 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.

Avatar

Avatar
Validate 25
MVP
Singaiah_Chintalapudi
MVP

Likes

130 likes

Total Posts

233 posts

Correct Reply

37 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Ignite 5
Ignite 3
View profile

Avatar
Validate 25
MVP
Singaiah_Chintalapudi
MVP

Likes

130 likes

Total Posts

233 posts

Correct Reply

37 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Ignite 5
Ignite 3
View profile
Singaiah_Chintalapudi
MVP

06-07-2018

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.

Avatar

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,078 likes

Total Posts

3,112 posts

Correct Reply

1,060 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,078 likes

Total Posts

3,112 posts

Correct Reply

1,060 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
Jörg_Hoh
Employee

07-07-2018

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