Error while clearing dispatcher cache via dispatcher flush agent.

[Aj_9625932]

Hi,

We are trying to clear dispatcher cache via dispatcher flush agent, (/etc/acs-commons/dispatcher-flush/dispatcher-flush---acs.html), it is giving us the error below.

if we use "Delete Cache"  option:

"Your dispatcher flush requests have been issued with the following results:

An error occurred during replication. Possible issues include invalid flush paths or lack of active dispatcher flush agents.

Please review your Dispatcher Flush Agent logs to ensure all replication requests were successfully processed".

We tried using "invalidate cache" option, Success message is showing, but we are not sure whether cache is getting cleared. (I think cache is not being cleared).

It is may be timed out issue, how can we resolve this issue, can anyone please help us.

Thanks,
Ajay Boddu.

[EstebanBustamante]

What did you see in the flush agent (in author) log? Can you post that log along with the dispatcher's log?

[Aj_9625932]

/bin/receive?sling:authRequestLogin=1 since null
26.06.2023 15:19:02.734 *INFO* [HealthCheck Synchronized Clocks] org.apache.sling.discovery.oak.SynchronizedClocksHealthCheck execute: no topology connectors connected to local instance.
26.06.2023 15:19:02.766 *INFO* [qtp1592387125-9265] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials
26.06.2023 15:19:04.790 *INFO* [qtp1592387125-9265] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials
26.06.2023 15:19:11.078 *WARN* [qtp1592387125-9265] com.adobe.ams.environment.indicator.wcm.impl.AemEnvironmentIndicatorFilter not accepted for uri /etc/acs-commons/dispatcher-flush/dispatcher-flush---acs/_jcr_content/configuration.flush.html
26.06.2023 15:19:11.081 *INFO* [52.74.112.93 [1687792751078] POST /etc/acs-commons/dispatcher-flush/dispatcher-flush---acs/_jcr_content/configuration.flush.html HTTP/1.1] com.day.cq.replication.impl.ReplicatorImpl Setting up replication with options: ReplicationOptions{synchronous=true, revision='null', suppressStatusUpdate=true, suppressVersions=true, filter=com.adobe.acs.commons.replication.dispatcher.DispatcherFlushFilter@4a84637b, aggregateHandler=null}

[sudheersundalam1]

Hi Ajay,

I would also check the permission of the folder /var/www/html and the folders inside it if the cache location is set to "/var/www/html". For the AMS servers, it is "apache:apache" (owner/group) with read and write permission.

Sometimes while setting up the dispatcher, we might forget to change the folder permission from "root" user to "apache" user which prevents dispatcher from both creating and clearing the cache due to permission issue on the linux server.

Thanks,

Sudheer.

[Raja-kp]

@Aj_9625932 

As you indicated, invalidation works properly, which suggests there is nothing wrong with flush agent configuration.

To get to know more about issue details:
Tail your author error log or replication log while deleting the cache?
Check the Dispatcher flush agent log?

Regards,

Raja

[Aj_9625932]

Hi Raja,

Thanks.! 
this is what I could see in Author instance error logs.

"/bin/receive?sling:authRequestLogin=1 since null
26.06.2023 15:19:02.734 *INFO* [HealthCheck Synchronized Clocks] org.apache.sling.discovery.oak.SynchronizedClocksHealthCheck execute: no topology connectors connected to local instance.
26.06.2023 15:19:02.766 *INFO* [qtp1592387125-9265] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials
26.06.2023 15:19:04.790 *INFO* [qtp1592387125-9265] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials
26.06.2023 15:19:11.078 *WARN* [qtp1592387125-9265] com.adobe.ams.environment.indicator.wcm.impl.AemEnvironmentIndicatorFilter not accepted for uri /etc/acs-commons/dispatcher-flush/dispatcher-flush---acs/_jcr_content/configuration.flush.html
26.06.2023 15:19:11.081 *INFO* [52.74.112.93 [1687792751078] POST /etc/acs-commons/dispatcher-flush/dispatcher-flush---acs/_jcr_content/configuration.flush.html HTTP/1.1] com.day.cq.replication.impl.ReplicatorImpl Setting up replication with options: ReplicationOptions{synchronous=true, revision='null', suppressStatusUpdate=true, suppressVersions=true, filter=com.adobe.acs.commons.replication.dispatcher.DispatcherFlushFilter@4a84637b, aggregateHandler=null}"

Thanks,
Ajay

[Tanika02]

Hello @Aj_9625932 -

Based on the provided log entries, it seems that the authentication and access configurations are restricting anonymous access, and given requests require valid credentials.

[Raja-kp]

@Aj_9625932 Provided logs are not related the acs-common invalidation action. Tail your error log while trying to invalidate the cache !!

[fmateen]

Which version of ACS commons you have? 

Some of the previous version of ACS commons have bugs and cache flush takes too much time or fails. You probably have to update the acs commons.