Run installation diagnostics
Collect a current, read-only picture of installation health before changing permissions, connections or scheduled processing.
Run the current check
Open Administration → System and utilities → Installation checks and run the installation check. Read its timestamp together with the results: a previous successful check does not describe a changed server. The check reports conditions; it does not silently repair the installation.
Read errors in context
Examine database connectivity, required procedures and events, scheduler state, runtime requirements and filesystem findings. A warning that grants could not be inspected is different from a confirmed missing privilege. Compare each finding with the actual feature that is failing.
Inspect report processing
For delayed reports, review import progress, source position and the age of execution information. Pending source rows alone do not establish that the importer is permanently stuck.
Review a targeted repair
If a permissions repair is offered, inspect its generated dry-run command first. Apply only the documented repair with the required maintenance confirmation and correct installation path.
Connect a finding to the affected function
Read the result level and accompanying explanation together. An error identifies a failed check; a warning can describe a condition that could not be verified or needs review. Work from the affected service toward the visible symptom, rather than changing several settings at once.
| Check area | Where to continue |
|---|---|
| Database connection and source tables | Check application and CDR settings and the availability of source CDR/queue-log data. A reachable database does not prove that every required table or privilege is available. |
| Procedures, events and scheduler | Inspect required routines and scheduled database events in Database and procedures. Check the scheduler state separately from whether event definitions exist. |
| PHP and filesystem | Check the reported runtime extensions, memory and accessible paths. Compare web PHP with the PHP used by scheduled commands before changing the server. |
| Import progress | Compare source position, pending work and last execution across successive checks. Increasing progress with pending rows differs from repeated failures at the same position. |
Repeat the relevant check
After the targeted correction, rerun diagnostics and compare the specific finding, then verify the user-facing feature. Remember that web PHP and command-line PHP can load different extensions and settings. A browser operation succeeding does not prove that a scheduled command uses the same runtime.
Preserve evidence and recovery state
Share relevant findings without passwords, keys or customer data. Do not delete installer state, update plans or import cursors to remove a warning. If a reset or update is interrupted, follow its dedicated recovery procedure; changing the displayed symptom is not the same as completing recovery.
Use the controls, understand what changes
Run a fresh check and read its timestamp. Expand or inspect the failing finding before applying a suggested command. A read-only check reports conditions; it does not silently repair permissions, SQL objects or scheduled jobs. Verify the corrected feature after the next check.
Complete product screenshots
This is Installation diagnostics, available in Administration → System and utilities. Verify installation checks database connections, required PHP components, application files and report processing. Below the results, read the explanation of each warning or error. The permission-repair panel provides commands to review and correct file access from SSH; opening it does not change permissions. Open the screenshot to read the example results at full size.
Open complete screenshot
Read the workspace section by section
Match the numbers and panels below to the complete workspace. These screenshots use illustrative data; the procedures above explain how to work with your own installation.
Permission repair guidance
This panel shows two commands to run over SSH on the PBX. First use --dry-run to list the proposed file-permission corrections without applying them. Review the result and arrange maintenance before using --apply --maintenance-confirmed to apply the corrections. Then run Verify installation again to check the result.