Service Restart and Control
Manage all 21 Eenos service-control menus, interpret status metrics and use confirmed start, stop, restart and detailed-status actions.
Open System → Service Restart in your administrator WAP session. Despite the group name, its pages provide Start, Restart, Stop and View Status controls.
Service menus
Every menu is documented below, including entries that appear only when the server provides the relevant feature.
| Area | Service guides |
|---|---|
| Web servers | Apache HTTPD, Nginx, OpenLiteSpeed, Varnish |
| Databases | MySQL, PostgreSQL, MongoDB |
| Mailing lists | Mailman, Mailman Web |
| Mail services | Exim, Dovecot, Spamd |
| Network and scheduled work | Pure-FTPd, Bind DNS, SSH, Cron |
| Security | Eenos BFD, ClamAV, On-Access Scanner, ClamAV FreshClam |
| PHP | PHP-FPM |
Availability and status fields
Most sidebar entries depend on the server configuration. Bind DNS, SSH, Cron, Eenos BFD and PHP-FPM have unconditional sidebar entries, with additional installation/configuration checks when opened. The On-Access Scanner entry requires both ClamAV and its scanner availability. A visible entry is not proof that the corresponding service is running.
Standard service pages show:
| Field | Interpretation |
|---|---|
| System Service | Selected service and its service-manager unit. |
| Current State | Active/Inactive summary with the underlying status text. |
| Uptime / Downtime | Duration associated with the reported state. |
| State Since | When that state began. |
| Memory Usage | Reported service memory, or Unknown when unavailable. |
The summary marks status as Active when its reported text begins with active. A failed status lookup can appear as Unknown with an Inactive summary; inspect detailed status before diagnosing the cause. Metrics describe the service process, not end-to-end application health.
Service actions
| Action | Effect |
|---|---|
| Start | Requests that the selected service start. |
| Restart | Requests a service restart; active connections may be interrupted. |
| Stop | Requests that the selected service stop; dependent functions may become unavailable. |
| View Status | Retrieves detailed status from the service manager without changing service state. |
Choose the action, review the confirmation and confirm, or cancel to leave it unsubmitted. The form carries the selected action and service identity; standard pages reject a submitted service that does not match the page. PHP-FPM also validates the selected runtime identity. These are fixed controls, not a field for arbitrary commands or unit names.
Demo sessions can request status but cannot start, stop or restart services. The page reports validation failures, command failures or success through service alerts. State-changing command outcomes are recorded as service activity events.
Before and after a change
Check current status and the reason for the operation first. Coordinate interruption of shared services with affected users. Ensure configurations and required dependencies are ready, and keep a recovery path when touching administrative access.
Restart is an operational change
Stopping or restarting can affect every account using the service. A successful command result does not prove that websites, databases, mail or security checks work correctly. Verify the affected function and investigate failures rather than repeatedly submitting the same operation.
These pages control local services. They do not install missing software, edit service configuration, manage remote database daemons or guarantee recovery from an invalid configuration. PHP-FPM uses its own runtime table and controls.