Skip to main content Skip to complementary content
  • New archived content: Talend MDM, Talend Data Catalog 8.0, and Talend 7.3 products reached their end of life in 2024. Their documentation was moved to the Talend Archive page and will no longer receive content updates.
Close announcements banner

Installing the Talend Runtime service on systemd-based Linux systems

Before you begin

In the following procedure:
  • TALEND-CONTAINER is the name that was used for the -n <Service Name> option in the wrapper:install command.
  • <TalendRuntimePath> is the Talend Runtime installation directory.

All the following commands must be executed with super-user privileges.

Procedure

  1. Install the service and enable it at system boot:
    systemctl enable <TalendRuntimePath>/bin/TALEND-CONTAINER.service
    Troubleshooting:

    If the systemctl enable command fails with the error Failed to enable unit: Cannot alias ..., follow these steps:

    1. Open the [TALEND_RUNTIME_PATH]/bin/TALEND-CONTAINER.service file in a text editor.
    2. Locate the line starting with Alias= and delete it.
    3. Save the changes.
    4. Execute the systemctl daemon-reload command.

    After completing these steps, the systemctl enable command should work as expected.

  2. Start the service:
    systemctl start TALEND-CONTAINER

    To ensure the systemd service starts correctly, stop any Talend Runtime container that was previously launched using the trun command. Otherwise, systemd may attempt to start a second instance of Talend Runtime, which will fail because the TCP/IP ports are already in use.

Results

The service is installed and started.
You can use the following commands to manage the service:
  • To stop the service: systemctl stop TALEND-CONTAINER
  • To check the current service status: systemctl status TALEND-CONTAINER
  • To see service activity journal: journalctl -u TALEND-CONTAINER
  • To uninstall the service and disable it at system boot: systemctl disable TALEND-CONTAINER

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!