Fixed Ubuntu upgrades restarting Exasol services

Detail name	Value
Changelog Number	27107
Type	Bug
Status	Resolved
Affected Versions	Exasol 8.34.0, Exasol 8.29.9
Fix Versions	C4 4.29.0, Exasol 2025.1.5, C4 4.28.5, Exasol 2025.2.0
Resolution Date	2025-10-28

Description

The Ubuntu upgrades starting from Ubuntu 24.04 now automatically restart all the system services as a part of the upgrade process. As a result, the Exasol services including c4_cloud_command was being restarted which restarted the database itself causing disruption. We previously fixed this issue by adding the Exasol services to the ignore list of the “needrestart” component responsible for this behavior, but the fix only applied for newly created Exasol installations.

Workaround

Run the following commands on every node:

mkdir -p /etc/needrestart/conf.d
cat << EOF > /etc/needrestart/conf.d/exasol.conf
\$nrconf{override_rc}{qr(^c4_cloud_command\.service\$)} = 0;
\$nrconf{override_rc}{qr(^c4\.service\$)} = 0;
\$nrconf{override_rc}{qr(^exasol-admin-ui\.service\$)} = 0;
EOF

Fix

The fix is now applied during the update process (c4 update cluster) for rootful installations. For rootless installations we will be requiring the users to rerun c4 _ preplay command on all the nodes before the update.

Changed behavior

For rootless installations, "c4 _ preplay" now needs to be rerun on all the nodes before every update.