📖 ~1 min read
Table of contents
Symptom & Impact
Database stays down after restart, causing application errors and transaction interruption.
Environment & Reproduction
After relocating datadir on RHEL 8, systemctl start mariadb fails with access or initialization errors.
Root Cause Analysis
Incorrect file ownership, SELinux context mismatch, or stale service path assumptions block startup.
Quick Triage
Run systemctl status mariadb and review journalctl -u mariadb for permission and path diagnostics.
Step-by-Step Diagnosis
Verify my.cnf datadir value, filesystem permissions, and labels with ls -lZ and semanage fcontext.
Solution – Primary Fix
Set correct mysql ownership, apply restorecon after fcontext update, then restart and enable mariadb.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.
Solution – Alternative Approaches
Use bind mounts with stable paths to minimize service configuration changes during storage migration.
Verification & Acceptance Criteria
MariaDB reaches active state, client queries succeed, and logs show clean initialization.
Rollback Plan
Repoint datadir to previous location and restore original config files from backup.
Prevention & Hardening
Document migration steps, validate SELinux labels in runbooks, and test service restart before cutover.
Related Errors & Cross-Refs
Often overlaps with disk mount timing issues and systemd dependency ordering after reboot.
Related tutorial: View the step-by-step tutorial for rhel-8.
View all rhel-8 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
See Red Hat and MariaDB documentation for datadir relocation and secure SELinux operation on RHEL 8.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.
