Troubleshooting

R2026b

For questions or issues about your installation of Embedded Coder^® Support Package for Service-Oriented Applications on Linux^®, see Install Embedded Coder Support Package for Service-Oriented Applications on Linux. Refer to these guidelines to resolve known issues:

Communication between SOA applications running on different machines does not work

• To establish communication between applications, all the ports for inbound and outbound UDP communication should be open.

• The machines should be under the same intranet.

Docker permission issue

• Docker command needs root permissions to manage Docker and have privileges. To manage docker as a non-root user, follow the steps mentioned in https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user.

Application deployment failed due to permission issue

• Target user should have read, write, and execute permissions for the deployment location.

Connection timed out error

To debug the connection timed out error that occurs while trying to connect, ensure the following:

• Refer to Target Computer Requirements to verify the target computer meets all the requirements.

• Ensure that firewalls and cloud security groups (such as AWS Security Groups) do not block the ports used for connection on the target computer, including the support package communication ports (default 5555 and 5556), DDS ports, and XCP TCP ports. For more information, see Configure Network Ports and Cloud security groups block network ports.

• For WSL targets, specify the eth0 interface IP as target IP address.

• For WSL targets, the default Linux distro will be used for connection. To set a specific distro as default, use the command

  wsl --setdefault <specific distro>

  For example, to set Ubuntu as default distro, run the following command on command prompt.

  wsl --setdefault Ubuntu

• For WSL targets that are connected to VPN, disconnect the VPN before trying to connect to the target.

• When you use a virtual machine as the target computer, configure its network settings to use a bridge network.

Default port already in use by another service

The support package uses ports 5555 and 5556 on the target computer by default for host communication. If another service on the target machine already uses one of these ports, the connection fails. For example, on GPU-enabled cloud instances such as AWS EC2 instances with NVIDIA GPUs, port 5555 may be in use by the NVIDIA Data Center GPU Manager (DCGM) service.

To resolve this issue, change the default ports used by the support package. Edit the <Support-Package-root>/toolbox/coder/linux/host/ContainerConfig.json file to specify ports that are not in use. For more information, see Configure Network Ports.

To identify which process uses a port on the target, run this command on the target:

sudo lsof -i :5555

Cloud security groups block network ports

Cloud environments such as Amazon Web Services (AWS) use security groups that block most inbound ports by default (other than common ports such as port 22 for SSH). This can prevent the support package from communicating with applications on the target.

Ensure that your cloud security group allows inbound traffic on the following ports:

• Support package communication ports — Ports 5555 and 5556 by default (or the custom ports you configured in ContainerConfig.json).

• XCP TCP port — The port specified in the linux.setXCPServiceConfiguration function.

All of these port numbers are configurable. For more information about changing ports, see Configure Network Ports.

Log messages not visible in Linux Runtime Manager

If the application runs but log messages do not appear in the Linux Runtime Manager log viewer, verify the logging configuration:

• Ensure the application is deployed with logging enabled. Log messages are visible in Linux Runtime Manager only when the application is configured to send log output over the network. If logging is directed to the console or a file, messages do not appear in the log viewer.

• The severity level filter in the Log Viewer panel controls which messages are displayed. For example, if the filter is set to Error, only error-level and higher severity messages appear. Set the severity filter to Verbose to see all messages.

For more information about viewing and filtering log messages, see Configure Run-Time Logging for AUTOSAR Adaptive Executables (AUTOSAR Blockset).

For more specific troubleshooting solutions, go to the MathWorks^® Support website MathWorks Help Center website.