Maintenance

Use maintenance windows, process controls and bounded cleanup

Review supported automation timing and precise owned cleanup instead of arbitrary server commands.

Platform
Go
Technology
Go

Set a maintenance window

EPAdmin's maintenance controls use the actual registered server/security capability and protected preview. Choose whole-second start/end instants, duration from one minute to 24 hours, an end in the future and a start no more than 30 days ahead. The browser shows its timezone, then sends UTC starts_at/ends_at in a typed maintenance.window.set request. Server time and the fresh protected preview are authoritative.

The status distinguishes not configured, scheduled, active, elapsed and unknown. A maintenance window is not an unattended OS/package update scheduler and does not supply missing update recovery acceptance. Check the real task and service policy before assuming an operation is allowed.

Process controls

Inspect the dated observed process identity and scope before requesting termination. The typed preview binds the intended process, owner and current state; a stale PID or a row copied from another account must not authorize a kill. Follow the durable result and independently inspect affected application health. Do not turn a process control into an arbitrary command executor.

Temporary metadata cleanup

Temporary Files / Disk Cleanup exposes the supported owned metadata-staging cleanup, not a general filesystem delete tool. The UI validates current observation, eligible file count and bounded scope; a limited or stale observation cannot justify cleanup. Review the generated before/after plan and exact confirmation, then follow the durable operation.

PHP journal controls

Source PHP journal preview validation binds website/account IDs, UID, account and website revisions, generation, operation ID and configuration digest. Its service state includes version/revision, desired runtime, boot enablement and owner operation. These fields prevent a control from applying to unrelated/replaced work; do not edit journals or manufacture a new owner ID to bypass a blocked recovery.

Verify and respect limits

After changes, reload the actual status and compare owned services/resources. Keep provider snapshots and protected recovery state. Package Manager, OS Updates, Security Patches and Update Scheduler remain unavailable menu actions; CPU/RAM historical monitoring and storage-volume provisioning are also not completed. A successful small cleanup or scheduled window is not production upgrade/reconstruction acceptance.

← All EmailaPanel guidesGet help →

Need help with EmailaPanel?

Tell us the product version and what you are trying to do. Keep passwords and private keys out of your message.

Contact Emaila