Stealthwatch 7.5.1 - Data store initialization fails to register

[SC99]

Hi, doing some investigation into Stealthwatch...setting this up in my lab with Data Store option. Mgmt server sent through okay but as I went threw the data store initialization at the console, it asks at the end to register with central manager.  I enter ip and creds and I accept the self-signed certificate but it immediately comes back with failed to register so I can't complete initialization.  Kind of stuck since it hasn't completed the basic initialization so web ui doesn't allow of config changes and ssh is disabled.  Anyone have this before?

[David Salter]

I've seen this where the Data Store is on a different subnet to the Manager and there was a firewall/ACL blocking connectivity.  You should be able to get to the console menu vis the sysadmin user account to re-initialize the Data Store and try again.

[SC99]

Everything is on the same subnet so there should be nothing blocking communications.  Not sure how to get to the console as I am still in that first initialization screens at console and I don't see a way to get to a command line or any sort of log.  Even if I forced a restart I think it would force me into this screen with sysadmin or tell me initialization not complete.

[David Salter]

Just to be 100% clear you are stuck in the initial config menu via CLI - you see something like this?

You would need a Token from TAC to get to CLI however if the web UI has started you can get to the logs from the support section:

In logs/system_config.log look for:

2024-09-09 13:54:30,036:INFO:Add Appliance - Initializing Central Management...

What do you see in the next few lines?  By all means DM the log (or a snippet).

[SC99]

sent you a DM but this is in the first time setup process....roughly page 57 in the system configuration guide for 7.5.1.

[SC99 · Accepted solution]

for anyone reading this, seemed like it was some issue with special characters in the admin password when trying to register datastore to central manager during first time initialization.....removing special characters resolved the issue.