Fixed c4_cloud_command not finding the current internal IP after reboot
Details
| Detail name | Value |
|---|---|
| Changelog Number | 24213 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 8.0.0 |
| Fix Versions | C4 4.26.0, Exasol 8.29.10, C4 4.19.7, Exasol 2025.1.0 |
| Resolution Date | 2025-05-12 |
Description
When a node was rebooted, “c4_cloud_command” could fail with a small probability with an error claiming that the specified CCC_HOST_ADDRS internal IP addresses didn’t contain the current machine’s internal IP address. The reason for that was that the network interfaces were not fully initialized at the point when the service ran.
Workaround
Restart the service on the nodes that had the issue with: “sudo systemctl restart c4_cloud_command”.
Fix
The “c4_cloud_command” service now starts only after “network-online.target” systemd target is reached, instead of “network.target”.
