Qlik Talend Remote Engine Fails to Start via Systemd – Exit Status 126

[Lusemar_Oliveira]

The Talend Remote Engine Service fails to start, and systemd commands do not work as expected, resulting in the following error messages in the system logs:

Subject: Unit process exited

Defined-By: systemd

Support: https://access.redhat.com/support

An ExecStart= process belonging to unit talend-remote-engine.service has exited.

The process' exit code is 'exited' and its exit status is 126.

Jun 19 14:10:13 cmips-etl-ate-talend systemd[1]: talend-remote-engine.service: Failed with result 'exit-code'.

Subject: Unit failed

Defined-By: systemd

Support: https://access.redhat.com/support

The unit talend-remote-engine.service has entered the 'failed' state with result 'exit-code'.

Jun 19 14:10:13 cmips-etl-ate-talend systemd[1]: Failed to start karaf.

Subject: A start job for unit talend-remote-engine.service has failed

Defined-By: systemd

Support: https://access.redhat.com/support

A start job for unit talend-remote-engine.service has finished with a failure.

The job identifier is [Job Number] and the job result is failed.

Jun 19 14:17:50 cmips-etl-ate-talend systemd[1]: Starting karaf...

Subject: A start job for unit talend-remote-engine.service has begun execution

Defined-By: systemd

Support: https://access.redhat.com/support

A start job for unit talend-remote-engine.service has begun execution.

Resolution

Solution for A

1. Test Manual Startup
   To isolate whether the issue is with the service wrapper or the engine itself, try starting the engine manually:

   cd /path/to/Talend-RemoteEngine/bin

   If the engine starts successfully, the problem is with the systemd wrapper or permissions, not the engine itself.
2. Check and Correct File Permissions
   Ensure that the service wrapper scripts (e.g., trun.sh, talend-remote-engine-wrapper, or talend-remote-engine-service) are executable by the user running the service. For example:

   chmod +x /path/to/Talend-RemoteEngine/bin/trun.sh
   chmod +x /path/to/Talend-RemoteEngine/bin/talend-remote-engine-wrapper
   chmod +x /path/to/Talend-RemoteEngine/bin/talend-remote-engine-service

   Also, verify that the files are readable by the intended user and, if necessary, by the systemd process.

Solution for B

1. Address SELinux Restrictions
   By default, SELinux may block execution of the Talend Remote Engine service wrapper, resulting in permission errors even if file permissions are correct.
2. Temporarily disable SELinux
   To confirm if it is the source of the problem:

   sudo setenforce 0 

   Then, retry starting the service. If the service starts successfully, SELinux is the cause.
3. Permanently disable SELinux (if your security policy allows):
   Edit /etc/selinux/config and set:

   SELINUX=disabled

   Reboot the server for the change to take effect.
4. Alternatively, set SELinux to permissive mode:
   Edit /etc/selinux/config and set:

   SELINUX=permissive

   Reboot the server for the change to take effect.

Disabling SELinux reduces system security. Consider creating a custom SELinux policy to allow execution if you must keep SELinux enabled.

Cause

Exit status 126 in systemd indicates that the command was found but is not executable. This typically points to a permission issue on the script or binary that systemd is attempting to launch.

In this context of Talend Remote Engine, this is often caused by:

Cause A

Incorrect file permissions on the service wrapper scripts or binaries.

Cause B

SELinux policies prevents execution of the wrapper script or service file.

Environment

• Talend Cloud 
• Talend Studio