https://tools.cisco.com/bugsearch/bug/CSCuv75866
On Tue, 6 Oct 2015 2:14 am Brian Meade wrote:
> Maybe this? https://tools.cisco.com/bugsearch/bug/CSCun33173
>
> Try manually stopping the Cisco Intercluster Sync Agent Service and
> deleting the certificate.
>
> On Sun, Oct 4, 2015 at 10:45 PM, J
Maybe this? https://tools.cisco.com/bugsearch/bug/CSCun33173
Try manually stopping the Cisco Intercluster Sync Agent Service and
deleting the certificate.
On Sun, Oct 4, 2015 at 10:45 PM, James Andrewartha <
jandrewar...@ccgs.wa.edu.au> wrote:
> On 02/10/15 02:57, Brian Meade wrote:
> > You can
On 02/10/15 02:57, Brian Meade wrote:
> You can try to download the tomcat.pem from the publisher and manually
> install it on the presence server as a tomcat-trust. Since the Common
> Name is the same, it should replace the existing tomcat-trust.
It did replace the existing tomcat-trust, however
You can try to download the tomcat.pem from the publisher and manually
install it on the presence server as a tomcat-trust. Since the Common Name
is the same, it should replace the existing tomcat-trust.
On Wed, Sep 30, 2015 at 10:19 PM, James Andrewartha <
jandrewar...@ccgs.wa.edu.au> wrote:
>
On 30/09/15 22:29, Brian Meade wrote:
> So if you stop the certificate change notification service on the
> publisher and that presence server then delete the tomcat-trust on the
> presence server, you see it propagate that old tomcat-trust again to the
> presence server after the services are star
So if you stop the certificate change notification service on the publisher
and that presence server then delete the tomcat-trust on the presence
server, you see it propagate that old tomcat-trust again to the presence
server after the services are started again?
On Wed, Sep 30, 2015 at 12:26 AM,
On 15/09/15 22:34, Brian Meade wrote:
> Stop the certificate change notification service on all nodes and then
> delete all the old tomcat-trust certs. You can then restart the service
> and they shouldn't come back.
This worked for most of them, but there's still one that is propagating
from the
Stop the certificate change notification service on all nodes and then
delete all the old tomcat-trust certs. You can then restart the service
and they shouldn't come back.
On Tue, Sep 15, 2015 at 1:22 AM, James Andrewartha <
jandrewar...@ccgs.wa.edu.au> wrote:
> Hi list,
>
> Our cluster is near
list
Subject: [cisco-voip] Phantom tomcat-trust cert
>Hi list,
>
>Our cluster is nearly 5 years old, so I've done the certificate dance,
>including using Digicert for the tomcat multi-server cert. However, some
>old certs that are about to expire keep appearing as tomcat-trust
Hi list,
Our cluster is nearly 5 years old, so I've done the certificate dance,
including using Digicert for the tomcat multi-server cert. However, some
old certs that are about to expire keep appearing as tomcat-trust certs.
I've deleted them several times, but they keep coming back overnight.
Ev
10 matches
Mail list logo