Tibcohost fails to start and the following error message will be logged in the tibcohost logs.
=======================
04 Aug 2017 16:55:29,214 [TibcoHostInstance-BPMHost2] [ERROR] com.tibco.amx.hpa.Host - TIBCO-AMX-HPA-CLI-000134: Error starting TIBCO Host.
TIBCO-AMX-HPA-000232: error changing event notification configuration
..
Caused by: TIBCO-AMX-HPA-000047: error initializing notification group
..
Caused by: javax.security.auth.login.LoginException: java.lang.RuntimeException: Key store not found or is not valid: com.tibco.trinity.runtime.base.provider.credential.keystore.KeystoreException: com.tibco.trinity.runtime.base.provider.credential.keystore.KeystoreRuntimeException: com.tibco.trinity.runtime.base.provider.credential.keystore.KeystoreRuntimeException: Failed to load key store: java.io.EOFException..
=========================

Tibcohost fails to start with the error message "Failed to load key store: java.io.EOFException".

ALL

This usually happens due to a corrupt keystore cache file for the tibcohost (qin.ems.credential.store.cache) which is located at {CONFIG_HOME}/tibcohost/<instanceName>/data_3.2.x/host/configuration/ folder. To resolve the issue you can try the steps below which will get a fresh keystore file from Admin({CONFIG_HOME}/admin/<instanceName>/shared/repo/trunk/artifacts/keystore/admin_default_keystore.jceks) to replace the corrupt one.

1). Stop tibcohost using the following option:
tibcohost stop -wait true

2). Remove the current cache file (qin.ems.credential.store.cache) from {CONFIG_HOME}/tibcohost/<instanceName>/data_3.2.x/host/configuration/ folder after making a backup.

3). Copy the Keystore From:
 {CONFIG_HOME}/admin/<instanceName>/shared/repo/trunk/artifacts/keystore/admin_default_keystore.jceks
To:
{CONFIG_HOME}/tibcohost/<instanceName>/data_3.2.x/host/configuration/

And rename it as qin.ems.credential.store.cache.

4). Restart the tibcohost and nodes using the following command:
tibcohost start -clearCache