Tasks stay "Queued" and changes are not applied

For server administrators · Updated 2026-10-29

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

The panel itself never changes the server directly: it queues a task, and the background agent sahaabd (running as root) carries it out. If the agent is stopped or busy, tasks wait and nothing you change in the panel happens.

Symptoms

  • The admin panel shows "… task(s) have been waiting over 2 minutes. The provisioning agent is probably not running: systemctl status sahaabd", with a View queue link.
  • New accounts, mailboxes or settings are saved in the panel but do not work.
  • Tasks in Task Queue stay Queued.

Causes

Most likely first:

  1. The agent is stopped — after a crash, a reboot that did not start it, or a manual stop.
  2. The agent is busy with long tasks. Long scans and backups run in a separate lane, so this rarely blocks other tasks, but a task stuck in Running can hold its lane.
  3. The panel's database is not reachable by the agent.

Fix

1. Start the agent

On the server as root (SSH, or Terminal in section Server if the panel still opens):

systemctl status sahaabd
systemctl restart sahaabd

Within a few seconds the queued tasks start. Service Manager (section Server) also lists sahaabd and can Restart it; the watchdog restarts it automatically when it stops.

To see what the agent does, read its recent log:

journalctl -u sahaabd -n 50

2. A task that runs forever

In Task Queue, click Running to see what runs and since when. When the agent restarts, a task that was still running is marked Failed with "Interrupted: agent restarted" at the end of its output, so you can Retry it. If the same task hangs again, read its Output and see A task failed.

3. Database

If journalctl shows "database error … reconnecting", check the mysql service (mariadb) in Service Manager or with systemctl status mariadb.

Run the queue once by hand

To process all queued tasks once and exit (useful to test while the service is stopped):

sahaab jobs:run

Good to know

  • After every panel update, the installer restarts the agent so it runs the new code.
  • Settings changed in Server Settings are read again before every task; you do not need to restart the agent after changing them.

Still not working?

If the agent stops again right after starting, the end of journalctl -u sahaabd shows why. Reboot the server at a quiet time if a system package was updated, and send the log to support if it keeps failing.

Was this article helpful?

Still stuck?

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