The 5.2 version of Mobility Suite fails to install when the trial on-box version of rabbitmq is chosen for installation.
The error, "Failed to provision software. Please check /var/log/nukona/load_settings.log for details" is displayed.
The installation script for Mobility Suite attempts to restart the rabbitmq daemon upon discovery that the on-box trial version was set to be configured with the product. Since the rabbitmq daemon is already running since it was setup and its connection was tested in the steps prior to finalizing the configurator phase, the daemon will fail to restart. The Mobility Suite installation does not check to see if the rabbitmq daemon is already running and assumes that it is not, since it is unable to restart it. The appstore_cu directory is unable to be processed because it requires the rabbitmq daemon to be running and the installation fails to process due to the previous checks for the rabbitmq daemon appearing to also fail.
The rabbitmq daemon needs to be turned off before installation can proceed as expected and this can be done by executing the following command from the Terminal:
sudo -u rabbitmq rabbitmqctl stop
The installation can proceed as expected once rabbitmq is turned off. The setup.sh script will not need to be re-run. The configurator process can be resumed rabbitmq has been turned off by pressing the '
Close' button where the error was displayed and pressing the '
Resume' button that appears once the error is cleared.
*Note* - Please ensure that the hosts file on the Mobility Suite/RabbitMQ server includes the hostname on the same line as its
::1 entries similar to the example below before any other entries:
*Note* - Verify that the top line of the Mobility Suite/RabbitMQ server's hosts file with the
127.0.0.1 entry is the one that includes the hostname and not any subsequent duplicate entries of
127.0.0.1 in the hosts file. The Mobility Suite/RabbitMQ installation will fail if this is not properly configured.
*Note* - If DNS is used to populate the hostname of the Mobility Suite/RabbitMQ server and the entry is replaced with a new one, then the Mobility Suite RabbitMQ server
needs to be rebooted before attempting installation. The RabbitMQ service will be unable to start because it will still be attempting to resolve to the old DNS entry/hostname.
Mobility Suite 5.2
RabbitMQ On-Box (Trial)
Imported Document ID: TECH228927
Subscribing will provide email updates when this Article is updated. Login is required.