-
Title
Unable to start FMS as Daemon -
Description
Unable to start the FMS as daemon process in a freshly installed RHEL environment.
-
Cause
The following error is observed in the FMS logs:
XXXX-XX-XX XX:XX:XX.XXX WARN [forge-startup] com.quest.nitro.startup.BindAddressUtil - Too many remotely visible IP addresses are available, the server will use the first one for remote references to itself: [/XX.XXX.X.XXX, /XXX.XXX.XXX.X].
XXXX-XX-XX XX:XX:XX.XXX INFO [forge-startup] com.quest.nitro.startup.BindAddressUtil - The server automatically chose XXXXXXXXXXX.XXXXXXX.XXX as the address to be used in remote references to itself. Use the server.remote.address property in server.config to override.
AND
XXXX-XX-XX XX:XX:XX.XXX FATAL [forge-startup] com.quest.nitro.startup.ForgeServer - Unexpected error during server startup, exiting with error code 1133. org.springframework.beans.factory.access.BootstrapException: Unable to initialize group definition. Group resource name [classpath*:com/quest/nitro/service/bootstrap-beanref.ctx.xml], factory key [forge-bootstrap]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'forge-bootstrap' defined in URL [jar:file:/home/foglight/Quest/Foglight/server/core/foglight.jar!/com/quest/nitro/service/bootstrap-beanref.ctx.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.context.support.ClassPathXmlApplicationContext]: Constructor threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.quest.nitro.bootstrap:name=Core0' defined in class path resource [com/quest/nitro/service/bootstrap-services.ctx.xml]: Invocation of init method failed; nested exception is org.springframework.beans.factory.access.BootstrapException: Unable to initialize group definition.
-
Resolution
1. Change the parameter in the /config/server.config configuration file
server.bind.address = "X.X.X.X";
server.remote.address = "host_name";
2. Check if the right Java version is used.
3. Make sure that the IP address in the etc/hosts file is correct. Ensure that the .is consistent.
4. Confirm if there is any firewall blocking. If yes, turn off the firewall on the FMS.
5. Restart FMS.