Linux service management
See every server’s services in one table. “Is httpd running everywhere?” takes a single row: how many servers have it, how many are up and how many aren’t monitored. Before you restart Apache/httpd or any other service, the panel tells you how many sites it will touch.
- Topic
- A · Fleet and servers
- Order
- 04 / 06
- Points
- 05
- Panel support
- 4 / 4 panels
- 01Fleet spreadHow many servers have a service and how many run it: “is httpd up everywhere” is one row.
- 02Same state as the profileWhen a service changes state, its row in the server profile updates too: both screens show the same truth.
- 03Switches per serviceMonitoring and start-on-boot are per service; anything restarting 4+ times in 24 hours is flagged.
- 04Impact in numbersWeb, database and panel services affect every site on the server; mail services affect mailboxes.
- 05Panel service stays upThe panel’s own service cannot be stopped; that would cut access to the panel, so the action is closed.
What it does.
When you restart a service, the confirmation says “198 sites and 1,204 mailboxes on this server will be briefly affected”. You know what to tell the customer before you click. Services that keep restarting themselves are flagged too, since that is usually where the real problem is. You can’t stop the panel’s own service, because stopping it would take your access with it.
Fleet spread by service name: how many servers have it, how many run it and how many are unmonitored. “Is httpd up everywhere?” becomes one row.
The restart confirmation puts a number on the impact. Web, database, panel and runtime services affect every site on that server; mail services affect mailboxes.
The panel’s own service can’t be stopped. Stopping it would cut access to the panel, so the action is closed from the start.
Monitoring and start-on-boot are set per service. Anything that restarts four or more times in 24 hours is flagged separately.
When a service changes state, its row in the server profile updates too, so both screens always agree.
Which panels support it?
Capability Service control (start/stop)
- yesManaged from the panel
- yesManaged from the panel
- yesManaged from the panel
- No panelyesManaged from the panel
Servers without a control panel have no account, reseller or mailbox management, because those come from the panel itself. Firewall, DNS, services and the terminal work over SSH. See the full table
Fleet and servers
The number of servers changes; where you look doesn’t.
- A.01Details Server health monitoring dashboardSee every server in your fleet on one screen: disk, memory, load and traffic. A single health score sits at the top. Under it is the list of what pulled the score down, such as a server offline, a critical alert or a backup that didn’t run. You know where to look first.
- A.02Details Connect cPanel, Plesk and DirectAdminAdding a server takes two steps: type its address, then pick the panel type. You don’t hand over a root password. A full-privilege API token works for cPanel/WHM and DirectAdmin, an admin key for Plesk, and an SSH key for a panel-less Linux server. The token is stored encrypted and never shown again.
- A.03Details Server profile: load, disk, memoryEverything about one server sits on a single page: hardware, operating system, panel version, running services, its accounts, open alerts and the last backup. If the panel version is behind the newest in your fleet, it is flagged at the top. You can open the terminal from here too.
- A.04This page Linux service managementSee every server’s services in one table. “Is httpd running everywhere?” takes a single row: how many servers have it, how many are up and how many aren’t monitored. Before you restart Apache/httpd or any other service, the panel tells you how many sites it will touch.
- A.05Details Server alerts by severityOpen server alerts sit in three tabs by severity, and a server filter shows what is open on one machine. You assign an alert to someone on the team, and everyone can see who is on it. An alert you acknowledge leaves the open list but stays in the record.
- A.06Details Background job queueLong-running background jobs such as migrations and version moves are tracked here. You see which step a job is on and how much is left, and its log opens inside the row. Restart a job that stalled, or cancel one you no longer need.
Connect your first server today.
Free for 14 days, no card needed. Create your account, add your first server with an API token or an SSH key, and the panel starts filling in a few minutes later.
No setup fee · Cancel anytime · EU-hosted