I have installed and configured the DB connect under my deployer. Added identities and connections.
Then copied the etc/apps/splunk_app_db_connect to /etc/shcluster/apps/ and pushed the bundle to shcluster.
As per doc: https://help.splunk.com/en/splunk-cloud-platform/connect-relational-databases/deploy-and-use-splunk-...
App is deployed but identity.dat file is generated every 30s on sh members and that is different than on my deployer.
DB Connect GUI on SH members gives me an error: "Identity password is corrupted."
What did I miss?
Hello @JykkeDaMan This can be addressed by following below steps:
Stop the Deployer
First, stop the deployer service to begin the resolution process.
Stop the Splunk Service on Each Cluster Node
On each cluster node, stop the Splunk service before proceeding.
Remove Keystore and Password Files
On each cluster node, remove the following files:
keystore/default.jks
certs/keystore_password.dat
Delete Secret Data from Splunk Storage Collections
Run the following command on each cluster node to delete the secret data:
curl -k -u username -X DELETE https://<host>:<management-port>/servicesNS/nobody/splunk_app_db_connect/storage/collections/data/secret
Repeat the Process on All Cluster Nodes
Perform steps 2 through 4 on all nodes in the cluster to ensure consistency.
Start the Splunk Service on All Nodes
After completing the above steps on all nodes, start the Splunk service again
Also raising support case can make your work more easily in such issues.
Ok, i'll try.
But was there something I did wrong when deploying the app? Why did I end up into this state and how to prevent it in the future?