How do I fix HTTP ERROR: 503 after upgrade of Geneos Web Dashboard

For Default Users

If user did not have customization to the startup script prior the upgrade, they are suggested to use the copy that comes as default in the Web Server download. Users should follow the Running Start Scripts section in the Web Dashboard documentation.

For those using the PS Templates

Organisations with implementation using the ITRS Professional Service Best Practice templates, please obtain the latest version of "webserverctl" script from your technical contact in ITRS or raise a support request.

For those using a Custom Script

If user built a custom start script based on GA3.2.0 or an earlier version, they will need to manually adjust the script. Users are advised to check the "run" and "geneows" scripts in the Web Server installation package, and apply the changes to their custom script accordingly. Here we have prepared a list of changes in GA3.x and GA4.x as of this writing.

• GA3.2.1 and above: SECURITY_CONFIG flag
• GA3.4.0 and above: ENABLE_SSL flag (optional, default is commented out)
• GA4.3.0 and above: SSO_PROPERTIES flag

1. Add variable definitions in the script header as appropriate

e.g.
SECURITY_CONFIG="-DsecurityConfig=${SCRIPTPATH}/config/security.xml"
#ENABLE_SSL="-ssl true"
SSO_PROPERTIES="-Dcom.itrsgroup.sso.config.file=${SCRIPTPATH}/config/sso.properties"

2. Reference the variables in the start JVM command. Below command is taken from version GA4.9.2 as an example. (Please check the actual version of Web Server for the "geneosws" script.)

e.g.

"$JRE_BIN_PATH/java -XX:+UseConcMarkSweepGC -Xmx1024M -server $HEADLESS $SECURITY_CONFIG $CONFIG $RESOURCES $JAVA_LIBRARY_PATH $LOG_PROPERTIES $PATH_FOR_LOG4J $JAVA_PROPS $SSO_PROPERTIES $BDO_FLAGS $JMX_FLAGS $DUMP_HEAP_ARGS $JAR_PATH $GWS_PORT $WEBAPPS $GWS_PORT $ENABLE_SSL &"

3. Verify security.xml is correct

Ensure that security.xml contains a valid path to the users.properties file

4. Restart the Web Server process

To enable Authentication

Please refer to the section Enabling Authentication in the Web Dashboard documentation. The 2 configuration files security.xml and users.properties will need to be updated, and the Web Server process should be restarted.