ENS Is Not Logging Connections From Mboxutil On All Hosts With Cassandra Store (Doc ID 2804016.1)

Last updated on SEPTEMBER 01, 2021

Applies to:

Symptoms

On a test system, "host1" was configured to use Cassandra. A user and folder were created and the "deliver" command was used to deliver a message to that folder.
"Host2" was configured to use the same Cassandra and an "mboxutil -l" was performed on that system.

In the ens log on host1, host2 was observed connecting to ensp on host1, when the "mboxutil -l" was performed on host2.
But, the ens log on host2 did not show any connection from host1 when "mboxutil -l" was performed on host1.

There are two other systems configured in the affinity list, but strace of "mboxutil -l" did not show any attempt to connect to them.

Why is mboxutil -l connecting to ENS at all?
And why does it only seem to connect to host1?

Another test was performed where "mboxutil -c user/<user>/test" was run on host1.

Again, the ens log on host1 showed the connection from itself, but there was no connection to ens on host2.

Then, "mboxutil -c user/<user>/test2" was perfomed on host2. Again, the ens log on host1 showed the connection from host2, but there was no connection to ens on host2.

It appears that:

- "mboxutil -l" on host2 causes a connection to ens on host1
- "mboxutil -l" on host1 does NOT connect to ens on host2

It appears to be only connecting to the first host in the list:

role.proxy:host\.example\.com.storehostlist = host1.example.com host2.example.com host01.sub.example.com host02.sub.example.com

The ens log on host1 showed connections by both the server itself, as well as from host2 when an mboxutil was performed:

-bash-5.0$ grep IP_of_host2 ens | wc -l
9

-bash-5.0$ grep IP_of_host1 ens | wc -l
0

Mboxutil -l on host2 causes a connection to ens on host1.
Mboxutil -l on host1 does NOT connect to ens on host2.

Changes

Cause