Cannot ping a configured and running satellite in Deploy
Ensure that the
deploy.satellite.enabled setting in the
deploy-satellite.yaml file is set to
yes, as described in Configure satellite communication.
This issue can be caused by the configuration of the satellite address. The IP address and port number that you specify when you create the satellite configuration item (CI) in Deploy’s repository must exactly match the values that appear in the satellite’s log when it is started.
For example, in this log:
13:32:27.802 INFO Remoting - Remoting started; listening on addresses :[akka.tcp://XL-Satellite@192.168.1.7:8380] 13:32:27.804 INFO Remoting - Remoting now listens on addresses: [akka.tcp://XL-Satellite@192.168.1.7:8380]
The satellite starts listening to the address
192.168.1.7 on port
8380. These are the values that you must use for the satellite in Deploy.
Note: If the satellite is listening to
127.0.0.1, you must use this value when adding the satellite to Deploy. Using
localhost is incorrect and will fail.
Deploying to a satellite returns an
akka configuration is distributed across the YAML files in
centralConfiguration directory. Based on the requirement, you can customize the
akka configuration in one of these files:
For more information, see Deploy Properties.
If you deploy an application to a satellite and you see an error such as:
akka.remote.OversizedPayloadException: Discarding oversized payload sent to Actor[akka.tcp://XL-Satellite@mycompany.local:8380/]: max allowed size 128000 bytes, actual size of encoded class akka.actor.ActorSelectionMessage was 162392 bytes.
akka.remote.netty.tcp.maximum-frame-size property to the
deploy.task.system block of the
deploy-task.yaml file. As of version 9.7, the default value of the property is
Note: If you continue to encounter the error, increase the setting by increments of
50000until the error does not occur. Ensure that the property’s value is the same in the configuration files on both Deploy and the satellite.
If you are using SSL connection to communicate with Deploy Satellite, add the
deploy.task.system.akka.remote.netty.ssl.maximum-frame-size property of the
Deploy Satellite does not require a restart after communication failure
If a communication failure occurs between the satellite and the Deploy server, the
akka task system continues to function and only the
akka communication system will require a restart.