Re: DNAC CatalystCenter activities logs frozen

LAN team · ‎06-10-2024

Hello,

SInce the 3 nodes of the cluster have been restarted, there's no more logs audit logs.

Installed version:2.3.5.5

Is it possible to restart the dedicated service without opening on more Cisco TAC Case ?

Thank you,

balaji.bandi · ‎06-10-2024

read the release notes of 2.3.5.5 check any caveats

in the cluster you can reboot each node by your self, that not required TAC assitance here.

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

maflesch · ‎06-10-2024

Hi,

I'm more curious as to why the cluster was restarted? Can you also provide the following:

- Screen shot of the issue being seen
- Attempt to access the activities page via the physical IPs of each node, not just the VIP
- The output from the CLI for the following:
-- magctl appstack status -f
-- magctl appstack status dnacaap

LAN team · ‎06-11-2024

Hi,

We have decided to restart each node, one by one, as the inventory page became very long, fro example, after adding a new device, it can takes more than 15 minutes to appear in inventory list.

No screenshot issue, it's just there no more new activity logs since the 5th of June.

$ magctl appstack status -f
NAMESPACE                  NAME                                                     READY   STATUS    RESTARTS   AGE    IP               NODE           NOMINATED NODE   READINESS GATES

[Tuesday Jun 11 14:05:12 UTC] maglev@xxx.xxx.6.64 (maglev-master-xxx-xxx-6-64)
$ magctl appstack status dnacaap
NAME                                        READY   STATUS    RESTARTS   AGE    IP               NODE           NOMINATED NODE   READINESS GATES
daas-runtime-5bd7f45655-tjpjq               1/1     Running   1          6d2h   xxx.xxx.46.150   xxx.xxx.6.65   <none>           <none>
dna-event-runtime-5744cbdb9d-8bh2f          1/1     Running   2          6d2h   xxx.xxx.46.191   xxx.xxx.6.65   <none>           <none>
dnacaap-app-services-6789b57878-xxxqp       1/1     Running   0          6d2h   xxx.xxx.46.165   xxx.xxx.6.65   <none>           <none>
dnacaap-runtime-864cc9fcfb-cw6jt            1/1     Running   1          6d2h   xxx.xxx.46.189   xxx.xxx.6.65   <none>           <none>
dnacp-formatter-services-679ccd95fb-l6dzh   1/1     Running   0          6d2h   xxx.xxx.46.169   xxx.xxx.6.65   <none>           <none>


$ magctl appstack status -f
NAMESPACE                  NAME                                                     READY   STATUS    RESTARTS   AGE    IP               NODE           NOMINATED NODE   READINESS GATES

[Tuesday Jun 11 14:08:20 UTC] maglev@xxx.xxx.6.65 (maglev-master-xxx-xxx-6-65)
$ magctl appstack status dnacaap
NAME                                        READY   STATUS    RESTARTS   AGE    IP               NODE           NOMINATED NODE   READINESS GATES
daas-runtime-5bd7f45655-tjpjq               1/1     Running   1          6d2h   xxx.xxx.46.150   xxx.xxx.6.65   <none>           <none>
dna-event-runtime-5744cbdb9d-8bh2f          1/1     Running   2          6d2h   xxx.xxx.46.191   xxx.xxx.6.65   <none>           <none>
dnacaap-app-services-6789b57878-xxxqp       1/1     Running   0          6d2h   xxx.xxx.46.165   xxx.xxx.6.65   <none>           <none>
dnacaap-runtime-864cc9fcfb-cw6jt            1/1     Running   1          6d2h   xxx.xxx.46.189   xxx.xxx.6.65   <none>           <none>
dnacp-formatter-services-679ccd95fb-l6dzh   1/1     Running   0          6d2h   xxx.xxx.46.169   xxx.xxx.6.65   <none>           <none>


$ magctl appstack status -f
NAMESPACE                  NAME                                                     READY   STATUS    RESTARTS   AGE    IP               NODE           NOMINATED NODE   READINESS GATES

[Tuesday Jun 11 14:13:52 UTC] maglev@xxx.xxx.6.66 (maglev-master-xxx-xxx-6-66)
$ magctl appstack status dnacaap
NAME                                        READY   STATUS    RESTARTS   AGE    IP               NODE           NOMINATED NODE   READINESS GATES
daas-runtime-5bd7f45655-tjpjq               1/1     Running   1          6d2h   xxx.xxx.46.150   xxx.xxx.6.65   <none>           <none>
dna-event-runtime-5744cbdb9d-8bh2f          1/1     Running   2          6d2h   xxx.xxx.46.191   xxx.xxx.6.65   <none>           <none>
dnacaap-app-services-6789b57878-xxxqp       1/1     Running   0          6d2h   xxx.xxx.46.165   xxx.xxx.6.65   <none>           <none>
dnacaap-runtime-864cc9fcfb-cw6jt            1/1     Running   1          6d2h   xxx.xxx.46.189   xxx.xxx.6.65   <none>           <none>
dnacp-formatter-services-679ccd95fb-l6dzh   1/1     Running   0          6d2h   xxx.xxx.46.169   xxx.xxx.6.65   <none>           <none>

maflesch · ‎06-11-2024

Then I would suggest opening a TAC case so the cluster can be inspected.