System Diagnostics
Note: A future update will add a dedicated Skipped status for tests that are optional or not applicable to the current installation.
The System Diagnostics tool runs a series of health checks on your WMD SED installation. It is intended for administrators to verify that the system is configured correctly and that key components are operating as expected.
For Users
Running Diagnostics
Click Run Diagnostics to start the tests. Each test runs in sequence and the results appear as they complete.
The diagnostics use three main result types:
- Passed - the check completed successfully.
- Failed - the check found a problem or could not complete successfully.
- Skipped - the check did not apply to this installation or was not relevant for the current configuration.
A skipped result does not usually indicate a problem. It normally means that a particular optional component, legacy component, or driver-specific test is not being used in this environment.
If a test fails, note the test name and result and contact your system administrator. Do not attempt to modify system settings based on diagnostic output unless you are the administrator.
For Administrators
What the Diagnostics Cover
The diagnostic suite tests the following areas:
- System details - PHP version, operating system, memory limits, loaded extensions, and other server-level configuration values.
- Database - connectivity to the WMD database, database platform detection, current database time, and selected driver-specific checks.
- Network - outbound connectivity tests used by the DNS, WHOIS, and RDAP subsystems.
- Configuration - presence and availability of key runtime paths, libraries, and installation settings.
Interpreting Results
Each test result includes a label, a status indicator, and where relevant, additional detail beneath the test entry.
- Passed means the check completed successfully.
- Failed means the check found a real issue, such as a missing dependency, a connection failure, invalid configuration, or an unavailable service.
- Skipped means the check was not applicable to the current installation. For example, some tests apply only to specific database drivers or optional legacy libraries.
Not every non-passed result requires action. In particular, skipped checks are informational and should not be treated as system faults by themselves.
After a Failed Test
Review the detail shown beneath the failed test, address the underlying issue, and then re-run the diagnostics to confirm the fix.
If a test is skipped, first determine whether that component is actually required for your installation. If the related feature is not in use, no action is normally needed.
Examples of genuine issues include insufficient PHP limits, blocked outbound network access, missing database tables after an incomplete upgrade, or missing extensions required by the configured database driver.