What information should I collect when reporting an EMSA issue?
Article ID: KB0086503
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
Description:
= = = = = = =
EMSA (TIBCO Enterprise Message Service Appliance) is a standalone appliance that offers the full functionality of a TIBCO Enterprise Message Service server. EMSA 1.0.x is running the EMS 7 daemon. EMSA customers usually takes advantage of the Fault Tolerance feature of EMSA. For most issues, you could treat it as a EMS 7 FT tibemsd64.
Regarding hardware related issue, try to collect the following information:
1). The following log files for each instance would be helpful for debugging EMSA issues (some may not be present for a given instance):
cli.log dr_status.log
primary-fsm.log
single-fsm.log dr_params.log
emsd.log
health-check.log
setup_params.log secondary-fsm.log
To export the logs:
Use SSH to login to the Appliance as tibadm and run the following commands (NOTE: due to a known issue the user may have to first log in via SFTP and delete existing files from the logs directories for each instance.)
emsacli> export 0 logs
emsacli> export 1 logs
2). The following command output should be useful most of the time.
>info 0
>info 1
>setup-show
>version-show
3). Depending on the nature of the issue (box/hardware vs EMS services) some additional information may be useful but would need to be collected via the 'admin' login going through the support challenge/response sequence to get a shell prompt. Once "in", data can be copied to the directory:
/tib-transfer/system/export/
so that it is available for download using the SFTP login.
EMSA Engg will provide you with the script or host it remotely and give access. Once logged in as admin you need to run commands such as svcs -a > svcs.out . Copy the files to the /tib-transfer/system/export/ directory to be taken out of the Appliance using tibfile user and send to EMSA Engg/Pluribus support.
Ask for the following files after the script has been run.
/var/nvOS/log/nvOSd.log
/var/adm/messages
4). Generate the svcs.out and forward to EMSA engineering.
# svcs -a > svcs.out
Description:
= = = = = = =
EMSA (TIBCO Enterprise Message Service Appliance) is a standalone appliance that offers the full functionality of a TIBCO Enterprise Message Service server. EMSA 1.0.x is running the EMS 7 daemon. EMSA customers usually takes advantage of the Fault Tolerance feature of EMSA. For most issues, you could treat it as a EMS 7 FT tibemsd64.
Regarding hardware related issue, try to collect the following information:
1). The following log files for each instance would be helpful for debugging EMSA issues (some may not be present for a given instance):
cli.log dr_status.log
primary-fsm.log
single-fsm.log dr_params.log
emsd.log
health-check.log
setup_params.log secondary-fsm.log
To export the logs:
Use SSH to login to the Appliance as tibadm and run the following commands (NOTE: due to a known issue the user may have to first log in via SFTP and delete existing files from the logs directories for each instance.)
emsacli> export 0 logs
emsacli> export 1 logs
2). The following command output should be useful most of the time.
>info 0
>info 1
>setup-show
>version-show
3). Depending on the nature of the issue (box/hardware vs EMS services) some additional information may be useful but would need to be collected via the 'admin' login going through the support challenge/response sequence to get a shell prompt. Once "in", data can be copied to the directory:
/tib-transfer/system/export/
so that it is available for download using the SFTP login.
EMSA Engg will provide you with the script or host it remotely and give access. Once logged in as admin you need to run commands such as svcs -a > svcs.out . Copy the files to the /tib-transfer/system/export/ directory to be taken out of the Appliance using tibfile user and send to EMSA Engg/Pluribus support.
Ask for the following files after the script has been run.
/var/nvOS/log/nvOSd.log
/var/adm/messages
4). Generate the svcs.out and forward to EMSA engineering.
# svcs -a > svcs.out
Issue/Introduction
What information should I collect when reporting an EMSA issue?
Feedback
Yes
No
Powered by
