NAS down

[Anon Anon]

Hi,

 

We recently upgraded nas version and post which we have nas probe down. On checking the logs I can see

 

May 19 10:03:00:403 [10288] nas: Subscriber destroyed...
May 19 10:03:00:403 [10288] nas: Destroying Correlation engine...
May 19 10:03:00:403 [10288] nas: Correlation engine destroyed...
May 19 10:03:00:403 [10288] nas: Destroying the NiS bridge...
May 19 10:03:00:419 [10288] nas: NiS bridge destroyed...
May 19 10:03:00:419 [10288] nas: QosBridge - waiting for thread to complete.
May 19 10:03:00:419 [10288] nas: QosBridge - destroyed...
May 19 10:03:00:419 [10288] nas: Destroying Activity-Logger...
May 19 10:03:00:419 [10288] nas: Activity-Logger destroyed...
May 19 10:03:00:419 [10288] nas: Destroying Transaction-Logger...
May 19 10:03:00:419 [10288] nas: Transaction-Logger destroyed...
May 19 10:03:00:419 [10288] nas: Destroying Replication engine...
May 19 10:03:00:419 [10288] nas: Replication engine destroyed...
May 19 10:03:00:419 [10288] nas: maint Maintenance Mode Destroyed
May 19 10:03:00:419 [10288] nas: Destroying Event publisher...
May 19 10:03:00:419 [10288] nas: Event publisher destroyed...
May 19 10:03:00:419 [10288] nas: Destroying NameService...

 

 

What these messages signify and what is a way to restore services. We even tried to downgrade the version which again shows the same error.

 

Thanks,

Ananda Guberan K

[Anon Anon]

did you deactivate and re activate the probe otherwise maybe a restart of the hub would work.

[Anon Anon]

Hi Neal,

Thanks for the update. I managed to bring the probe up and running. It was down because of alarm_enrichment as we are not using it in our environment. But I would still be interested in knowing the significance of the log messages generated.
Thanks again.

Thanks,
Ananda Guberan K

[Anon Anon]

Makes sense nas needs alarm_enrichment as it initially excepts the alarm Q then forwards to alarm2 which the nas attaches to.

[Matthias Gruber]

We also dont use the alarm-enrichment, and switched the Q's so alarm_enrichment can run, and is found on updates but doesnt do anything (just talking to itself). Perhaps a workaround for next time ;->

 

cheers

Matthias

 

[Anon Anon]

I've also disabled alarm_enrichment as I don't use it and it's an unstable component. Also, I really don't like anything that intercepts messages before they get to NAS.

 

I recommend you contact support if you decide to disable, as it is not quite so straight forward as "normal" probes. It's important to disabled alarm_enrichment properly, as it changes the alarm and alarm2 queues at startup.

 

-jon

[Anon Anon]

Sometimes I feel I'm the only person in the world using alarm_enrichment. Not sure if it makes me proud or scared.