Hi Chris,
this message
Fatal error - you will be redirected to the login page, please check logs
Model is empty, check connection settings
is a very typical error when setting up SH with BSM the very first time.
When you start the SH GUI, it reads information out of the file <SiteScope>\conf\sh\shModel.ser.
If this file doesn't exist, the GUI fails to start.
The missing file is caused by SH being unable to retrieve the model from BSM.
Things to verify:
- make sure you are running a version of System Health which matches the version of BSM.
If you are running BSM 9.26, you need to run SH 9.26
- you need to create a JBoss application user on each BSM system (GW, DPS)
as described in the manual Using System Health -> Chapter 1: Setting Up System Health -> How to add a JBoss user
This user and password needs to be specified in SH Setup under
Security
Application User
Password
- when you enter the hostname after you installed SH the first time, make sure to specify the fully qualified hostname only,
no "http://" or alike in front of it
you can verify the setting by checking the file <SiteScope>\conf\sh\systemhealth.properties
machine.names=sov02bac26.eu.hpecorp.net
(that's the line of one of my test systems)
- make sure BSM properly returns the SH model via
GW JMX 29000 -> SystemHealth:service=SH BSM modelbuilder
invoke com.hp.systemhealth.api.ModelContainer retrieveModel()
it should return a line like
com.hp.systemhealth.api.ModelContainerImpl@fad1a84
invoke retrieveModelWithAllPropsHTML()
it should return a table with systems and process names and alike
Things to try:
- stop SH
- run sh_config.bat | .sh
- enter the FQDN of the GW server (or LB, in case you use multiple GW servers and a LoadBalancer in front of them)
if this doesn't work
- enter the IP address of the GW server
- check the file <SiteScope>\logs\systemhealth.all.log
Example when an incorrect password for the JBoss application user has been specified
..
2016-11-28 12:14:18,627 [SiteScope Main] (BSMJMXConnectionProvider.java:36) DEBUG - Creating connection for jmxServiceUrl = service:jmx:remoting-jmx://sov02bac26.eu.hpecorp.net:4447
2016-11-28 12:14:19,580 [SiteScope Main] (BSMJMXConnectionProvider.java:52) INFO - failed to connect to JMX url: service:jmx:remoting-jmx://sov02bac26.eu.hpecorp.net:4447
javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms
..
Example when no JBoss application user has been defined in BSM, or BSM is not responding at all
..
2016-11-28 12:41:53,626 [SiteScope Main] (BSMJMXConnectionProvider.java:36) DEBUG - Creating connection for jmxServiceUrl = service:jmx:remoting-jmx://sov02bac16.eu.hpecorp.net:4447
2016-11-28 12:41:55,657 [SiteScope Main] (BSMJMXConnectionProvider.java:52) INFO - failed to connect to JMX url: service:jmx:remoting-jmx://sov02bac16.eu.hpecorp.net:4447
java.net.ConnectException: Connection refused: no further information
..
Example when BSM doesn't respond fast enough (that's an issue I currently work on):
..
2016-11-24 18:14:59,373 [SiteScope Main] (MBeanUtils.java:74) INFO - Error invoking performing operation for SystemHealth:service=SH BSM modelbuilder url service:jmx:remoting-jmx://sov02bac26.eu.hpecorp.net:4447
java.io.IOException: Unable to invoke invoke(), status=WAITING
at org.jboss.remotingjmx.protocol.v2.ClientConnection$TheConnection.invoke(ClientConnection.java:1072)
..
2016-11-24 18:14:59,388 [SiteScope Main] (ModelBuilderManagerImpl.java:244) ERROR - Error getting model, loading model from persistency
com.mercury.am.systemhealth.adapters.SHRemoteAdapterException
Caused by: java.io.FileNotFoundException: C:\SiteScope\conf\sh\shModel.ser (The system cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
With debug logging enabled one can see that the connection is closed / reset after 60 seconds:
2016-11-24 18:13:59,356 [SiteScope Main] (BSMJMXConnectionProvider.java:49) DEBUG - connection:org.jboss.remotingjmx.RemotingConnector@18e1940
2016-11-24 18:13:59,356 [SiteScope Main] (AbstractLog.java:14) DEBUG - conn = org.jboss.remotingjmx.RemotingConnector@18e1940
2016-11-24 18:14:59,373 [SiteScope Main] (MBeanUtils.java:74) INFO - Error invoking performing operation for SystemHealth:service=SH BSM modelbuilder url service:jmx:remoting-jmx://sov02bac26.eu.hpecorp.net:4447
java.io.IOException: Unable to invoke invoke(), status=WAITING
I'm pretty sure that your systems suffers from one of the usual issues
- missing JBoss user
- malformed hostname
- DNS issues preventing the system from properly resolving the hostname
Greetings
Siggi