Issue

Use this article to troubleshoot plugin, credential-resource, and encrypted-table issues.

Environment

• Product: ZCF
• Component: Cloud
• Affected object: database/management node
• Versions: 4.x, 5.x
• Scenario: Plugin, credential-resource, and encryption-table issues

Symptoms

• Management-node database, binlog, audit table, or metadata operations are abnormal.
• Database connections, schemas, table data, or reference relationships are involved during upgrades, plugins, service reinstallation, or resource cleanup.
• UI/API display and underlying state are inconsistent, suggesting database or metadata residue.

Possible causes

• Database space, binlog, audit-table, or historical-data growth is abnormal.
• Primary-secondary replication, database credentials, upgrade scripts, or service-reinstallation procedures do not fully match the current environment.
• References in the platform database are not cleared after underlying resource changes.

Resolution

1. Confirm the current version, management-node count, database primary-secondary roles, operation time, and failed task.
2. Check management-node disk space, database directories, mysql-bin, audit tables, and related service status.
3. Search management-server, upgrade, or plugin logs for database connection, SQL, table structure, UUID, or AK/SK errors.
4. If metadata cleanup or database modifications are involved, complete a database backup first and have ZStack technical support confirm the SQL and rollback path.

Key command

df -h
du -sh /var/lib/zstack /var/lib/mysql /usr/local/zstack 2>/dev/null
zsha2 status
grep -a -nE "mysql|mariadb|database|SQLException|binlog|relay|uuid|AK|SK" /usr/local/zstack/apache-tomcat/logs/management-server.log*

Remediation

• Resolve the identified database-space, primary-secondary replication, upgrade-parameter, plugin-configuration, or metadata-residue issue.
• Before deleting or modifying database data or clearing underlying residue, back up first and confirm the scope of impact.

Verification

• Confirm that the symptom described in this article no longer occurs.
• UI, API, management-node logs, and underlying command output corroborate one another.
• Observe at least one related task or alarm cycle to confirm that the issue does not recur.

Risks and rollback

• Do not directly modify the database without a backup and without confirming reference relationships.
• Cleaning binlogs, audit tables, or metadata can affect auditing, rollback, synchronization, and resource state.

Notes

• Before adjusting management services, databases, certificates, permissions, auditing, or security settings, confirm the HA state, service window, rollback plan, and compliance-retention requirements.
• If database modifications, underlying file operations, lock release, service restarts, driver or firmware upgrades, or bulk resource changes are required, contact ZStack technical support before proceeding.