MySQL connection, schema or storage problem

Prerequisites and authority

Start with read-only checks and authorized records. Capture evidence before changes. Stop and escalate when data replacement, financial changes or wider outages are possible.

MySQL, schema or storage failure

Advanced diagnostics: preserve storage and readable data. Do not delete MySQL volumes, edit raw database files or run schema repair as an exploratory step.

Basic

Check whether all application requests fail or one query/workflow fails. Record recent update/configuration changes and available disk space.

Intermediate

Inspect MySQL health/logs and confirm the API uses the intended internal service hostname and credentials. Identify the active volume with docker inspect bryannet-mysql; redact sensitive fields before sharing output.

Advanced

Use read-only support access to inspect the schema and relevant tables. Distinguish authentication failure, refused connection, incompatible schema, full disk and missing/wrong storage mount. A newly recreated container attached to another volume can resemble data loss.

Correct configuration/storage issues through the supported path. Preserve the original volume before any recovery attempt. Do not regenerate database credentials over an established MySQL account set.

Use Restore BryanNet safely if restoration is necessary. Verify schema/release compatibility, data identity and a representative transaction afterward. Stop and escalate when corruption, destructive migration or missing storage is suspected.