Will the hawk event service running on the admin server machine can shutdown the primary ems server, when the ems servers are running in FT mode

[harakishore kommanaboina]

We are using ems as a primary transport and there are 2 ems servers which are running in Fault Tolerance mode.

We are monitoring domain using hawk rules and whenever the hawk agent goesdown, we receive the alerts. Below are the parameters updated in hawkevent.cfg, under the standalone hawkagent path/tibco/config/tibco/cfgmgmt/hawk/bin/

i. -hawk_domain

ii. -ems_transport tcp:EMS:1 ,tcp:EMS:2 username password

iii. -ami_rvd_session

We are able to receive the alerts successfully, whenever any one of the hawkagent goes down from the domain.

Here comes my question: Is there any chance that the running hawk event service from the admin machine can shutdown the primary ems server which is running in FT mode, if we don't provide the below parameters in hawkevent.cfg file.

#ft

#ft_rvd_session

I didn't update the above parameters in hawkevent.cfg file, left with the default values and not sure about those parameters. But I am using ems as the primary transport and ems servers are running in FT mode.

Can anyone please suggest, what values I need to update in the above parameters, if the hawk event service is responsible for the shutdown of the primary ems server. Thanks in advance and it is really appreciated.

[Chenghao Chen]

Hello there,

#ft

#ft_rvd_session

First, these two properties are for hawk event service. They have nothing to do with the EMS FT.

Here are the questions for you:

-> Why do you prefer hawk event to shutdown the EMS server, but not hawkagent

-> The primary EMS server you want to shutdown is used by the domain hawkagent or standalone hawkagent Is it also used by the hawk event

-> In which condition you want to kill the primary EMS server

Thanks

Chenghao

[harakishore kommanaboina]

Hi Chenghao,

 

Thanks for your response. Appreciated.

 

I am not trying to shutdown the EMS server.

 

If we don't provide the parameters #ft, #ft_rvd_session in hawkevent.cfg, where I am using EMS as the primary transport, is there any chance that the hawkevent service is responsible to bring down any one of the EMS server.

 

Actually one of the ems server went down couple of times and I didn't see any specific reason in the logs. I am suspecting, whether the hawk event service is causing this issue (ems shutdown) or not.

 

Note: We have 2 EMS servers in a domain which are running in FT Mode. Thanks in advance.

 

 

 

 

[Chenghao Chen]

Hello there,

No, hawk event as ems client, it doesn't have any chance to kill ems server.

You may increase log trace level from EMS server side and see if it helps.

Also you may need some Linux commands to enable coredump or capture system signals.

Thanks

Chenghao

[harakishore kommanaboina]

Thanks a lot for the response.

 

can you please clarify, when we need to provide the values to the parameters #ft and #ft_rvd_seesion in hawkevent.cfg. Thanks in advance.

[Chenghao Chen]

Whenever you want to configure hawk event server in FT mode, you need to set them.

It's similar like EMS FT, start two hawk event processes, one is active, the other one is standby.