Ataccama ONE Agentic ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
latest (17.1.0) 17.0.0 16.3.x 16.2.0 16.1.0 16.0.0 15.4.0 15.3.0 15.2.0 15.1.0 14.5.x 13.9.x 13.8.x 13.7.x 13.6.x 13.5.0 13.4.x 13.3.x 13.2.x
Downloads

Manage and Troubleshoot the Hybrid DPE Service

A hybrid Data Processing Engine (DPE) deployed on a virtual machine (VM) runs on your own Linux server and connects outbound to your Ataccama ONE environment. This page explains how to check, restart, and collect logs from a hybrid DPE.

Run all commands on the DPE server. Most of them require sudo.

To troubleshoot specific errors, see Troubleshooting Hybrid Deployment.

How the hybrid DPE runs

The hybrid DPE is installed and managed as a systemd service. It starts automatically when the server boots, so you don’t need to start it manually after a server restart.

You manage it with the standard systemctl and journalctl commands, for example, to check its status, restart it, or read its logs.

The service is defined in these files:

DPE service definition files
/etc/systemd/system/dpe.service
/etc/systemd/system/dpe.service.d/dpe.conf

Default installation location

By default, DPE is installed in /opt/ataccama/one/dpe.

This path is usually a symbolic link to a versioned directory, for example, /opt/ataccama/one/dpe-assembly-16.3.0.260202-28336-9d20f394. To check which version is in use, run:

Check the installed DPE version
ls -l /opt/ataccama/one/dpe

The installation directory contains the following subdirectories:

Path Contains

/opt/ataccama/one/dpe/etc/

Configuration (application.properties)

/opt/ataccama/one/dpe/log/

Application logs

/opt/ataccama/one/dpe/lib/jdbc/

JDBC drivers

/opt/ataccama/one/dpe/tmp/

Temporary job workspace

/opt/ataccama/one/dpe/storage/

Local job state

All files must be owned by the dpe user and group.

Find the DPE service name

The service is usually called dpe. The name can differ, especially if more than one DPE is installed on the same server.

To find the service name, use any of the following commands:

Find the DPE service name
# List running services matching "dpe"
systemctl list-units --type=service | grep -i dpe

# List all installed service files matching "dpe", including stopped ones
systemctl list-unit-files | grep -i dpe

# List the systemd directory directly
ls -l /etc/systemd/system/ | grep -i dpe

Common service names include:

Name Meaning

dpe.service

A single DPE.

dpe@1.service, dpe@2.service

Multiple DPEs on one server, using a templated service.

dpe-2.service, dpe-dev.service

Multiple DPEs with custom names.

The commands on this page use dpe. If your service has a different name, replace dpe with it.

DPE log location

DPE writes application logs to /opt/ataccama/one/dpe/log/. The log files are in JSON format (*.json).

To list the log files, run:

List DPE log files
ls -lh /opt/ataccama/one/dpe/log/

DPE also writes to the systemd journal. The journal is usually the easier place to look for startup problems. See View recent DPE logs.

Restart the DPE service

To restart DPE:

  1. Run the following command:

    sudo systemctl restart dpe

  2. Check that the service is running again:

    sudo systemctl status dpe

To restart DPE and watch the startup log live, run the following command. To stop following the log, press Ctrl+C.

Restart DPE and follow the log
sudo systemctl restart dpe && sudo journalctl -u dpe -f

You can also stop, start, or check the status of the service:

Other service commands
sudo systemctl stop dpe
sudo systemctl start dpe
sudo systemctl status dpe

Apply changes to the service configuration

If you change /etc/systemd/system/dpe.service.d/dpe.conf, reload systemd before you restart DPE. Otherwise, your change is ignored.

Reload systemd and restart DPE
sudo systemctl daemon-reload
sudo systemctl restart dpe

View recent DPE logs

To show the last 100 lines of the DPE journal, run:

Show the last 100 lines of the journal
sudo journalctl -u dpe -n 100 --no-pager

You can also use the following variations:

Other ways to view DPE logs
# Follow the log live
sudo journalctl -u dpe -f

# Show the last 100 lines of the application log files
sudo tail -n 100 /opt/ataccama/one/dpe/log/*.json

# Show only errors from the last hour
sudo journalctl -u dpe --since "1 hour ago" -p err --no-pager

If there are several application log files, tail shows the last 100 lines of each file in turn, so the output is not in chronological order across files.

Collect logs for Ataccama Support

To send logs to Ataccama Support, export the journal for the relevant time window and package it with the application logs:

  1. Export the journal. Use either a specific time window or the last 24 hours:

    # Specific time window: adjust the timestamps
sudo journalctl -u dpe --since "2026-08-10 08:00" --until "2026-08-10 10:00" --no-pager > ~/dpe-journal.log

# Last 24 hours
sudo journalctl -u dpe --since "24 hours ago" --no-pager > ~/dpe-journal.log

  2. Package the journal export with the application logs:

    cd ~
sudo tar -czf dpe-logs-$(date +%F).tar.gz dpe-journal.log /opt/ataccama/one/dpe/log/

  3. Attach dpe-logs-<date>.tar.gz to your support ticket, where <date> is the date the archive was created, in YYYY-MM-DD format.

In the support ticket, also include:

  • The DPE version.

  • The exact timestamps, including the time zone, of when the problem occurred.

  • Whether the issue resolves on its own or requires a restart.

See also

Was this page useful?