topic ACS SE Database replication fails in Network Access Control

ACS SE Database replication fails

paulhowlett_2 — Sun, 10 Mar 2019 22:23:21 GMT

Hello, I recently upgraded our ACS SEs from 4.0 to 4.1. All appeared to go OK but I checked the logs recently and saw the the database replication is failing with the message:

ACS '[hostname]'is running a different version of ACS - aborting.

All ACS SE were upgraded at the same time and display the same versions when examining the Appliance Upgrade page. Does anyone have any ideas what the problem is?

Thanks in advance.

Re: ACS SE Database replication fails

Premdeep Banga — Fri, 14 Sep 2007 23:21:05 GMT

Hi,

Make sure that both

"Cisco Secure ACS" & "Appliance Management Software" show the same status from, System Configuration > Appliance Upgrade Status.

i.e., both need to be on same version, and all the appliances need to be on the same version too.

Other then that, with whichever ACS SE, your replication is failing, console into ACS SE and issue "show" command, see if you can point something odd, like,

Upgrade in progress message.

Regards,

Prem

Re: ACS SE Database replication fails

magurwara — Tue, 25 Sep 2007 08:45:02 GMT

Hi, I am having a related problem but in my case I am using ACS for Windows ver.4.0. I am replicating from one primary ACS to three other ACS using scheduled nightly replication.

The problem is that the data is being updated on all three ACS servers, but in the database replication logs on the primary I get messages stating that "ACS-server-name replication failed possibly due to short time-out or dead". Moreover, not all three servers timeout. Sometimes one server timeout, and other times two servers timeout, etc.

On the replicated servers logs, the only log, in case server times out, shows that "replication cycle starting....". while when replication is successfull, it also shows Replication cycle completed successfully.

I have played around with the timeouts but the result is random. I have also checked if there are any bandwidth issues, but replication is scheduled at night with minimal network traffic and the servers are also not being used for authentications.

Don't understand why I don't see successful messages all the time, specially when the data does get updated on the replica ACS.

Thanks.

MAG