[cisco-voip] DB replication problem

[Joe Martini (joemar2)]

Ratko,

 

State 3 means that tables are out of sync between nodes or the server
cannot establish a connection with a certain server, so it doesn't know
if it has in sync tables or not.

 

Check the state on all your other servers, they shouldn't show state 2 -
good, if you're on 6.x or above.  If you can find a server with a state
in either 4 or 0, fixing that will correct the node in state 3.  If
everything looks good, the "utils dbreplication repair" will synchronize
the database tables.

 

Joe

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ratko Dodevski
Sent: Wednesday, December 02, 2009 4:30 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] DB replication problem

 

Hi, recently I had to restore my publisher from a backup, and I've
noticed that dbreplication is with value 3 - bad. I've tried issuing
commands like dbreplication stop, start, reset.. but no use... any
ideas???

-- 
Ratko

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091202/4f35c510/attachment.html>