[cisco-voip] CM 6.1 replication issue

[Justin Steinberg]

are you running that report from the publisher?    that error isn't
indicating DB replication failure. it is indicating that CM1 can't be
reached.  Which would be very odd should you be running this report from
CM1.

There are a few bugs related to the Unified Reporting system when you have
mixed case letters in the hostname.  sometimes it can create false positives
for failure alerts.

what does 'utils dbreplication status' show on the pub?

after you run the command, you will need to do a 'file view activelog
/<insert-log-file-name-here>'  to see the entire contents of the dbstatus
report.

Justin

On Wed, Aug 20, 2008 at 4:29 PM, Voll, Scott <Scott.Voll at wesd.org> wrote:

>  How do I fix a replication issue in 6.1?  do I have to stop the
> dbreplicaiton on node / pub then do a reset node?
>
>
>
> CM 2 was offline for an extended period yesterday but is up now.  What
> needs to be done?
>
>
>
> Thanks
>
>
>
> Scott
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080820/584a2c55/attachment.html>