执行sudo a2enmod rewrite后重启VM无法访问PostgreSQL数据库

Let’s walk through the most likely causes and fixes for this issue, since you’ve narrowed down the trigger to enabling Apache’s rewrite module:

1. First, confirm PostgreSQL is actually running #

Even if you restarted the service, it might have failed to initialize after the VM reboot. Run these checks in your VM’s terminal:

• Check service status: sudo systemctl status postgresql (for systemd-based distros) or sudo service postgresql status (for older init systems)
• If it shows "failed" or "inactive", dig into the logs: use sudo journalctl -u postgresql (systemd) or look at PostgreSQL’s dedicated log file (usually in /var/log/postgresql/ or defined by log_directory in postgresql.conf). Logs will often tell you exactly why the service wouldn’t start.

2. Verify port 5432 isn’t being hijacked #

While a2enmod rewrite itself doesn’t use port 5432, enabling the module might have triggered an Apache config change or started a related service that’s now using that port. Check which process is bound to 5432:

• Run sudo lsof -i :5432 or sudo netstat -tulpn | grep 5432
• If you see Apache or another non-PostgreSQL process here, you’ll need to either reconfigure that process to use a different port, or adjust PostgreSQL’s port setting in postgresql.conf (don’t forget to restart PostgreSQL after changing it).

3. Check if system permissions or firewall rules changed #

Enabling Apache modules can sometimes ripple into system-level settings that block PostgreSQL:

• Firewall checks: If you use ufw, run sudo ufw status to ensure port 5432 is allowed (even for localhost, strict rules can block loopback connections). For firewalld, use sudo firewall-cmd --list-all to confirm the postgresql service or port 5432 is in the allowed list. You can temporarily disable the firewall to test if that’s the issue.
• pg_hba.conf verification: Double-check that your pg_hba.conf allows localhost connections. Look for lines like local all all trust or host all all 127.0.0.1/32 md5 – missing or misconfigured lines here can block connections even if the service is running.

4. Confirm PostgreSQL starts automatically on boot #

It’s possible the Apache module change altered service dependencies, causing PostgreSQL to not launch on VM startup:

• Run sudo systemctl is-enabled postgresql – it should return enabled
• If not, enable it with sudo systemctl enable postgresql

5. Test by reverting the rewrite module change #

To confirm the a2enmod rewrite command is the root cause:

• Disable the module: sudo a2dismod rewrite
• Restart Apache: sudo systemctl restart apache2
• Reboot the VM and try connecting with pgAdmin III again
• If the connection works now, dig into Apache’s configuration files (like apache2.conf or site-specific configs) for any rewrite rules or settings that might be interfering with PostgreSQL’s network binding. Sometimes enabling rewrite can trigger unusual network-related configs that clash with database services.

内容的提问来源于stack exchange，提问作者Magas