Explorer (DUX) fails to start when executed by a non-root user

Products

• Automic Dollar Universe

Issue/Introduction

After assigning the whole folder structure to another user other than root post installation of Dollar Universe Explorer, the product fails to start.

When attempting to start the instance, the unistartdux script terminates with the following error: => This Dollar Universe Explorer instance can only be started by instance owner or "root" user.

Investigation reveals that the RUNNING_PID file cannot be created in the duexplorer/bin directory due to the permissions being set to 555 during installation.

Environment

• Product: CA Automic Dollar Universe Explorer
• Version: 7.x
• Operating System: Linux / Unix

Cause

The DUX installation sets the permissions of the bin directory to 555 (read and execute only). This prevents the non-root owner from writing the RUNNING_PID file or other tracking metadata (e.g., es_uvms_fields_updated_do_not_touch) to that directory during the startup sequence.

Resolution

Workaround: 

Grant write permissions to the instance owner for the bin directory.

1. Log in as the root user or a user with sudo privileges.
2. Navigate to the Dollar Universe Explorer installation root.
3. Change the permissions of the bin directory to 755: chmod 755 bin
4. Verify that the instance owner (e.g., admindu) can now create files in the bin folder.
5. Start the DUX service using the unistartdux script.

Solution:

Fix Status: This issue is confirmed as a product limitation (tracked via DE208159).

To receive updates on the fix status, subscribe to this article.

Additional Information

For further details on running Dollar Universe components as a non-root user, see DUAS systemd script for RHEL9.