Docs / Monitoring / Service Management

Service Management

Panelica 1.0.375 Verified 2026-07-24 Monitoring

Service Management is ROOT's control panel for every service Panelica runs: nginx, Apache, the PHP-FPM pools, PostgreSQL, MySQL, Redis, BIND, Postfix, Dovecot, the FTP server and the rest. Start, stop, restart or bulk-manage them, grouped by category, with the critical ones protected from being stopped by accident.

Panel locationTools → Service Managementhttps://YOUR-SERVER-IP:8443/tools/services (ROOT only)

Service Management

Total

Running

Stopped

Health

91%

postgresql 🛡 protected running

The layout

Four cards summarize the fleet: total services, running, stopped, and a health percentage (or an error count if any service failed). Services are then grouped into collapsible category cards, Critical, Web, Database, Email, Infrastructure and Optional, each with an icon and color. A row per service shows its name and status, with the status live (running or stopped), and its actions.

Behind the scenes, a note on the detail columns: the table has PID, uptime, CPU, memory and ports columns, but the fast status query the page uses returns only the name and running/stopped state, so those extra columns are usually blank. This is a deliberate performance trade: reading full per-service metrics for every unit was slow on busy servers, so the page shows what it can read instantly. For live CPU and memory of the running processes, use the Monitoring Dashboard and Process Manager.

Starting, stopping, restarting

Each running service offers Restart and Stop; each stopped one offers Start. Single actions apply immediately (no confirmation) and retry a few times, verifying the service really reached the target state, and if it fails you get an error dialog with the actual journalctl and systemctl status output plus a "Try Again" button. The top bar adds Start All / Stop All / Restart All, and each category card has its own Restart for the group; bulk actions ask for confirmation and skip services that are already in the target state.

Critical services are protected, but can still be restarted. The four services the panel itself depends on, the backend, PostgreSQL, the panel's nginx and Redis, cannot be stopped from here (the Stop button is locked, and the backend refuses it), because stopping them would take the panel down with them. They can still be restarted, which is safe. Restarting the backend uses a special reconnect flow so your session survives rather than logging you out. Everything else can be stopped, so read the dependency warning on a service before stopping it, other services that rely on it are listed.

Boot-time control

ROOT can set whether each service starts on boot. Disabling boot-start requires a typed reason (and is refused for critical services), so there is always a record of why a service was left off after a reboot; re-enabling is one click. A dependency map underlies this, so the panel can warn you which services would be affected.

Docker-based legacy PHP

Legacy PHP versions (5.6 to 7.4) run in Docker rather than as native services, so they appear here with a "Docker Runtime" badge and slightly different controls (they can be restarted but have no traditional start/stop, since they are on-demand per-user containers).

Access

Strictly ROOT at the route. See roles and permissions. The page operates on Panelica's isolated panelica-* systemd units through the panel's own service tool, never touching unrelated system services.

Panelica Documentation · Written and verified against the live panel. · Last verified 2026-07-24 on Panelica 1.0.375