For the earlier question of “where to look next”, basically here’s the order of operations -
-
Check whether the “BES WebUI” service exists and whether it starts successfully.
-
Check the service_wrapper.log beneath the “BES WebUI” directory. The Service_Wrapper.log is the first log that WebUI writes. The Service Wrapper is responsible for gathering WebUI sites from the root server, if there are database connection errors (to BFEnterprise) or failures authenticating to the root server or gathering sites, those should be reflected here.
-
Check the logs beneath “BES WebUI\WebUI\logs”. These logs are generated by the Node.JS servers that make up WebUI. They won’t be written until Service_Wrapper successfully launches Node.JS. The most likely places to find errors affecting WebUI startup would be in service-app.log or datasync.log
What to look at next depends a lot upon what’s found in those logs.
Also check whether the WebUI ports are open.
netstat -anob
This will show listening ports and the executable & PID that has the port open. By default WebUI uses port 443 for its web interface, but also uses a number of ports for the various Node.JS services - I believe by default ports in the range of 5000 - 5100 are listed for potential use, in practical terms I usually see 5000 - 5030 or so depending upon how many WebUI apps are actually enabled. (These are used in a Loopback fashion, they don’t need to be accessible outside of the WebUI host itself, so no firewall rules needed for them.)
Check whether there is another application listening on any of those ports. I recall the Nutanix Guest Additions, if this is a Nutanix VM, tends to use port 5000 and in that case we would need to move WebUI’s port range. WebUI would be using these ports as “node.exe”.