Rhino fails to start

If you get the following error during the build:

FAILED - Hit exception: Timed out waiting for Rhino to start

examine target/rhino.log to identify the problem, as below.

"Endpoint for this node does not match active interface on this host" error

Symptoms

A message like this in target/rhino.log:

Endpoint for this node does not match active interface on this host. Endpoint: 172.17.0.1:12100

Cause

You have encountered a limitation using host networking mode with VMBC, where Rhino does not correctly identify the network interfaces in use. This is an artifact of using Docker-in-Docker and happens only on some operating systems.

Solution

Re-run VMBC without the -n flag.

If you have custom build scripts that require internet access and removal of the -n flag causes them to fail, you need to find an alternative approach, such as downloading yum packages or other files beforehand and including them in the custom build hooks archive.

Watchdog timeout error

Symptoms

Messages like the following in target/rhino.log:

Watchdog Failure has been notified to all listeners because condition 'GroupHeartbeat for group rhino-cluster (sent=10 received=0)' failed
*** WATCHDOG TIMEOUT ***
Failed watchdog condition: GroupHeartbeat for group rhino-cluster (sent=10 received=0)
Failed watchdog condition: GroupHeartbeat for group rhino-management (sent=10 received=0)
Failed watchdog condition: GroupHeartbeat for group rhino-admin (sent=10 received=0)
Failed watchdog condition: GroupHeartbeat for group domain-0-rhino-ah (sent=10 received=0)
Failed watchdog condition: GroupHeartbeat for group domain-0-rhino-db-stripe-0 (sent=10 received=0)

Cause

You have encountered a limitation using host networking mode with VMBC, where Rhino cannot communicate on the clustering network interface. This is an artifact of using Docker-in-Docker and happens only on some operating systems.

Solution

Same as for the "Endpoint for this node does not match active interface on this host" error.

"Connection to PostgreSQL database failed" error

Symptoms

A message like this in target/rhino.log:

Connection to PostgreSQL database failed: server="localhost:5432", user="rhino", database="rhino_100"

Cause

You are running VMBC with the -n flag, and also have a local PostgreSQL server instance running on the host.

Solution

Either run VMBC without the -n flag, or temporarily stop the host’s PostgreSQL server instance (for example, by running sudo systemctl stop postgresql on a systemd-based operating system).

Errors importing your application into Rhino

"One or more components already deployed, or defined multiple times in the deployable unit" error

Cause

You provided a directory of deployable units, and within those deployable units, you included one or more built-in Rhino components, and/or your application’s deployable units define the same component more than once.

Solution

Ensure the directory of deployable units does not contain any built-in Rhino components. It must only contain components and libraries specific to your application.

Ensure none of your application’s deployable units define the same component more than once, including across different jar files. The error message includes details of the (first) duplicate component that Rhino found.

Previous page