Hi, Try v1.22.9 of the oak-segment-tar which is what adobe support gave us and said will be in the next service pack. It worked for us as well.

We appear to  have resolved this after a lot of testing.We are awaiting Adobe Support to confirm and validate the bug/ and fix ...  but for us our fix was to  install oak-segment-tar-1.24.0.jar  on the primary ,  then   give it a restart. Then once it was up we  ran our curl command to  see  if it w...

We havent been successful  in resolving this.   But we did a few things today to  try and isolate it. 1: Built 2 new servers2: Setup AEM v6.4 on one as the 'primary' then shut it down and copied it to the 'standby'3: Configured the 'standby' and verified it was  making the requests to the primary an...

Sounds liek your repeating the exact same tests  and environment checks that we are as well. If we have any success in isolating the exact root cause we will share. At this point  our theory is that the http:// request from the standby server using CURL is hitting the primary http://  interface  and...

Hi,   We are having the same issue  it  seems. I have  noticed that the "Standby"  never EVER makes the requests to the primary for some reason. On the Standby server,  i  did a  curl -v http://ipaddress:8088     and  got a  response back indicating the port was open.On the primary,  i saw in the lo...