Issue with setting up a relay on besclient.config

Usage and Config Platform
1

Hello,

I have one server (AIX VIO 6.1) that we are facing issues when setting up the relay for it to report to.

We stop the client and add/replace the config for the __RelayServer1 value but after the client is started again the config file is overwritten with default settings.

The only unusual thing in the logs is " Action site masthead keys are not compatible, starting client reset"

We have already replaced the actionsite.afxm many times (it is the same as the one on the BES Root Server).

What does this “Action site masthead keys are not compatible, starting client reset” mean regarding the logs?
Is this what is causing the config changes not to “stick”?

Current Date: March 28, 2017
Client version 9.1.1117.0 built for AIX 6.1 ppc64
Current Balance Settings: Use CPU: True Entitlement: 0 WorkIdle: 10 SleepIdle: 480
ICU data directory: ‘/var/opt/BESClient’
ICU init status: SUCCESS
ICU deployment character set: ISO_8859-1:1987
ICU local character set: ISO_8859-1:1987
ICU transcoding between deployment and local character sets: DISABLED
At 14:42:44 -0500 -
Starting client version 9.1.1117.0
FIPS mode disabled by default.
Cryptographic module initialized successfully.
Using crypto library libBEScrypto - OpenSSL 1.0.1h-fips 5 Jun 2014
Restricted mode
Action site masthead keys are not compatible, starting client reset
At 14:42:45 -0500 -
Beginning Relay Select

All help is appreciated.

2

The only thing I can see is that there may have been some existing content (an existing /var/opt/BESClient/__BESData directory) when you did this.

The message means that the actionsite masthead and the masthead in /etc/opt/BESClient did not have a compatible signature in them so the client needs to reset.

Was this a working deployment before? Did you alter the config file in some way it got confused?

This does perform a hard reset of the client so yes it will overwrite the settings. Could the relay you are pointing it at be a part of a different deployment?

3

Thank you!

Thank was exactly it! The files/directories were not properly removed when reinstall was done, we have cleared the BESData directory and it all went smooth from there. Thanks again.