Tasks stay queued: the agent (sahaabd) is not running

For server administrators · Updated 2026-10-29

On this page
  1. Symptoms
  2. Causes
  3. Fix
  4. Still not working?
  5. Good to know

The control panel never changes the system itself. A background agent, sahaabd, running as root, carries out every task. When the agent is stopped, the panel accepts your changes but nothing happens on the server.

Symptoms

  • A yellow notice on admin pages: … task(s) have been waiting over 2 minutes. The provisioning agent is probably not running: systemctl status sahaabd.
  • New accounts, domains, mailboxes or certificates do not appear on the server.
  • In Task Queue, tasks stay queued and none is running.
  • In the Transfer Tool: The connection task has been waiting … seconds without starting.

Causes

  1. The agent stopped or crashed (for example after the server ran out of memory).
  2. The agent cannot reach the panel's database (MariaDB is stopped).
  3. A very long task is running, for example an account transfer from another server. Other tasks wait until it is finished. In Task Queue, one task is then running. Backups and scans run in a separate lane and do not block the others.

Fix

Restart the agent

Connect to the server over SSH as root and run:

systemctl restart sahaabd
systemctl status sahaabd

The status should say active (running). Queued tasks start within seconds.

Check the database server

If the agent stops again at once, check MariaDB:

systemctl status mariadb

Start it with systemctl start mariadb if it is stopped, then restart the agent.

Read the agent's log

journalctl -u sahaabd -n 100 --no-pager

Lines with database error or error: explain what is wrong.

Still not working?

Process the queued tasks once by hand, which shows any error directly in your terminal:

sahaab jobs:run

If a task fails, open it in Task Queue to read its output; see how to retry a failed task.

Good to know

  • The watchdog checks the agent every minute and restarts it if it stopped.
  • Restart in the Service Manager cannot start the agent, because that restart is itself a task. Use the command line.
Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.